No space left on device

Hi guys,
I'm having some trouble with the provided implementation of distribution through compose (contrib/compose)
I'm running on a $5 DO node with 20gb of disk space, 2.2 of which is used before running docker-compose up:

Compose pulls the FS layers, starts registry v1, then tries to start registry v2, and promptly runs out of disk space:

The end result is that only registry v1 is running, and all 20gb of disk space is used:

Is this expected behavior - does distribution need more than 20gb of disk space just to start with no images?

Hi,
I strongly suggest you follow the documentation instead of whatever is in the contrib folders, specifically starting with https://github.com/docker/distribution/blob/master/docs/deploying.md
In particular, why would you need to run registry:1? Furthermore, the contrib folders will build the images instead of using the official ones (like the docs encourage you to use), thus consuming way more disk space.
So, no, the registry:2 image should not need more a couple hundred MB.
Hope that helps - let me know (usually on irc #docker-distribution is a better place for support questions).

Hi,
Thanks for the pointers. I was lazily hoping for a magical "docker-compose up" just to test out distribution + nginx before I dived in myself. I'll go through the docs and do it properly.

Here you have one such all-in-one-lazy compose file:
https://github.com/docker/distribution/blob/master/docs/authentication.md#setting-things-up
(careful about NOT using bcrypt to generate the password - doc caveat for now)


feat: groupby different kcl files according to the api version

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

Close https://github.com/kcl-lang/kcl/issues/1501
Close https://github.com/kcl-lang/modules/issues/169
feat: groupby different kcl files according to the api version

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 86 (0.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-2.3%) to 14.19%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/options/import.go
0
8
0.0%

pkg/fs/util.go
0
12
0.0%

pkg/import/crd/groupby.go
0
66
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-2.3%

Covered Lines:
85

Relevant Lines:
599

💛  - Coveralls


Updated VSCode: Not working

I just updated my visual studio code, and the plugin has stop working.
I press open preview, a new tab is open, but a black one. No error message, no feedback, nothing, just a black tab.
SO: Linux
VSCode: 1.9.0

Duplicate of #12


Change the order of Angular packages

Feature/Change Description
Upgrade core and cli in the same order as in the official upgrade guide
Developer Checklist

[ ] Updated documentation or README.md
[ ] If adding new feature(s), added and ran unit tests
[ ] If create new release, bumped version number
[ ] Ran npm run style:fix for code style enforcement
[ ] Ran npm run lint:fix for linting
[ ] Ran npm audit to discover vulnerabilities

@duluca I have updated the version and I also modified the contributor's list in the README file 😃


Build failing - missing curlbuild.h

Following the instructions, the build is failing due to missing curlbuild.h
/home/btcr/btcr-DID-method/src/curlWrapper.cpp:5:10: fatal error: curl/curlbuild.h: No such file or directory
 #include <curl/curlbuild.h>
          ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [src/CMakeFiles/createBtcrDid.dir/build.make:128: src/CMakeFiles/createBtcrDid.dir/curlWrapper.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:320: src/CMakeFiles/createBtcrDid.dir/all] Error 2
make: *** [Makefile:141: all] Error 2

I have curl 7.65.0 installed and don't have a curlbuild.h in my /usr/include/curl directory.
If I removing the following line from curlwrapper.cpp, make completed without error:
#include <curl/curlbuild.h>

Thanks! I'm going to build this on our test systems to see why it was I once thought I needed that header. I ought to be able to merge shortly.


Develop intuitive and clear directory organization for CWL workflows and tools

Gedankenstütze:

/workflows/tools//tool1.cwl
/workflows/tools//tool2.cwl
/workflows/wf/wf1.cwl
/workflows/wf/wf2.cwl

Better ideas, other ideas?

Second version might be better if we want to be consistent with ARC model...
Are the tools in a separate folder? In ArcPrototype and Facultative-CAM-in-Talinum there are cwl scripts and other scripts (fsx, R) in same subfolder of workflow step/tool folder. (Overall very different structure of other projects in data hub)
DataPLANT has graph with workflows/workflow1/ but also not sure if script and cwl are in separate folder. They are in separate branches but have no folder icon...

Yes that's the picture that i saw on their website :)


New unison approach

this uses unison inside of a container to sync two volumes.  The first volume UNISON_HOST_DIR is mounted as a standard docker bind mount.  That UNISON_HOST_DIR gets sync'd to the UNISON_DIR which is a named volume that is shared with the app container.  This isolation of the two volumes allows the app container to run at full speed.

@dougmartin you should give this a try. I'm pretty sure it will work on windows too. And I suspect it will really speed things up.  You need to add the docker-compose-sync.yml into your .env COMPOSE_FILE list.   You also need to rebuild the app container with a docker-compose build app.

@knowuh you might be interested in this one as well.

cool, I will give it a try.

This works well for me.
Access the app server on my local machine is way faster. Guard works too, so I can just run docker-compose exec app docker/dev/run-ci.sh and tests run when I save changes in my editor.
👍

👍  Much, much, much, much faster now on Windows.  The only downside for me is the amount of sync messages that stream in the window running Docker.  I sometimes do puts style debugging so maybe this will force me to get interactive debugging working.

@dougmartin you can open a new terminal and run docker-compose logs -f app that will stream the logs just from the app container.


GPU Operator Installation Failed

When try to follow step:
helm install --version 22.09 --create-namespace --namespace gpu-operator-resources --devel nvidia/gpu-operator --wait --generate-name
Got Error message:
Error: INSTALLATION FAILED: Get "https://<IP_ADDRESS>:6443/apis/apiextensions.k8s.io/v1/customresourcedefinitions/nodefeaturerules.nfd.k8s-sigs.io": dial tcp <IP_ADDRESS>:6443: connect: connection refused - error from a previous attempt: http2: server sent GOAWAY and closed the connection; LastStreamID=661, ErrCode=NO_ERROR, debug=""
I thought it maybe due to a backend timeout. I tried again but got connection refused.
Error: INSTALLATION FAILED: Kubernetes cluster unreachable: Get "https://<IP_ADDRESS>:6443/version": dial tcp <IP_ADDRESS>:6443: connect: connection refused
Please direct me how to proceed. Thanks!
Thanks,
Frank

This was resolved after I restart service
sudo systemctl restart kubelet.service
Thanks,
Frank


Show all project tags the viewer has permissions on

This PR addresses an issue where only publicly available projects were shown on the Post details page. Updated behavior to display tags, categories, and tournaments based on the current user's permissions.
Also fixes this sentry issue -- https://metaculus.sentry.io/issues/6175262080/?referrer=slack&notification_uuid=78b53203-b356-44e8-b487-f20f72fdab1f&environment=production&alert_rule_id=15493011&alert_type=issue
fixes #1126
fixes #1819

This also gets us closer to allowing users to apply their own custom tags. :)


Command "cds add cloud-logging --with-telemetry" adds  "telemetry": "to-cloud-logging" for local development

First i would like to thank you for bringing this new capability to add cloud logging and telemetry libraries with a single command.
Here's one observation that i feel can be improved.

When i use the command cds add cloud-logging --with-telemetry, it adds "telemetry": "to-cloud-logging" property at cds.requires level.
Running cds watch breaks the startup of application as the applications starts looking for Cloud Logging Credentials.
Moving the property under production solves this
"[production]": {
"db": "hana",
"auth": "xsuaa",
"multitenancy": true,
"telemetry": "to-cloud-logging"
},

It will be great if this can be adapted with the    cds add cloud-logging --with-telemetry command.

Also,
The Indentation of Cloud logging Service in mta is wrong.
The current generated code is :
  - name: incident-management-cloud-logging
     type: org.cloudfoundry.managed-service
     parameters:
       service: cloud-logging
       service-plan: standard
       config:
       ingest_otlp:
         enabled: true

Required indentation:
 - name: incident-management-cloud-logging
   type: org.cloudfoundry.managed-service
   parameters:
     service: cloud-logging
     service-plan: standard
     config:
       ingest_otlp: # this requires one indentation
         enabled: true

After fixing and deploying the application, i am getting the following error

2024-09-24T07:49:20.667+0000 [APP/PROC/WEB/0] STDOUT Invoking pre-start scripts.
2024-09-24T07:49:20.917+0000 [APP/PROC/WEB/0] STDOUT Invoking start command.
2024-09-24T07:49:21.332+0000 [APP/PROC/WEB/0] STDOUT ><EMAIL_ADDRESS>start
2024-09-24T07:49:21.332+0000 [APP/PROC/WEB/0] STDOUT > cds-serve
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR /home/vcap/app/node_modules/@cap-js/telemetry/lib/tracing/index.js:43
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR const { kind, root, ratio } = cds.env.requires.telemetry.tracing.sampler
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR ^
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR TypeError: Cannot destructure property 'kind' of 'cds.env.requires.telemetry.tracing.sampler' as it is undefined.
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR at _getSampler (/home/vcap/app/node_modules/@cap-js/telemetry/lib/tracing/index.js:43:11)
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR at module.exports (/home/vcap/app/node_modules/@cap-js/telemetry/lib/tracing/index.js:122:66)
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR at module.exports (/home/vcap/app/node_modules/@cap-js/telemetry/lib/index.js:36:26)
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR at Object.<anonymous> (/home/vcap/app/node_modules/@cap-js/telemetry/cds-plugin.js:12:31)
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR at Module._compile (node:internal/modules/cjs/loader:1364:14)
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR at Module.load (node:internal/modules/cjs/loader:1203:32)
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR at Module._load (node:internal/modules/cjs/loader:1019:12)
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR at Module.require (node:internal/modules/cjs/loader:1231:19)
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR at require (node:internal/modules/helpers:177:18)
2024-09-24T07:49:21.582+0000 [APP/PROC/WEB/0] STDERR Node.js v18.20.4
2024-09-24T07:49:21.594+0000 [APP/PROC/WEB/0] STDERR npm notice
2024-09-24T07:49:21.594+0000 [APP/PROC/WEB/0] STDERR npm notice New minor version of npm available! 10.7.0 -> 10.8.3
2024-09-24T07:49:21.594+0000 [APP/PROC/WEB/0] STDERR npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.3
2024-09-24T07:49:21.594+0000 [APP/PROC/WEB/0] STDERR npm notice To update run: npm install -g<EMAIL_ADDRESS>2024-09-24T07:49:21.594+0000 [APP/PROC/WEB/0] STDERR npm notice
2024-09-24T07:49:21.617+0000 [APP/PROC/WEB/0] STDOUT Exit status 1
2024-09-24T07:49:21.623+0000 [CELL/SSHD/0] STDOUT Exit status 0
2024-09-24T07:49:28.118+0000 [CELL/0] STDOUT Cell 33f1a3f2-ba19-4b38-8ea3-d7769595d920 stopping instance c4aa54d4-0586-45bc-492f-9c2b
2024-09-24T07:49:28.118+0000 [CELL/0] STDOUT Cell 33f1a3f2-ba19-4b38-8ea3-d7769595d920 destroying container for instance c4aa54d4-0586-45bc-492f-9c2b
2024-09-24T07:49:28.132+0000 [API/35] STDOUT Process has crashed with type: "web"
2024-09-24T07:49:28.147+0000 [API/35] STDOUT App instance exited with guid 674110e5-6a93-443f-8660-b011b01c96d2 payload: {"instance"=>"c4aa54d4-0586-45bc-492f-9c2b", "index"=>0, "cell_id"=>"33f1a3f2-ba19-4b38-8ea3-d7769595d920", "reason"=>"CRASHED", "exit_description"=>"APP/PROC/WEB: Exited with status 1", "crash_count"=>12, "crash_timestamp"=>1727164168114639998, "version"=>"a022b9a0-f057-4e21-8952-84ac33ed6326"}
2024-09-24T07:49:28.317+0000 [PROXY/0] STDOUT Exit status 137
2024-09-24T07:49:30.590+0000 [CELL/0] STDOUT Cell 33f1a3f2-ba19-4b38-8ea3-d7769595d920 successfully destroyed container for instance c4aa54d4-0586-45bc-492f-9c2b

and 2. fixed in @sap/cds-dk, 3. fixed by https://github.com/cap-js/telemetry/pull/234


Rename API urls /api/changePassword and /api/resetPassword

Would be better to avoid the code duplication - to extract the logic to separate function, but accepting this PR any way

I though about what you mention about extracting the logic, but at the same time I though that as we are keeping backward compatibility it also included the logic inside, in case the new one progress over time.
Worth the discussion for later, and if necessary we change it.


Table horizontal scroll after resizing a column

Browser
Chrome
Expected behavior
If the table is smaller than the viewport width or the table container, then the table should scroll horizontally

Actual behavior
last column gets broken after resizing if preceding column has fixed width.

last column gets broken after resizing if preceding column has fixed width.

It's not broken, it's just narrow because it doesn't have a fixed width and is thus resized down to the minimum cell width, which is 25 pixels by default but which you can configure when creating the column resizing plugin.

oh, you're right, sorry.


where do install this "Before this plugin will activate"

somehow i do not see this in the package control ui. so where can i clone this repo or how do I make it available in the install menu (cmd+shift+p) => "install packages"

Sorry for taking so long. If it is not in install packages then it is probably already installed. Otherwise PackageControl is down.
You can clone this right into your Packages folder as well git clone https://github.com/SublimeLinter/SublimeLinter-tslint.git


lens becomes unresponsive when trying to download logs.

Describe the bug
I have had a few issues with lens recently, first I couldn't see the logs but removing ~/.config/Lens/extensions fixed it.
On every reboot, I seem to run into though.
[Error: EACCES: permission denied, rmdir '/home/teto/.config/Lens/extensions/example-extension/dist'] {
  errno: -13,
  code: 'EACCES',
  syscall: 'rmdir',
  path: '/home/teto/.config/Lens/extensions/example-extension/dist'
}
Trace
    at App.<anonymous> (/nix/store/awpa9hrf7m50zznjhdjg86r93kyh1px2-lens-4.2.4-extracted/resources/app.asar/static/build/main.js:1:189261)

Once I was able to see the logs of a pod (can be tricky, you have to go to the pods list and click one button at the top right), I tried to download the logs but then lens becomes unresponsive with the following log.
(kontena-lens:2): GLib-GIO-ERROR **: 15:47:30.768: No GSettings schemas are installed on the system
Nothing happens and I have to kill lens.
(I've installed lens via nix-env with a rcent nixpkgs<PHONE_NUMBER>3528e005606552a63a83fcf500db47)
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
Maintainer information:
cc @dbirks

Yeah I've been hitting the same issue on reboot. It (though I don't know exactly what) creates the extensions folder as root, and then lens can't remove it on startup -- or at least that's as far as I've been able to troubleshoot. I'm still pretty new to nixos.

I dont think it can create them as root (apart if it's setuid but I dont see why it would be and I dont think it is the case). Also all the files belong to me. I haven't looked into but it calls rmdir while there are still files there so that could be it.
I am curious, coudl you reproduce the issue about downloading the logs ?
NB: thanks for packaging it, this software is really awesome.

@dbirks would you consider packaging straight from source (e.g., without the appimage). I just remembered about https://github.com/NixOS/nixpkgs/pull/123358 and tested but it exhibits the same issues :(

I'm still hitting this issue.
I'm still seeing exactly the same error message as described in the issue #135852, just with newer version.
It seems that Lens try to re-create extension directories on every start, but they create the extension directories without write permission. Then, on next start, when they try to delete files from the directories, it fails.
[node1:~/.config/Lens/extensions]$ ls -la
total 0
drwxr-xr-x 1 honza honza 240 23. pro 17.17 .
drwx------ 1 honza honza 992 23. pro 17.20 ..
dr-xr-xr-x 1 honza honza 128 23. pro 17.17 kube-object-event-status
dr-xr-xr-x 1 honza honza  50 23. pro 17.17 lenscloud-lens-extension
dr-xr-xr-x 1 honza honza 104 23. pro 17.17 license-menu-item
dr-xr-xr-x 1 honza honza 136 23. pro 17.17 metrics-cluster-feature
dr-xr-xr-x 1 honza honza 108 23. pro 17.17 node-menu
dr-xr-xr-x 1 honza honza 106 23. pro 17.17 pod-menu
dr-xr-xr-x 1 honza honza 102 23. pro 17.17 survey
dr-xr-xr-x 1 honza honza 108 23. pro 17.17 telemetry

I am facing it too. This is very annoying.

Same here, I tried giving write permission to the whole folder but it didn't help....

same here, I found related upstream issue https://github.com/lensapp/lens/issues/5261


Bootstrap SDK libraries

Looks like some of the "to be removed" functionality is still present. Is is it safe to say there will be a follow up which removes these items prior to cutting the 0.16.0 release

@rnpridgeon yes there will be a number of follow-up PRs


Add support for migrating from newer versions of MySQLPlayerDataBridge

Support for new version of MPDB Migration

The community consensus seems to be that it's still possible to migrate from new versions of MPDB. It would be good to update the dependencies anyway and test.


Verify correctness of KVStore rate limiter

It seems in some occasions the KVStore rate limiter was not working, verify its behavior with a unit test against etcd should be enough.
https://github.com/cilium/cilium/blob/3430980860e68dbb92d7f0faa79a49d09b6e6786/pkg/kvstore/etcd.go#L160-L166

I can take this. Please assign it to me.

Thanks!

@JieJhih any update?

I'm still under survey the code. You could unassign me.

I'm still under survey the code. You could unassign me.

Sure. Please feel free to take up the issue whenever you are ready.


chaperone activity tree reorg

Prompted by an earlier source forge item on chaperone
activity, I have submitted a proposal for reorganizing
the tree. Please give me feed back.
Chaperone tree
Function ontology Proposal
----%chaperone activity(new term)
-----------%nucleotide hydrolysis dependent chaperone
activity
-----------------%chaperone _cofactor activity
dependent chaperone activity (new)
-----------------%chaperone_cofactor activity
independent chaperone activity(new)
----------%nucleotide hydrolysis independent chaperone
activity (new)
-----------------%holding chaperone activity (new)
-----------------%protein disulfide isomerase (term exists)
-----------------%peptidylprolyl isomerase (term exists)
----%binding
-----------%protein binding
-----------------% co-chaperone activity (synonyms:
chaperone cofactor activity, chaperone activator
activity, chaperone regulator activity) (new)
Definitions:
Chaperone activity: (NEW)
Refers to the activity of assisting in covalent and
non-covalent rearrangements in order to fold a
macromolecule  (such as a polypeptide or nucleic acid)
to its correct 3-dimensional structure or properly
assemble multi-polypeptide complexes, including those
that contain nucleic acids and carbohydrates.  This
activity is independent of and not part of the activity
and function of the final assembled structure or complex.
Nucleotide hydrolysis dependent chaperone activity (new)
Refers to the activity of a class of chaperone
molecules that assists in the correct non-covalent
folding of macromolecules over cycles of nucleotide
hydrolysis dependent binding and release.
Comment: Consider additional terms ATPase activity and
GTPase activity terms.
chaperone_cofactor activity depedent chaperone activity
(new)
Refers to the activity of a class of chaperone
molecules that assist in the correct non-covalent
assembly of post-translational proteins and are
dependent on additional protein cofactors. This
function happens over one or several cycles of
nucleotide hydrolysis dependent binding and release.
chaperone_cofactor activity independent chaperone
activity (new)
Refers to the activity of a class of chaperone
molecules that assist in the correct non-covalent
assembly of post-translational proteins and do not
dependent on additional protein cofactors. This
function happens over one or several cycles of
nucleotide-dependent binding and release.
Nucleotide hydrolysis independent chaperone activity (new)
Refers to the activity of a class of chaperone
molecules that assists in the correct folding of
macromolecules in the absence of nucleotide hydrolysis.
Holding chaperone activity (new)
Refers to the activity of a class of chaperone
molecules that hold or sequester macromolecules to
prevent their aggregation or misfolding and is
independent of nucleotide hydrolysis. Such substrate
macromolecules attain their native conformation with
the assistance of other chaperone molecules.
Co_chaperone activity
Refers to the activity of proteins that activate the
chaperone molecule (ring shaped multisubunit complexes)
to sequester the misfolded substrates and release the
folded products.
The following terms have to be obsoleted.
1) Hsp 70-90 organizing protein (synonym of holding
chaperone activity)- mentions specific gene product in
the term and this protein (HOP) transfers substrates
from Hsp70 to hsp 90.
2) co-chaperone activity (synonym of chaperone cofactor
activity)
co-chaperonin activity (obsolete)
co-chaperones are proteins that bind to chaperones and
the complex folds the misfolded proteins. Co-chaperones
by themselves do not have chaperone activity. So gene
products like GroES, also called co-chaperonin, should
be annotated to chaperone cofactor activity. Some of
them are nucleotide exchange factors also.
Co-chaperones and co-chaperonins are used interchangeably.
3) chaperonin ATPase activity (synonym) consider
ATPase activity and the nucleotide hydrolysis dependent
chaperone activity terms.
4) glyco-protein specific chaperone activity
(obsolete)- consider GO-process term N-linked
glycoprotein maturation and nucleotide hydrolysis
independent chaperone activity
5) tubulin-specific chaperone activity (obsolete)
consider protein complex assembly/tubulin folding and
one of the chaperone activity terms
6) fimbrium specific chaperone activity (obsolete)
refers to proteins that assist in the linear
organization of the protein pilus which forms the
tubular structure or the organelle, fimbria (aka pilus)
which helps bacteria attach to surface. These proteins
are not involved in correcting the folding of pilus,
they just help them come together.
Consider : protein binding, bridging (GO-function) and
fimbrium biogenesis process term.
7) chaperone inhibitor activity (obsolete)- Consider
ATPase inhibitor activity, regulation of protein
folding (proposing new term in process ontology) and
its children terms
8) ribosomal chaperone activity- consider ribosome
biogenesis and nucleotide
dependent chaperone activity
9) heat shock protein activity: synonym of nucleotide
dependent chaperone activity
10) histone chaperone activity (obsolete):  Consider
histone binding, chromatin assembly/disassembly,
nucleosome assembly
In the following terms chaperone has been used to mean
carrier/transport
These terms have to be children/synonym of some
transport term.
1) Copper chaperone activity synonym of copper ion
tansporter activity, remove from chaperone activity node
2) Metallo chaperone activity synonym of metal ion
transporter activity, remove from chaperone activity node
3) Superoxide dismutase copper chaperone activity (gene
product ?obsolete?)- child of copper ion transporter
activity, remove from chaperone activity node.
Reported by: rbalakri
Original Ticket: "geneontology/ontology-requests/1427":https://sourceforge.net/p/geneontology/ontology-requests/1427

thanks www.movied.org


getOrientationBehavior

RN: 0.57.7
GoCoder: 1.5.0
react-native-wowza-gocoder: 1.0.6
macOS Mojave 10.14.1
error:
getOrientationBehavior
BroadcastManager.java:100
Attempt to invoke virtual method 'init java.lang.String.hashCode()' on a null object reference
Any tips to solve it?

Make sure you are the prop videoOrientation on the BroadcastView component. It can be either portrait or landscape


Intermediate debugging results

I have been taking care of other stuff hence didn't finish coding IDEAL-3, if that would help let me know.  When I do, I'd like some additional debug snapshots from your current code to make sure I am getting the same intermediate results.

Code compendium completed.


Fix BigQuery interconnection with Trino

Riskthinking data no longer accessible via Trino

opened on behalf Punyan:  https://os-climate.slack.com/archives/C050RMU9HFA/p1694441874154939

We need more information on this issue. @erikerlandson can you please provide more information on this issue? Thanks :)


test(button): update Button Chromatic test's disabled iterations

Summary
Button
Github issue: N/A
I updated the Live Preview story for Button so that the disabled iteration is in the same row, visually, as the pseudo-states. Disabled elements cannot be interacted with so cannot ever have any pseudo-state other than default, so it does not make sense to loop the disabled = true status through every pseudo-state iteration, only through the default state. Furthermore, the Storybook addon we use to simulate pseudo states does not properly render the states when disabled=true (it shows them as having hover, active, and focus statues visually which is not actually possible). So I removed every permutation of the Button for disabled=true, except for the case where pseudo-state is default. Then I put this instance in the same row in the UI as the other pseudo-state iterations of ButtonIcon; this matches how components are shown in Zeroheight as well.
This update makes more sense because it's not actually possible to have disabled x hover, disabled x active, or disabled x focus states, however these had been rendered in the Live Preview story, which was misleading.
More about the disabled attribute for context:

https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/disabled
https://johnsweetaccessibility.com/2020/07/can-i-focus-disabled-controls/

Other updates:

Changed the names of the style consts to be more generic, for potential reuse and / or adoption of reusable styles for across multiple Live Preview stories
Removed control panel options since changing them didn't actually do anything, and this story page already shows every possible relevant combination of options anyway

New layout, with single disabled component per iteration:

Old layout, with false focus state shown upon disabled components:

Checklist

[x] Default Story in Storybook
[x] LivePreview Story in Storybook
[x] Test Story in Storybook
[x] Tests written
[x] Variables from defaultTheme.ts used wherever possible
[ ] If updating an existing component, depreciate flag has been used where necessary
[ ] Chromatic build verified by @chanzuckerberg/sds-design

GH issue for Button Chromatic test: #468


Fixed iOs touch behaviour

Brings iOs touch behaviour in line with other devices.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Description
Due to iOs Safari emulating hover states via firing a mouseenter event on first touch, the user has to touch twice to select a date.
This fixes said behaviour and allows for a single click selection. As this required a user flag to disable mouse events completely on touch interaction ( due to IOs scrolling behaviour ), tests have been made to secure hot swap between mouse and touch input on the same device still works.
Behaviour for date range selection tested on:

Mobile Devices:

IPhone 4 ( Safari )
Nokia 3.1, Android 8.1 ( Chrome )

Desktop

Debian 9, Chrome
Debian 9, Firefox

Emulator

Nexus 5, API 27 ( Chrome )
Nexus 7, API 27 ( Chrome ), both with attached mouse and touch

Related Issue: #241

Hey do you know if we can merge this? Thank you :)

The PR was well tested and should be good to go. 👍

When is this merged?

hey guys, the owner of repository is really busy nowadays, I will try to help him about PRs this weekend. I'm just spending my spare time to understand how everything is connected inside the component then will merge a lot of PRs to make a new version :)

@keremciu any updates on this? Looks like it's a small change and well tested according to @Maggistro Thanks!

Any updates here? Anything we can help with the merge this? Thanks


Do not store standard types statically but keep them on the Schema instead

When working with 2 schemas that have different standard types this becomes problematic.
For example, I have a schema that uses a custom ID type, but the other wants to use the default.
I can imagine this is not easily possible currently because of the way types are resolvable without a Schema (#1149).

This is a large breaking change, so I will plan this for v16.
Until then keep in mind that while static, the standard types can be manipulated dynamically. Unless you need to serve both schemas in the same execution context, you can work around this issue.

See issue https://github.com/webonyx/graphql-php/issues/1424 for a possible solution


Is it open sources ?

Hi,
We want to use this for our production environment in Elasticsearch2.x  for our enterprise customers.
Here are couple of questions:

Is it a open source ?
Anybody has experience using it in production grade ?

Thanks,
Indu

Hi Indu-sharma,
to your questions.
License
It is not an open source license (OSI) but a free software license (FSF) originally. They are pretty similar.
Apache License Version 2.0 (like e.g. Android, Docker, Swift)
See:

Wikipedia
Official license document
Differences OSI/FSF

Production grade
You should ask via:

Stackoverflow
Twitter @hendrikdev22  or
Mail<EMAIL_ADDRESS>for more information.

Regards,
mko


Timeout option not working

I set up the following:
var start = Date.now();

var request = require('request');
request({
    url: 'http://localhost:8080/test-connection-length',
    method: 'get',
    timeout: 600000, //10 min
}, function (error, response, body) {
    clearInterval(interval);
    if (error) {
        console.error(error);
        console.error(error.stack);
    }
    console.log('got response: ', response);
});

var interval = setInterval(function(){
    console.log('Waiting: ', (Date.now() - start) / 1000);
}, 1000);

The test server endpoint just sits and doesn't respond, writing a similar console log every second as well.
Even though I have a 10min timeout set, the result is the following in the client:
Waiting:  116.572
Waiting:  117.577
Waiting:  118.579
Waiting:  119.584
got response:  undefined
{ [Error: socket hang up] code: 'ECONNRESET' }
Error: socket hang up
    at createHangUpError (_http_client.js:215:15)
    at Socket.socketOnEnd (_http_client.js:300:23)
    at Socket.emit (events.js:129:20)
    at _stream_readable.js:908:16
    at process._tickCallback (node.js:355:11)

Process finished with exit code 0

Shouldn't this happen at 10mins, not 2?

Nevermind.  I wasn't setting the response timeout on the express server. Closing.


Update search UI in discharge patients page

Is your feature request related to a problem? Please describe.
Update search UI for Discharge Patients page like it was it was implemented in patients index page.
Describe the solution you'd like
Replace existing search UI in discharge patients page with smart search UI
Before

After

@Jacobjeevan @rithviknishad I want to work on this. Please assign this to me

@Jacobjeevan can you assign this issue to me.

Hey @ayushsaini7717  It is already assigned to me. You can look for other issues.


Need to discuss getting started with Rowan post-Alpha

The project menu options in alpha are not general enough for a product. We need to discuss how a customer will get started with Rowan and build Jadeite functionality to match.
Assigning to Dale for initial thoughts.
Post alpha.

@ericwinger Is this still a relevant issue?

Think we're past this.


Deleted models leave behind their Collection keys.

I'm using Redis Desktop Manager to look at the stored keys and noticed that JOhm was leaving behind a bunch of orphaned keys after the parent objects were being deleted. They all seemed to be Collection indexes.
Test case:
@Model
public class Test {
	@Id
	public Long id;
	@Attribute
	public String name;
	@CollectionList(of = TestMessage.class)
	public List<TestMessage> messages;
}

@Model
public class TestMessage {
	@Id
	public Long id;
	@Attribute
	public String message;
}

Test test = new Test();
test.name = "Test";
JOhm.save(test);

TestMessage testMessage = new TestMessage();
testMessage.message = "HelloWorld";
JOhm.save(testMessage);
test.messages.add(testMessage);

JOhm.delete(Test.class, test.id, true, true);

String key = String.format("Test:%d:messages", test.id);
boolean keyexists = _jedisPool.getResource().exists(key);
LOGGER.info(String.format("Key Exists: %s", keyexists?"YES":"NO"));

I have done some improvments in my fork, I think I already solved this issue. Give me few days to make a pull request because I have done other changes. Some of them are:

@SupportAll - id removal from collection when deleting
Sentinel support - so JOhm can be used with HA Redis/Sentinel

Sorry my Github mails were in my spam I did not notice your issue before!
I will look into it.

Only Arrays where supported while deleting a model and its children. I'm adding support for the other various collections (CollectionList, CollectionSet and so on).
Now @zTristan in your example, you're just checking that the key Test:1:messages has been deleted but not that TestMessage:1 (which was contained in Test:1:messages) has been deleted also, is that the behaviour you were expecting at first sight ?

I just released version 0.6.7 including the latest pull requests from @dpoldrugo and the fix for issue #9 and #5.

Now @zTristan in your example, you're just checking that the key Test:1:messages has been deleted but not that TestMessage:1 (which was contained in Test:1:messages) has been deleted also, is that the behaviour you were expecting at first sight ?
@agrison yes, it was just the indexes for the collection. The object themselves were being cleaned up.

Thanks for the update! I'll pull down 0.6.7 and verify!


make kustomize doesn't install kustomize with go 1.18

go get  no longer builds a module:
In earlier versions of Go, 'go get' was used to build and install packages.
Now, 'go get' is dedicated to adjusting dependencies in go.mod. 'go install'
may be used to build and install commands instead.

~ % go version
go version go1.18.1 linux/amd64

This was fixed in #173.


fix: Support for route segment withAxiom

Issues fixed

support for dynamic route segment for withAxiom  and withAxiomRouteHandler

looks great, just needs to run format script to fix the linting errors and then we are good to go.


godot error initializing : directional shadow framebuffer status invalid and other

First error is a duplicate of #28894

Duplicate of #28894 indeed. Not enough details to know if there's anything else here.


Missing tools includes on kernel module build

Users have encountered the following issue while trying to build kernel modules on rpi3:
fatal error: tools/be_byteshift.h: No such file or directory
This actually boils down to tools/include not being included in the headers, by simply adding this directory the issue is resolved.

Fixed by #6


cilium v1.15.2 has gRPC error when adding service.cilium.io/lb-l7 annotation to service of type: LoadBlanacer

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
cilium v1.15.2 has gRPC error when adding service.cilium.io/lb-l7 annotation to service of type: LoadBlanacer.
I have checked this manifest to make sure it works.
$ kubectl annotate service grpc-java-example-hostname-service service.cilium.io/lb-l7=enabled
service/grpc-java-example-hostname-service annotated

$ grpcurl -v -plaintext  <IP_ADDRESS>:50051 helloworld.Greeter.SayHello
Error invoking method "helloworld.Greeter.SayHello": rpc error: code = Unknown desc = failed to query for service descriptor "helloworld.Greeter":

# remove annotate
$ kubectl annotate service grpc-java-example-hostname-service service.cilium.io/lb-l7-
$ grpcurl -v -plaintext  <IP_ADDRESS>:50051 helloworld.Greeter.SayHello

Resolved method descriptor:
rpc SayHello ( .helloworld.HelloRequest ) returns ( .helloworld.HelloReply );

Request metadata to send:
(empty)

Response headers received:
content-type: application/grpc
grpc-accept-encoding: gzip

Response contents:
{
  "message": "Hello , from grpc-java-example-hostname-78b4b64c79-gkkbh"
}

Response trailers received:
(empty)
Sent 0 requests and received 1 response

At this time Cilium-agent outputs the following log.
cilium-qnjll cilium-agent level=info msg="[cilium.bpf_metadata: IPv4 conntrack map global lookup failed: Success" subsys=envoy-filter threadID=251
cilium-qnjll cilium-agent level=warning msg="[cilium.bpf_metadata (east/west L7 LB): Non-local pod can not use original source address: <IP_ADDRESS>" subsys=envoy-config threadID=251
cilium-qnjll cilium-agent level=warning msg="[[Tags: \"ConnectionId\":\"6\"] cilium.network: Cilium Socket Option not found" subsys=envoy-filter threadID=251
cilium-qnjll cilium-agent level=warning msg="[cilium.l7policy: Cilium Socket Option not found" subsys=envoy-filter threadID=251
cilium-qnjll cilium-agent level=info msg="Envoy: Accepted access log connection" subsys=envoy-manager
cilium-qnjll cilium-agent level=info msg="Envoy: Closing access log connection" subsys=envoy-manager
cilium-qnjll cilium-agent level=info msg="Envoy: Accepted access log connection" subsys=envoy-manager
cilium-qnjll cilium-agent level=info msg="Envoy: Closing access log connection" subsys=envoy-manager
cilium-qnjll cilium-agent level=warning msg="[cilium.l7policy: Cilium Socket Option not found" subsys=envoy-filter threadID=251
cilium-qnjll cilium-agent level=warning msg="[cilium.l7policy: Cilium Socket Option not found" subsys=envoy-filter threadID=251
cilium-qnjll cilium-agent level=info msg="Envoy: Accepted access log connection" subsys=envoy-manager
cilium-qnjll cilium-agent level=info msg="Envoy: Closing access log connection" subsys=envoy-manager

cilium was installed with the following helm parameters.
helm install cilium cilium/cilium --version 1.15.2 \
  --namespace kube-system \
  --set nodeinit.enabled='true' \
  --set nodeinit.reconfigureKubelet='true' \
  --set nodeinit.removeCbrBridge='true' \
  --set cni.binPath='/home/kubernetes/bin' \
  --set gke.enabled='true' \
  --set ipam.mode='kubernetes' \
  --set ipv4NativeRoutingCIDR='<IP_ADDRESS>/14' \
  --set kubeProxyReplacement='true' \
  --set loadBalancer.l7.backend='envoy' \
  --set ingressController.enabled='true' \
  --set ingressController.loadbalancerMode='dedicated' \
  --set k8sServiceHost='<IP_ADDRESS>' \
  --set k8sServicePort='443'

I have tested it with several versions and it works fine with the 1.14.4 version.
Cilium Version
1.15.2
Kernel Version
5.15.133+
Kubernetes Version
Client Version: v1.28.4
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.8-gke.1067004
Regression
1.14.4
Sysdump
cilium-sysdump-20240325-095530.zip
Relevant log output
No response
Anything else?
No response
Cilium Users Document

[ ] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@squeed
I think that issue is irrelevant.
Because ALPN negotiation is a recognition of the mechanism when it comes to TLS communication.
In my case, as I mentioned in the issue, the error occurs when TLS is disabled.
Also, v1.14.2 is able to communicate normally.

Not stale, this is still a problem.


User is not redirected to Cluster explorer on a rancher upgrade

Rancher Server Setup

Rancher version: master-head commit id: 9e0d1b2
Installation option (Docker install/Helm Chart): Helm install

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1

Information about the Cluster

Kubernetes version: 1.20.7

Describe the bug
User is not redirected to Cluster explorer on a rancher upgrade
To Reproduce

On 2.5.9 , deploy a downstream cluster (not required) in the Ember UI
Upgrade rancher to master-head.
User is still in Ember UI on the upgraded setup

Expected Result
User should be redirected to Cluster Explorer, since that is the default UI from 2.6.0

I'm paraphrasing what @vincent99 said in our chat as a comment here for whoever picks this up:
The most simple effective solution would bet to drop all existing UI session (tokens) once upon the first startup of 2.6, and anybody who was logged in will go back to the login page and then into Vue from there.

Yes the simplest solution I can think of is to delete all UI session tokens (there's an annotation identifying them as UI), just once, upon first startup of 2.6.
The UI can't really do much on it's own here because the user already has some existing old version loaded and running in their browser, and we haven't gone back into the past to define a way for it to know it should do anything.

PR: https://github.com/rancher/rancher/pull/33849

Available to test in v2.6.0-rc1

Sending back to "Working" as we need UI change as UI stores the last path the user was at in browser storage. After they log back in they still get redirected to Ember-based UI because that was their last know path. @vincent99, please let us know when you have an update on this.


—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

<

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMOJJADDG3R72YOBEF5DPYFZNPA5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWWDZ5Y#issuecomment-497827063

,

or mute the thread

<

https://github.com/notifications/unsubscribe-auth/ACYCMOISR5O6QTDM6SNHX53PYFZNPANCNFSM4HLWK34A

.

--

You are receiving this because you authored the

thread.

Reply to this email directly or view it on GitHub:

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-497836532

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

<

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMOKQJSLGYATCIVOYU6LPYODM3A5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXRDIA#issuecomment-498012576

,

or mute the thread

<

https://github.com/notifications/unsubscribe-auth/ACYCMONKICSDIB7ELFGU5ZTPYODM3ANCNFSM4HLWK34A

.

--

You are receiving this because you authored the thread.

Reply to this email directly or view it on GitHub:

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-498025291

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

<

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMOIWQ4EDXV6WMJ3HMZLPYQFWDA5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWX3GWQ#issuecomment-498053978

,

or mute the thread

<

https://github.com/notifications/unsubscribe-auth/ACYCMOPYHKSRMFMGVIJ7VR3PYQFWDANCNFSM4HLWK34A

.

--

You are receiving this because you authored the thread.

Reply to this email directly or view it on GitHub:

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-498246063

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

<

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMOJPNQ6GREN2AJ5NAJLPZVU2NA5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXISAIY#issuecomment-500244515

,

or mute the thread

<

https://github.com/notifications/unsubscribe-auth/ACYCMOMJ4DY4X3N6UD6NUH3PZVU2NANCNFSM4HLWK34A

.

--

You are receiving this because you authored the thread.

Reply to this email directly or view it on GitHub:

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-500250625

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

<

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMOOVYJRT5CQKIYP2TQLPZWANVA5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXITSMI#issuecomment-500250929

,

or mute the thread

<

https://github.com/notifications/unsubscribe-auth/ACYCMOK5U43JMDD7G3QYR6DPZWANVANCNFSM4HLWK34A

.

--

You are receiving this because you authored the thread.

Reply to this email directly or view it on GitHub:

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-500265092

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

<

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMONB7OOEYSCGAAGPTRLPZXYODA5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJBL6I#issuecomment-500307449

,

or mute the thread

<

https://github.com/notifications/unsubscribe-auth/ACYCMOMEBHIYA6PNWZX3QIDPZXYODANCNFSM4HLWK34A

.

--

You are receiving this because you authored the thread.

Reply to this email directly or view it on GitHub:

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-500390909

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMOI7KTXUAIAW3UZFIOTPZ5B7RA5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXMDEIA#issuecomment-500707872,

or mute the thread

https://github.com/notifications/unsubscribe-auth/ACYCMOJKQPDJ4U6RMQMH2KDPZ5B7RANCNFSM4HLWK34A

.

--

You are receiving this because you authored the thread.

Reply to this email directly or view it on GitHub:

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-500834517

HI
Is it possible to change alignment of vertical and horizontal scale numbers.
I find it always thinking what means 0.0 or 100.0
It probably is a personal preference, but for me it would
be more intiuitve if horizontal scale text was are aligned to decimal point "."
and vertical text is aligned to its vertical center.
Or it can be left aligned as it is but then I'd like to have some
horizintal and vertical
lines, preferably at vertical and horizontal windows (not on the main grid) that
precisely mark value with its position on the graphic
On 6/11/19, D EMARD<EMAIL_ADDRESS>wrote:

Well diamond on other hand can sometimes swallow
the obvious syntax error... fixing such things is essential
for multiplatform compatibility :)
I quickfixed the mouse2rgtr to move vt offset but it acts
a bit "strange", i need to rethink how to improve in a way
that is good and simple
On 6/11/19, Miguel Angel<EMAIL_ADDRESS>wrote:

Thanks. I've fixed. I didn't have  time to compile it on Diamond. ISE let

it pass. Very dangerous.

On Tue, Jun 11, 2019 at 3:38 AM emard<EMAIL_ADDRESS>wrote:

HI with latest git, I get this compile error:

E: CD297

:"/home/guest/src/fpga/hdl4fpga/library/scope/scopeio_segment.vhd":151:6:151:7|Width

mismatch, location has width 9, value 13

line 151 is:

row <= unsigned(trigger_level)+2**(y'length-2)-unsigned(vt_offset);

On 6/10/19, Miguel Angel<EMAIL_ADDRESS>wrote:

Great!

On Mon, Jun 10, 2019, 03:32 emard<EMAIL_ADDRESS>wrote:

YES, it synthesizes much better now and uses less LUTs!

It works now even on one suspicious board there was

always having fmax problems.

I need to make small pull request for compiling on ULX3S

after new video rework.

On 6/10/19, Miguel Angel<EMAIL_ADDRESS>wrote:

I've merged work into master. I replaced dpram with rom. My
ecp3versa

is

working. spartan s3 works at 1080p now.

I hope your the code improves your synthesis too.

On Sun, Jun 9, 2019 at 7:34 PM emard<EMAIL_ADDRESS>

wrote:

OK

If possible to make it take valid data after a clock cycle,

then it may be realized either as LUT or as BRAM.

optimizer will decide what fits better.

If there is no clock, then optimizer has no BRAM option.

On 6/10/19, Miguel Angel<EMAIL_ADDRESS>wrote:

I´ll replace it with a rom but It should have used a distribute
ram

or

LUT.

They are small only 8 words.

I used a ram because in the future they can be changed
dynamically.

On Sun, Jun 9, 2019 at 5:55 PM emard<EMAIL_ADDRESS>

wrote:

HI I tried "work" branch.

I got black screen and only mouse pointer visible.

in video.vhd there's some dpram instance used as ROM

without clock. For ECP5, ROM made of BRAM

still must have the clock

At line 71

wr_clk => '-',

I don't know is it correct but I changed to:

wr_clk => video_clk,

On 6/3/19, D EMARD<EMAIL_ADDRESS>wrote:

HI

That's great, if youe have explaination why display must look

like

this

for low frequency mode, that's ok. I wouldn''t rush up
either,

it's

better

to have some time of rethinking abut what's the best to do.

I don't need much low frequency mode but instead of that I
would

rather have properly implemented one-shot trigger which

automatically

freezes.

Also what I considered important option is to be able to
change

timebase

(horizontal zoom) during freeze mode. this currently seems it

doesn't

work

On 6/3/19, Miguel Angel<EMAIL_ADDRESS>wrote:

Ok ... thanks for the code ... I haven't tried it yet ...
but

if

the

signal is a low frequency one, I think it is a buffer fill

problem

...

I

can fixed it, I saw that and it should be a simple one. It
is

showing

part

of the old capture buffer

I'll tell you when I fix it, may it'll be ready in a couple
of

days

...

I

hope you are not in a rush

thanks

On Sun, Jun 2, 2019 at 3:22 PM emard
<EMAIL_ADDRESS>

wrote:

Here is example that demonstrates the trigger problem.

When input_ena=1 constantly and trigger is active (display
not

frozen)

A wave with slightly different period than 2048 (e.g. 2040)

then

the

square

wave edges are dispalyed wrong - as dashed line and at
angle.

| |

| |

| |____

When i set freeze bit, then the frozen display is drawn

correct

here is toplevel code that generates the squarewave with
2040

period

see "replacement for ADC that manifests the problem"

ULX3S/scopeio/scopeio.vhd

https://github.com/emard/hdl4fpga/blob/master/ULX3S/scopeio/scopeio.vhd#L183

On 6/2/19, D EMARD<EMAIL_ADDRESS>wrote:

HI

I think I have to make a test example because this

situation doesn't appear at any simple signal

On 6/2/19, Miguel Angel<EMAIL_ADDRESS>wrote:

I saw that and I thought I fixed on last update of
scopeio.

Can

you

send

me

a picture or ask Goran to post one on discord ?

On Sun, Jun 2, 2019 at 5:56 AM emard

<EMAIL_ADDRESS>

wrote:

The new triggering method techically works better but

visual

appearance

of the vertical traces is now somehow flickering.
Vertical

parts

of the traces are not continuous, they are dashed lines

now.

On 5/31/19, D EMARD<EMAIL_ADDRESS>wrote:

And yes, you are right oneshot_ena should be external

signal

when signal is not triggered oneshot_ena = 0 and then

activated

by oneshot_ena = 1. When trigger event appears and if

oneshot_ena

is still at 1, screen should freeze and display what

happened

exactly

at the moment of trigger event

On 5/31/19, D EMARD<EMAIL_ADDRESS>wrote:

Your latest changes seem to work correctly!

when I press btn, trace jumps immediately

no more PWM pattern.

Still at BTN press, I can see a flash of some 45 deg

trace slopes that is draw wrong, but it's just for a

short

moment of time. Definitely trigger system works much

better now

I welcome idea of implementing one-shot mode !

On 5/31/19, Miguel Angel<EMAIL_ADDRESS>

wrote:

yes ... i only skeched and compiled

i haven't tested much

On Fri, May 31, 2019, 16:07 emard

<EMAIL_ADDRESS>

wrote:

Great!

I'm a bit confused about input_oneshot - should be
it

named Input_trigger (as external trigger) ?

I thought one-shot mode should be a trigger mode

controlled

by

scopeio_rgtr, similar like it already controls

trigger

edge

as

rising

or

falling

On 5/31/19, Miguel Angel
<EMAIL_ADDRESS>

wrote:

...

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-497820567

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

<

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMOJJADDG3R72YOBEF5DPYFZNPA5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWWDZ5Y#issuecomment-497827063

,

or mute the thread

<

https://github.com/notifications/unsubscribe-auth/ACYCMOISR5O6QTDM6SNHX53PYFZNPANCNFSM4HLWK34A

.

--

You are receiving this because you authored the

thread.

Reply to this email directly or view it on GitHub:

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-497836532

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

<

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMOKQJSLGYATCIVOYU6LPYODM3A5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXRDIA#issuecomment-498012576

,

or mute the thread

<

https://github.com/notifications/unsubscribe-auth/ACYCMONKICSDIB7ELFGU5ZTPYODM3ANCNFSM4HLWK34A

.

--

You are receiving this because you authored the thread.

Reply to this email directly or view it on GitHub:

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-498025291

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

<

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMOIWQ4EDXV6WMJ3HMZLPYQFWDA5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWX3GWQ#issuecomment-498053978

,

or mute the thread

<

https://github.com/notifications/unsubscribe-auth/ACYCMOPYHKSRMFMGVIJ7VR3PYQFWDANCNFSM4HLWK34A

.

--

You are receiving this because you authored the thread.

Reply to this email directly or view it on GitHub:

https://github.com/hdl4fpga/hdl4fpga/issues/8#issuecomment-498246063

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub

<

https://github.com/hdl4fpga/hdl4fpga/issues/8?email_source=notifications&email_token=ACYCMOJPNQ6GREN2AJ5NAJLPZVU2NA5CNFSM4HLWK34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXISAIY#issuecomment-500244515

,

or mute the thread


PrinterState() suite Failure

This issue related to #121 and #123.
Our printer fails testNoMediaInTray() and testTonerCartridge().
Because these test cases check 'input' or 'tray' is in 'caption' field or 'message' field field in CDS, but the paper source is called 'Cassette 1' in 'caption' field or 'message' field on this printer.
I think other test cases which call VerifyUiStateMessage() have the same problem.
In addition, this printer passed these tests at 30e56a1b2509a6e7aadf1ebc2371484e103367d1.
How to fix it?
Please give your opinion.

Regarding testNoMediaInTray(), I've pushed this commit which now accepts "cassette" as a required keyword: https://github.com/google/cloudprint_logocert/commit/dd0583c806cc3f659eb8542be69c179340b2397d
Please let me know the error you get for testTonerCartridge() as that test case does not check for input/tray, it checks for ink/toner.

Thank you for your changes.
dd0583c806cc3f659eb8542be69c179340b2397d works fine with my printer.
testTonerCartridge() works fine before/after dd0583c806cc3f659eb8542be69c179340b2397d.


(PDB-1887) Update PDB version to 3.1.0

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1835/

Closing to target against stable


BLD: add unix-specific build flags to ignore errors

Reference issue

https://github.com/rgommers/scipy/pull/107
What does this implement/fix?

compiler flags to match those generated by the HiGHS CMake build system

Additional information

Unix flags done, now builds on Linux without warnings

-Wclass-memaccess is not actually in upstream build flags and emits warnings there too.  Will work on an upstream patch

Working on Windows/MacOS flags

We probably can remove the Linux qualifier. I only added that as I intended to try on Mac and windows to make sure - I just ran into build issues on Mac

Okay thanks, I'll push a commit to use the flags unconditionally. And then will check if macOS/Clang complains locally.


Overriding Handlers isn't possible anymore

With the introduction of v3, overriding handlers is not possible anymore through just the handler configuration.
I am using Symfony 4.
Previously, the slack handler could have been overridden by setting the monolog.handler.slack.class parameter as in:
https://github.com/symfony/monolog-bundle/blob/2.x/Resources/config/monolog.xml
Now, it looks like this: https://github.com/symfony/monolog-bundle/blob/master/Resources/config/monolog.xml
With no parameter to override handlers.
To achieve the same result, one would have to create a new service, and pass to it all the handler parameters, then call the original constructor of the handler.
Can we have the handler overriding parameters back?

All these parameters lead to overhead - see https://github.com/symfony/symfony/issues/11881 - so no they are not coming back sorry.


CT: Beam Object Expired - Bug

The first time in most Scripts when the Beam Component generates a bunch of Beams, we get this Error Message. After closing it and "Recompute" the Structure gets properly generated and the Message doesn't appear until I start Rhino/Gh the next time.

Video:
https://drive.google.com/file/d/1jYLG2DL7icN2ssBnGggrDiBjgth0A5FW/view?usp=sharing
Gh File:
https://drive.google.com/file/d/1hIC3F2Yt7NHSxMWMoh_bErowTpj9Dtit/view?usp=sharing

@chenkasirer did this get fixed?

I've seen this before but never consistently. the question is if this can be consistently reproduced. otherwise I'm afraid this might be a Grashopper issue. We could try to reproduce it and look for a log then start a thread on the GH forum.


pagerRef.current.setPage is now working in useEffect

pagerRef.current.setPage is now working in useEffect, only when used with setTimeout. Any way to make the initial index state (rather than use difference)?
thanks

+1

can you give me some more context on the issue? and a snack repro if possible? thanks!

Any way to make the initial index state (rather than use difference)

Is this a separate issue? You want to initialize the pager with index other than 0? You're correct that the initial index is always 0, but what you map that 0 to is up to you. Pager index 0 could map to anything — including an item in the middle of some data array you have in state — part of the intentional design of this pager is that its agnostic of the data it renders — its only job is to page through indices, starting at 0 and going negative into infinity, or positive into infinity.

Hello @computerjazz
first of all thank you for the library, is very very good for what I am trying to achieve.
I am basically using infinite page to create a Instagram Like stories component. Each story has an ID which I can use as Index for the infinite-pager.

Everything works fine except that I don't have a way to start from that specific index. I cloned your code and I was able to make it work by adding a startAtIndex prop but the only way to make it work is by doing
useEffect(() => {
    if (startAtIndex) {
      const timeout = setTimeout(() => {
        setPage(startAtIndex, { animated: false });
      }, 300;

      return () => clearTimeout(timeout);
    }
  }, [startAtIndex]);

(which I think is what was mentioned in the issue above).  That 300 is clearly an imperative value that must be avoided and in fact it works on IOS in my case but not in Android (which has decreased performances compare to IOS). By incrementing the timeOut of course it works but it's ugly as you see the first page and then it jumps to the selected.
I know this maybe is not in your design pattern, but it will be fantastic if there was a way to add it or if you could tell me how to achieve this as it will make me able to finish this feature for my project.
Thanks

Thanks for the details! I agree it would be a minor change to be able to set the initial index and I'll consider adding it as a prop. Is there a reason why you can't do something like:
const renderPage = useCallback(({ index }) => {
  const indexWithOffset = index + startAtIndex
  const item = myData[indexWithOffset]
  // render your item...
}, [startAtIndex])

return (
      <InfinitePager
        renderPage={renderPage}
      />)

const renderPage = useCallback(({ index }) => {
  const indexWithOffset = index + startAtIndex
  const item = myData[indexWithOffset]
  // render your item...
}, [startAtIndex])

Thanks for the quick reply @computerjazz. Is nice to see someone actually replying. I have used a lot of react native library and they all seems abandoned and no ones ever reply. Anyway, yes this could work but then, it messes up the array. Meaning I start from the 2 second page but I can't go back to the previous ones

as for the original issue  with setPage on mount -- should be fixed in 0.3.10: https://github.com/computerjazz/react-native-infinite-pager/releases/tag/v0.3.10


Robot turns on spot

The robot still turns on spot without moving forwards when using the straight line navigation.
Tested with F13/RB36 on https://github.com/zauberzeug/field_friend/pull/96, but I don't think it is related to the changes done there.

rosys_1       | 2024-07-16 15:39:37.586 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:39:37.690 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:39:37.791 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:39:37.891 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:39:37.992 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:39:38.092 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:39:38.196 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:39:38.296 [INFO] field_friend/hardware/tornado.py:242: Ref ground not triggered: Bottom ground reached
rosys_1       | 2024-07-16 15:39:38.297 [INFO] field_friend/hardware/tornado.py:251: finalizing moving z axis down
rosys_1       | 2024-07-16 15:39:46.723 [INFO] field_friend/hardware/tornado.py:207: moving z axis to 0
rosys_1       | 2024-07-16 15:39:49.051 [INFO] field_friend/hardware/tornado.py:212: z axis moved to 0
rosys_1       | 2024-07-16 15:39:52.971 [INFO] field_friend/automations/puncher.py:105: punched at -0.02 with depth 0.01, now back to rest position "reference"
rosys_1       | 2024-07-16 15:39:52.972 [INFO] field_friend/automations/implements/weeding_implement.py:91: workflow completed
rosys_1       | 2024-07-16 15:39:52.973 [INFO] field_friend/automations/implements/weeding_implement.py:154: Moved weed 57f77f9c-5fcb-498c-9793-8393e65d7486 from Point(0.13, -0.03) to Point(0.13, -0.03) by 0.004740341087867542 to safe 9a78e552-4615-4daa-894c-3a818fbc6316 at Point(0.13, 0.0)
rosys_1       | 2024-07-16 15:39:52.974 [INFO] field_friend/automations/implements/tornado.py:64: Skipping weed because it was already punched
rosys_1       | 2024-07-16 15:39:53.586 [INFO] field_friend/automations/implements/weeding_implement.py:154: Moved weed 57f77f9c-5fcb-498c-9793-8393e65d7486 from Point(0.12, -0.03) to Point(0.12, -0.03) by 0.004740484667725961 to safe 9a78e552-4615-4daa-894c-3a818fbc6316 at Point(0.11, 0.0)
rosys_1       | 2024-07-16 15:39:53.587 [INFO] field_friend/automations/implements/tornado.py:64: Skipping weed because it was already punched
rosys_1       | 2024-07-16 15:39:54.003 [INFO] field_friend/automations/implements/weeding_implement.py:154: Moved weed 57f77f9c-5fcb-498c-9793-8393e65d7486 from Point(0.1, -0.02) to Point(0.1, -0.03) by 0.005229677636585651 to safe 9a78e552-4615-4daa-894c-3a818fbc6316 at Point(0.09, 0.0)
rosys_1       | 2024-07-16 15:39:54.004 [INFO] field_friend/automations/implements/tornado.py:82: Targeting crop 9a78e552-4615-4daa-894c-3a818fbc6316 which is 0.08091422189536067 away at world: Point(-0.36, -2.78), local: Point(0.09, 0.0)
rosys_1       | 2024-07-16 15:39:54.511 [INFO] field_friend/automations/implements/weeding_implement.py:154: Moved weed 57f77f9c-5fcb-498c-9793-8393e65d7486 from Point(0.08, -0.03) to Point(0.08, -0.03) by 0.005571287367279465 to safe 9a78e552-4615-4daa-894c-3a818fbc6316 at Point(0.08, 0.0)
rosys_1       | 2024-07-16 15:39:54.512 [INFO] field_friend/automations/implements/tornado.py:82: Targeting crop 9a78e552-4615-4daa-894c-3a818fbc6316 which is 0.06432214687245745 away at world: Point(-0.36, -2.78), local: Point(0.08, 0.0)
rosys_1       | 2024-07-16 15:39:54.918 [INFO] field_friend/automations/implements/weeding_implement.py:154: Moved weed 57f77f9c-5fcb-498c-9793-8393e65d7486 from Point(0.06, -0.03) to Point(0.06, -0.03) by 0.00563157202652103 to safe 9a78e552-4615-4daa-894c-3a818fbc6316 at Point(0.06, 0.0)
rosys_1       | 2024-07-16 15:39:54.919 [INFO] field_friend/automations/implements/tornado.py:82: Targeting crop 9a78e552-4615-4daa-894c-3a818fbc6316 which is 0.04452849722041616 away at world: Point(-0.36, -2.79), local: Point(0.06, 0.0)
rosys_1       | 2024-07-16 15:39:57.442 [INFO] field_friend/automations/implements/weeding_implement.py:154: Moved weed 57f77f9c-5fcb-498c-9793-8393e65d7486 from Point(0.01, -0.03) to Point(0.01, -0.03) by 0.004958876874267788 to safe 9a78e552-4615-4daa-894c-3a818fbc6316 at Point(0.02, 0.0)
rosys_1       | 2024-07-16 15:39:57.443 [INFO] field_friend/automations/implements/tornado.py:26: Performing Tornado Workflow..
rosys_1       | 2024-07-16 15:39:57.443 [INFO] field_friend/automations/implements/tornado.py:32: Drilling crop at Point(-0.35, -2.78) with angle 30.0°
rosys_1       | 2024-07-16 15:39:57.444 [INFO] field_friend/automations/puncher.py:67: Punching at 0.0038732758021282994 with depth 0.01...
rosys_1       | 2024-07-16 15:39:57.444 [INFO] field_friend/hardware/y_axis.py:47: moving yaxis to 0.0038732758021282994 with speed 500
rosys_1       | 2024-07-16 15:39:57.444 [INFO] field_friend/hardware/y_axis_canopen_hardware.py:76: moving to steps: 105738
rosys_1       | 2024-07-16 15:39:59.352 [INFO] field_friend/hardware/y_axis_canopen_hardware.py:89: yaxis moved to 0.0038732758021282994
rosys_1       | 2024-07-16 15:39:59.353 [INFO] field_friend/automations/puncher.py:163: Drilling with tornado at 30.0°...
rosys_1       | 2024-07-16 15:39:59.353 [INFO] field_friend/hardware/tornado.py:220: moving z axis down
rosys_1       | 2024-07-16 15:40:00.356 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:00.458 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:00.559 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:00.660 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:00.763 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:00.864 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:00.977 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:01.078 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:01.178 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:01.280 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:01.380 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:01.481 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:01.581 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:01.683 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:01.784 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:01.885 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:01.985 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:02.085 [INFO] field_friend/hardware/tornado.py:237: moving z axis down
rosys_1       | 2024-07-16 15:40:02.185 [INFO] field_friend/hardware/tornado.py:242: Ref ground not triggered: Bottom ground reached
rosys_1       | 2024-07-16 15:40:02.185 [INFO] field_friend/hardware/tornado.py:251: finalizing moving z axis down
rosys_1       | 2024-07-16 15:40:10.556 [INFO] field_friend/hardware/tornado.py:207: moving z axis to 0
rosys_1       | 2024-07-16 15:40:12.862 [INFO] field_friend/hardware/tornado.py:212: z axis moved to 0
rosys_1       | 2024-07-16 15:40:13.872 [WARNING] rosys/rosys.py:232: less than 300 mb of memory remaining -> start garbage collection
rosys_1       | 2024-07-16 15:40:14.245 [INFO] field_friend/localization/gnss_hardware.py:102: Parse error: ('could not parse data', '$')
rosys_1       | 2024-07-16 15:40:14.246 [WARNING] field_friend/localization/gnss_hardware.py:109: No location in GNSS data -- maybe it was provided in GGA message?
rosys_1       | 2024-07-16 15:40:14.247 [WARNING] field_friend/localization/gnss.py:94: new GNSS record is None
rosys_1       | 2024-07-16 15:40:14.247 [INFO] field_friend/automations/automation_watcher.py:62: not pausing automation because GNSS connection lost but GNSS watch is not active
rosys_1       | 2024-07-16 15:40:15.233 [WARNING] rosys/rosys.py:235: finished garbage collection
rosys_1       | 2024-07-16 15:40:16.679 [INFO] field_friend/automations/puncher.py:105: punched at 0.00 with depth 0.01, now back to rest position "reference"
rosys_1       | 2024-07-16 15:40:16.680 [INFO] field_friend/automations/implements/weeding_implement.py:91: workflow completed
rosys_1       | 2024-07-16 15:40:16.681 [INFO] field_friend/automations/implements/weeding_implement.py:154: Moved weed 57f77f9c-5fcb-498c-9793-8393e65d7486 from Point(0.0, -0.03) to Point(0.0, -0.03) by 0.006885315488495594 to safe 9a78e552-4615-4daa-894c-3a818fbc6316 at Point(0.0, 0.0)
rosys_1       | 2024-07-16 15:40:16.682 [INFO] field_friend/automations/implements/tornado.py:64: Skipping weed because it was already punched
rosys_1       | 2024-07-16 15:40:17.591 [INFO] field_friend/automations/implements/tornado.py:70: Closest crop is out of working area
rosys_1       | 2024-07-16 15:40:24.643 [WARNING] rosys/hardware/estop.py:56: E-Stop [0] changed

Same happened in Follow Crop Mode with new setting as you can see in #103
rosys_1       | 2024-07-16 17:19:12.518 [INFO] field_friend/automations/plant_locator.py:51: backup: autoupload: Autoupload.FILTERED rosys_1       | 2024-07-16 17:19:14.690 [INFO] rosys/vision/mjpeg_camera/mjpeg_camera_provider.py:90: activating camera "b8:a4:4f:a9:43:1f-1" at ip "<IP_ADDRESS>" ... rosys_1       | 2024-07-16 17:19:14.691 [INFO] rosys/vision/mjpeg_camera/mjpeg_camera_provider.py:90: activating camera "b8:a4:4f:a9:43:1f-2" at ip "<IP_ADDRESS>" ... rosys_1       | 2024-07-16 17:19:14.691 [INFO] rosys/vision/mjpeg_camera/mjpeg_camera_provider.py:90: activating camera "b8:a4:4f:a9:43:1f-3" at ip "<IP_ADDRESS>" ... rosys_1       | 2024-07-16 17:19:14.692 [INFO] rosys/vision/mjpeg_camera/mjpeg_camera_provider.py:90: activating camera "b8:a4:4f:a9:43:1f-4" at ip "<IP_ADDRESS>" ... rosys_1       | 2024-07-16 17:19:14.692 [INFO] rosys/vision/mjpeg_camera/mjpeg_device.py:44: Capturing images from http://<IP_ADDRESS>/axis-cgi/mjpg/video.cgi?camera=1 rosys_1       | 2024-07-16 17:19:14.707 [INFO] rosys/vision/mjpeg_camera/mjpeg_device.py:44: Capturing images from http://<IP_ADDRESS>/axis-cgi/mjpg/video.cgi?camera=2 rosys_1       | 2024-07-16 17:19:14.720 [INFO] rosys/vision/mjpeg_camera/mjpeg_device.py:44: Capturing images from http://<IP_ADDRESS>/axis-cgi/mjpg/video.cgi?camera=3 rosys_1       | 2024-07-16 17:19:14.732 [INFO] rosys/vision/mjpeg_camera/mjpeg_device.py:44: Capturing images from http://<IP_ADDRESS>/axis-cgi/mjpg/video.cgi?camera=4 rosys_1       | 2024-07-16 17:19:15.817 [WARNING] rosys/vision/detector_hardware.py:35: sio connect error on 8004: Connection refused by the server rosys_1       | 2024-07-16 17:19:15.817 [ERROR] rosys/vision/detector_hardware.py:47: connection to f7797a9f-5244-4b2b-b23b-b8b6e7681cf7 at port 8004 failed; trying again rosys_1       | 2024-07-16 17:19:17.515 [INFO] field_friend/vision/camera_configurator.py:27: updating camera config rosys_1       | 2024-07-16 17:19:17.537 [INFO] rosys/hardware/battery_control.py:28: releasing battery relay rosys_1       | 2024-07-16 17:19:18.517 [INFO] field_friend/vision/camera_configurator.py:36: camera: 32e4-9230-platform-3610000.xhci-usb-0:2.3:1.0 is active rosys_1       | 2024-07-16 17:19:18.518 [INFO] field_friend/vision/camera_configurator.py:46: parameter width with value 1280 rosys_1       | 2024-07-16 17:19:18.518 [INFO] field_friend/vision/camera_configurator.py:46: parameter height with value 720 rosys_1       | 2024-07-16 17:19:18.518 [INFO] field_friend/vision/camera_configurator.py:46: parameter auto_exposure with value True rosys_1       | 2024-07-16 17:19:18.519 [INFO] field_friend/vision/camera_configurator.py:46: parameter fps with value 10 rosys_1       | 2024-07-16 17:19:18.519 [INFO] field_friend/vision/camera_configurator.py:48: 9 != 10 rosys_1       | 2024-07-16 17:19:18.519 [INFO] field_friend/vision/camera_configurator.py:98: Updated camera 32e4-9230-platform-3610000.xhci-usb-0:2.3:1.0 parameters, requesting backup... rosys_1       | 2024-07-16 17:19:18.818 [INFO] rosys/vision/detector_hardware.py:45: trying reconnect f7797a9f-5244-4b2b-b23b-b8b6e7681cf7 rosys_1       | 2024-07-16 17:19:18.819 [INFO] rosys/vision/detector_hardware.py:57: connecting to detector at ws://localhost:8004 rosys_1       | 2024-07-16 17:19:18.843 [INFO] rosys/vision/detector_hardware.py:59: connected successfully rosys_1       | 2024-07-16 17:19:22.507 [INFO] field_friend/vision/calibratable_usb_camera_provider.py:24: backing up camera: {'id': '32e4-9230-platform-3610000.xhci-usb-0:2.1:1.0', 'name': '32e4-9230-platform-3610000.xhci-usb-0:2.1:1.0', 'connect_after_init': True, 'streaming': False, 'focal_length': 1830, 'calibration': {'intrinsics': {'matrix': [[900.7563580745991, 0.0,<PHONE_NUMBER>520205], [0.0,<PHONE_NUMBER>884107,<PHONE_NUMBER>0322316], [0.0, 0.0, 1.0]], 'distortion': [-0.3936727926969431, 0.1910463197137935, 0.004863672318620469, 0.0004754694660314551, -0.04783286390279313], 'rotation': {'R': [[1.0, 0.0, 0.0], [0.0, 1.0, 0.0], [0.0, 0.0, 1.0]]}, 'size': {'width': 1280, 'height': 720}}, 'extrinsics': {'rotation': {'R': [[-0.008812065190163532, 0.7845453340130073, -0.6200088437962019], [0.9999610194820463, 0.007257303739787835, -0.005029021659822479], [0.0005540970229195576, -0.620028991597044, -0.7845787038631892]]}, 'translation': [0.2925151857987712, 0.014639470490577467, 0.3090187031839868]}}, 'auto_exposure': True, 'exposure': False, 'width': 1280, 'height': 720, 'fps': 9} rosys_1       | 2024-07-16 17:19:22.511 [INFO] field_friend/vision/calibratable_usb_camera_provider.py:24: backing up camera: {'id': '32e4-9230-platform-3610000.xhci-usb-0:2.3:1.0', 'name': '32e4-9230-platform-3610000.xhci-usb-0:2.3:1.0', 'connect_after_init': True, 'streaming': True, 'focal_length': 1830, 'calibration': {'intrinsics': {'matrix': [[900.7563580745991, 0.0,<PHONE_NUMBER>520205], [0.0,<PHONE_NUMBER>884107,<PHONE_NUMBER>0322316], [0.0, 0.0, 1.0]], 'distortion': [-0.3936727926969431, 0.1910463197137935, 0.004863672318620469, 0.0004754694660314551, -0.04783286390279313], 'rotation': {'R': [[1.0, 0.0, 0.0], [0.0, 1.0, 0.0], [0.0, 0.0, 1.0]]}, 'size': {'width': 1280, 'height': 720}}, 'extrinsics': {'rotation': {'R': [[-0.008812065190163532, 0.7845453340130073, -0.6200088437962019], [0.9999610194820463, 0.007257303739787835, -0.005029021659822479], [0.0005540970229195576, -0.620028991597044, -0.7845787038631892]]}, 'translation': [0.2925151857987712, 0.014639470490577467, 0.3090187031839868]}}, 'auto_exposure': True, 'exposure': False, 'width': 1280, 'height': 720, 'fps': 9} rosys_1       | 2024-07-16 17:19:24.741 [INFO] rosys/rosys.py:69: automation started rosys_1       | 2024-07-16 17:19:24.743 [INFO] field_friend/automations/navigation/follow_crops_navigation.py:30: Activating Recorder... rosys_1       | 2024-07-16 17:20:02.570 [WARNING] rosys/rosys.py:232: less than 300 mb of memory remaining -> start garbage collection rosys_1       | 2024-07-16 17:20:02.959 [INFO] field_friend/localization/gnss_hardware.py:102: Parse error: ('could not parse data', '$') rosys_1       | 2024-07-16 17:20:02.966 [WARNING] field_friend/localization/gnss_hardware.py:109: No location in GNSS data -- maybe it was provided in GGA message? rosys_1       | 2024-07-16 17:20:02.967 [WARNING] field_friend/localization/gnss.py:94: new GNSS record is None rosys_1       | 2024-07-16 17:20:02.967 [INFO] field_friend/automations/automation_watcher.py:62: not pausing automation because GNSS connection lost but GNSS watch is not active rosys_1       | 2024-07-16 17:20:03.941 [WARNING] rosys/rosys.py:235: finished garbage collection rosys_1       | 2024-07-16 17:21:00.983 [INFO] rosys/rosys.py:69: automation paused because pause button was pressed

@pascalzauberzeug is it really happening with "straight line navigation"? With "follow crops" I can imagine how a constellation of crops could lead to such a turn. But with "straight line" I've never experienced it before. If it does happen with "straight line", I think we need much more detailed logging to get to the bottom of this.
Both your logs show new GNSS record is None. Have you picked the logs because of this message or are the logs truly the time where the robot made it turn? To verify the behaviour with lost signal, I created https://github.com/zauberzeug/field_friend/pull/124. It does not turn the robot.

@rodja Yes, I ran F13 only on straight line. The log I posted is just the minute before I pressed the e-stop

Could you add more logging? Like the yaw change when calling the _drive method? Or maybe activate serial logging so we can find out what is send to the motors when the turn happens...


CLN: lint

What do these changes do?

[ ] commit message follows format outlined here
[ ] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] signed commit with git commit -s
[ ] Resolves #?
[ ] tests added and passing
[ ] module layout described at docs/development/architecture.rst is up-to-date
[ ] added (Issue Number: PR title (PR Number)) and github username to release notes for next major release

but how did you generate them?

flake8 modin/pandas/

I've tried this before but I think using flake8 to format directly butts heads with what black thinks is correct.

I've def had this happen before - flake8 and black often clash.

Don't we need to change the tests so CI passes?

the commit linter doesn't like "CLN".  suggestions?

@jbrockmendel the lint failure says, "CLN taskId must start with project key FEAT,DOCS,FIX,REFACTOR,TEST,PERF".
I think "REFACTOR" fits here.

@jbrockmendel could you please fill the PR template here (including the issue number), as otherwise it's unclear what you're aiming to fix here.


aci: add ManifestFromImage helper function

Do not merge! Work in progress.

@kelseyhightower consider the Reader/ReadSeeker thing non-blocking, feel free to land this whenever. LGTM.


ERROR in typescript snippet

You don't have to use * as when its already exporting RandExp

@littlepiggy03 since you added the typescript definition files, what's your take on this?

@sksankarraj It's not an error. Like what you said, it's just don't have to use * as, not mustn't. (See also in #70)
@fent Since esModuleInterop is on by default, so feel free to merge. :smile:

Thanks!


add link to sms logs page

enable logging page applies to sms logs but the link to sms logs description page was missed

@hapatim
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Createclient without args fails

Hi,
I've fixed an issue that happens when a client issues createclient without arguments.
Current code only checks whether args are null or not. I've added a patch that also checks for undefined condition.
Pull request is here
Cheers

This has been fixed by #786


Use CMAKE_INSTALL_DATADIR to install man pages

Just FYI, there is GNUInstallDirs for this sort of things:

https://cmake.org/cmake/help/latest/module/GNUInstallDirs.html#module:GNUInstallDirs

hint: CMAKE_INSTALL_MANDIR

C_I_DATADIR is from GNUInstalldirs too, but thanks for the MANDIR hint.

Is anything missing in this pull request? I think I address concerns from the review.


Zero vector as result of matrix-vector multiplication

Executing this code...
  val W = (1 to 4).asNDArray(2,2)
  val x = (1 to 2).asNDArray(2,1) //column vector
  println("W\n" + W)
  println("x\n" + x)
  println("res\n" + W ** x)

...gives me the following result:
[main] INFO org.reflections.Reflections - Reflections took 249 ms to scan 3 urls, producing 82 keys and 375 values
W
[[1.00,2.00]
 [3.00,4.00]]
x
[ 1.00, 2.00]
res
[ 0.00, 0.00]
-- org.jblas INFO Deleting /var/folders/ys/hqpkdtqj373d8d_4xjwwd16m0000gn/T/jblas4653590412525705521/libjblas.dylib
-- org.jblas INFO Deleting /var/folders/ys/hqpkdtqj373d8d_4xjwwd16m0000gn/T/jblas4653590412525705521/libjblas_arch_flavor.dylib
-- org.jblas INFO Deleting /var/folders/ys/hqpkdtqj373d8d_4xjwwd16m0000gn/T/jblas4653590412525705521

Process finished with exit code 0

Any ideas what might be happening here?

Does not seem to be a ND4S problem. I get the same behavior in ND4J and opened an issue there.


[Feature request] Ability to use more place holders in the storage URL

Hi,
I wanted to append the clipped articles in the current daily note, but for that, I would need to be able to use the current date. It would be nice if there were a way to do that. Maybe there is and I'm just not seein it. And, of course, I would need to be able to append to an existing note, which is not currently the case

I can't access the data in your Obsidian Vault, so to me it's not possible to append to an existing note.
The only thing i can do from the browser extension is create a URI link to your Obsidian Vault. It's the link the only source of information. Like so:
obsidian://new?vault=${encodeURIComponent(         obsidianVault       )}&file=${encodeURIComponent(         finalFolderPath       )}&content=${encodeURIComponent(newContent)}


ChipCryptoTests are failing on esp32 qemu

ChipCryptoTests are failing with both automake & GN
====================================================
   Chip ge3775af: src/crypto/tests/test-suite.log
====================================================

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: qemu_crypto_tests.sh
==========================

esptool.py v2.9-dev
1+0 records in
1+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.0134144 s, 313 MB/s
6+1 records in
6+1 records out
24608 bytes (25 kB, 24 KiB) copied, 6.82e-05 s, 361 MB/s
0+1 records in
0+1 records out
3072 bytes (3.1 kB, 3.0 KiB) copied, 3.34e-05 s, 92.0 MB/s
17+1 records in
17+1 records out
1162992 bytes (1.2 MB, 1.1 MiB) copied, 0.000654602 s, 1.8 GB/s
Adding SPI flash device
==60125==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4
load:0x3fff0034,len:6908
load:0x40078000,len:13720
load:0x40080400,len:3880
entry 0x40080680
I (496) boot: ESP-IDF v4.1 2nd stage bootloader
I (513) boot: compile time 20:51:03
I (532) boot: chip revision: 0
I (548) boot.esp32: SPI Speed      : 40MHz
I (551) boot.esp32: SPI Mode       : DIO
I (553) boot.esp32: SPI Flash Size : 2MB
I (579) boot: Enabling RNG early entropy source...
I (622) boot: Partition Table:
I (624) boot: ## Label            Usage          Type ST Offset   Length
I (629) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (635) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (639) boot:  2 factory          factory app      00 00 00010000 001f0000
I (660) boot: End of partition table
I (680) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x3aa98 (240280) map
I (1188) esp_image: segment 1: paddr=0x0004aac0 vaddr=0x3ffbdb60 size=0x04190 ( 16784) load
I (1256) esp_image: segment 2: paddr=0x0004ec58 vaddr=0x40080000 size=0x00400 (  1024) load
I (1302) esp_image: segment 3: paddr=0x0004f060 vaddr=0x40080400 size=0x00fb8 (  4024) load
I (1351) esp_image: segment 4: paddr=0x00050020 vaddr=0x400d0020 size=0xc4388 (803720) map
I (2850) esp_image: segment 5: paddr=0x001143b0 vaddr=0x400813b8 size=0x17b14 ( 97044) load
I (3161) boot: Loaded app from partition at offset 0x10000
I (3165) boot: Disabling RNG early entropy source...
I (3196) cpu_start: Pro cpu up.
I (3198) cpu_start: Application information:
I (3201) cpu_start: Project name:     chip-tests
I (3204) cpu_start: App version:      e3775af
I (3206) cpu_start: Compile time:     Sep 17 2020 20:51:00
I (3211) cpu_start: ELF file SHA256:  766efcbb9d6de0a8...
I (3213) cpu_start: ESP-IDF:          v4.1
I (3216) cpu_start: Starting app cpu, entry point is 0x400811bc
I (18431) cpu_start: App cpu up.
I (20049) heap_init: Initializing. RAM available for dynamic allocation:
I (20088) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (20106) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (20116) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (20129) heap_init: At 3FFBDB5C len 00000004 (0 KiB): DRAM
I (20140) heap_init: At 3FFCEC60 len 000113A0 (68 KiB): DRAM
I (20149) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (20158) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (20167) heap_init: At 40098ECC len 00007134 (28 KiB): IRAM
I (20267) cpu_start: Pro cpu start user code
I (6710) spi_flash: detected chip: gd
I (6783) spi_flash: flash io: dio
W (6813) spi_flash: Detected size(4096k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I (6824) cpu_start: Starting scheduler on PRO CPU.
I (60) cpu_start: Starting scheduler on APP CPU.
I (7078) CHIP-tests: This is ESP32 chip with 2 CPU cores, WiFi/BT/BLE,
I (7088) CHIP-tests: silicon revision 0,
I (7088) CHIP-tests: 2MB external flash

I (8498) CHIP-tests: Starting CHIP tests!
[ CHIP Crypto PAL tests ]
[ CHIP Crypto PAL tests : Test encrypting AES-CCM-128 test vectors                   ] : PASSED
[ CHIP Crypto PAL tests : Test decrypting AES-CCM-128 test vectors                   ] : PASSED
[ CHIP Crypto PAL tests : Test encrypting AES-CCM-128 invalid plain text             ] : PASSED
[ CHIP Crypto PAL tests : Test encrypting AES-CCM-128 using nil key                  ] : PASSED
[ CHIP Crypto PAL tests : Test encrypting AES-CCM-128 using invalid IV               ] : PASSED
[ CHIP Crypto PAL tests : Test encrypting AES-CCM-128 using invalid tag              ] : PASSED
[ CHIP Crypto PAL tests : Test decrypting AES-CCM-128 invalid ct                     ] : PASSED
[ CHIP Crypto PAL tests : Test decrypting AES-CCM-128 invalid key                    ] : PASSED
[ CHIP Crypto PAL tests : Test decrypting AES-CCM-128 invalid IV                     ] : PASSED
[ CHIP Crypto PAL tests : Test encrypting AES-CCM-256 test vectors                   ] : PASSED
[ CHIP Crypto PAL tests : Test decrypting AES-CCM-256 test vectors                   ] : PASSED
[ CHIP Crypto PAL tests : Test encrypting AES-CCM-256 invalid plain text             ] : PASSED
[ CHIP Crypto PAL tests : Test encrypting AES-CCM-256 using nil key                  ] : PASSED
[ CHIP Crypto PAL tests : Test encrypting AES-CCM-256 using invalid IV               ] : PASSED
[ CHIP Crypto PAL tests : Test encrypting AES-CCM-256 using invalid tag              ] : PASSED
[ CHIP Crypto PAL tests : Test decrypting AES-CCM-256 invalid ct                     ] : PASSED
[ CHIP Crypto PAL tests : Test decrypting AES-CCM-256 invalid key                    ] : PASSED
[ CHIP Crypto PAL tests : Test decrypting AES-CCM-256 invalid IV                     ] : PASSED
mbedTLS error: CCM - Authenticated decryption failed
mbedTLS error: CCM - Authenticated decryption failed
[ CHIP Crypto PAL tests : Test decrypting AES-CCM-256 invalid vectors                ] : PASSED
E (13498) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (13498) task_wdt:  - IDLE1 (CPU 1)
E (13498) task_wdt: Tasks currently running:
E (13498) task_wdt: CPU 0: IDLE0
E (13498) task_wdt: CPU 1: tester
[ CHIP Crypto PAL tests : Test ECDSA signing and validation using SHA256             ] : PASSED
E (18498) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (18498) task_wdt:  - IDLE1 (CPU 1)
E (18498) task_wdt: Tasks currently running:
E (18498) task_wdt: CPU 0: IDLE0
E (18498) task_wdt: CPU 1: tester
mbedTLS error: ECP - The signature is not valid
[ CHIP Crypto PAL tests : Test ECDSA signature validation fail - Different msg       ] : PASSED
mbedTLS error: ECP - Bad input parameters to function : ASN1 - ASN1 tag was of an unexpected value
[ CHIP Crypto PAL tests : Test ECDSA signature validation fail - Different signature ] : PASSED
E (23498) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (23498) task_wdt:  - IDLE1 (CPU 1)
E (23498) task_wdt: Tasks currently running:
E (23498) task_wdt: CPU 0: IDLE0
E (23498) task_wdt: CPU 1: tester
[ CHIP Crypto PAL tests : Test ECDSA sign msg invalid parameters                     ] : PASSED
[ CHIP Crypto PAL tests : Test ECDSA signature validation invalid parameters         ] : PASSED
[ CHIP Crypto PAL tests : Test Hash SHA 256                                          ] : PASSED
[ CHIP Crypto PAL tests : Test Hash SHA 256 Stream                                   ] : PASSED
[ CHIP Crypto PAL tests : Test HKDF SHA 256                                          ] : PASSED
[ CHIP Crypto PAL tests : Test DRBG invalid inputs                                   ] : PASSED
[ CHIP Crypto PAL tests : Test DRBG output                                           ] : PASSED
E (28508) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (28508) task_wdt:  - IDLE1 (CPU 1)
E (28508) task_wdt: Tasks currently running:
E (28508) task_wdt: CPU 0: IDLE0
E (28508) task_wdt: CPU 1: tester
[ CHIP Crypto PAL tests : Test ECDH derive shared secret                             ] : PASSED
E (33508) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (33508) task_wdt:  - IDLE1 (CPU 1)
E (33508) task_wdt: Tasks currently running:
E (33508) task_wdt: CPU 0: IDLE0
E (33508) task_wdt: CPU 1: tester
[ CHIP Crypto PAL tests : Test adding entropy sources                                ] : PASSED
[ CHIP Crypto PAL tests : Test PBKDF2 SHA256                                         ] : PASSED
E (38508) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (38508) task_wdt:  - IDLE1 (CPU 1)
E (38508) task_wdt: Tasks currently running:
E (38508) task_wdt: CPU 0: IDLE0
E (38508) task_wdt: CPU 1: tester
[ CHIP Crypto PAL tests : Test P256 Keygen                                           ] : PASSED
***ERROR*** A stack overflow in task tester has been detected.
abort() was called at PC 0x4008da90 on core 1

ELF file SHA256: 766efcbb9d6de0a8

Backtrace: 0x4008d6e5:0x3ffd7e00 0x4008da79:0x3ffd7e20 0x4008da90:0x3ffd7e40 0x4008ef63:0x3ffd7e60 0x400908cc:0x3ffd7e80 0x40090882:0x3ffd7e80 0xffffffff:0x3ffd7e80 |<-CORRUPTED

Rebooting...
idf: *** ERROR:  Tests did not run to completion.
FAIL qemu_crypto_tests.sh (exit status: 1)

@pan-apple

This might be due to upgrading to a newer ESP IDF version + adding new features in Crypto APIs (which in turn depend on additional mbedTLS APIs). The failure seems to be related to stack overflow. We can try increasing the stack size for QEMU configuration.


Changing code sample to increase legibility

Before

After

Notice that the lines beginning with #=> don't go off the right of the content area.

Thanks @cloudbring :smile:


TypeError: list indices must be integers or slices, not str

I'm calling the Knowledge and get this Answer:
{
  "result": [
    {
      "metadata": {
        "_source": "knowledge",
        "position": 1,
        "dataset_id": "30d3abd8-eeac-49c4-95ab-5cb0e07bd9e9",
        "dataset_name": "Knowledge Base",
        "document_id": "a1b04523-e802-4e7c-b448-0a8864e8edcf",
        "document_name": "1234-5678-9123",
        "document_data_source_type": "upload_file",
        "segment_id": "c57cfeec-b5af-4d9a-819a-d6588e77b7a7",
        "retriever_from": "workflow",
        "score": 0.95606345,
        "segment_hit_count": 5,
        "segment_word_count": 2144,
        "segment_position": 10,
        "segment_index_node_hash": "e1334738c6caf32fdd0ebcceb4f0cce3cfd028ce21f8219b0328b8dd8f980060"
      },
      "title": "1234-5678-9123",
      "content": "XXXXXXX"
    }
  ]
}

In the next Step  I'm using the Code Component with this Code:
def main(data: str, user: str) -> str:
    first_result = data["result"][0]
    if first_result["metadata"]["position"] == 1 and first_result["metadata"]["document_name"] == user:
        return {"result": "OK"}
    else:
        return {"result": "Nope"}

Testing the Code inside the Code Component with user emil works fine ("result":"Nope" )and no Error is thrown.
Inside the Flow i'm always getting  the Error:
Run failed: Traceback (most recent call last):
File "/var/sandbox/sandbox-python/tmp/274210ea_af06_444c_93c9_866199b2fc72.py", line 48, in
File "", line 20, in
File "", line 4, in main
TypeError: list indices must be integers or slices, not str
error: exit status 255

I can't figure out why this happens.

Hi, it was a Layer 8 problem. I didn't get that the answer from th knowledge isn't a dictionary but a list.
Correct Code:
import json
def main(data_list: list, str, user: str) -> str:
data_dict = json.loads(data_list)
first_result = data_dict["result"][0]["metadata"]["document_name"]
if str(first_result) == user:
return {"result": "OK"}
else:
return {"result": "Nope"}


cmd/compile: DWARF information for local variables missing

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
go version devel +dbe54d2 Thu Mar 10 07:01:34 2016 +0000 linux/amd64

What operating system and processor architecture are you using (go env)?

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/a/n/go/"
GORACE=""
GOROOT="/usr/local/go-tip"
GOTOOLDIR="/usr/local/go-tip/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build814262766=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"

What did you do?
Compiled this program with go build -gcflags='-N -l' then checked the output of objdump --dwarf ./testvariables.

What did you expect to see?

I expected main.foobar to have all its local variables like it did on <=1.6

What did you see instead?

Only few local variables survive:
 <1><7b>: Abbrev Number: 2 (DW_TAG_subprogram)
    <7c>   DW_AT_name        : main.foobar
    <88>   DW_AT_low_pc      : 0x4010e0
    <90>   DW_AT_high_pc     : 0x4025c0
    <98>   DW_AT_external    : 1
 <2><99>: Abbrev Number: 4 (DW_TAG_variable)
    <9a>   DW_AT_name        : i32
    <9e>   DW_AT_location    : 5 byte block: 9c 11 c0 77 22     (DW_OP_call_frame_cfa; DW_OP_consts: -1088; DW_OP_plus)
    <a4>   DW_AT_type        : <0x2910a>
 <2><ac>: Abbrev Number: 4 (DW_TAG_variable)
    <ad>   DW_AT_name        : a4
    <b0>   DW_AT_location    : 5 byte block: 9c 11 b0 78 22     (DW_OP_call_frame_cfa; DW_OP_consts: -976; DW_OP_plus)
    <b6>   DW_AT_type        : <0x29257>
 <2><be>: Abbrev Number: 4 (DW_TAG_variable)
    <bf>   DW_AT_name        : a11
    <c3>   DW_AT_location    : 5 byte block: 9c 11 b0 7b 22     (DW_OP_call_frame_cfa; DW_OP_consts: -592; DW_OP_plus)
    <c9>   DW_AT_type        : <0x291eb>
 <2><d1>: Abbrev Number: 5 (DW_TAG_formal_parameter)
    <d2>   DW_AT_name        : baz
    <d6>   DW_AT_location    : 1 byte block: 9c         (DW_OP_call_frame_cfa)
    <d8>   DW_AT_type        : <0x22781>
 <2><e0>: Abbrev Number: 5 (DW_TAG_formal_parameter)
    <e1>   DW_AT_name        : bar
    <e5>   DW_AT_location    : 4 byte block: 9c 11 10 22        (DW_OP_call_frame_cfa; DW_OP_consts: 16; DW_OP_plus)
    <ea>   DW_AT_type        : <0x22aeb>
 <2><f2>: Abbrev Number: 0
 <1><f3>: Abbrev Number: 2 (DW_TAG_subprogram)

So it looks like you just got lucky for 1.6 (and earlier).  The old compiler spills, e.g., a2, then reloads it and stores it to a temporary, and then calls convT2E on that temporary.  If it doesn't need to spill for whatever reason, you won't get source names in the dwarf info.
Here's an example where spills don't happen, and thus the compiler loses names for all Go versions I tested (1.5.1, 1.6, tip):
func main() {
	a := 6
	b := 7
	fmt.Printf("%d %d\n", a, b)
}

Fixing this in SSA will be difficult, as the frontend has already introduced the nameless temporary for the convT2E call.
Still worth fixing if we can, but I don't see any easy fixes.

In general you should not depend on most of these variables surviving to appear in the DWARF info

My concern isn't the test failure (I presume I can fix it by just passing the values as arguments). Rather I was worried about user experience: isn't this a bit too aggressive for -N?

Thanks for fixing this!