Create an HTML file and style it using Inline, Internal and External CSS

I want to work on this issue

i want to work on tihs isuue

i want to work on this issue could you please assign me this issue


Number of how protein-coding genes still too high

Should be 19158
(number of distinct entities in goa_human and goa_human_isoform)

This seems fine:
https://github.com/geneontology/amigo/blob/master/conf/examples/amigo.yaml.production#L137-L139
is this definitely what is used on production?

This also looks fine http://amigo.geneontology.org/amigo/load_details
mysterious...

@kltm found it
coming from
gene_association.goa_uniprot_noiea.gz

in theory this should have homo sapiens removed...

Current count is 19624, so apparently fixed along the way somewhere...


mongodb-chatbot-evaluation ready to use?

Hi,
is mongodb-chatbot-evaluation ready to use?
I installed you and tried an "out-of-the-box"
tsc --module commonjs --target es2017 --outDir build src/eval/eval.config.ts

but eval.config.ts can not import most functions from 'mongodb-chatbot-evaluation'
Module '"mongodb-chatbot-evaluation"' has no exported member 'makeGenerateConversationData'.ts(2305)

it should be ready to use. you can find it at mongodb-chatbot-evaluation on npm. we are actively using and running it. i don't see any issues on the package. which version are you using? 0.1.0 is latest and should work.
we also just published more thorough docs if you want to look at those https://mongodb.github.io/chatbot/evaluation/

Hi @eric-gardyn , have you had any luck using the evaluation package? Let us know if we can help or if this issue can be closed. Thank you!


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit dc6f40d:
:clock10: Full build: the average full build time is 5 min(s) 56 sec(s), this is based on the last 685 build(s) for this repository.

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

File
Status
Preview URL
Details
Dependent Files

docfx.json
:white_check_mark:Succeeded

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


CSP Violation

I am using version 1.3.0 of this lib and the sample page settings are pointed at my agencies authorize url and it is functioning properly.
If I update the lib to 1.4.x and build/start the server I am displayed a CSP violation when clicking sign in.
It appears this commit introduced the issue? Does the sample need to be updated to align with the CSP policy?
If I am not pointing at the local server, but my agencies installation, why does the client version make a difference in the CSP violation?

It appears this commit introduced the issue? Does the sample need to be updated to align with the CSP policy?

That commit is in the sample/fake token server piece only used for doing smoke screen testing of this library. I don't see how that should affect anything in the library. It was added, in fact, to prove that the library works properly with server CSP restrictions.


JavaScript variables are not being registered outside of cells

Describe the bug
Apologies if this is a misunderstanding of kernel limitations.
I can import a C# variable into JavaScript without issues. However, if I declare a JS variable in a JS cell using either let or const, that variable does not seem to be registered in the variables section, is not available in the next cell (even if it's a JS cell), does not share correctly to C# or other kernels, and perhaps most interestingly, doesn't log out at the end of the same cell it was defined in if it was the closing value as in:
let jsVar = 42;
jsVar; // jsVar is not displayed after the cell

JavaScript otherwise appears to function just fine, but variable persistence and sharing just isn't working for me.
See https://github.com/IntegerMan/PolyglotNotebookTalk/blob/main/cs_js.dib for my sample notebook.
Please complete the following:
Which version of .NET Interactive are you using? (In a notebook, run the #!about magic command. ):

OS

[x] Windows 11
[ ] Windows 10
[ ] macOS
[ ] Linux (Please specify distro)
[ ] iOS
[ ] Android

Browser

[ ] Chrome
[ ] Edge
[ ] Firefox
[ ] Safari

Frontend

[ ] Jupyter Notebook
[ ] Jupyter Lab
[ ] nteract
[x] Visual Studio Code
[ ] Visual Studio Code Insiders
[ ] Visual Studio
[ ] Other (please specify)

Screenshots

This is by design. The JavaScript kernel executes your code submission within a function, and so variables declared in that function aren't visible outside unless you use this syntax:
x = 123;

By not using the let, const, or var keywords with your variable declaration, you're enabling JavaScript variable hoisting to make the variable visible to other cells (i.e. within other functions in the top-level scope).
As for return values from JavaScript cells, the trailing expression syntax isn't supported in JavaScript. So while in C# Script, this is equivalent to a return statement:
123

in JavaScript you need to write this:
return 123;

Thank you so much for the reply @jonsequitur. I'll play around with that tonight!

Looking forward to your thoughts. I'll update the docs with these details because it's unintuitive.

I'll keep the issue open for now and close it once the docs are updated.

So I've been playing with this and if I do:
let jsVar = 42;
return jsVar;

I do see the value 42 after the cell, which is good, but no variable sharing occurs either. Is variable sharing just not possible between different JS cells in Polyglot?

let / const  / var are scoped to the evaluation. to make them globally visible do
jsVar = 42;
return jsVar;


use SIGTERM on timeout so custom plugins can produce a backtrace/clean up

atm it uses CommandContext which always sig- kills, making it so we don't see a backtrace of where things went wrong and cleanup/trap blocks are not run
ideally logic should be sigterm ... wait 1-xs sigkill
alternatively call out that this is a sigkill and make the example timeout 10 original-command  (which does not work since it only accepts a path, so need at least a workaround for that)
So only solution is: path -> wrapper script -> timeout 123 actual script which is pretty ugly :(

I'd love to see command instead of path so I can just put in whatever I want
timeoutGracePeriod or termTimeout so 2 timeouts can be configured ... maybe timeoutSignal

/cc @eatwithforks

/remove-lifecycle stale


CVE-2021-3803 Upgrade nth-check to 2.0.1 from 2.0.0

Can you please consider upgrade nth-check from 2.0.0 to 2.0.1 because of this vulnerability https://github.com/advisories/GHSA-rp65-9cf3-cjxr
I know it is painful to address all these not relevant to mjml vulnerabilities. So I created the PR to make your life easier
It would be great if you can merge this to master & do a version release
Thank you

👍  I don't know when this will be released as the vulnerability is really limited


Port generated lib files

Ports https://github.com/Microsoft/TSJS-lib-generator/pull/321

@mhegazy Do you have a new RWC capture?

will get one in as well.


Update LAB_10 SQL connection string password

In the ADO.NET connection string, we need to use the "Student" password used in Ex 1, not "Pa55w.rd1234".
Module: 03
Lab: 10
NOTE: The connection string password does not matter since the application replaces it, but it may be confusing to instruct the student to add an incorrect one.
Changes proposed in this pull request:

Fixed Bold formatting
Fixed incorrect connection string password.

Or, we could just leave the connection string as is (leave "{your_password}" in the connection string), as the application will replace it with the correct password.


Scroll back to the top after opening a directory in FileDialog

This also changes the behavior in EditorFileDialog.
This closes #26041.

Thanks!


[BUG] useNavigation's show prop does no interaction.

Describe the bug
useNavigation's show prop does no interaction.
Expected behavior
When called show('resource',id) it should go to show page
"@pankod/refine-antd": "^3.41.0",
"@pankod/refine-core": "^3.69.0",

onMutationSuccess: (data) => {
      show('reports', data.id);
    }

Hey @aliemir
Thank you for your reply.
Yes, it worked when I set it to redirect:false. But
const { queryResult } = useShow({ resource: 'getReport' });

still not working.

Only show prop did navigation. Data is still not coming.

Nice to hear that! Since we have this issue explained in another one, can we close this one and continue on that on its own issue? 😅

Yes. Thank you! 👍


Script for comparison of CoCa zero-shot to open_clip implementation

Stack from ghstack (oldest at bottom):

-> #507
#506

Differential Revision: D51332626

Some modifications to CoCa class and an evaluation script to validate that our implementation matches the ImageNet zero-shot performance of the one in open_clip repo on their pretrained ViT-L/14.
Test:
python eval.py --pretrained /home/ebs/checkpoints/open_clip_coca_vit_l_14_laion2B-s13B-b90k-remapped.pt
...
TorchMultimodal zero-shot accuracy: {'imagenet-zeroshot-test-top1': 0.75628, 'imagenet-zeroshot-test-top5': 0.94284}
...
    accuracy                          0.757     50000
   macro avg      0.768     0.757     0.751     50000
weighted avg      0.768     0.757     0.751     50000

@ebsmothers has imported this pull request.  If you are a Meta employee, you can view this diff on Phabricator.


Add filestat_get for stdout, stdin and stderr

This makes fstat work for stdout, stdin and stderr as expected.
This seemed like the only reasonable functions to implement from the
filestat_* set, for stdout, stdin and stderr.
Fixes #2515

Review maybe @sunfishcode ?


GPGS xml version fix

GPGS xml version fix

Can't believe I forgot this again 🤦♂ thx!

@jizc can you please open issues for people so people can contribute more efficiently and move this library forward?


Allow NifiCluster Pod to be suspended when process crashes, to allow for debugging

Is your feature request related to a problem?
Configuration problems during NiFi startup can result in the NiFi process crashing, for example if no nifi.sensitive.props.key is defined for Cluster nodes.
The Pod is immediately terminated and replaced with a new Pod by NiFiKop, which will quickly fail again. It is very difficult to retrieve the logs/any information as to why the Pod keep crashing.
Describe the solution you'd like to see
A way to suspend the Pod for a set period before it is deleted by NiFiKop, e.g. a setting in the operator that waits for a set time before deleting and re-creating the Pod, to allow for log retrieval
Describe alternatives you've considered
No response
Additional context
No response

Hi @ChrisSamo632, you can use sidecars to use to tails the logs with a shared volume with the nifi container. So if NiFi crashes, you still have access to the logs. And you can add as much sidecar as you want with each one of the tailing a specific log file.  Personnaly, that's what we do.

Something like:
apiVersion: nifi.konpyutaika.com/v1
kind: NifiCluster
metadata:
  name: nifikop
spec:
  ...
  nodeConfigGroups:
    default_group:
      ...
      storageConfigs:
        - mountPath: /opt/nifi/nifi-current/logs
          name: logs
          pvcSpec:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 50Gi
            storageClassName: ssd-wait
  sidecarConfigs:
    - args:
        - tail
        - -n+1
        - -F
        - /var/log/nifi-app.log
      image: busybox:1.36
      name: app-log
      resources:
        limits:
          cpu: 50m
          memory: 50Mi
        requests:
          cpu: 50m
          memory: 50Mi
      volumeMounts:
        - mountPath: /var/log
          name: logs

Nice idea, I guess a problem is that I've redirected logging to STDOUT/STDERR to avoid having log files build up within the Pod/volume, so much of the logging is only available while the Pod's main container is running - these logs are intended to be collected by a central logging process within the cluster, although I've not enabled that yet, which probabl isn't helping me here, but I'm unsure on whether the errors would then be collected in the short time the Pod's online before crashing and being replaced


Update: Adding Coverage summary to Travis build

What is the purpose of this pull request? (Check any that's applicable)

[x] Feature
[ ] Bug fix
[ ] Dependency updates
[ ] Documentation updates
[ ] Build related changes
[ ] Changes an existing functionality
[ ] Other, please explain:

Does this introduce a breaking change?

[ ] Yes
[x] No

What changes did you make? (Give an overview)
Made changes to add code coverage summary in travis build.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add void to LineData's NON_PASCAL_TYPES

I guess title is self-explanatory, I think a PR is overkill
First thing I tried was creating a void using the func|fnc Macro which will just turn into the default "type"
Extending LineData;gd:8->NON_PASCAL_TYPES by void would fix this
const NON_PASCAL_TYPES: Array[String] = ["void", "bool", "float", "int"]
At first glance I see no reason why this would be left out

Definite oversight. Pushing a fix!

Fixed in 082a65527d4ec2ae2f101868527c6cf67e403031

Thanks a bunch!

Wow, congrats on that amazing response time!
Thanks to you too 🎉


Replace color phases with color ramp for Particles2D. (need some review/guidance)

I've tried to replace color phases for particles 2d with more convenient to use color ramp with dedicated editor. I'm completely not sure that I did everything correctly, especially from multithreading point of view, but at least it works. So it would be nice to hear some advices or ways of improvement of this patch.
To do this task I made a copy of existing gradient editor from shader graph editor and do some modifications to it (I decided to try replace original one with modified version later).
So what was done:
-new resource for color ramp  + editor
-backward compatibility. Old coloring for particles 2d will be converted to color ramp (or to new color property if only one color phase was used before).
-undo/redo support.

this looks good overall, but I would add a function to the ColorRamp
resource, something like:
Color ColorRamp::get_color_at_offset(offset) const
so Particles2D can use this more efficiently by just calling a function
On Sun, May 24, 2015 at 4:01 PM, Biliogadafr<EMAIL_ADDRESS>wrote:

I've tried to replace color phases for particles 2d with more convenient
to use color ramp with dedicated editor. I'm completely not sure that I did
everything correctly, especially from multithreading point of view, but at
least it works. So it would be nice to hear some advices or ways of
improvement of this patch.
To do this task I made a copy of existing gradient editor from shader
graph editor and do some modifications to it (I decided to try replace
original one with modified version later).
So what was done:
-new resource for color ramp + editor
-backward compatibility. Old coloring for particles 2d will be converted
to color ramp (or to new color property if only one color phase was used
before).
-undo/redo support.
[image: colorramp]
https://cloud.githubusercontent.com/assets/10543859/7789160/db0fa4f0-025f-11e5-9d3d-472ba1bc2898.png
[image: particlecolorramp]
https://cloud.githubusercontent.com/assets/10543859/7789161/e08fb51e-025f-11e5-92f2-c8c9ec00f376.gif
You can view, comment on, or merge this pull request online at:
https://github.com/okamstudio/godot/pull/1973
Commit Summary

Replace color phases with color ramp for Particles2D.

File Changes

M scene/2d/particles_2d.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-0 (168)
M scene/2d/particles_2d.h
https://github.com/okamstudio/godot/pull/1973/files#diff-1 (15)
A scene/gui/color_ramp_edit.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-2 (368)
A scene/gui/color_ramp_edit.h
https://github.com/okamstudio/godot/pull/1973/files#diff-3 (52)
M scene/register_scene_types.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-4 (2)
A scene/resources/color_ramp.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-5 (111)
A scene/resources/color_ramp.h
https://github.com/okamstudio/godot/pull/1973/files#diff-6 (52)
A scene/resources/default_theme/checker_bg.png
https://github.com/okamstudio/godot/pull/1973/files#diff-7 (0)
M scene/resources/default_theme/theme_data.h
https://github.com/okamstudio/godot/pull/1973/files#diff-8 (5)
M tools/editor/editor_node.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-9 (2)
A tools/editor/icons/icon_color_ramp.png
https://github.com/okamstudio/godot/pull/1973/files#diff-10 (0)
A tools/editor/plugins/color_ramp_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-11 (83)
A tools/editor/plugins/color_ramp_editor_plugin.h
https://github.com/okamstudio/godot/pull/1973/files#diff-12 (37)

Patch Links:

https://github.com/okamstudio/godot/pull/1973.patch
https://github.com/okamstudio/godot/pull/1973.diff

—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/pull/1973.

If possible, for performance also, you could try using a VMap , which would
likely make a get_color_at_offset() function faster if you have a lot of
color nodes
On Sun, May 24, 2015 at 4:24 PM, Juan Linietsky<EMAIL_ADDRESS>wrote:

this looks good overall, but I would add a function to the ColorRamp
resource, something like:
Color ColorRamp::get_color_at_offset(offset) const
so Particles2D can use this more efficiently by just calling a function
On Sun, May 24, 2015 at 4:01 PM, Biliogadafr<EMAIL_ADDRESS>wrote:

I've tried to replace color phases for particles 2d with more convenient
to use color ramp with dedicated editor. I'm completely not sure that I did
everything correctly, especially from multithreading point of view, but at
least it works. So it would be nice to hear some advices or ways of
improvement of this patch.
To do this task I made a copy of existing gradient editor from shader
graph editor and do some modifications to it (I decided to try replace
original one with modified version later).
So what was done:
-new resource for color ramp + editor
-backward compatibility. Old coloring for particles 2d will be converted
to color ramp (or to new color property if only one color phase was used
before).
-undo/redo support.
[image: colorramp]
https://cloud.githubusercontent.com/assets/10543859/7789160/db0fa4f0-025f-11e5-9d3d-472ba1bc2898.png
[image: particlecolorramp]
https://cloud.githubusercontent.com/assets/10543859/7789161/e08fb51e-025f-11e5-92f2-c8c9ec00f376.gif
You can view, comment on, or merge this pull request online at:
https://github.com/okamstudio/godot/pull/1973
Commit Summary

Replace color phases with color ramp for Particles2D.

File Changes

M scene/2d/particles_2d.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-0 (168)
M scene/2d/particles_2d.h
https://github.com/okamstudio/godot/pull/1973/files#diff-1 (15)
A scene/gui/color_ramp_edit.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-2 (368)
A scene/gui/color_ramp_edit.h
https://github.com/okamstudio/godot/pull/1973/files#diff-3 (52)
M scene/register_scene_types.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-4 (2)
A scene/resources/color_ramp.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-5 (111)
A scene/resources/color_ramp.h
https://github.com/okamstudio/godot/pull/1973/files#diff-6 (52)
A scene/resources/default_theme/checker_bg.png
https://github.com/okamstudio/godot/pull/1973/files#diff-7 (0)
M scene/resources/default_theme/theme_data.h
https://github.com/okamstudio/godot/pull/1973/files#diff-8 (5)
M tools/editor/editor_node.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-9 (2)
A tools/editor/icons/icon_color_ramp.png
https://github.com/okamstudio/godot/pull/1973/files#diff-10 (0)
A tools/editor/plugins/color_ramp_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1973/files#diff-11 (83)
A tools/editor/plugins/color_ramp_editor_plugin.h
https://github.com/okamstudio/godot/pull/1973/files#diff-12 (37)

Patch Links:

https://github.com/okamstudio/godot/pull/1973.patch
https://github.com/okamstudio/godot/pull/1973.diff

—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/pull/1973.

Hm.. doesn't seems that it runs faster after this changes (actually the same fps(44) with ~10 particle systems with 1000 particles each and color ramp with 35 points... without color ramp + 3-4 fps). Need to check a bit more. Also not sure that it was a good idea to check and correct sorting in get_color_at_offset(), method. On the other side I'm not sure that it is good idea to assume that editor (or user) will provide correct order..

I woldn't count on user providing correct order. Did you try inlining the
function? (get_color_at_offset())
On Wed, May 27, 2015 at 5:43 AM, Biliogadafr<EMAIL_ADDRESS>wrote:

Hm.. doesn't seems that it runs faster after this changes (actually the
same fps(44) with ~10 particle systems with 1000 particles each and color
ramp with 35 points... without color ramp + 3-4 fps). Need to check a bit
more. Also not sure that it was a good idea to check and correct sorting in
get_color_at_offset(), method. On the other side I'm not sure that it is
good idea to assume that editor (or user) will provide correct order..
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/pull/1973#issuecomment-105825777.

I still don't think it will make much a difference, but it's just something
that in the worst case it should be a bit faster
On Wed, May 27, 2015 at 9:11 AM, Juan Linietsky<EMAIL_ADDRESS>wrote:

I woldn't count on user providing correct order. Did you try inlining the
function? (get_color_at_offset())
On Wed, May 27, 2015 at 5:43 AM, Biliogadafr<EMAIL_ADDRESS>wrote:

Hm.. doesn't seems that it runs faster after this changes (actually the
same fps(44) with ~10 particle systems with 1000 particles each and color
ramp with 35 points... without color ramp + 3-4 fps). Need to check a bit
more. Also not sure that it was a good idea to check and correct sorting in
get_color_at_offset(), method. On the other side I'm not sure that it is
good idea to assume that editor (or user) will provide correct order..
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/pull/1973#issuecomment-105825777.

Changed it to be inlined. Indeed works just a bit faster on very large amount of points and particles.

Yay! I was wainting for this for so long! Great job! =D

I would also love to be able to send this easly to shader program.

Great addition!

I've made some small new features and fixed some bug here: https://github.com/okamstudio/godot/pull/2068

Can anyone make this available for the 3d particles as well?

that is a little more complicated, the 3D particles need to move outside
the visual server first (they are old, deprecated code)
On Wed, Jun 17, 2015 at 10:20 AM, Thomas Morley<EMAIL_ADDRESS>wrote:

Can anyone make this available for the 3d particles as well?
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/pull/1973#issuecomment-112796611.

Well, that's slightly disappointing. Is it true that all work on the 3d engine is on hold for now?

It's kind of on hold because there is not really much more that can be done
with GLES2, so still waiting for Vulkan
On Wed, Jun 17, 2015 at 1:06 PM, Thomas Morley<EMAIL_ADDRESS>wrote:

Well, that's slightly disappointing. Is it true that all work on the 3d
engine is on hold for now?
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/pull/1973#issuecomment-112861638.


Fixed Issue #3738

@ewojjowe @alimemonzx Any way we can get this merged without the commit? Or do we have to open another PR for getting this fixed?


Feature/advanced view control (#1)

We really like this plugin: it gives a quick overview of the most important jobs, and displays all the information we need. As we are managing a couple applications, and going more and more towards CI/CD pipelining and continuous delivery, we missed so far a solution for clustering jobs (and displaying a title), and we would have liked to have a better control regarding the order of the displayed jobs, so we could actually reflect pipelines in this view.
As a picture says more then thousand words :-) see: https://raw.githubusercontent.com/cgiorgetta/jenkins-build-monitor-plugin/master/docs/5_Job_clustering_and_advanced_ordering.png
With two additional configuration parameters, and little additional code, we now have a solution which works for us, and it is just extending the current solution (no breaking changes).
As this might be nice for others as well, here a PR.

Revoke as PR is open for too long...


Publish to npm?

It would be great if this could be published to npm 😄 .

Just published 0.0.1, and updated README with install instructions 👌


Bound tasks

In my latest work on the scheduler, I have introduced a 'bound task' which is done to enable me to launch tasks that are never stolen from one thread to another. This kind of thing is needed for first touch of numa domains (for example) and another use case is things like
#pragma omp parallel for schedule(static,1) num_threads(8)

where threads are mapped statically to cores. This can now be done with my scheduler.
The cost is that each core now maintains a new queue of bound tasks, in addition to high/normal/low priority tasks.
However, this also introduces a slight problem. I cheated, by adding a new priority of thread_priority_bound to complement high/low priority tasks. But this is not optimal and a better way of doing it is to have the thread_schedule_hint structure carry a flag that indicates thread or numa domain and a bound tag in it.
This in itself is not a problem and can be easily added, however it makes sense when doing this to also move the thread priority to the schedule_hint structure at the same time, and then expose the structure via executor params so that we can create an executor for cores/numa domain, high/low priority and bound tasks using a single type. We could/should also put stacksize into the same struct so that we have a thread_schedule_param object with flags for all of them. an enum would work for most.
Problem. I currently treat bound tasks as high priority, but it is conceivable that we might want a bound task of a different priority, this would require more and more queues as we introduce more and more options. Not a great solution. Since we use lifo or fifo and don't have a (lockfree) priority based queue, it will not be simple to add more and more options.
Does anyone have other suggestions for changes along these lines that can make life easier?

Doesn't libCDS have a lock-free priority queue?

Integrating libCDS is a big job in its own right - we don't really have the manpower to consider that at the time being.

closing this because #4249 adds this support, but the topic should be revisited as we move to a better way of combining scheduler params, executor params, launch policies and task information


[Phase 3] Improve Triton unit test pass rate

This task captures the effort to improve Triton unit test pass rate to 95% (from 90% in Phase 2) on gfx90a.

test_core operators:

AddPtrOp
ArithConstantSplatOp
BroadcastOp
ConvertLayoutOp
ElementWiseOp
FuncOp
GetProgramIdOp
LoadOp
MakeRangeOp
ReduceOp
ReturnOp
SplatOp
StoreOp


fixes #428 replace compilation.hooks.optimizeChunkAssets.tap with tapAsync

Codecov Report

Merging #447 (d121373) into master (17f9f14) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #447   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          266       266
  Branches        26        26
=========================================
  Hits           266       266

Impacted Files
Coverage Δ

src/WebpackLicensePlugin.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

@zoltan-mihalyi thanks!


Broken images in TechDocs

As I was browsing around the demo site I could see that all images are broken within the documentation. See attached picture.

@backstage/maintainers
The images are broken because they have absolute source to the host backstage.io which is being blocked by the Content Security Policy. I think this should be updated to include img-src https://backstage.io (or img-src https://*). What do you say?
Console errors

Default CSP values in Backstage
https://github.com/backstage/backstage/blob/a3b2c5a68b851a4f2ba471f865c8082bfa36cba3/packages/backend-common/src/service/lib/ServiceBuilderImpl.ts#L53

Yay more CSP issues 🙌   img-src https://backstage.io seems reasonable for now unless theres any other places? In which case it makes sense to just use * up to you folks to decide :)

Images loading now, wohoo
https://demo.backstage.io/docs/default/Component/backstage/features/software-catalog/

Thank you both! 🎉


⚠ Bofrost.at has degraded performance

In 8a3f6a2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 883 ms

Resolved: Bofrost.at performance has improved in 8a47db6 after 14 minutes.


LateInitializationError: Field 'idToken' has not been initialized.

LateInitializationError: Field 'idToken' has not been initialized.
how can fix this  ?

The LateInitializationError: Field 'idToken' has not been initialized message shouldn’t be an issue in this code, as idToken is declared as a nullable (String?). By default, a nullable variable is null if not initialized, so there’s no need for an initial value.
If the error persists, it’s likely that there’s confusion from Dart’s analyzer or some other part of the codebase might be unintentionally accessing idToken in a way that expects a non-nullable type. However, the code here is correctly handling idToken as nullable and shouldn’t raise an initialization error.
Note: Make sure you use the latest version of this package

The LateInitializationError: Field 'idToken' has not been initialized message shouldn’t be an issue in this code, as idToken is declared as a nullable (String?). By default, a nullable variable is null if not initialized, so there’s no need for an initial value.
If the error persists, it’s likely that there’s confusion from Dart’s analyzer or some other part of the codebase might be unintentionally accessing idToken in a way that expects a non-nullable type. However, the code here is correctly handling idToken as nullable and shouldn’t raise an initialization error.
Note: Make sure you use the latest version of this package


Add support for Tomcat 10

With Tomcat 10, the expression Engine (within el-api.jar) moved to the jakarta.el package, thus the payload for tomcat does no longer work on Tomcat 10.
We need to create a new Controller that handles this cases. Actual change would be minimal.

Basically, simple change "javax.el.ELProcessor to "jakarta.ex.ELProcessor".
 //prepare payload that exploits unsafe reflection in org.apache.naming.factory.BeanFactory
ResourceRef ref = new ResourceRef("javax.el.ELProcessor", null, "", "",
             true, "org.apache.naming.factory.BeanFactory", null);
ref.add(new StringRefAddr("forceString", "x=eval"));
ref.add(new StringRefAddr("x", payload));

Hello! I would like to contribute to this issue. Could you please assign it to me? :)

Hi! It's already done, see d46724f677330653463b748ee7e284a94be58c0e.


Configurable query

Enhancement to allow configurable based queries.
Summary of changes:

datejs dependancy needed to be added to allow for human readable time based queries.
Code added to read and serialise query from config into url encoded parameters.
README updated with examples.

Hey, im not sure how to resolve the travis build issue. As for the security risk, is that a bad thing seen as its used only as a mirror module?

i will take care about travis, as it is not set up correctly yet.
will look into this pr(vulnerability and functionality) tomorrow

ok i have linted everything and removed datejs and used momentjs instead, what do you think about discover date part?

Looks nice, and removes the extra dependancy. 👍


Forcing the vagrant cloud server url to https://vagrantcloud.com

Instead of atlas.hashicorp.com
Without this patch, you'll get this error:
cyprien.diot@techCyp:~/salt-vagrant-demo$ vagrant up
Bringing machine 'master' up with 'virtualbox' provider...
Bringing machine 'minion1' up with 'virtualbox' provider...
Bringing machine 'minion2' up with 'virtualbox' provider...
==> master: Box 'bento/ubuntu-16.04' could not be found. Attempting to find and install...
    master: Box Provider: virtualbox
    master: Box Version: >= 0
The box 'bento/ubuntu-16.04' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/bento/ubuntu-16.04"]
Error: The requested URL returned error: 404 Not Found

What the output of vagrant --version on your machine?
I just tested and it downloaded the box from https://vagrantcloud.com just fine.

@UtahDave You're right, looks like it works with Vagrant >= 2.0 but not with Vagrant < 2.0.0.
Where I got this issue:
cyprien.diot@techCyp:~/salt-vagrant-demo$ vagrant --version
Vagrant 1.9.2

But it works with Vagrant 2.0.4:
[root@021071bf715f work]# vagrant box add bento/ubuntu-16.04
==> box: Loading metadata for box 'bento/ubuntu-16.04'
    box: URL: https://vagrantcloud.com/bento/ubuntu-16.04
^[[1;7BThis box can work with multiple providers! The providers that it
can work with are listed below. Please review the list and choose
the provider you will be working with.

1) hyperv
2) parallels
3) virtualbox
4) vmware_desktop

Enter your choice: ==> box: Waiting for cleanup before exiting...
==> box: Exiting immediately, without cleanup!
[root@021071bf715f work]# vagrant --version
Vagrant 2.0.4

On debian based distributions (like Ubuntu 17), Vagrant 2.0.4 is not yet available, so I still think this Pull Request is useful.
Thank you;

This works without any problems on Mac OS X 10.3.5, Vagrant 2.1.2, VirtualBox 5.2.16r123759.
Segue: I didn't know about Vagrant::DEFAULT_SERVER_URL.replace('https://vagrantcloud.com'), not needed, but cool to know you wanted to use Artifactory or other custom repository.

@wixyvir
I'm getting this error:
[salt-vagrant-demo (wixyvir-fix_vagrant_server_url)]$ vagrant up
Vagrant failed to initialize at a very early stage:

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /home/me/repos/salt-vagrant-demo/Vagrantfile
Line number: 5
Message: RuntimeError: can't modify frozen String

My version of vagrant:
$ vagrant --version
Vagrant 2.1.5

Yes this is not compatible with Vagrant 2 anymore and all supported OS are now packaging Vagrant 2


Feature Request: Traefik Example with more valid options

Hi,
now i did your Traefik workable. With my Container on the Host it work fine.
May you add Options to enhance the Container?
Maybe to add Services on other Hosts or Cluster Traefik Container on more Docker Hosts? Or is a Kubernetes Traefik the better option for this scenario?
In my Case i have 5 Container Server, 3 with exposed Services. In your Video to Nginx Proxy Manager you show me, i have to change the Reverse Proxy. Iam a beginner with traefik and have no idea, which is the best Way.
Thanks

Decided to keep compose files as simple as possible; hence, I'm not adding additional examples to the boilerplate templates directly. Check out my other repos, like the cheat-sheets or video tutorials, for more in-depth explanation, and examples.


SSR broken when served from a server build

Version: 1.0.0 (beta8)
Environment: React
Type: Bug

Description
Probably due to the singleton nature of the StyleContainer, SSR doesn't work if the routes come from a webpack build. Related to #267
Steps to reproduce

git clone https://github.com/mattkrick/react-look
cd react-look
npm run build:server
npm run demo:universal
Observe the FOUC

Expected Behavior
no FOUC
Actual Behavior
a big FOUC
CC @jordanh

Hi @rofrischmann!
Last night @mattkrick & I were investigating #267 on our Action codebase. In our universal app, we require() the client build into the server. This causes there to be two StyleContainer singletons, making the current react-look SSR interface challenging to use. (Matt's demonstrates this rather clearly by modifying the react-look example app in this changeset)
@mattkrick and I believe in "don't hate, iterate." We ❤  react-look and were thinking about how we might modify the API. I'd like to run something by you and gather your reaction. If you like it, we'd be happy to try an implementation:

Add a second context variable to <LookRoot> alongside _lookConfig called _lookRoot
Add the parameter styles to the look() component decorator that accepts objects returned by StyleSheet.create({...}).
Modify the look() decorator so these styles then are added to <LookRoot>'s specific StyleContainer instance by pulling it from the react context

Caveats:

This won't fix StyleSheet.addCss() or StyleSheet.addFont() in spots where a second StyleContainer is at play, but this could be worked around by locating these calls elsewhere in the application

This doesn't move you closer to stripping your dependency on React 😉

@mattkrick @jordanh I really love how you're tackling the issue. That's what I call true open source.
First of all I want to point out that I am not trying to get rid of React. react-look is a React specific library and will always be. Furthermore I am right now creating some kind of low-level API to handle styles with JavaScript as well as rendering to DOM, ...
I will want to bring this to Look as well to solve some issues as well as API design problems. I had some similar ideas to what you have proposed above. I would love to see those changes in production! This will help at least until my new renderer is up and ready if not at all as I might use it for that as well.

Ah, @rofrischmann, I had misunderstood your comments on #267. Makes sense!
I'll fork the react-look codebase and see what we can cook up...

@rofrischmann, have you opened up lines of communication with the khan academy folks over in https://github.com/Khan/aphrodite? I definitely think there's room for both: Aphrodite fills the barebones, front-end agnostic niche, and react-look fills the react/react-native full-feature niche.
That established, I think we could share the best ideas between the packages. Checking out how they do SSR (https://github.com/Khan/aphrodite/blob/master/src/index.js#L25), it's pretty eloquent & would solve #275. There may be room to optimize it for react builds, but as is, I think it serves as a good base for a refactor.

I have not yet checked aphrodite in detail, but found they're doing great stuff. Sadly it was not available when I started with Look at all. Still I am working on sth. different which might not go well with aphrodite (at least not in every aspect). Though I will study its source code and compare both ideas. Thanks for mentioning!

what's the different thing your thinking about doing? Just wanna make sure if I make a PR I stay within those lines

Quick update about possible solutions:
Solution 1: Add styles to the HOC (@look(styles))
This is pretty easy. By passing the styles to a HOC that has access to context, we can build on the variable in the context (eg _lookConfig) instead of a singleton that comes from an import. For a working implementation, see: https://github.com/kriasoft/isomorphic-style-loader.
Solution 2:
Have addCSS return a HOC that returns a proxy proxy. For example:
StyleContainer.subHOC = StyleSheet.addCSS({...})
StyleContainer.subHOC === function(configInContext) { return new Proxy(StyleContainer.tmpStyles,...)}

Then, in the look HOC, it connects the subHOC to the context object. Finally, when the component accesses a style, eg styles.foo, it determines if target === styles, then registers target[prop] with the configInContext
Pro, no API change. Con, Proxies will require a babel tool to work with browsers <IE11. Not sure what your target is.
Solution 3: Make the user write a function inside their component
This is the route aphrodite took. <FooComponent styles={css(styles.foo)}/>.
When that function is called, it puts that single style prop into a buffer & then sends that buffer to the style tag in the DOM.
This has the added benefit of eliminating styles that are declared but never used. That's nice!
But, again it requires a breaking API change & makes for a slightly clunkier API than solution 1.
Solution 4:
Don't use real CSS. This is the option that radium takes & that's why they can write @Radium and don't have this problem. I don't like this option.

First of all, thanks for rolling up all those information!
I'd like to give some comments on each method:
Solution 4
For me, that's a no-go. Look was pure inline before, which still didn't play well as performance was suboptimal and you had to either use fallbacks (with CSS again) for media query, pseudo, ... or implement each on your own (which was a true mess and a lot of code, still not as performant as the CSS equivalent). Also note that with React 15, Radium will face huge problems as assigning strinsgs with fallback values is no longer possible e.g. display: -webkit-flex;display:flex.
Solution 3
With this solution we would loose a lot of dynamic feature as it only transforms the styles once into classNames and then stays static (if I understood it wrong). How would you add dynamic classNames?
Solution 2
This seems to be kind of overload. I don't know, I don't like that at all.
Solution 1
Solution 1 is the one I actually like the most. It has a slightly different API, but building on top of React's context seems to be the right way. With this solution each <LookRoot> would carry its own StyleContainer which also opens some level of optimizations as well.

@rofrischmann good catch on solution 3. To solve it, what we'd have to do is create that css function inside the look HOC and attach props & state to its closure. Like you, I still think the first is more eloquent. Plus, that means we could offload a lot of the magic behind addCSS and stick it in the HOC, at least for the non-native version (haven't dug into the react-native code yet).

Extra thoughts: Part of the API that i really like is that styles is defined outside of the component, it's not passed in via props. To keep that & eliminate the singleton would be a little bit of a challenge:

The StyleSheet.create method would likely to write to a temporary StyleContainer, since we can't trust that the singleton is used everywhere.
For that same reason, we can't use an autoincrementing hash, since there might be naming conflicts with other singletons. We could consider something like a murmurhash to hash on the contents of the object (but it's still really fast).
The @look would need to access the temporary StyleContainer and then take those values & dump it in a context._lookConfig.styleContainer, which would be the style container that has all the values from all the singletons.

After realizing all the work involved, solution 3 looks a little nicer, especially since a similar API already exists for using multiple classes: c(class1, class2). We could instead offer up a function that has the props & state encapsulated, eg this.props.css. That function would hash the style, put the values in the context._lookConfig.styleContainer, and return the hashed class name. This has the added benefit of only appending styles that are used. The function could also take multiple args, so it would eliminate the need for the StyleSheet.combine method.


Unsetting uploads stopped working

hi guys,
this stopped working:
uploads:
  unset@: true

while
content:
  unset@: true

still works...
any reason?

I think you have to unset media-order as well as this is tied closely to uploads.

urgh..thanks...will add it,,,but now I have to go thru all my grav installations and blueprints and add this...there was no easier solution than breaking BC?

Well, unsetting uploads is not something that the average users does, and is not something we even test regularly.  The problem with Grav is that its so flexibly that there's really an unlimited number of combinations of things, and we can't always test or foresee every issue.  This one has come up a couple of times, and the solution is simple enough. Ensuring 100% backwards compatibility on every scenario is not always possible, but we do try our best!

alright, fair enough, thanks for clarification @rhukster. btw I don't know if you saw my question in 2.0 thread but if you need any help with coding do let me know. I'm willing to help as much as I can. Just not sure where to start...


compatible to Python 3

Coule we change the code so that it runs also under Python 3?
I had the idea to add a Siegtank converter which would allow to import a complete Siegetank project into our netCDF Storage and continuously sync it, as it progresses.
The idea was to just get the actual status of a siegetank project. Get all the trajectories one by one, strip water and store the essential part (I assume that I don't need water and or momenta) in our storage.
Unfortunately Siegetank requires Python 3 and to avoid having to seperate scripts it would be great to keep out code also runnable (if not optimal) under Python 3.
This seems to involve mainly

change print to print()
take care of unicode strings
rewrite some iterables (e.g. iterates() does not work in Python 3)

which is not too much work. Most of it can be done automatically.
Would that be a good goal? I mean importing from Siegetank is a nice gimmick but potentially not relevent unless we want to use Siegetank at some point to run our trajectories (which would be compatible withe the next simulation generator scheme)

I just saw that my idea has a compatibility check mode and it will highlight all parts that are not 2.7 and 3.5. I will have a look at how complicated that is...

This has been superseded by #714. Closing with the intent of keeping further developments there.


do not cast not null column to nullable implicitly

Signed-off-by: xufei<EMAIL_ADDRESS>What problem does this PR solve?
Issue Number: ref #5514
Problem Summary:
What is changed and how it works?
For every Function expression, TiFlash used to cast its result type to TiDB's result type, this pr skips the cast from not null type to nullable type since this cast is meaningless, and TiFlash has some optimization for not null type.
Note this only affects the cast of Function result, for the cast of ExchangeSender, TiFlash still need to do the not null to nullable cast.
Check List
Tests

[ ] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-all-tests

/merge

/merge


AttributeError: module 'tensorflow' has no attribute 'gfile'

I trained a simple mnist model with tensorflow 2.0 on Google Colab and saved it in the .json format. Then on running the command
!simple_tensorflow_serving --model_base_path="/" --model_platform="tensorflow"
It is showing the error AttributeError: module 'tensorflow' has no attribute 'gfile'

What's the version of your tensorflow? It should has tf.gfile by default.

I had the same error. It's tensorflow 2.0 the new version.

It may be the API change from TensorFlow 2.0.
We may change the usage of this API for this newer version.

Thank you!

Hi @shravankumar9892 @anyaozm,
Could you solve the problem? My tensorflow version is 2.0.0-alpha0, but i still encounter the "AttributeError: module 'tensorflow' has no attribute 'gfile'" error after running the line '''  simple_tensorflow_serving --model_base_path="./models/tensorflow_template_application_model'''

Thank you

I uninstalled Tensorflow and all the files from the repository I pip installed. The installed TensorFlow and did the 2nd option and bazel built instead of doing the pip. It worked. You might wanna try pip3 if you’re using python 3. But the other setup worked for me.

any new update on tf.gfile issue ? if the API has changed what would be the new one in TF-2.0 ?

I will update this project for TensorFlow 2.0 when it's officially released. Any contribution is welcome if you are interested in this.

In tf2.0 , the gfile package has been moved into tf.io. so u can use tf.io.gfile

Thanks all. This have been resolved by https://github.com/tobegit3hub/simple_tensorflow_serving/commit/e9adcaa46d6af448321d70bcac0b4544eba4935f .
And we have done more code change to make STFS to run with TensorFlow 2.x now.

Related to https://github.com/tobegit3hub/simple_tensorflow_serving/commit/02f25974f48e9c07391c158e9c4c715ab943a998 .

Same error occurred while running a notebook from the Tensorflow site  - Build a linear model with Estimators

Download the dataset:
from official.wide_deep import census_dataset
from official.wide_deep import census_main

census_dataset.download("/tmp/census_data/")

AttributeError                            Traceback (most recent call last)
 in ()
2 from official.wide_deep import census_main
3
----> 4 census_dataset.download("/tmp/census_data/")
/content/models/official/wide_deep/census_dataset.py in download(data_dir)
76 def download(data_dir):
77   """Download census data if it is not already present."""
---> 78   tf.gfile.MakeDirs(data_dir)
79
80   training_file_path = os.path.join(data_dir, TRAINING_FILE)
AttributeError: module 'tensorflow' has no attribute 'gfile'

@Gurubux It was resolved in this problem with new TensorFlow APIs.

Hi, I am still facing the same issue even after using tensorflow 2.2 and chaning the configuration as mentioned. Please look at image below.

Same here. Same issue still exists even with Tf2.2.0.  The error comes while working with tokenization.FullTokenizer(vocab_file, do_lower_case) so we cant even go to the file and change it


Propagate line and column number to the type checker

Currently line and column number is attached to each token, but discarded in the parser during the construction of abstract syntax trees.

+1

@wxzh Do you have time to take a look at this?

I think we should raise the urgency of this issue. Otherwise it'll be hard to work in our language.

+1

Your are the issue manager :). If you think it is urgent, make it urgent!
One thing that may help on the meantime is to also print the expression with the type-error. Although this is not as precise as a line number, it will definitely help pinpointing where the problem is (and I guess it is easier to implement).

@brunocdsoliveira copy :+1:

Partially done. For now, most cases are covered except those without expression or location information in type-checking.
Possible further improvement:

Tagging types with location

Tagging names with location

Change type-checking monad to trace current expression

@wxzh There still has many situation that the compiler won't report line:column when type mismatch.
It's hard for me to make a minimal test case for you, but what I just do is to modify the type parameters of a Algebraic Data Type. I count on the compiler to find those mismatching on functions for me, but seems it doesn't work.

Why I unassigned @wxzh ? I haven't touched anything!
One situation, say I have a function
let fn[A] (a : A) = ...

and I also have a type/data
type NewType[B] = Const

When I call the fn by fn[NewType]  xxx, then compiler may reports something like this
error: kind mismatch:
  expected ‘*’,
     found ‘(* => *)’

without line:column

@zonyitoo This is because we do not trace the location of type for now as listed in possible improvement 1. It is possible to give a more precise location information about type but this will influence a lot of existed code. I am not sure whether to modify or not.
For kind mismatch, I think reporting the type name that causes the error can help a little bit. I'll change it.

@wxzh alright. So I cannot count on the compiler to help me find out which one should be modified. Ah ...

Also, there still have some situations of type mismatch that the compiler won't report the location of. I can reproduce it now because that would cause a huge mess of my code (over 1000 lines).

@zonyitoo The only thing the compiler can tell you is that the two types' kinds are different. You should decide which one should be modified.

@zonyitoo Check whether b95a307 provides the information you want

@wxzh Seems nothing changed, still report kind mismatch without location.

@zonyitoo I know. What I added for kind mismatch is printing the ill-kinded type. For now, all type mismatches should have location and ill-typed expression.

@wxzh I still get this output
error: kind mismatch:
  expected ‘*’,
     found ‘(* => *)’

@zonyitoo My pull request has not been merged yet ..

@zonyitoo It's merged, have a try!

@wxzh @bixuanzju Helpful for small program, but when I try to delete one kind param in 1000 line, then I won't be able to find it, even I know what exactly the kind mismatch is...

Do you think it can be closed?

Nope. Still, some nodes in the AST are not annotated with location. The task is two-fold:

Annotate all AST nodes with location;
Report location in all error messages.


Add more thorough checking

Closes #9
Closes #3

Thanks, all good and two issues closed to boot. :)


Initial memop syscall implementation + tests

This PR adds memop syscalls corresponding to memop 0, 1, 2, 10, and 11 to libtock-rs. Any instances where the underlying raw system calls were being used to call memop are migrated to the safe higher level syscall APIs as possible. This PR also adds a function to libtock-runtime for retrieving the value of _heap_start as set by the linker.
This PR also builds out some initial infrastructure for unit tests to include the memop syscall, and some tests of the system call implementation itself. This was definitely the trickier part of this PR. Because many of these memop APIs need to accept pointers for argument0, and because the unit tests include Miri's strict provenance tests, I modified the expected syscall type and the syscall log type to use the "Register" type for memop argument0, enabling tests to pass pointers to actual buffers without Miri complaining or without tests failing on 64 bit systems. Another tricky aspect of getting these tests right is that memop is the only system call which uses two different underlying raw system calls (syscall1 and syscall2 in this case). That makes the system call logging etc. a little weird -- I chose to still use a single type, and just follow a convention where I always pass 0 as the second argument when testing any memop calls that will use syscall1 under the hood, but I am open to suggestions for improvement there as well.
This PR has not yet been tested on hardware, but I wanted to go ahead and open this PR so I could get feedback on the unit test infrastructure. I will test on hardware shortly when I am back in the bay area.

I tested this on nrf52840dk and the console example runs fine and the fault output looks right if I fault it using the process console:
 ╔═══════════╤══════════════════════════════════════════╗
 ║  Address  │ Region Name    Used | Allocated (bytes)  ║
 ╚0x20011000═╪══════════════════════════════════════════╝
             │ Grant Ptrs      120
             │ Upcalls         320
             │ Process         668
  0x20010BAC ┼───────────────────────────────────────────
             │ ▼ Grant          76
  0x20010B60 ┼───────────────────────────────────────────
             │ Unused
  0x20010100 ┼───────────────────────────────────────────
             │ ▲ Heap            0 |   2656               S
  0x20010100 ┼─────────────────────────────────────────── R
             │ Data              0 |      0               A
  0x20010100 ┼─────────────────────────────────────────── M
             │ ▼ Stack         184 |    256
  0x20010048 ┼───────────────────────────────────────────
             │ Unused
  0x20010000 ┴───────────────────────────────────────────
             .....
  0x00040800 ┬─────────────────────────────────────────── F
             │ App Flash      1920                        L
  0x00040080 ┼─────────────────────────────────────────── A
             │ Protected       128                        S
  0x00040000 ┴─────────────────────────────────────────── H

Given the safety requirements for memop_brk and sbrk, is there an argument to be made we should also have memop_pbrk (I don't know if p is good, but "positive" brk)? I know it's not conventional, but the existing conventions weren't designed for Rust. I'm not sure how brk is going to be used in libtock-rs, but we aren't linking with newlib, and it seems like we typically allocate and not deallocate.
Or could pbrk potentially be unsafe too?

I believe pbrk would be safe -- we had a similar function in libtock-rs 1.0. I think that is probably a good idea to add, actually, though maybe with a different name. I will get to that soon

Added a safe memop_increment_brk() and one test for it.


is there a way to generate a pdf or some kind of easily read documentation file on this?

tx in advance...i understood from a tweet by Charles that there was a pdf here for Chi Calculus (link: https://twitter.com/IOHK_Charles/status/999453156319752192)

To turn the documented χ-calculus formalization into a PDF file, you have to install Isabelle, clone this repository, switch to the chi-calculus-formalization branch, go to the Chi_Calculus subdirectory, and run make. The PDF will end up in Chi_Calculus/output/document.pdf. If you want, I can also send you a PDF by e-mail.
In any case, please note that this is still work in progress. Most of the job is done, but some proofs and parts of the documentation are still missing.

Some things have changed meanwhile. Now the current state of the χ-calculus formalization is in master in the Isabelle subdirectory, and updated building instructions are provided in the README.md file in this directory.


[Data vis: charts] Design

Designs for Charts pages:
Tab: Basic charts

Tab: Advanced charts

@shixiedesign did you want us to match the chart example data to the sketch file?
stacked bar sketch file vs. code example

Also, I'm going to wait on adding the code snippets below, since that component isn't built and I assume we want it to match however we will be doing the updated React examples for components with theme switcher etc? (the one for components is custom and not really reusable right now) I'll come back to that part after helping finish up the Grid pages with Jeanne.


Feature suggestion. Interface to draw debug information.

I hope more drawing interfaces can be provided to facilitate scene debugging. For example, interfaces for drawing various primitive shapes.
I notice that the default viewer is implemented through pyrender. I successfully draw some primitive shapes through pyrender's drawing interface, but I am not sure if this will affect the simulation process or the rendering of the camera sensor.
https://github.com/user-attachments/assets/b98009fc-593a-4f17-8571-dd4b765f13a5

code for drawing
import genesis as gs
from genesis.ext.pyrender import Scene as PyScene
from genesis.ext.pyrender import Mesh as PyMesh
from genesis.ext.pyrender import Node as PyNode
import genesis.ext.trimesh as trimesh
import numpy as np

gs.init(backend=gs.cpu)

scene = gs.Scene()

plane = scene.add_entity(
    gs.morphs.Plane(),
)
franka = scene.add_entity(
    # gs.morphs.URDF(
    #     file='urdf/panda_bullet/panda.urdf',
    #     fixed=True,
    # ),
    gs.morphs.MJCF(file="xml/franka_emika_panda/panda.xml"),
)

scene.build()
pyrender_scene = scene.viewer._pyrender_viewer.scene
# create a cube mesh through trimesh

cube = trimesh.creation.box(extents=[1.0, 0.5, 0.5])
cube_mesh = PyMesh.from_trimesh(cube)
cube_node = PyNode(mesh=cube_mesh, translation=np.array([0.1, 0.15, 0]))
pyrender_scene.add_node(cube_node)
for i in range(100):
    scene.step()

Is there any plan to support such feature?

We do have! If you look into scene.py we have something like draw_debug_points draw_debug_box etc

Thank you for the response! I will try these functions.


Code - home_page Component

Todo

[x] Code home_page component

@input #4
@input #5
@input #8
@input #9
@input #10
[x] code home_page
@output home_page_v0.1.0

tasks - 2024.01.28

[x] Update home_page_v0.1.0

[x] update the home_page component
@output :package: home_page_v0.1.1

worklog
worklog-196

feedback

proposals


corrected $user to $username in ln. 491 and 492, works now

Thanks for fixing!
I just discovered it myself :D
It is fixed now.
I will close the pull request.


Improve the ROOT_DIR definition

Description

Make sure to resolve symbolic links, uses an absolute path in ROOT_DIR, and raise an error if the path does not exist by using the resolve method. https://docs.python.org/3/library/pathlib.html#pathlib.Path.resolve
Use parent.parent.parent because "Explicit is better than implicit" and because it causes less cognitive overload that parents[2].

Rationale
A similar change will be sent when django 3.1 is released.

Should wsgi.py and asgi.py with the app_path name also be changed, too?

Should wsgi.py and asgi.py with the app_path name also be changed, too?
By consistency, I think so

Added fixes for wsgi.py and asgi.py


Unexpected behavior when referencing a NN from an array.

What is wrong?
Trying to call 'train()' method on a neural network instance from an array of type any, it throws an exception: Network error rate is unexpected NaN, check network configurations and try again. Most probably input format is not correct or training data is not enough.
Code used is basically from examples within the documentation page.
The way I reference nn seems to cause the issue.
Where does it happen?
Create an array of any, create the nn, and try to train it by nn_array[name].run(data)
Expected behavior (i.e. solution)
I expect it to run training successfully, since if I try to successfully retrieve the instance it works by nn_array[name]
Version information
Nodejs: 12
Brain.js: Latest
How important is this (1-5)?
5

Using Record<string, NeuralNetwork> fixed the issue.

Nice!  Can you post the code to reproduce?

@robertleeplummerjr
Now I'm not even sure where to point to the issue.
I managed to produce it in a number of cases.
For example, the train function is quite sensitive about what we put in it.
Let's say I fallow the book example, where I'm asking NN to generate some text based on what it was trained.
I specify an array of strings, but even trough every single element is a string, I'm not able to enter some values. (getting the error again)
And sometimes I get the error trough using JSON.parse(), so what I ended up doing was making an object and assigning the data to it, and when I pass it, no errors.
Without using any parsing, TypeScript did a job for me and compiled raw data from HTTP request into an actual object.
I might be doing something wrong, but the whole documentation is just a basic examples.
Some examples even without the context, so I had to figure out what to do.
There is no explanations regarding the sensitivity of Neural Network, nor what's happening in the background.
I might be understanding somethings wrong, but there is no documentation in a sense to get deeper into how the library is actually working. I'm building a wrapper around it, which becomes very time costly because of minor issues.
I hope that this make sense, thank you for reading.

I really do want to help here, but if you could use a jsfiddle or observablehq and post an example that reproduces the issue, I can resolve it quickly.

@robertleeplummerjr
You're being very kind. I apologize for not providing the repo.
You'll be updated soon.

Closing due to inactivity.


REGoth crashes due to not yet loaded resources

Steps to reproduce:

Use current master (2d71e247cec81dac3fdaaa365f114d0ebc9c73fb)
Load ADDONWORLD.ZEN (Gothic 2) in the world viewer and make sure the init scripts are run (world->runInitScripts();)
Quit the world viewer
Start the world viewer without deleting the cache

An exception with the description Trying to access a resource that hasn't been loaded yet. will be raised in the function ModelScriptFile::_buildMeshesByNameMap by the call bs::String nameUpperCase = m->getName();.
The exception is most likely a sign that resources are accessed which are not saved as part of the prefab. The "hasn't been loaded yet" is a bit misleading here, as those resources will never be loaded.
The display name of the affected ModelScriptFile is "SCAVANGER" if that helps.

Can you try using the AI branch? I did a lot of work on rtti for worlds which has the init scripts ran because it didn't work.

It seems like this happens only on some ModelScriptFile-resources, SCAVANGER being one of them. If you just ignore those during loading, the world loads fine. I'll commit the workaround, but we should look into what's different for those model script files.


Proof of concept of using shared pinned buffers

This is just a PoC, but just doing this on the fragment environment seh_frag.py I'm getting a 30% wall time improvement for simple settings, with batch size 64 (I'm sure we could have fun maxing that out and see how far we can take GPU utilization).
Some notes:

The effect is mostly felt when sampling (which is where most time is spent in the first place), and both sending Batch and GraphActionCategoricals through shared buffers improves time
Passing batches to the training loop (which are much bigger and "rarer") doesn't seem to have a significant speedup
I also removed local grad clipping
I need to merge some other improvements to the fragment environment

I'm of a mind to merge this actually. It's not the cleanest implementation possible but there are significant gains here (as mentioned, a 30% speedup with the default settings on seh_frag.py). Will test across tasks and report back.

Made significant simplifications to the method by subclassing Pickler/Unpickler, found some very tricky bugs (I was making a bad usage of pinned CUDA buffers and ended up with rare race conditions). Speedups remain (might even be a bit faster).

Merged with trunk + made a few fixes. Pretty happy with this now!


Mandar theme destiny pool has no buttons

Mandar theme is missing the group manager and request destiny rolls buttons

Fix in #1037


Documentation: add intermediate page

Page URL:
(all pages)
Currently, the "Documentation" entry in the menu at the top of the page links directly to the OpenITI documentation (https://openiti.github.io/documentation/)
Would it not be better to have a Documentation page like we have a page for each of the other main sections, and from there, link to the OpenITI documentation? At some point, we will have documentation that is not OpenITI-related as welll.

 Nav updates

This change has now been added, see here: https://mabarber92.github.io/docs/openITI
Unfortunately to get the images to work, I had to find and replace the starts of the image addresses in the documentation (I think this is due to the workings of Jekyll, but not completely sure).
I'll work on a process that automatically grabs this data from the OpenITI Docs whenever the website is updated.


Don't prompt user to open Keppel when USB device plugged in

When a USB fingerprint reader is plugged in, as of the latest code, we now receive a message prompting us "Would you like to open Keppel every time  is plugged in?"
Since Keppel is used only from ODK, it does not make sense to open Keppel when the USB device is plugged in. While it does not break anything per se, the message is extraneous and confusing for the user, since it looks a lot like the permission prompt.

@tobiasmcnulty this pop up allows you to set Keppel as the default app for the USB device (by checking the box below the message) which will then prevent it from needing to ask for USB permission in the future. Otherwise, permission is only granted for that boot of the device.
There's a stack overflow discussion around the topic here. In short, we have to respond to the event of the device being plugged in instead of asking for permission when we want to connect to the device.
Is the problem that you see Keppel open every time the device starts? We could look at smoothing out that flow if so (maybe just immediately closing or showing a message that the device is connected for instance).

After discussing this with @tobiasmcnulty again, it seems like the ideal would be for nothing to be shown when a USB device is connected (and permission is granted). If this isn't possible, the backup solution would be to show a simple "OK" dialog with a message (like "Scanner connected").

We've decided to leave this as-is for the moment.

Reopening this as one of the devices we're playing with has an embedded scanner which gets "connected" on every unlock and pops up the Keppel settings. I'm wondering if we should make the following changes:

Just show a toast with "Scanner connect" (or similar text) when a matched scanner is connected
Add a "setup" button to settings that will connect/disconnect the scanner so that users can set up the default permissions (checking always allow) explicitly without needing to use a form.


FoundationEssentials: tweak FileManager utilities for Windows

Add a helper for time conversion and remove some functions which do not make sense on Windows - users are not identified by integral IDs but rather by SIDs. This helps reduce the error diagnostics when building FoundationEssentials on Windows.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows

Let's see where we stand with this PR - I still have some backlog to work through so I cannot determine this very well locally.

@parkera, @jmschonfeld I might need help to get this merged - I wanted to see how we were doing on Windows, and didn't realise that it would block the merge for the PR :(

@compnerd I left two comments about things the look like they might still be unresolved, once we square those away we can help make sure this gets merged. Does that Windows run show us what you were looking for (that we're at least heading in the right direction w.r.t. the number of build failures)?

Yeah, it seems that we are headed in the right direction. We are getting further, but still have a long road.

@swift-ci please test

@swift-ci please test

@swift-ci please test


VID: Reorganize and create new events

Aims to close #1817

I'd like both @shenkeyao and @ggutoski to approve this before merging :)


Object reactions and check_input_allowed

If the function check_input_allowed returns False, an object should not allow more reactions.

Implemented in 8c6e270.


Fix config file location

Solves #313

Related to https://github.com/newrelic/helm-charts/pull/638/files

In the end, the path with integrations.d was not making any issues because the configuration was mounted in the integration container but not in the agent sidecar but this can lead to misunderstandings.
I have ditched all the work from the last 2 hours because tests were passing but when I tried to run the integration itself failed because the Integration SDK also manages flags its own way.
flag provided but not defined: -c
Usage of /private/var/folders/n0/x5b9pcyx5f3528l599g3mymh0000gn/T/GoLand/___2go_build_github_com_newrelic_nri_kubernetes:
Exiting.

So I simply added the local folder as a source were to load the configuration file and changed path where to load the integration configuration.


Does awcy supports MXF?

Hi, I was trying to generate results against MXF file
Q1) I was able to get it to read MXF but then workers never picked it up, i get following logs
I also tried to directly run it through x264 and saw it x264 works on it
2021-12-17 18:58:01.771 Retrying work  gtptest.mxf with quality 10 for run @2021-12-17T18:55:29.787Z ... 4 of 5 retries.
2021-12-17 18:58:01.771 Encoding gtptest.mxf with quality 10 for run @2021-12-17T18:55:29.787Z on awcy-worker.awcy-worker
2021-12-17 18:58:05.589 Failed to copy back gtptest.mxf-40-stdout.txt, continuing anyway
2021-12-17 18:58:05.589 Decoding result for gtptest.mxf at quality 40 failed!
2021-12-17 18:58:05.589 stdout:
2021-12-17 18:58:05.589
2021-12-17 18:58:05.589 stderr:
2021-12-17 18:58:05.589 /awcyfiles/work/slot0/rd_tool/metrics_gather.sh: line 118: kill: (-3764) - No such process
2021-12-17 18:58:05.777 Retrying work  gtptest.mxf with quality 40 for run @2021-12-17T18:55:29.787Z ... 5 of 5 retries.
2021-12-17 18:58:05.777 Encoding gtptest.mxf with quality 40 for run @2021-12-17T18:55:29.787Z on awcy-worker.awcy-worker
2021-12-17 18:58:06.589 Failed to copy back gtptest.mxf-30-stdout.txt, continuing anyway
2021-12-17 18:58:06.589 Decoding result for gtptest.mxf at quality 30 failed!
2021-12-17 18:58:06.589 stdout:
2021-12-17 18:58:06.589
2021-12-17 18:58:06.589 stderr:
2021-12-17 18:58:06.589 /awcyfiles/work/slot1/rd_tool/metrics_gather.sh: line 118: kill: (-3849) - No such process

Right,

Is your workers working for normal files and normal awcy tasks as expected?

It really depends on how you config the codecs encode/decode paramters in the rd_tool, you might require to add support to rd_tool's encoding mechanism, if the codec you supplied supports it, and if it that binary is present inside slotX\$codec, and then it should work properly, Natively it uses x264 binary, and then YUV2YUV4MPEG to decode the encoded files from x264.
Can you see the encoded files present there? The logs says, error in decoding, did you modify the $codec's decoding parameter of yours? If not, I would try to do that first.


update output - expose API version

Related to https://github.com/apiaryio/fury-adapter-swagger/pull/207

Updated

Feel free to update. It is team work :)
On Mon, 3 Sep 2018, 18:11 Kyle Fuller<EMAIL_ADDRESS>wrote:

@kylef requested changes on this pull request.
The commit messages for these commits don't follow our commit message
format.
The commits should look something like:
feat: Expose API Version in parse result
chore: Release 2.16.0
@klokane https://github.com/klokane I can push these changes and we can
merge this. Although I don't want to force push to your branch without
permission.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apiaryio/swagger-zoo/pull/64#pullrequestreview-151844480,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAd59f8wjLEiPywMOrVM-fF3jAcq0-8uks5uXVSVgaJpZM4WXgvF
.


Add support for Brushes and Page.Background property

It would be great to add support for Brushes, and I'm specifically interested in Page.Background property.
The only thing I'm not sure how it should be implemented - as a wrapped component (since Brushes inherit XF.Element), or simply expose this property as XF.Brush.
Second option looks much better with SolidColorBrush:
<ContentPage Background="XF.Brush.Crimson">
    <WhateverContent />
</ContentPage>

vs
<ContentPage>
      <Background>
             <SolidColorBrush Color="XF.Color.Crimson" />
      </Background>

     <ChildContent>
            <WhateverContent />
     </ChildContent>
</ContentPage>

It's not that obvious with something like LinearGradientBrush.
<ContentPage Background="gradientBrush">
    <WhateverContent />
</ContentPage>

@code {
    static readonly XF.LinearGradientBrush gradientBrush = new()
    {
        GradientStops = {
            new(Colors.LightBlue, 0),
            new(Colors.DarkBlue, 1)
        }
    };
}

vs
<ContentPage>
      <Background>
             <LinearGradientBrush>
                    <GradientStops>
                          <GradientStop Color="Colors.LightBlue" Offset="0" />
                          <GradientStop Color="Colors.DarkBlue" Offset="1" />
                    </GradientStops>
             </LinearGradientBrush>
      </Background>

     <ChildContent>
            <WhateverContent />
     </ChildContent>
</ContentPage>

Exposing it as XF.Brush is much easier to implement, and looks nicer in some cases, but there will be issues when values are dynamic, not static. You won't be able to add some conditions in Razor tree, you'll need to handle updates on your own, which is not great.

On the other hand, for solid color you'll probably use BackgroundColor property, so I'd prefer second option.


Going Backwards On ContentTweaker Block causing player to sink.

https://youtu.be/QRgX8G2Mg40
What the title says.

Didn't post script, so I'm left with the only thought being an error with the script (Gonna guess slipperiness set to 0)

#loader contenttweaker
import mods.contenttweaker.VanillaFactory;
import mods.contenttweaker.Block;
var copperOreBlock = VanillaFactory.createBlock("copper_ore", blockmaterial:rock);
copperOreBlock.setBlockHardness(5.0);
copperOreBlock.setBlockResistance(5.0);
copperOreBlock.setToolClass("pickaxe");
copperOreBlock.setToolLevel(1);
copperOreBlock.setBlockSoundType(soundtype:stone);
copperOreBlock.register();
I don't even HAVE that in my script. Well, the wiki never said anything about it, I think, so I had no idea that setting slipperiness to 0 caused that. What do I set it to in order to disable it. (Since this is closed, you might as well send it to<EMAIL_ADDRESS>

No it's called reopening the issue now you provided info, but that's not your exact script. as that isn't valid.

That is my script. It does allow the block to appear ingame.
https://imgur.com/a/LeIibAw

Ok, based on what was said eariler, it was an error on my part. I didn't define slipperiness, so I have set that to 1. Going to use trail and error now. https://imgur.com/a/FRHOlTC  Closing this.


Automotive Workgroup F2F Meeting 2024-09 slides from EU support for F…

…OSS in automotive

sign-off was missing


Either not firing infiniteHandler or firing it forever

Hi there,
I'm trying to implement the infinite loadingm but I'm not able to do it. I've read the documentation and some similar issues, I tried also force-use-infinite-wrapper option without luck.
This is my code:
  <div
      style="overflow: auto"
      class=" columns is-multiline is-variable is-1 my-2"
      v-if="view == 0"
    >
      <div
        class="infinite column py-2 is-6-tablet is-12-mobile is-4-desktop is-3-fullhd"
        v-for="student in list"
        v-bind:key="student.id"
        style="overflow: auto"
      >
        <show-student-teacher
          :student="student"
          :classroom="classroom"
        ></show-student-teacher>
      </div>
      <infinite-loading
        ref="infiniteLoading"
        force-use-infinite-wrapper=".infinite"
        @infinite="infiniteHandler"
      >
      </infinite-loading>
</div>

If I load for example only 3 students, it works properly until it fills all the page, when I reach the bottom, the event doesn't fire. If I load 20 students, the event never fires as they fill all the page.
I tried moving the wrapper to the first div and in this case, infiniteHandler is called forever until there are no more students.
I'm using  Bulma for CSS and both divs are flex. I've tried to add manually "overflow: auto" without luck.
Thanks

After a lot of trying, it seems that is working using my  as the wrapper has solved the issue.


Browser dark theme interferes with editor text color

Hey,
Looks like browser's dark theme is interfering with the editor styles.
Below are text color styles which browsers are using in different cases.
Strapi and Tiptap versions
"@strapi/strapi": "4.1.7",
"strapi-tiptap-editor": "0.7.4",

Tested on Windows with Chrome, Firefox, and Edge
Browser & Strapi in dark mode = dark editor text on dark background)
@media (prefers-color-scheme: dark)
<style>
.bGOtGv .ProseMirror {
    color: rgb(24, 24, 38);
}

Browser in light mode & Strapi in dark mode works correctly = light editor text on dark background
@media (prefers-color-scheme: light)
.bGOtGv .ProseMirror {
  color: rgb(255, 255, 255);
}

Hi!
Thanks for reporting the bug. I have fixed this issue in 0.7.5, so please upgrade to that version.

Thanks for fixing it so quickly! 👍


Get a list of all playlist and descriptions from a channel

Hello,
I am trying to create a podcast from a channel.
Is there a way to get a list of all playlists from a channels (e.g. in the same way we get a list of videos from a playlist) ?
And continuing on that, is there a way to get the playlist description?
-rsd

I am also looking for such a feature. Also, is there a way to download all videos of a channel organized by playlist?

+1

Is there a way to get a list of all playlists from a channels […] ?

Been meaning to answer this for a long time (since before I had an account). Why, yes, there is!
It's been a while, but I devised a shell script for this.
It involved chaining a series of youtube-dl & jq (or whatever your favourite JSON parser / processor is) commands.
From memory:

youtube-dl --flat-playlist --dump-json [whatever other options you want …] (http://www.youtube.com/[channel or user name]/playlists URL|--batch-file file-containing-URLs)
pipe that output into jq, have jq output a flat (text/plain, not JSON) list of playlist URLs
pipe that list of playlist URLs into another youtube-dl (you'll need to tell it to use stdin for the source of --batch-file, however you do that on your OS / in your shell)
either have that same (step number 3) instance of youtube-dl do whatever downloading you want, else pipe its output (via --dump-json) into yet another jq which performs whatever processing / extraction of metadata you wish

Adapt to suit your needs.


ocean.assets.update() failing with an error giving no clear information

I'm trying to update a dataset description using the API. I'm calling ocean.assets.update(asset, wallet), which returns ValueError: Invalid value to publish in the metadata: {'code': -32000, 'message': 'execution reverted'}, although ocean.assets.validate(asset.metadata) returns true.
I can't tell what's wrong from this error. Could we include some more meaningful information?

@kboyeldieu - can you print your asset and wallet values please?

@kboyeldieu please reopen if issue still persists on your side


Fix typos in cspice script

Coverage remained the same at 97.024% when pulling 117cc6bc192c80d4df2dc1618ff0a3f7095d3f1b on migueldvb:cspice into 52b4d65d45fb7d81afb02f6d8686f2ae60d265ee on AndrewAnnex:master.

hey I do want to merge this in, but I have been thinking of adding a CLA to the repo as that is generally the right thing to do. It might take me a few days to get to that.

I may instead adopt a DCO, haven't quite learned enough yet to make a decision though.
Or I can just kick that can down the road...

opting to kick the proverbial can, I may adopt a DCO later though. Will merge this soon


Optimize data preprocessing before training

A couple of preprocessing could be done to improve performance of the network. Including:

Bias field correction (explore the impact of it)

@jcohenadad Is N4 good enough for this or do you need more flexibility/options etc?

N4 is ok in general, but for for small FOV and highly heterogeneous tissues it is often not appropriate. But it's a good start. And AntsPy might offer it now...?

Okay, Yup, various forms of N3 and N4.  I will see how best to incorporate this as a start to play with preprocessing and if more interesting methods come along. I will build it general enough to allow flexibility of various bias correction approaches with clearly defined interfaces.
Functional Requirement added:

Must be able to accommodate alternative bias field correction algorithms


Selection of 1micron sections resets view

When selecting a 1micron section in BigBrain template the view is reset to the center instead of keeping the current view.
I think you are already aware of this but I couldn't find a corresponding issue, so I added it 🙂

fixed by https://github.com/FZJ-INM1-BDA/siibra-explorer/pull/1420
will be in prod in next release


Prefix CSV bulk upload requires unspecified column display

Environment

Nautobot version (Docker tag too if applicable): v2.2.25
Python version: 3.11
Database platform, version: PG15
Middleware(s): N/A

Steps to Reproduce

Affecting ipam/prefixes CSV Import feature
Upload a bulk Prefix CSV file to Prefix that contains the columns marked as required: prefix, status

The job will get an error: Row <id>: prefix : this field is required.

Expected Behavior
Upload is parsed without error, job completes

Observed Behavior
job error: Row <id>: prefix : this field is required.
Mitigation
The unspecified column display is included in the CSV export (including the prefix column separately)
For the CSV Upload to complete I mirrored this, and include both a display and prefix colum in my CSV upload
Headers from Prefix CSV Export
display,id,object_type,natural_slug,prefix,type,network,broadcast,prefix_length,ip_version,date_allocated,description,status__name,role__name,parent__namespace__name,parent__network,parent__prefix_length,namespace__name,tenant__name,vlan__pk,rir__name,created,last_updated,tags

I'm not sure I follow - are you saying that if you omit the display column, you get an error about the prefix column? Can you provide a CSV file that demonstrates the issue?

| are you saying that if you omit the display column, you get an error about the prefix column
Correct, this is what I was able to reproduce this locally. I just tried again now in the demo v2.2.5 instance an did not see the same behavior. I will perform more testing and update/confirm this.

This is working for me today on demo.nautobot.com

@MeganerdDev if you can reproduce on the demo instance let us know

@gsnider2195 The test you did is not completely valid.  It appears you must upload the CSV file, not provide CSV text input to hit this issue.  There appears to be some behavior different there.
I am facing same issue on 2.2.5.  Reproducible on demo.nautobot.com running 2.2.8.
Create a CSV File with this contents and attempt to import from CSV file upload:
prefix,status
<IP_ADDRESS>/32,Active

This will fail.  The same CSV text put into CSV Text Input field works.
Workaround for CSV file import to work is to create a CSV file with this data:
display,prefix,status
<IP_ADDRESS>/32,<IP_ADDRESS>/32,Active

Note that the column order matters as well.  If display column is present, but it is not the first column, then CSV File Upload import will also fail.
This broke sometime recently - somewhere between 2.1.7 and 2.2.5.  Recently have done a ton of CSV imports where this issue was not faced on the earlier 2.1.7 code.

That's really weird, as there's virtually no difference between the code paths for text field versus file upload:
        if csv_file:
            csv_bytes = csv_file
        else:
            csv_bytes = BytesIO(csv_data.encode("utf-8"))

I'll see if I can reproduce this locally and throw in a few more debugs to troubleshoot.

Worked here on 2.2.7 with file upload:

Also worked today on demo.nautobot.com:

If you're able to reproduce this again, could you capture the Job keyword arguments from the "Additional Data" tab of the failed JobResult?

Aha! Thank you for chasing that down. It looks like this might be addressable by opening the file with encoding utf-8-sig instead of utf-8.

Django 3 and 4 don't appear to offer an encoding option when opening a FileField/FieldFile (may be addressed in 5.0 by https://github.com/django/django/pull/17173)
It may be possible/desirable for the Job to use a codecs.EncodedFile (a la https://stackoverflow.com/questions/4729832/processing-a-django-uploadedfile-as-utf-8-with-universal-newlines) to guarantee that the file encoding is correct


[BUG] Enhance "Root Access Settings"  to mention even with KES that the MINIO_ROOT_USER and MINIO_ROOT_PASSWORD are still required

Describe the bug
https://min.io/docs/minio/linux/reference/minio-server/settings/root-credentials.html
The follow doc makes it seem that the fields MINIO_ROOT_USER and MINIO_ROOT_PASSWORD are no longer required in the /etc/default/minio if KES is being leveraged to create a key upon startup.
While the key does exist within Hashi Vault (for this example) - commenting these MINIO_ROOT_USER and MINIO_ROOT_PASSWORD settings result in nodes being unable to properly startup and communicate with each other.
Even with KES using external systems, these are still required settings. It is easy to infer from the doc that you can rid the file of these passwords.

Thanks for the docs bug @ocient-jlarson !


ClrLabel throws an error when element class attribute is not set

Select one ... (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Actual behavior
https://github.com/vmware/clarity/blob/794ee83bc7aae3b1d4c53a093d56cf69f8679979/src/clr-angular/forms/common/label.ts#L39 throws an error (Cannot read property 'indexOf' of null) when label element doesn't have a class attribute.
Reproduction of behavior
https://stackblitz.com/edit/clarity-light-theme-v012-g7vtt9
Environment details

Angular version: 6.1.0

Clarity version: 0.12.6

OS and version: Win 10

Browser: all

We haven't released a clrCheckbox component yet, so that is why you're seeing this error. I'll keep this bug report open to harden against this case, but so far we have the clrInput, clrTextarea, and clrPassword components released. clrSelect and clrRadio are open PRs, and a few more will follow soon.

This was fixed in the radio form changes, closing as fixed in 0.13


EcmaScript is for React, AcneScript is for makeup

There was a typo on the frontpage, where AcneScript (The famous frontend makeup library) had been mixed up with EcmaScript.

This is the Consulting Drivenes Github Bot. Hello! Nice to meet you. Thank you very much for your contribution! It was indeed a typo. We value external contributions very much. Can you please sign 48 CLAs (Contributor License Agreements) and agree to patent grant? Can you also run yarn, prettier, npm, and continuous integration on the project?

This is the bot. I merged the request. Hello. This is another bot. Why did you merge the request without 48  signatures to contributor license agreements?

As we say in Norway: "Dette var en skikkelig tull-request"


Allow users to sign in with Google to associate a user with calendars

Overview
Users should be allowed to sign in with Google so that they can see their saved calendars
Goal
Allows users to click on a sign in button to log them into Google
Requirements

[ ] Add a button to allow a user to login with Google
[ ] Associate Users with Calendars in the table based on the Google Account

Implemented google authentication and can store their profile for calendar storage (still need to create tables and api to query and store calendars)


Performance improvements

This PR is a collection of performance improvements:

AGAS: all non-migratable (non-managed) components now store their lva and component type directly in the gid
AGAS: all migratable component now have a special bit set in their gid
LCOS: future state is now stored as a std::atomic<state>

More testing is needed. I'll close this PR and create separate ones for each of the things proposed here.


chore: remove file_cache_bench and s3_bench

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
They are old and unmaintained. (>2years)

Checklist

[ ] I have written necessary rustdoc comments.
[ ]  I have added necessary unit tests and integration tests.
[ ]  I have added test labels as necessary.
[ ]  I have added fuzzing tests or opened an issue to track them.
[ ]  My PR contains breaking changes.
[ ]  My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
[ ]  My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

[ ]  My PR needs documentation updates.

Release note

#19926
#19927  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.