aliasing fd causes Search Directory to hang

I have fd aliased to a less pager, like so:
function fd --wraps=fdfind --description 'alias fd=fdfind'
  if isatty stdout
    command fdfind --color always $argv | less
  else
    command fdfind $argv
  end
end

This is causing Directory Search to hang until all results have been found.
#280 Fixes than by checking that unwrapped fd is called.

Hi Susensio, I wonder if it's possible fish functions don't support streaming in pipelines, so they block until they have received all the data? Anyway, I don't think this isn't a bug with fzf.fish

Does Search Directory still hang if, instead of creating a wrapper function for fd, you use an alias?

Oh it probably does because fish aliases basically creates a function unlike other shells. Okay yeah, let's add command fd I'll update the docs to tell people to symlink instead of aliasing. However, I don't want to look for fdfind and use it if it's available because Search Directory is becoming monstrous and I despise maintaining it.

I've submitted a PR #282 that solves the fd or fdfind binary problem without aliases. I think it's fairy simple and doesn't add much complexity.
The problem with #280 and symlink that you suggest is that it would be a breaking change and suddenly the extension will stop working for the people that use fish aliases


New version: Anysphere.Cursor version 0.44.9

Created by 🥟 Dumplings in workflow run #10586.

Log
Updated: 0.44.8 → 0.44.9
No ReleaseNotes for version 0.44.9
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

@wingetbot run


Simplify RateCheckerChartMenu and fix BAH linter warnings

Additions

Adds missing jsdocs to BAH methods.
Adds missing MIME type for PNG in chart export.

Removals

Removes "RateCheckerChartMenu.STATES" export as it was only exported for the tests.
Removes test of internal private method "_setState".
Unused references in Slider.js.

Changes

Converts open/closed state of chart download menu to simple strings from an object to remove need for Object.assign.
Converts logic stored in data- attributes to directly use textContent of list nodes in download menu.
Removes complexity warning from exportChart method by converting switch into if/else and an object lookup hash.
Update RateCheckerChartMenu test markup structure to follow that of production.

Testing

Pull the branch and gulp clean && gulp build
The "Download chart" options in the upper-right of the chart on http://localhost:8000/owning-a-home/explore-rates/ should work (first three will download an image, last will open the print dialog box). Clicking the "Download chart" text will open/close the menu.
gulp test:unit should pass.

Screenshots

codecov can be ignored.

Probably out of scope for this PR, but it'd be nice if the chart exports included a title and the x-axis label. Also, why does the print version have blue instead of green bars?

Hmmmmmmm got me, but good observation! You're saying you want to print what you see on screen when you click print?? 😜

Issues for noted issues:
https://[GHE]/CFGOV/platform/issues/3281
https://[GHE]/CFGOV/platform/issues/3280

Thanks for opening those!


documentation suggestion -- when should we use which type of operator?

Feature Request
documentation suggestion -- when should we use which type of operator?
As we were reviewing the different types of operators we could create, it wasn't clear when we should use Helm based operators vs Go based operators. For example, do we get more power and control with Go based? Helm seems simpler, but are there things we're unable to do later on if we use Helm?
Describe the solution you'd like
On the README and perhaps elsewhere, add high level advice about when to use which type.
Workflow
The SDK provides workflows to develop operators in Go, Ansible, or Helm.
<insert help here>

@gregsheremeta take a peek at this capability level diagram for a decent overview of which operator has what level of control. This diagram should probably be put somewhere more visible than our doc/images dir.

This diagram should probably be put somewhere more visible than our doc/images dir.

I'd suggest the front page README or front page of the docs.

With the merge of https://github.com/operator-framework/operator-sdk/pull/2070 I understand that we can close this one @estroz. WDYT?


Sbt 0.13.15 can't startup without being connected to internet

steps
Delete all dependency caches on your machine (ivy, maven, etc)
Run sbt from a empty directory or even simple project with just build.sbt and build.properties
See the error message that sbt can't find a dependencies and it won't start.
problem
Sbt needs dependencies to start up that aren't in the preloaded cache
expectation
That sbt can start without internet connection, when user has no ivy or maven cache.
notes
The first dependency not found is:  org.fusesource.jansi#jansi;1.11: not found
The cache only has  org.fusesource.jansi#jansi;1.4

Thanks for the report. Could you copy paste the full error output to here or gist plz?

FWIW here's the log of sbt running on from an OpenJDK 9 Docker container while disconnected from wifi - https://gist.github.com/eed3si9n/5d80ea9d6e1f6f59ff80231cb2ecab46

Just checked linux and it works fine. That is primarily what I care about. Looks like the issue is just for windows?

Fixed in 0.13.16 (and 1.0.0) with https://github.com/sbt/sbt-launcher-package/pull/160.


Made h1 to h4 tags replaced by "**"

WordPress

Becomes
** WordPress
------------------------------------------------------------

Culled from MailChimp tool (http://templates.mailchimp.com/resources/html-to-text/) and i loved it.

I'm not really a fan of this change - I don't think we should be rendering the long lines of dashes and I'm not sure why H1-H4 should have ** and H5-H6 has nothing.


feat(semigroup): adds implementations of semigroup along with laws an…

Adds support for Semigroup as described in the Static Land spec: https://github.com/rpominov/static-land/blob/master/docs/spec.md#semigroup
I'd like this to be a trial run for future PRs, so please let me know if you'd like me to do anything differently. I read through the contributor guidelines, and followed your lead code-wise.
This relates to issue #9

This is good @dwhitney, keep them coming :)

@dwhitney also, if you need a release, let me know.

Cool I'll get another one in sometime this week! I don't need release yet
On Mon, Mar 26, 2018, 2:25 AM Alexandru Nedelcu<EMAIL_ADDRESS>wrote:

@dwhitney https://github.com/dwhitney also, if you need a release, let
me know.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/funfix/funland/pull/10#issuecomment-376059044, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACCoZamzasY9FiecnmTWZxROu-0x-Q1ks5tiInDgaJpZM4S5BM5
.


Build fails with CLang 3.8 ("sized operator delete")

Error message:
libtool: link: /afs/cern.ch/sw/lcg/external/llvm/3.8/x86_64-slc6/bin/clang++ -DNO_TCMALLOC_SAMPLES -g -O2 -o low_level_alloc_unittest src/base/low_level_alloc_unittest-low_level_alloc.o src/low_level_alloc_unittest-malloc_hook.o src/tests/low_level_alloc_unittest-low_level_alloc_unittest.o  ./.libs/libspinlock.a ./.libs/libsysinfo.a ./.libs/liblogging.a ./.libs/libmaybe_threads.a /afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6/lib/../lib64/libstdc++.so -Wl,-rpath -Wl,/afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6/lib/../lib64 -Wl,-rpath -Wl,/afs/cern.ch/sw/lcg/contrib/gcc/4.9.3/x86_64-slc6/lib/../lib64
./.libs/libsysinfo.a(sysinfo.o): In function `ProcMapsIterator::~ProcMapsIterator()':
/var/build/jenkins/workspace/lcg_experimental/BUILDTYPE/Release/COMPILER/clang38/LABEL/slc6-physical/build/externals/gperftools-2.5/src/gperftools/2.5/src/base/sysinfo.cc:519: undefined reference to `operator delete(void*, unsigned long)'
./.libs/libsysinfo.a(sysinfo.o): In function `tcmalloc::FillProcSelfMaps(char*, int, bool*)':
/var/build/jenkins/workspace/lcg_experimental/BUILDTYPE/Release/COMPILER/clang38/LABEL/slc6-physical/build/externals/gperftools-2.5/src/gperftools/2.5/src/base/sysinfo.cc:519: undefined reference to `operator delete(void*, unsigned long)'
/var/build/jenkins/workspace/lcg_experimental/BUILDTYPE/Release/COMPILER/clang38/LABEL/slc6-physical/build/externals/gperftools-2.5/src/gperftools/2.5/src/base/sysinfo.cc:519: undefined reference to `operator delete(void*, unsigned long)'
./.libs/libsysinfo.a(sysinfo.o): In function `tcmalloc::DumpProcSelfMaps(int)':
/var/build/jenkins/workspace/lcg_experimental/BUILDTYPE/Release/COMPILER/clang38/LABEL/slc6-physical/build/externals/gperftools-2.5/src/gperftools/2.5/src/base/sysinfo.cc:519: undefined reference to `operator delete(void*, unsigned long)'
/var/build/jenkins/workspace/lcg_experimental/BUILDTYPE/Release/COMPILER/clang38/LABEL/slc6-physical/build/externals/gperftools-2.5/src/gperftools/2.5/src/base/sysinfo.cc:519: undefined reference to `operator delete(void*, unsigned long)'
clang-3.8: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [low_level_alloc_unittest] Error 1

I think this is related to this:

This was introduced by r229241 - Revise the implementation logic of sized deallocation: Do not automatically generate weak definitions of the sized operator delete (in terms of unsized operator delete). Instead, provide the funcitonality via a new compiler flag, -fdef-sized-delete

Thanks for report. But I am not able to reproduce the problem. Is that clang-3.8 with it's own libc++ or something else? GNU/Linux ?

The build was performed on SLC6 machine, with libstdc++ from gcc 4.9. I'll check the suggestion in the linked bug report.

I would like to reproduce this. Can you please describe how you got clang 3.8 on that box?

Gentle ping. Can you please share more details on your exact setup? I would very much like to reproduce the problem

Hi,
the compiler was produced by a different person, and I'm waiting for her to
answer. I'll ask her again.
-- iarspider
On Jul 16, 2016 5:34 AM, "Aliaksey Kandratsenka (aka Aliaksei
Kandratsenka)"<EMAIL_ADDRESS>wrote:

Gentle ping. Can you please share more details on your exact setup? I
would very much like to reproduce the problem
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gperftools/gperftools/issues/804#issuecomment-233103805,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAm2urSxlW0rjw9on1x9ytmkgtd2Dohxks5qWEMXgaJpZM4IqfHR
.

Gentle, ping. In about month or so I plan to do sweep of all tickets. And I'll have to close this ticket if there is still no update.

I have the same issue here with both clang version 3.8.0 and 4.0.0: gperftools/src/base/sysinfo.cc:550: undefined reference to 'operator delete(void*, unsigned long)'

More details please. As soon as I can reproduce the problem, I will be able to help.

The same issue on OS X 10.11.6 with Apple LLVM version 7.3.0 (clang-703.0.29):
/bin/sh ./libtool  --tag=CXX   --mode=link g++ -DNO_TCMALLOC_SAMPLES -D_THREAD_SAFE  -DNDEBUG -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -fno-builtin-malloc -fno-builtin-free -fno-builtin-realloc -fno-builtin-calloc -fno-builtin-cfree -fno-builtin-memalign -fno-builtin-posix_memalign -fno-builtin-valloc -fno-builtin-pvalloc  -Wno-unused-result -fsized-deallocation   -g -O2 -version-info 8:5:4 -no-undefined  -Wl,-U,___lsan_ignore_object  -o libtcmalloc_minimal.la -rpath /usr/local/lib src/libtcmalloc_minimal_la-tcmalloc.lo    libtcmalloc_minimal_internal.la
libtool: link: g++ -dynamiclib  -o .libs/libtcmalloc_minimal.4.dylib  src/.libs/libtcmalloc_minimal_la-tcmalloc.o   -Wl,-force_load,./.libs/libtcmalloc_minimal_internal.a   -g -O2 -Wl,-U -Wl,___lsan_ignore_object   -install_name  /usr/local/lib/libtcmalloc_minimal.4.dylib -compatibility_version 9 -current_version 9.5 -Wl,-single_module
Undefined symbols for architecture x86_64:
  "operator delete(void*, unsigned long)", referenced from:
      TCMallocImplementation::~TCMallocImplementation() in libtcmalloc_minimal_la-tcmalloc.o
      SbrkSysAllocator::~SbrkSysAllocator() in libtcmalloc_minimal_internal.a(libtcmalloc_minimal_internal_la-system-alloc.o)
      MmapSysAllocator::~MmapSysAllocator() in libtcmalloc_minimal_internal.a(libtcmalloc_minimal_internal_la-system-alloc.o)
      DevMemSysAllocator::~DevMemSysAllocator() in libtcmalloc_minimal_internal.a(libtcmalloc_minimal_internal_la-system-alloc.o)
      DefaultSysAllocator::~DefaultSysAllocator() in libtcmalloc_minimal_internal.a(libtcmalloc_minimal_internal_la-system-alloc.o)
      __GLOBAL__sub_I_symbolize.cc in libtcmalloc_minimal_internal.a(libtcmalloc_minimal_internal_la-symbolize.o)
      SysAllocator::~SysAllocator() in libtcmalloc_minimal_internal.a(libtcmalloc_minimal_internal_la-malloc_extension.o)
      ...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [libtcmalloc_minimal.la] Error 1

Is that still relevant?


More info at: https://travis-ci.com/Qiskit/qiskit-terra/jobs/302633721

The CI's IQX provider had a misconfigured backend.


As a CIF program administrator, I want to break scoring ties, so that the order of ranked projects is fixed and clear

Description:
Breaking ties in case there are equal scores on projects (which should be a rare case)
Acceptance Criteria:
Given
When
Then
Development Checklist:

[ ] Checklist item
[ ] Checklist item
[ ] Checklist item
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

@nanyangpro - I feel we discussed this issue before and that breaking scoring ties was not a significant issue for CIF. Can you confirm? If so, I'll move this ticket into the icebox.

Confirmed, this is a low-priority one. thanks @LindsayMacfarlane!


Update soft-delete.js

Closes #257
Closes #389

Wouldn't you still need a catch to avoid the dreaded UnhandledPromiseRejectionWarning?

Thank you.
I'll wait on publishing this is you plan to sumbit more PRs.


v2.50 release

What features and issues are more urgent for version 2.5.0?  And what is your plan for 2.5.0?

@dota17 @jjenkov @ChristianWilkie

I like you guys feedback on this. In my mind it is

get jenkins up and running with code coverage
its been a while since last release, so get a release out soon

maybe we should upgrade to java 8 ,just like @jjenkov says java 6 or java 7 is too old   #169

I would say, that the highest priority should be to just get a release out. As far as I can see, v. 2.4.0 is 3 years old. I would go for a minimum of functionality in 2.5.0, just to bring SuperCSV "back to life" .

If upgraded to J8, would SuperCSV work correctly under J9+? My application uses SCSV, and a problem that I run into is its incompatibility with J9+ just generally. It would be a big upgrade for me if that issue was resolved. (as always, thank you for maintaining this!)

@DraqueT  Is the approach to make a J9 specific release? or will the https://github.com/super-csv/super-csv/pull/152 suffice?

Hi, @kbilsted
I don`t think super-csv version 2.5.0 make a J9 specific release. I think it is enough that ensuring super-csv 2.5.0 can be imported and used in java9 module application(#138 ).
Because java9 modules is important and influential. When we upgrade Java 9, we need to design reasonable modules for super-csv,
And

Hi, @kbilsted
Are you plan to upgrade to java8 in 2.5?
If so, we can incorporate super CSV java8 into super CSV and address #152. that will ensuring super-csv can be imported and used in java9 module application.

Adding support for escaping quotes using \" instead of leaving this as unhandled seems reasonable, very hard to recover from errors based on this otherwise.

@dota17  I'd vote for caution. Can you make things work in a side branch for JDK 9 for now and get experince with it with some users?
isn't java8-specifc jar a part of the existing mvn build?

I can probably help out on getting this to compile on Java 8. This is used on one of the Apache projects I'm working on and there are some bug fixes I could really stand to have. Glad to see active development again.

The master branch does build just fine on Java 8 though. Not sure if what some of the other issues actually were.

@shawnweeks thanks. I'll install jdk8 and retry

@shawnweeks thanks. I'll install jdk8 and retry

I just ran "mvn clean install" using adoptopenjdk on macos. All the test cases ran and everything. Jars appear to be there in the build not sure what else needs to be tested but it should at least build until we move the compile versions forward.

Hi, @kbilsted
I am sorry. Can you change the name of the branch from java9 to java8 ：）.

sorry yes. I have been away for some days. Had some business I had to do.

Any chance for a 2.5.0 release soon?
What issues/things are still open to do so?

Any chance for a 2.5.0 release soon?
What issues/things are still open to do so?

Same question here, do you have a 2.5.0 release soon or is anything open here ?


[Bug] [Module Name]  workflow is always running when worker sendResult success but master not received

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
[Bug] [Module Name]  workflow is always running when worker sendResult success but master not received
What you expected to happen
[Bug] [Module Name]  workflow can be complated
How to reproduce
[Bug] [Module Name]  workflow can be complated
Anything else
No response
Version
dev
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

closed by #7611


Docker CLI needs mechanism to pass extra docker params

CWLTools needs a patch to, need to discuss

Jake at UCSC can probably work on this.  We should patch the CWL 1.0 version and issue a pull request.  This is related to #324

Required for https://dockstore.org/containers/quay.io/pancancer/pcawg-dkfz-workflow

Note to self, we have a mechanism to pass extra cwltool params as documented at https://staging.dockstore.org/docs/advanced-features#running-cwl-runner-with-extra-tags but we still have no solution to bypass cwltool and inject extra parameters to the docker run  command


Fix message body writers error handling

The recent changes made to helidon-common-reactive changed the rules for the message body  writer error handling.
In 1.x BaseProcessor had a catch-all logic that would catch any exception thrown by mappers. In  2.0 there is no catch-all logic and the error handling has to be done downstream.
This means that all mappers must implement a try-catch and delegate to onError properly.
Maybe we can come-up with a base class to enforce consistent behavior across all mappers used by message body operators.
CC @danielkec

BaseProcessor was removed and replace with a complete set of new tools. This issue is not relevant anymore.


Add Screenspace Refractions

Currently with refractions SP just does what the game (and every game of the era) did, sample a normal map, apply a transform to it and use it as an offset into a copy of the scene buffer. It'd be cool to offer the user the option to actually perform refraction with ray tracing. This would require access to the depth buffer, which isn't as simple as it sounds since it is sometimes split in two, one for near scene and one for the far scene.
Also accessing the depth buffer would require dropping MSAA, which I'd really like to avoid doing (unless it opens up some other significant visual improvement as in the effects/materials system). Nonetheless it'd be a cool thing to implement in the long term.

No longer a goal.


plunker template is not working anymore

Bug, feature request, or proposal:
BUG
What is the expected behavior?
Plunker template should work
What is the current behavior?
Plunker template for material is broken
Error: (SystemJS) XHR error (404 Not Found) loading https://rawgit.com/angular/cdk-builds/master/bundles/cdk.umd.js/overlay
Error: XHR error (404 Not Found) loading
What are the steps to reproduce?
Goto https://github.com/angular/material2
Click on Plunker Template link
or
directly open flowing link:
http://plnkr.co/edit/o077B6uEiiIgkC0S06dd?p=preview
or
https://goo.gl/DlHd6U

Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U

What is the use-case or motivation for changing an existing behavior?
We should be able to reproduce error in plunker
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
13 Aug Angular Material Master
Last commit info: 85a6fff fix demo app (#6437)
Is there anything else we should know?

It seems it is solved
thank you

The plunkr doesn't have the imports in alphabetical order (THE HORROR!!!) Thus, here are the imports in alphabetical order:
// CDK Secondary entry points
'@angular/cdk/a11y': <EMAIL_ADDRESS>'@angular/cdk/bidi': <EMAIL_ADDRESS>'@angular/cdk/coercion': <EMAIL_ADDRESS>'@angular/cdk/collections': <EMAIL_ADDRESS>'@angular/cdk/keycodes': <EMAIL_ADDRESS>'@angular/cdk/observers': <EMAIL_ADDRESS>'@angular/cdk/overlay': <EMAIL_ADDRESS>'@angular/cdk/platform': <EMAIL_ADDRESS>'@angular/cdk/portal': <EMAIL_ADDRESS>'@angular/cdk/rxjs': <EMAIL_ADDRESS>'@angular/cdk/scrolling': <EMAIL_ADDRESS>'@angular/cdk/table': <EMAIL_ADDRESS>'@angular/cdk/testing': <EMAIL_ADDRESS>

Once again, all the plunks referenced at the main website  are broken.
Cause: links are broken, likely after the update to Material version 5.0.0.
Some plunks (like the abovementioned  plunk ) can be fixed by fixing the version of rxjs to 5.5.2.
Some are broken, because not all required packages are in place.
Compare these URLS:
5.5.0
2.0.0-beta.12
There, at 5.0.0 some packages , like Rxjs , are missing.
@mahmood-sajjadi , can you pls look into it, and /or reopen the issue?

Some plunks (like the abovementioned  plunk ) can be fixed by fixing the version of rxjs to 5.5.2, like this:
'rxjs'<EMAIL_ADDRESS>Here's this plunk, but fixed .  I tried copy-pasting systemjs.config.js to some other broken plunks, and those begin to work too!


Add an About section

I suggest adding an About section saying "Fortran functions for dates and times" and adding topic tags datetime, dates, times.

I appreciate your kind advice!


Check for CONTRIBUTING.md

Simple binary check for a CONTRIBUTING.md file in the repository using the GitHub action

Per @harshkachhadia - should be non-empty


fix: Rename to follow expected convention

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow Banners to render basic markdown such as links and emphasis.

Added reactMarkdown component and dependency.

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[x] Reviewed and tested on Mobile, or determined not required.
[x] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

Thank you for jumping on this - has been on my list for a while to discuss built-in markdown support, and this was a good prompt to do so.

Should we consider publishing a markdown component outside of the kit directory? I am not sure - I can't think of anything really to add or normalize on the API, but at the same time we typically publish a non-kit cmp for components we expect developers to be using regularly.
Not for the banner usage, but thinking of other in-app usages like comments, we could consider adding https://github.com/remarkjs/remark-breaks as a preconfigured plugin. Github makes this modification to standard MD in a few places and I always find it intuitive:

By way of example
this is on another line
(but wouldn't be in standard markdown, I don't think)

Changelog entry should include it in a Libraries section + a callout in the New Features section to recommend that apps cut over to the Hoist export + remove from their package.json to take advantage of our managed upgrade cycle (compatibility testing, etc) and to avoid potentially including multiple versions of the library should we have non-overlapping version specs.
I'm all for adding this as a built-in, but we should check to how much this increases the bundle size of e.g. Toolbox. It looks like a fair amount of dependencies, and with the usage within the built-in banner, we know it will always be included in any/every app bundle.

Another thought - at some point it would be great to have a user-friendly MarkdownInput component with something like the formatting toolbar in this Github commenting box.
Codemirror has a markdown mode and we could certainly configure that, but then you are in monospace/non-wrapping "code editing" mode and that's not really the experience I think we would want for user (or even admin) facing MD editing.
Not something we need to do for this PR, but it could be a companion comp we could consider when we go to use MD more widely for use cases like in-app comments (something I'd like to offer in one of our current apps).

Thanks for taking a look Anselm - I've updated the PR. Including the remark-breaks plugin was justification enough to wrap this in its own Markdown component. I've updated the CHANGELOG entry, and ensured the "Read More" popup is also rendered as markdown.

According toolbox/yarn startAndAnalyze with the inlineHoist flag set to true, this PR increases the bundle size 23.81 MB > 24.39 MB

This looks great to me ---  we might want to add some text in the banner admin discussing what is going to work, and what won't.  Happy to merge this now


About y-axe translations

Hi! I saw that you updated the code of diffdrr. In the tutorials, I found that translations=torch.tensor ([[0.0, 850.0, 0.0]], device=device). If I change the data, what settings should Y-axis be based on.
Thank you！

Hi @shenao1994, I need to make a dedicated notebook going over the new geometry in DiffDRR (this pull request summarizes a lot of the changes - #207), but I can provide a quick example here:

The isocenter of your CT is now placed at the origin of world coordinates
The camera (i.e., X-ray source) is placed at the origin and the detector plane at (0, -f, 0) where f is the C-arm's focal length (source-to-detector distance, no longer the radius)
Increasing y moves the camera further away from the patient
You can mimic this by pointing your finger into your chest (your finger is the camera). Increasing y moves your finger further from your chest.

These changes were made to make the camera in DiffDRR better mimic physical C-arms. In the DICOM of some C-arm images, you'll find spatial parameters encoded like the source to detector distance, source to isocenter distance, primary positioner angle, and secondary positioner angle. DiffDRR now can directly decode these parameters to produce a camera pose.
But as I said, this is still under active development and I need to make a dedicated tutorial notebook for how this geometry works.
Please let me know what further questions you may have!

Hi @shenao1994, I need to make a dedicated notebook going over the new geometry in DiffDRR (this pull request summarizes a lot of the changes - #207), but I can provide a quick example here:

The isocenter of your CT is now placed at the origin of world coordinates
The camera (i.e., X-ray source) is placed at the origin and the detector plane at (0, -f, 0) where f is the C-arm's focal length (source-to-detector distance, no longer the radius)
Increasing y moves the camera further away from the patient
You can mimic this by pointing your finger into your chest (your finger is the camera). Increasing y moves your finger further from your chest.

These changes were made to make the camera in DiffDRR better mimic physical C-arms. In the DICOM of some C-arm images, you'll find spatial parameters encoded like the source to detector distance, source to isocenter distance, primary positioner angle, and secondary positioner angle. DiffDRR now can directly decode these parameters to produce a camera pose.
But as I said, this is still under active development and I need to make a dedicated tutorial notebook for how this geometry works.
Please let me know what further questions you may have!

Thank you very much for your patient explanation. I am currently working on the registration of real X-ray. Therefore, I need to know how the coordinate system of diffdrr is established. My current understanding is that CT volume is transformed into the camera coordinate system of diffdrr. I don't know if I understand it correctly. I hope to understand the whole coordinate system transformation process, which is very helpful for subsequent application to real scenes. I will wait for you to give some details about the diffdrr geometric transformation. Thank you again!

No problem! I'll send you an email when the geometry tutorial is pushed.


#270 exposed ReRoute priority

Fixes / New Feature #
Fixes #270
Proposed Changes

Expose ReRoute priority in configuration.json so that people can define their own ReRoute priority
excluding /{catchAll} which is still hardcoded to 0.

Coverage increased (+0.01%) to 82.044% when pulling 8f8d3ccce9eded7b2430e250a24baac7c1853543 on feature/expose-re-route-priority into 16c70e8b65d2f7feed0ced557408b6ff8ed3c53e on develop.


Hooks are applied one frame late

In Bevy 0.11, scenes are spawned in the Update schedule, so it's possible for run_hooks to run before they are spawned, so that the hooks are applied one frame late.
For me, this manifested in a shadow being visible for one frame before NotShadowCaster took effect.
In Bevy 0.12-dev, scenes are spawned in the SpawnScene schedule which runs between Update and PostUpdate.
A fix in either environment could be to schedule run_hooks in PostUpdate.  But maybe it's more proper to run in the appropriate schedule, ordered after scene_spawner_system.

Thank you for opening the issue. I've participated to https://github.com/bevyengine/bevy/pull/9260 as you can see. Yeah. I think running the hook in scene_spawner_system is going to be the solution.

This should be fixed with v9.0.0.


Fix the crash:Scroll the first page to second > when the scrolling do no...

During Page Scrolling,we should avoild user to tap the segmentButton to fix the crash.

We find the crash situation:

Launch the demo > scrolling in the first page > and then quickly tap the fourth segment button => the app will crash

So I add isPageScrollingFlag to avoid user to tap the segment button during scrolling to fix the crash.

Thank you for RKSwipBetweenViewControllers.

This is great! I'm going to make a few changes though.  In general, when you have a flag like this, you should use the complementary functions to turn it on / off.  For example, if you turn the flag on in scrollViewWillBeginDragging then you should turn it off in scrollViewWillEndDragging


Custom Static Analysis Rules with DacFx 150 Not Executed on Build from VS 2022 Command Line

Repro steps to be added subsequently
Steps to Reproduce:

Create custom rules using older versions of dacfx (150)
Copy the dlls to C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\Extensions
Create a sqlproject with a script that won't be valid according to the rules you created
make sure True is set in the project
run "msbuild [your project].sqlproj /p:rebuild

Expected: Build should show the message from the custom rule as warning
Actual: There's no warning
Did this occur in prior versions?  If not - which version(s) did it work in?
(DacFx/SqlPackage/SSMS/Azure Data Studio)

I verified building the same rules with DacFx 160, which is the one VS 2022 uses, fixes the problem. The reason that rules compiled with DacFx 150 cannot be loaded in VS 2022 is that MEF for some reason cannot match the types. Here's the debug message from MEF trying to load the custom rules: The import requires metadata 'PlatformCompatibility' to be of type 'Microsoft.SqlServer.Dac.Extensibility.TSqlPlatformCompatibility' but the provided value 'All' is of type 'Microsoft.SqlServer.Dac.Extensibility.TSqlPlatformCompatibility'

as workaround, rebuild the custom rules using DacFx 160

@llali - This issue stems from a support case where we observed this issue with the custom rules (SqlServer.Rules) from https://github.com/tcartwright/SqlServer.Rules/releases. Are you suggesting that it's not a problem with VS 2022/SSDT, but the way the custom rules were built/compiled? I'm not familiar with this aspect of Custom Rules, so I'm requesting clarification. Is this something that the custom rules developer must do?

Here are instructions that @llali created and I'm passing along for how to get the rules built in the SqlServer.Rules repo and get them to play nicely with VS 2022 (and its command-line equivalent):

Clone tcartwright/SqlServer.Rules: SQL Server static code analysis rules for SSDT database projects (github.com)

replace any version "150.5164.1" to "162.1.167". This is the dacfx version the project was using.

there are some old packages that need to be updated to System.Runtime.CompilerServices.Unsafe to 6.0.0

run msbuild /restore

run msbuild

get the dlls from git\SqlServer.Rules\SqlServer.Rules\bin\Debug\net472 and copy to C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\Extensions\SqlServer.Rules

I cleaned everything in C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\Extensions\SqlServer.Rules so now it only has these:

Now if you run the build on SQL Project, you will see the rules are applied

Root cause appears to be that MEF has a problem with assembly version changes (150.x.x vs 160.x.x)

Thanks @chlafreniere and @llali for your work on this!!!

as mentioned above this is by design. If the rules are compiled with DacFx 150, they cannot be used in a SQL project building with dacfx 160. Please compile the rules with latest version of dacfx. additional warnings are added to build diagnostic logs so user gets some information about why rules are not loaded


Use statting instead of read in resolver

This changes the resolver FS to use direct stat calls instead of going straight to a read call. Now that statting is part of the base FS API this makes more sense.

@guybedford Can you add a test for this?

@styfle I tried but it's actually really hard to test... so considering it as more of a refactoring.

Codecov Report

Merging #22 into master will increase coverage by 0.08%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage   89.89%   89.97%   +0.08%
==========================================
  Files          10       10
  Lines         970      978       +8
==========================================
+ Hits          872      880       +8
  Misses         98       98

Impacted Files
Coverage Δ

src/node-file-trace.js
90.32% <100%> (+0.66%)
:arrow_up:

src/resolve-dependency.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Add pagination functionality

This PR adds the structure needed for changing the pages shown on the front end. This is done via 2 buttons "prevPage" and "nextPage", and a visual indicator of the current page number.
Currently, each page has a fixed number of 20 build snapshots, but the plan is for the user to be able to choose how many entries per page it wants. The styling will come in a later PR.

I'd recommend we move the pagination-navbar to render conditionally with the build-snaphot-container. This way if no data is returned, we don't still have the pagination section.

Theoretically, this app should always have data once we properly deploy it, and the only cases where we don't have any data to show would be in test builds and now, in the beginning. I don't think this warrants the addition of new logic just for this case.

I'd recommend we move the pagination-navbar to render conditionally with the build-snaphot-container. This way if no data is returned, we don't still have the pagination section.

Addressed this by making the buttons invisible instead of grey-ed out, in #193. No additional logic needs to be added.

Opened issue #208, which aims to move the Pagination structure to its own component.

This PR got "emergency merged" to provide the functionality needed for the live demo. It was added in the list at #214 for PRs that need readability re-review.


PLC.eraseTerm is overly constrained to non-debruijn Terms

The eraseTerm function is very simple (as it ought to be), by removing any
ast info that contains types.
Previously this eraseTerm it was broken for DeBruijn terms so we decided to constrain this function to non-debruijn terms, by requiring HasUnique name TermUnique
https://github.com/IntersectMBO/plutus/blob/d99ba339726530873ea126b291983c6f2677986b/plutus-core/plutus-core/src/PlutusCore/Compiler/Erase.hs#L8-L16
Previosly, if the input TPLC.term is in debruijn (level or index) format, then
the resut Var nodes in the UPLC.Term output would end up having sparse debruijn levels or indices.
E.g.
λχ Λα. χ in our de bruijn is λ. Λ *. 2 , but after erase
it would end up:
erase (λ. Λ *. 2)  === λ . 2
whereas the result should be instead λ.1
Solutions to unconstrain it:

make PlutusCore.DeBruijn functions use two separate universes with two separately counting debruijn levels (this has the extra small benefit of having smaller ints at the uplc ast, and thus flat could potentially compact it even more).
make a special erase for DeBruijn which would keep a reader counter and decrement the counter at self-recursion and decreement the Var levels/indices accordingly.

@michaelpj ' comment on this:

June 22, 2021 at 3:27 PM
There's a more general problem that lots of program transformations are invalid if you're using indices, since you can't move around terms with indices without adjusting them.
I'd be tempted to do something like: add an IsRelocatable name empty class, provide an instance for everything except indices, and require it for transformations that move things around.

make PlutusCore.DeBruijn functions use two separate universes with two separately counting debruijn levels (this has the extra small benefit of having smaller ints at the uplc ast, and thus flat could potentially compact it even more).

I strongly believe that this is what we should do.


Update Android Studio components.

The debug build is working as expected (hurray!) with JDK 11 and API 28.
With these updates, I think the adjustment in #3079 is no longer necessary.
(@zulipbot add "area: Android")

The build is working from Android Studio and failing on the command line.
Here's the error message on my machine:
Building and installing the app on the device (cd android && ./gradlew installDebug)...

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine java version from '11.0.1'.

And here's the error output from Travis:
Checking the license for package Android SDK Build-Tools 28.0.3 in /usr/local/android-sdk/licenses
Warning: License for package Android SDK Build-Tools 28.0.3 not accepted.

<==-----------> 15% CONFIGURING [9s]FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':@remobile_react-native-toast'.
> Failed to install the following Android SDK packages as some licences have not been accepted.
     build-tools;28.0.3 Android SDK Build-Tools 28.0.3
  To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
  Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html

  Using Android SDK: /usr/local/android-sdk

The UX here is kind of obnoxious, but I think this error message is telling you how to fix it:

To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.

Try doing that?

I think that error message isn't exactly applicable in this context, since it's appearing only on the Travis CI build. I'm looking at https://docs.travis-ci.com/user/languages/android/#ci-environment-for-android-projects and to figure out if any tweaks to .travis.yml might be a fix!

Pinging @gnprice! The Travis build is passing.

Thanks @jackrzhang ! And it builds for me.
From those release notes:

3.2.1 (October 2018)
With this update, you no longer need to specify a version for the SDK Build Tools. The Android Gradle plugin now uses version 28.0.3 by default.

So I think we can actually drop the buildToolsVersion line? (But we'll want to keep those lines you added to get Travis to provide those build tools.) I'll quick try it out.

Yep, that seems to work. I'll merge with that additional change.

Sounds good!

And merged -- thanks again!


Subject appear twice

Expected behaviour
In Settings / Global settings / Display, i've plugged "Correspondent above subject".
Actual behaviour
Correspondent disappear, and the subject appear twice.
Steps to reproduce
Environment
K-9 Mail version:
5.010
Android version:
5.1
Account type (IMAP, POP3, WebDAV/Exchange):
Gmail, IMAP
UP: sorry for the last issue in french, i've just made it too fast, was thinking of french dev...
Thanks for anderstanding, nothing against you.

Here's a screenshot with "Correspondent above subject" enabled:

And here's one with the setting disabled:

As you can see, with the setting disabled, the subject is just repeated at the start of the preview, where I'd now expect to see the correspondent appear.

This only happens when switching the setting and returning to the message list. The list will be displayed properly if the message list screen is closed and reopened.

This should be fixed in recent beta versions (5.7xx).


Stripe account plugin

Plugin Implemented,
variant-x override under pricing section
after account created, you can select on pricing section dropdown for the stripe account.

Closing as we migrated this to API version.


Update google.golang.org/grpc and github.com/golang/protobuf

google.golang.org/grpc v1.38.0 is used by Kubernetes since
https://github.com/kubernetes/kubernetes/pull/100488.
Signed-off-by: Kazuyoshi Kato<EMAIL_ADDRESS>

TestContentClient has been flaky (see #4927 and #5430).

Hi, I'm curious about this change. Does it mean containerd is now no longer affected by https://github.com/containerd/ttrpc/issues/62 ?

This PR forgot to sync go.mod in integration/client/go.mod, so the new protobuf is not tested during intergation test. I try to run the integration in my repo https://github.com/zhsj/containerd/commit/0fa92b5ce9a34b3b916f0713d75bfc22c4bf6a7d and it seems the test fails. However the log doesn't give any useful message, so I'm not sure if it's related to protobuf updates.

Also curious if this won't have side effects

This PR forgot to sync go.mod in integration/client/go.mod, so the new protobuf is not tested during intergation test.

Ah, sorry. #5623 will address that (thanks @dims!).

Does it mean containerd is now no longer affected by containerd/ttrpc#62 ?

I believe these replace directives (github.com/gogo/googleapis and google.golang.org/genproto) are the workaround we have for the issue. Let me confirm.
https://github.com/containerd/containerd/blob/c07711c8c05bd0a86f57216b214044ee4712f585/go.mod#L76-L80

The github.com/gogo/googleapis looks like it's redundant (v1.3.2 is their latest release), but perhaps the genproto one is related (?)
I'm mostly concerned about making sure we remain backward compatible with (older) clients; I'm not very familiar with the issues, but I know there were some hairy situations, and want to be sure existing clients don't break in unexpected ways when using the containerd API (otherwise it would require a major version update of the containerd API).

We embed containerd and Kubernetes in a single binary in k3s, and we're running into containerd/ttrpc#62 after updating Kubernetes to 1.22, as it requires grpc v1.32.0 or newer. It seems like someone needs to bite the bullet on updating ttrpc to modern grpc?


Writing asynchronous checkpoints

Currently checkpoints are not written asynchronously in Flax, which means that by default, the program waits with execution until the checkpoint is saved. Writing a checkpoint asynchronously should be as simple as launching a new thread on a function that saves the checkpoint:
pool.apply_async(checkpoints.save_checkpoints, (ckpt_dir, optimizer, step))

Important: copy optimizer to CPU before calling apply_async, otherwise it may happen that you need 2x TPU memory to store parameters, if you are training the model while transferring data (asynchronously) from TPU->CPU.
Users have argued that it may be worthwhile to just add a utility function that does this to make sure it is done right.

@marcvanzee Hi! Can I work on this issue? If so, anything in particular I should be aware of? (Apart from the details mentioned in your comment above).

@marcvanzee Hi! Can I work on this issue? If so, anything in particular I should be aware of? (Apart from the details mentioned in your comment above).

Hi @ayush-1506, definitely, please give it a try! Thanks for picking this up.

@marcvanzee Thanks! I'm wondering what the API should look like over here: We want to continue training while also saving the checkpoints, since these two are independent of each other. Ideally the user could spawn a new process that saves the checkpoint, but this is going to be manual. What kind of a utility function are we looking at over here? (What should this look like?)

Actually, thinking about this some more, I think writing a utility function that writes the checkpoint asynchronous safely would require a full copy of the parameters, which seems a like a bad idea. Otherwise, as you say, we should somehow disallow modifying the parameters, but I'm not sure if there is a clean solution for this.
So on second thought I'd actually be somewhat hesitant to implement this as a standard utility function into Flax. @jheek, @levskaya: any thoughts?

Generally you want to copy the params from device to host in the main thread (to avoid OOM). Then use a async thread to do the serialisation & IO. It's mostly safe there is just the one edge case where you should block the save_checkpoint if the previous one is still busy.


[WIP] Official document

Description
Please describe your pull request.
Issue ticket number
closes #52
Additional Context

Codecov Report
Base: 92.60% // Head: 92.60% // No change to project coverage :thumbsup:

Coverage data is based on head (2010620) compared to base (4cbc840).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #90   +/-   ##
========================================
  Coverage    92.60%   92.60%
========================================
  Files          259      259
  Lines         3798     3798
  Branches       481      481
========================================
  Hits          3517     3517
  Misses         185      185
  Partials        96       96

Flag
Coverage Δ

build
94.90% <ø> (ø)

cli
89.38% <ø> (ø)

core
92.99% <ø> (ø)

extension-dbt
97.43% <ø> (ø)

extension-debug-tools
98.11% <ø> (ø)

extension-driver-duckdb
100.00% <ø> (ø)

extension-driver-pg
94.87% <ø> (ø)

integration-testing
96.15% <ø> (ø)

serve
90.38% <ø> (ø)

test-utility
∅ <ø> (∅)

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

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


Monitoring emails

It seems that when FREME NER fails we get a notification email for each e-Service. We should receive only one email in this case.

Today I ran software updates on our servers. It also installed a new version of Zabbix. When taking a look at the monitoring emails please take a quick look if Zabbix still works.

still plenty of mails are send when some service is down.

@ArneBinder will fix it early next week.

whats that status of this?

We are working on it

I have checked all triggers, there are no unwanted dependencies.
So I set the timeouts to 60 sec and increased the amount of retries. I hope this will help.

Arne please try to direct to the URL of FREME dev to a page that you can control, e.g. on FREME dev. Then delete the page and see if you get the the problem described above.

Last week we wanted to run an update of Zabbix which did not work out. Right now the zabbix server is running but the frontend does not work. Will fix this soon.

I updated the frontend also and now it seems to work. We get no monitoring emails but I think this is a configuration issue. The implementer of this task is absent right now so we will work on this task not before the 2nd week of april.

Milan got no monitoring emails because he was not configured in the email recipient list. This is fixed now.
Monitoring works better now. After the trigger times have changed we get way less error reports so we think we get less false errors.
@ArneBinder will prepare logging until the next release and during the release we will switch off freme ner and see how the logging behaves.

I just received an email that there was problem with Tilde's e-Translation. However, I should be subscribed only to e-Entity and e-Link.

I just received an email that there was problem with Tilde's e-Translation. However, I should be subscribed only to e-Entity and e-Link.

We will need some time to st this up because we have so much other things on the stack right now. When you want to receive only certain mails then you should setup a filter in your client that sorts all other monitoring emails in the trash bin.

Increased the zabbix logLevel to log the sent requests (see https://www.zabbix.com/documentation/3.0/manual/web_monitoring#extended_monitoring).

This should be fixed. There were templating issues and some macros were not replaced with the correct values, so just freme-ner and the external services were queried. But there is this bug.


[Top Bar] Foundation Site 6.2.1 NOT WORKING AS ADVERTISED

How can we reproduce this bug?

CREATE index.html file and put in your code as follows ...

a) take your recommended code from here --> http://foundation.zurb.com/sites/docs/installation.html "HTML Starter Template"
(see 1st attached image: 'Github - Top Bar issue - 1 - HTML starter template code.jpg') and then
b) take your recommended from here --> http://foundation.zurb.com/sites/docs/top-bar.html "Basics" (see 2nd attached image: 'Github - Top Bar issue - 2 - Top Bar Basics code.jpg') ...
c) combined, the code will look simply like what you see in the 3rd attached image: 'Github - Top Bar issue - entire HTML code.jpg'.
d) Finally, Firefox displays the HTML file as you see in the 4th attached image: 'Github - Top Bar issue - 4 -  Resulting Page in Firefox NO DROPDOWN.jpg' ... and sadly ... THERE'S NO DROPDOWN (highlighted for effect). Mind you, note the 'magical' addition of  ' ="" ' {equals/quotation/quotation} right after ' data-dropdown-menu ' ... could those three characters, magically inserted, be the issue here???! If so, what's a guy to do about this?
What did you expect to happen?
I expected to see a dropwdown menu.
What happened instead?
No dropdown menu and the magical appearance of ' ="" ' (see above)
Test case:
Give us a link to a CodePen or JSFiddle that recreates the issue.
I'm unable to comply with your request as I'm not (yet) that advanced. ["Sorry bout that." -Hagrid]

CodePen with Foundation 6 and MotionUI
CodePen with Foundation 6, Flexbox grid and MotionUI

I think the issue is not having the correct URL referenced to the foundation.min.js. As you can see in your directory structure the foundation.min.js is located in js/vendor/ directory.
So the correct script for referencing the foundation.min.js is:
<script src="js/vendor/foundation.min.js"></script>

Instead of
<script src="js/foundation.min.js"></script>

Also, please check the console tab for any 404 resources that are related to Foundation.
I hope that helps.

Brilliant! Thank you SO MUCH!!!
I have to run, but will be back.


i want build login page, How to set css style same as chainlit?

i want build login page, How to set css style same as chainlit?
any example?

You can reuse the css files of the Chainlit frontend, or customize the provided login page : https://docs.chainlit.io/authentication/password


Include telegram badge to README.md

There is a way to include our telegram as a badge on github, the library is here
Our group on telegram: https://telegram.me/joinchat/AKDWc0BDOqriD1n-mntRBg

Talking with @cuducos we decided that we don't want to do it right now :)

Just to clarify: the Telegram group is for devs interested in contributing, so the CONTRIBUTING.md is the proper place for the link (and there it is, in the very first paragraph). No need to call more attention repeating it in the general-public README.md.


[BUG] Incompatible with Combat Utility Belt

Module Version: v3.2.23
Describe the bug
When Combat Utility Belt is installed, with or without Enhanced Conditions enabled, mounting sends the error: Enhanced_Condititions.HasCondition.Failed.NoMapping and the error keeps calling until it is dismounted.
To Reproduce
Steps to reproduce the behavior:

Install Combat Utility Belt and Mount Up!
Mount a token
Errors appear in game and in console

Expected behavior
Errors should not appear.
Browser:
Opera GX
Foundry Version:
9.268
Game System:
DnD5e - 1.6.3
Additional Info:
It seems like the Mount Up is trying to remove a condition that doesn't exist. I've played with all the settings I could find in Mount Up to stop calling for conditions and I cannot find anything. This happens with or without Enhanced Conditions enabled in Combat Utility Belt, so I don't think it can be fixed on that side, though I tried changing the types of conditions I was using to no avail.

Of course, I uninstalled and reinstalled the Mount Up! Module and it seems to be working fine now. I also instead of from the CubPuter (Combat Utility Belt) disabled and re-enabled Enhanced Conditions from the module settings in case this helps.
It seems that the issue no longer persists after these steps.

@Runesmite sorry to bother i have some problem to replicate the problem, can you click f12 and send a screenshot of the error?
Can i ask you if the problem persist on the browser chrome ?


Apply black for the whole dir of 'tools'

This change:

applies black format for the whole dir of 'tools' with all the scripts there.
adds make format to apply black changes.
makes make black print out what code changes it would suggest (instead of "Oh no! 1 file would be reformatted. But I won't tell you how". Might not be an exact quote but it feels this way)

/test all

/test all

/cc @nmagnezi

/cc @omertuc

/lgtm


ci: run docs prerelease script when creating release

Current dependencies on/for this PR:

main

PR #2213   👈

This comment was auto-generated by Graphite.


Various fixes in java.net.URI

Noticed these when using URI and then running tests from Apache Harmony which is licensed under Apache License 2.0.

I will squash recent minor commits when PR is good to go.

What's the status of this PR?

The last CI error seems spurious, and I could not rerun so leavee it.
I will update per your request to avoid using Scala collections.

Updated and CI passes.


Add Start a Business intervention test

Adds logic to show users the correct page based on how many SaB pages they've seen in their session
Have checked that this works as desired. The desirable behaviour is:
Should give users a cookie ABTest-start_a_business_segment which logs which segment they're in.
When they first visit a SaB page (defined in the extra yaml file and assuming they accept additional tracking cookies):

all users start in segment A
The rendering app is sent 2 headers, one defining whether the page is a SaB page, the other defining their segment (here: A)
They are then given a cookie with a value of B, to indicate that they've visited one SaB page and that on the next SaB page request, they're in the B segment
This cookie has an expiry time of 30 mins so that they are put back into the A segment after the session is expired
All page requests where they already have the cookie will have the cookie reset with another 30 minute expiry time - so that the expiry time is re-started on every request

When users visit another SaB page with the B segment:

they are shown the B variant (with the banner)
The cookie is again reset on every page request with an additional 30 minutes

If the user visits a SaB page with ?hide-intervention=true  query parameter (which is included in a link in the banner to hide the banner), or they visit the SaB checker (/next-steps-for-your-business)

They are moved to segment C (which doesn't show the banner)
The cookie has an expiry time of approx 6 months (significantly longer than the A/B period) so that they won't be shown the intervention even if they start a new session

So just to check:
Where you say

All page requests where they already have the cookie will have the cookie reset with another 30 minute expiry time - so that the expiry time is re-started on every request
is when a user has a B variant?

Once a user is on the C variant, there is no way they will go back to an A or B variant for the next six months?

So just to check:
Where you say
* _All page requests where they already have the cookie will have the cookie reset with another 30 minute expiry time - so that the expiry time is re-started on every request_

is when a user has a B variant?
Once a user is on the C variant, there is no way they will go back to an A or B variant for the next six months?

Thanks for your comments, I believe I've fixed those all now. To answer your questions:
yes, the A/B variant cookie expiry is 30 mins - so that if they start a new session they start afresh
Without deleting their cookies, no, there is no way back to A or B once they've been in C - we chose to do this because you can only end up in C if you choose to hide the banner or go to the actual checker that we're linking to - in which case it would be annoying to continue to see the banner. If we run another A/B within 6 months we'll have to use a slightly different cookie name


Update clang format in build md

Description
Refresh clang-format information.
A small regression was created with this commit
https://github.com/KhronosGroup/Vulkan-Samples/commit/6076d7403e557f8e2f741ad02147b50d133e2d0a
Variable AfterCaseLabel, was added in clang-format-9, so it is not supported by version 8
General Checklist:
Please ensure the following points are checked:

[ ] My code follows the coding style
[ ] I have reviewed file licenses
[ ] I have commented any added functions (in line with Doxygen)
[ ] I have commented any code that could be hard to understand
[ ] My changes do not add any new compiler warnings
[ ] My changes do not add any new validation layer errors or warnings
[ ] I have used existing framework/helper functions where possible
[ ] My changes do not add any regressions
[ ] I have tested every sample to ensure everything runs correctly
[ ] This PR describes the scope and expected impact of the changes I am making

Note: The Samples CI runs a number of checks including:

[ ] I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
[ ] My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions

Sample Checklist
If your PR contains a new or modified sample, these further checks must be carried out in addition to the General Checklist:

[ ] I have tested the sample on at least one compliant Vulkan implementation
[ ] If the sample is vendor-specific, I have tagged it appropriately
[ ] I have stated on what implementation the sample has been tested so that others can test on different implementations and platforms
[ ] Any dependent assets have been merged and published in downstream modules
[ ] For new samples, I have added a paragraph with a summary to the appropriate chapter in the samples readme
[ ] For new samples, I have added a tutorial README.md file to guide users through what they need to know to implement code using this feature. For example, see conditional_rendering

Merging with 3 approvals


Fix for RBAC to deny modification of catalog items, when user has view permission only

The basics of the PR is the same as https://github.com/ManageIQ/manageiq/pull/3114 but contains also merged product features according to Dan's comment.
My intension with the create new PR is that I'm removing the before_filter call from catalog_controller and I'm not sure if this action is wanted.
Anyway I found also other features could be merged (i.e. edit Button/Button Group, remove Button/Button Group). And I also found that some of the hash items of the CATALOG_X_BUTTON_ALLOWED_ACTIONS could be removed as they're not used.

@h-kataria According to your advice, I was able to merge the product features, but the victim of the merging is removal  before_filter :check_privileges hook from catalog_controller
@dclarizio @h-kataria please review

marking this PR as WIP, it's still not doing the right thing, we shouldnt need to remove before_filter call from catalog_controller

@jzigmund you can follow the approach i took in https://github.com/ManageIQ/manageiq/pull/3919 to use common feature id for 2 buttons.

@h-kataria updated PR, merged product features(w/o removing the hook 'check_privileges'), please review.

@jzigmund can you rebase your branch, "rbac_common_feature_for_buttons" method has been moved to application_helper so that can be access from controllers as well as toolbar building code.

@h-kataria rebased, removed that method (imo not needed)

@dclarizio @h-kataria please review

@h-kataria we don't need to whitelist the actions all the time (the same variable common_buttons) before using the rbac_common_feature_for_buttons. Anyway the method doesn't help me when I want to extend the common features. I'd consider of using the method in future extension of common features/buttons.

@h-kataria rebased, please review.

@h-kataria rebased, please review

@dclarizio @h-kataria rebased, please review.

@jzigmund i did some testing for this PR this still doesn't seem to be working right. I created a test User with view only Permissions for Catalog Items accordion but i still see Edit/Add buttons when i select Custom Buttons Group or a Button node in the tree. See my screenshots below:
Test role:

I still see Reorder button on Actions folder node:

Buttons are still available on Button & Button group node:

When i click on "Add a new Button" button from button group screen, i get an error(didnt try other buttons):
[----] I, [2015-10-09T09:44:19.796386 #11093:e87998]  INFO -- : Completed 200 OK in 1008ms (Views: 0.3ms | ActiveRecord: 15.9ms)
[----] I, [2015-10-09T09:44:23.169868 #11093:e87998]  INFO -- : Started POST "/catalog/x_button/1000000000051?pressed=ab_button_new" for <IP_ADDRESS> at 2015-10-09 09:44:23 -0400
[----] I, [2015-10-09T09:44:23.231927 #11093:e87998]  INFO -- : Processing by CatalogController#x_button as JS
[----] I, [2015-10-09T09:44:23.232164 #11093:e87998]  INFO -- :   Parameters: {"pressed"=>"ab_button_new", "id"=>"1000000000051"}
[----] F, [2015-10-09T09:44:23.291494 #11093:e87998] FATAL -- : Error caught: [ActionController::RoutingError] invalid button action
/home/hkataria/dev/manageiq/app/controllers/catalog_controller.rb:52:in `x_button'

@jzigmund can you also add some spec tests to support your changes.

@h-kataria @martinpovolny please review, all issues should be solved.

@h-kataria : your comments resolved?
@jzigmund : please, rebase

@jzigmund @h-kataria @martinpovolny is this PR a WIP or ready for final review?

@martinpovolny i will test in UI to verify if reported issues are resolved.

@chessbyte proper PR (fix for BZ) + merged product features + small code adjustment .. at the beginning the PR was bugfix only ..
@martinpovolny please do, thank you.

rebased

@jzigmund i am logged in as admin, i seeded MiqProductFeature, but for some reason i am seeing no toolbar buttons on Catalog Items accordion to add/edit Catalog Items.

am i missing something?

@h-kataria thank you for review, fixed the issue, rebased the PR's branch. Please review again.

or @martinpovolny @skateman @himdel in case you have a time, thank you.

@jzigmund can you add some specs which are failing on master and passing in this branch?

@jzigmund i am logged in as admin and for some reason first time i went to catalog items accordion(thru replace_right_cell) it didn't show toolbar buttons until i refreshed the screen, after that, when i press "Add a button" button that blows up with error:
***** MIQ(catalog_controller-group_update): Session object size of 82.4 KB exceeds threshold of 50 KB
[----] I, [2015-11-12T19:14:50.657014 #21578:bfd998]  INFO -- : Completed 200 OK in 181ms (Views: 0.1ms | ActiveRecord: 8.0ms)
[----] I, [2015-11-12T19:14:52.407393 #21578:bfd998]  INFO -- : Started POST "/catalog/x_button/10000000000101?pressed=ab_button_new" for <IP_ADDRESS> at 2015-11-12 19:14:52 -0500
[----] I, [2015-11-12T19:14:52.432264 #21578:bfd998]  INFO -- : Processing by CatalogController#x_button as JS
[----] I, [2015-11-12T19:14:52.432340 #21578:bfd998]  INFO -- :   Parameters: {"pressed"=>"ab_button_new", "id"=>"10000000000101"}
[----] F, [2015-11-12T19:14:52.463219 #21578:bfd998] FATAL -- : Error caught: [ActionController::RoutingError] invalid button action
/home/hkataria/dev/manageiq/app/controllers/catalog_controller.rb:58:in `x_button'

@jzigmund i still see toolbar buttons for test user that only has view access to Catalog Item accordion, with fix in this PR user should not see these buttons if they only have view access to Catalog Items correct? see attached screenshots:

@jzigmund Need to address comments from @h-kataria

Closing this PR in favor of https://github.com/ManageIQ/manageiq/issues/6353


Make the argument to init optional in the Typescript declaration too

Pull request #1579 made the argument to the generated init() function optional (when the target is "web"), but not in the .ts.d file. This brings the two back in sync.
Tested locally, using a .ts file that mostly contains the same code the "without a bundler" example includes in its index.html.

Seems reasonable to me, thanks!


WIP Initial datafile datatypes

Description
Related Issue
Testing
Signed-off-by: Mairi Dulaney<EMAIL_ADDRESS>

Closing to be reopened against a feature branch.


Could you please export the "mandatory abstract" deadlines with the Google Calendar URL?

@abhshkdz Thanks for the great work! I use the google calendar url here to keep track of conference deadlines, I missed the AAAI abstract deadline and it'd be really great if you can also add the mandatory abstracts deadline to the Google calendar, many thanks!

Thanks for the suggestion; hopefully https://github.com/abhshkdz/ai-deadlines/commit/a4cb0838aa470fb2031497bf5344dcbc88a2f623 fixes it.

Thank you so much! I see this fixed the .ics file import option, but the google calendar link doesn't seem to include the abstract deadline. I tested importing the .ics file and it works fine, but adding the google calendar from the url doesn't work.

It takes a while for Google Calendar to trigger updates to external calendars.
I see it at my end now; could you check again please? If it doesn't show up, maybe try removing and re-adding the calendar.

It's working now, thank you so much!


Uperf scale mode code changes

Description
Code changes for uperf scale mode. These code changes contain a uperf-scale role altogether separate from the existing upef workload.
Context: https://github.com/cloud-bulldozer/benchmark-operator/pull/525
Testing
Sample CR
apiVersion: ripsaw.cloudbulldozer.io/v1alpha1
kind: Benchmark
metadata:
  name: uperf-scale-benchmark
  namespace: benchmark-operator
spec:
  clustername: myk8scluster
  elasticsearch:
    url: https://search-perfscale-dev-chmf5l4sh66lvxbnadi4bznl3a.us-west-2.es.amazonaws.com:443
  workload:
    name: uperf-scale
    args:
      hostnetwork: true
      serviceip: true
      servicetype: "nodeport"
      networkpolicy: true
      multus:
        enabled: false
      samples: 1
      kind: pod
      test_types:
        - stream
      protos:
        - tcp
      sizes:
        - 16384
      nthrs:
        - 1
      runtime: 30
      colocate: true
      density_range: [1, 5]
      node_range: [1, 5]
      step_size: add1

Tested for all possible scenarios. Below are the uuids to check in ES cluster here.
6807088c-f59c-5dd8-a9cc-4b43bfff4f4c - Scale mode without service
0628446a-2571-5ff2-9482-6f5c08032f5a - Scale mode with clusterip service
98ae3edc-944d-5bec-8f4b-9b807ca768e0 - Scale mode with nodeport service
3be3d070-562b-5942-b2a5-450483ed8926 - Scale mode with network policy
2647411c-c40a-58a2-8ee1-c1122d4d65d5 - Scale mode with resources
And also verified the results in the client pod using the below script. The below script can also be used for verification on the reviewers side as well.
echo -n "`oc get all | grep -i -e 'completed' | cut -f 1 -d ' '`" > output.txt

cat output.txt | awk '{print $0}' | while
	read each
do
	echo "client name: $each"
	echo "client info"
	echo -n "`oc get $each -o yaml | grep -i -e "clientfor" -e 'port' -A 2`"
	echo -e "\n"
	echo "client logs"
	echo -n "`oc logs $each | tail -n 5`"
	echo -e "\n\n"
done

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@42582ad). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #776   +/-   ##
=========================================
  Coverage          ?   53.47%
=========================================
  Files             ?        8
  Lines             ?      331
  Branches          ?        0
=========================================
  Hits              ?      177
  Misses            ?      154
  Partials          ?        0

Flag
Coverage Δ

gha
53.47% <0.00%> (?)

python-3.9
53.47% <0.00%> (?)

unit
53.47% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Update renovatebot/github-action action to v34.128.3

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
patch
v34.128.0 -> v34.128.3

Release Notes

renovatebot/github-action
v34.128.3
Compare Source
See the the changelog for changes in all releases.
34.128.3 (2023-02-10)
Bug Fixes

deps: update renovate/renovate docker tag to v34.128.3 (54d60da)

v34.128.2
Compare Source
See the the changelog for changes in all releases.
34.128.2 (2023-02-09)
Bug Fixes

deps: update renovate/renovate docker tag to v34.128.2 (7cc520e)

v34.128.1
Compare Source
See the the changelog for changes in all releases.
34.128.1 (2023-02-09)
Bug Fixes

deps: update renovate/renovate docker tag to v34.128.1 (384eebf)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Branch automerge failure
This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


feat: [#4446] Azure Blob Storage should support Identity authentication

#minor
Description
This PR allows using the MSI authentication for Azure Blob Storage.
Specific Changes

Added a new option in the constructor with the necessary parameters for creating the blob storage client using a msi credentials.

Testing
The following image shows the new validations and unit test passing.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

12 of 13 (92.31%)  changed or added relevant lines in 1 file are covered.
82 unchanged lines in 5 files lost coverage.
Overall coverage increased (+0.002%) to 84.505%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/botbuilder-azure-blobs/src/blobsStorage.ts
12
13
92.31%

Files with Coverage Reduction
New Missed Lines
%

libraries/botbuilder-lg/src/templateExtensions.ts
1
84.48%

libraries/botframework-streaming/src/utilities/createNodeServer.ts
1
78.57%

libraries/botframework-streaming/src/namedPipe/namedPipeServer.ts
12
50.68%

libraries/botframework-streaming/src/namedPipe/namedPipeClient.ts
17
34.09%

libraries/botframework-streaming/src/namedPipe/namedPipeTransport.ts
51
3.92%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
20035

Relevant Lines:
22474

💛  - Coveralls

/promoted 4486


Needs a screencast demo

Hax to get a file onto github to hotlink from the readme 😺

Fixed by https://github.com/joho/pico8-vscode/commit/b0f1d3952c163983f3b4ae19b8bb75a74e38b3c9


Fix(svg parent): svg.js no longer has .parent but was changed to pare…

…nt()

Waiting for rewrite.


react-native run-ios --simulator without empty spaces

🐛 Bug Report

React Native is unable to launch apps on an iOS simulator instance if its name does not contain any empty spaces.
To Reproduce

create an iOS Simulator instance with a name that does not contain any empty spaces (e.g. aSimulator)

xcrun simctl create aSimulator com.apple.CoreSimulator.SimDeviceType.iPhone-SE com.apple.CoreSimulator.SimRuntime.iOS-12-1

create a new React Native app
Lanch the app created in the second step on the iOS simulator instance created in the first step.

react-native run-ios --simulator="aSimulator"

Output
react-native run-ios --simulator="aSimulator"
Found Xcode project themoviedb.xcodeproj

Cannot read property '2' of null

TypeError: Cannot read property '2' of null
    at findMatchingSimulator (/Users/matax/Developer/ReactNative/themoviedb/node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js:34:26)
    at resolve (/Users/matax/Developer/ReactNative/themoviedb/node_modules/react-native/local-cli/runIOS/runIOS.js:147:31)
    at new Promise (<anonymous>)
    at runOnSimulator (/Users/matax/Developer/ReactNative/themoviedb/node_modules/react-native/local-cli/runIOS/runIOS.js:134:10)
    at Object.runIOS [as func] (/Users/matax/Developer/ReactNative/themoviedb/node_modules/react-native/local-cli/runIOS/runIOS.js:106:12)
    at Promise.resolve.then (/Users/matax/Developer/ReactNative/themoviedb/node_modules/react-native/local-cli/cliEntry.js:117:22)

Expected Behavior

React Native should launch apps on iOS simulator instances regardless of their name.
Environment

  React Native Environment Info:
    System:
      OS: macOS 10.14.3
      CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
      Memory: 3.89 GB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 11.10.1 - /usr/local/bin/node
      npm: 6.7.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
      Android SDK:
        API Levels: 26, 27, 28
        Build Tools: 28.0.3
        System Images: android-28 | Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.3 AI-182.5<IP_ADDRESS>14842
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.3 => 16.6.3
      react-native: 0.58.6 => 0.58.6
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native-git-upgrade: 0.2.7

Hello there 👋
Could you try with the latest RN version 0.59.x? If the issue persist, can you post an issue into https://github.com/react-native-community/react-native-cli ? (CLI has been extracted).


fix: reframed a sentence

The sentence was a little too 'some' I made it little less 'some'
-  If you are still interested some lines below there are some instructions for migrating from the old particles.js
+ If you are interested there are some simple instructions just below to guide you to migrate from the old particles.js

Hey @matteobruni can you tell me what happened to my PR #2194
I am still unclear what happened here

I changed the target branch and merged there, I'm preparing 1.34.1 on the new target branch so I needed this PR there


mpd 0.20 has a crashing bug - 0.20.4 has the fix.

Issue description
MPD 0.20 crashes with error:
mpd: src/filter/plugins/ChainFilterPlugin.cxx:58: void ChainFilter::Append(const char*, Filter*): Assertion `out_audio_format.IsValid()' failed.

Steps to reproduce

Ensure mpd server is running
Try to play using any method
mpd crashes

See:
https://bugs.musicpd.org/view.php?id=4618
Technical details

System: NixOS: 16.09
Nix version: 1.11.6
Nixpkgs version: 17.03pre99759.f66d782

Want to make a pull request? We can also back port the fix to stable.

@fpletz: Thank you.  @Mic92: Will do a PR next time around.  :+1:


Extend NamedOperations to accept new types of parameter

This was originally tacked onto another issue, but should be handled separately:
"I think it is worth thinking about how parameters that are not int, str, or bool are actually passed. It feels weird (to me) that you cannot pass a Long parameter into a named operation."
Identify whether there are any other input types that NamedOps should accept and add them.

You can have Long parameters, as well as doubles, floats and other Java types. There is even an example using a Long in the documentation and in the tests:
https://github.com/gchq/Gaffer/blob/3ed00784f19e6b11daba65007ad94d9328c70f24/core/graph/src/test/java/uk/gov/gchq/gaffer/graph/hook/NamedOperationResolverTest.java#L188

@n3101 I can see the json and python examples in the doc:
"param1" : {
    "description" : "Limit param",
    "defaultValue" : 1,
    "valueClass" : "java.lang.Long",
    "required" : false
}

@t92549 Well I see this java example:
Map<String, Object> paramMap = Maps.newHashMap();
paramMap.put("param1", 2L);
final NamedOperation<EntityId, CloseableIterable> operation =
new NamedOperation.Builder<EntityId, CloseableIterable>()
.name("2-hop-with-limit")
.input(new EntitySeed(1))
.parameters(paramMap)
.build();
if I toggle to see  the corresponding full json I get:
{
"class" : "uk.gov.gchq.gaffer.named.operation.NamedOperation",
"input" : [ {
"class" : "uk.gov.gchq.gaffer.operation.data.EntitySeed",
"class" : "uk.gov.gchq.gaffer.operation.data.EntitySeed",
"vertex" : 1
} ],
"operationName" : "2-hop-with-limit",
"parameters" : {
"param1" : 2
}
}

Those examples are equivalent, they just look a bit different due to the differences in Java and json.
Although there is a strange bug where "class" : "uk.gov.gchq.gaffer.operation.data.EntitySeed", is shown twice in the json

@t92549 Ok, I think this is a doc issue. I see that it is already covered by https://github.com/gchq/gaffer-doc/issues/156 (point 4)


MacOS: Support fullsize content (no titlebar, but window controls)

fullsize_content: false

fullsize_content: true

Very cool! I guess it is up to the user to add some space for the close buttons in the top left?

Very cool! I guess it is up to the user to add some space for the close buttons in the top left?

Yes.

Thanks!


Added logging for user-callback errors

I was having issues tracking my errors raised from within my callback to .insert().
There are two ways to catch this... You can listen to connection.on('parseError', ...), or you can just try-catch. I think the try-catch is a better approach.
I feel that there is more to do here... maybe the user of mongolian-deadbeef should be able to register a callback for callbackErrors for a server/db/connection/cursor.

I agree, but this is really a problem with mongodb-native—it's catching exceptions where it probably shouldn't. It should be avoided with the new buffalo branch. It also should be fixed with the connection2 branch. Could you try those two out and see if they work the way you desire?

Also, not sure why require('util').inspect(error) is called on line 227. If the error is an exception, error.stack won't be logged that way.

Sure.
Gotta head out for a bit, but can you tell me what the two branches are for? (I know you wanted to remove the mongodb-native dependency, but what's the other one?)
Also, have you read this? (https://jira.mongodb.org/browse/SERVER-2141) If 10Gen wants to create an official mongodb driver that feels like the mongodb console, perhaps they are duplicating your work. I would get in touch with them if you haven't already.

Jae

On Dec 24, 2011, at 5:38 PM, Marcello Basta-Forte wrote:

I agree, but this is really a problem with mongodb-nativeit's catching exceptions where it probably shouldn't. It should be avoided with the new buffalo branch. It also should be fixed with the connection2 branch. Could you try those two out and see if they work the way you desire?

Reply to this email directly or view it on GitHub:
https://github.com/marcello3d/node-mongolian/pull/69#issuecomment-3269659

There are a few BSON format incompatibilities in Buffalo which makes perfect backwards-compatibility impossible. I need to write some documentation before I merge it to master. I also need to get more people testing the new branch, but I don't have a good way to do that.


How do you fix the position of the dadbatle spotlight event?

Describe your problem here.
I am curently making a mod pack and i desided to use the spotlight event for parts of a song, but when changing the characters the placement of the spotlight gets all weird, so much that you can see where the image ends at the top.

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
In terms of changing the sorce code for the build itself, no

just remake the spotlight event smhsmh

look in the lua script and look for these

if its on there
if not, i dont realy know


Arabic language support

Hello.
I noted that the Arabic isn't supported yet. so I'm willing to add it. Any advice?

In order to support a new language, a list of stopwords is required. Also, it would be nice to have a proper stemmer/lemmatizer for that language but that is much more complex.

Cool, I'll work on it.


Broken release on foundryvtt.com

Hi
There seems to be a broken release (Version 0.3.17) on https://foundryvtt.com/packages/forien-quest-log

These points to a different project for this release:
Installation Link: https://github.com/League-of-Foundry-Developers/foundryvtt-forien-unidentified-items/releases/download//module.json
Update Notes: https://github.com/League-of-Foundry-Developers/foundryvtt-forien-unidentified-items/blob/v0.3.0/changelog.md

@haskjold Thanks for reporting. I too just noticed this very weird push to FQL. I didn't do it and since this is still managed through the league it seems to be a mistake by someone else working on Forien's Unidentified Items and they made a mistake in overwriting the package info for FQL. :O
It is fixed now though and I verified that the download / install completes. I'll close this issue.


User following

Added a route for following, and added prev checking so that the user cant follow someone twice

thanks, i shall work on that as well

Thanks i shall work on that as well


Make plugin data and ports implement and require Send and Sync.

According to the LV2 core spec, nothing prevents hosts to process a block of audio using the plugin in a thread, then process another block in another thread, using the same instance (as long as both do not run at the same time).
I enforced this by requiring and implementing Send on both plugins (on the Plugin trait) and ports structure (and on all port types), so hosts can (virtually) send the instance between threads safely. :slightly_smiling_face:

Oh you're right there, I misunderstood what Sync really meant. Will change it ASAP! :slightly_smiling_face:
I just figured out what you meant by "force-implementing Send/Sync", I guess you meant about InputPort and OutputPort, right? I just noticed they are not needed, I'll remove them.

Oh, you're right there. I messed up while implementing Sync a bit everywhere.
Obviously all port output types must not be Sync, but I'm wondering if it makes sense for input port types to be Sync as well? If not, we could drop the Sync requirement on the plugin's Ports type, considering it is only accessible in the run method anyways.

From my point of view, we could and therefore should drop all Send and Sync implementations: This is very plugin-specific code that however is only used by internal code. And the internal code doesn't move these structures between threads. Therefore, we don't need the Send and Sync implementations.
One could argue that they might be relevant for host-specific code in the future, but I would suggest a different data model for the host side than for the client side; Maybe something like having a pool of buffers from which pointers are sent to plugins. Since these Send and Sync implementations aren't needed for hosts neither, we should drop them.


Add Hash#put_if_absent

Resolves #8660.
This is faster than hash[key] ||= value for two reasons:

If the given key cannot be found, Hash#insert_new will not attempt to match the key against any existing keys at all. (This suggests that find_entry_with_index followed by set_entry or insert_new might be faster than upsert too, which makes #upsert completely unnecessary, but I haven't verified that.)
A missing key goes directly to insert_new, whereas ||= means any existing value must be upcast to a nilable value and evaluated for truthiness first.

Hash-like types such as ENV.class and URI::Params do not have this. For those types it might be better if a generic implementation is offered via #10886.

#put always updates the given key like #[]=, only that it returns a different thing

Too many API options. Why not keep it simple? What's a case where the existing way is too slow?

A little benchmark shows some non-negligible improvement when keys are absent:
          ||=   1.88M (531.95ns) (± 2.12%)  448B/op   1.22× slower
put_if_absent   2.29M (436.61ns) (± 1.55%)  448B/op        fastest

When keys aren't absent, then it's negligible.

Why is there no equivalent API in Ruby, I wonder?

I can only speculate on that... Ruby's Hash API generally seems to be a bit bare. I believe methods like #transform_values and #transform_keys are relatively recent additions (in Ruby's timeline).
Anyway, regardless what Ruby is doing, this method seems to be very reasonable to me. It's optimization effect is basically a no-brainer.
Sure, it adds another tool in the toolcase that you have to know about. But the name is pretty self-explanatory. So I don't think this is bloating the API with unneccessary stuff. It's a useful enhancement.

It is indeed proposed for Ruby in relatively recent times: https://bugs.ruby-lang.org/issues/17342


Incorporate community filtering into pipeline with github auto-checking

Add https://github.com/cccntu/filtersource into our pipeline. Modify https://github.com/bigscience-workshop/data_tooling/blob/master/ac_dc/oscar_sample_filter.py to be able to pick and choose filters created by filtersource.  @cccntu

I think this is low priority until we have many good filters over there that we want to use it.

I think we will be doing basic character based filtering. proportion of non in lang. character is too high. this might benefit from the automatic CLI.


#79 specify docker for docker-maven-plugin.

Fix for #79.

I have read the Dynamic Solutions Individual Contributor License Agreement (CLA) Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA


Depth point clouds extremely slow when zoomed out

Load a depth point cloud (e.g. examples/python/arkitscenes/main.py) and zoom out, so that all the points are in a small portion of the screen. On my M1 MacBook Pro, the performance plummets until it reaches 100ms per frame of GPU time.

#3713 has more details by now


Access cudaMemoryType in the pointer attributes and fix for HIP

The enums cudaMemoryType and hipMemoryType have a nonzero offset...🤦🏻♂ Also, the struct members are misaligned mismatched.

Jenkins, test this please

Jenkins CI test (for commit 20034385dcd90910d50d3cddbeb9a6036ee840e6, target branch master) succeeded!

@emcastillo Failed to backport automatically.

Not cleanly cherry-picked

I created a manual backport #5571.


Antipiracy screen

tonyhax version: tonyhax-v1.4.1
Game name: Saru! Get You! (ape escape)
Game code: SCPS-10091
Executable hash: i don´t know
Triggered at: after the tonyhax interface
Is the console chipped?: Yes
Is it an original disc or a burned copy?: original disc

I've had a look and I can't neither reproduce it on my console neither find the antipiracy on the disc files, so I'm not sure if I'll be able to patch it.

@socram8888 I have a gameshark cheat that can bypass, if you want I can share it.

@qkwyx that'd be helpful to find the antipiracy code, thanks

Saru! Get You!  (NTSC-J)
D0136A8A 1040
80136A8A 1000
Saru! Get You!  (NTSC-J) (Alternative code)
D0136B00 2021
80136AFC FFF6
D0136B00 2021
80136AFE 1000
Saru! Get You!  Playstation the Best (NTSC-J)
D0136AAA 1040
80136AAA 1000
I tested it on my 5501 with a burned copy same as redump.

Tried on my SCPH-102 and I cannot replicate it by any means. I've set a breakpoint on no$psx at 80136A88 (the address that code "80136A8A" indicates there's a conditional branch) and I can't still find any way to replicate it.

I thought the cheat codes can help the cause of it. Anyways, nice setup and thanks for your continuous support on Tonyhax.

Tried on my SCPH-102 and I cannot replicate it by any means. I've set a breakpoint on no$psx at 80136A88 (the address that code "80136A8A" indicates there's a conditional branch) and I can't still find any way to replicate it.
EDIT: For the record, I am using the v1.0 version, with MD5 of 5c70c89355b58111c1fafd050bdeef49.

I think I figured out why you can't see the address being written to. This game appears to only be using the test commands/SCEX counters to test for 'dumb' modchips. No readTOC is being sent or anything like that.
It also appears that unless this test fails (emulators all seem to pass it) then that address won't be written to. That's my theory anyways, I need to figure out how to emulate a dumb modchip really to confirm this I guess. But the AP code is definitely there if you look at the CD commands being sent immeditely before the 'sony computer entertainment inc presents' screen.
The reason most of the AP games are slipping through the original AP patch of Tonyhax is because there are multiple different versions of the AP module. If you notice it seems to be the earliest games with AP that fail.

Send GetSCEXcounters (Gen 1, only can detect dumb modchips)
Send GetSCEXcounters AND readTOC (Gen 2, can detect disc swap/unlock/dumb modchips)

I'm addressing AP in Tonyhax International completely different then what the OG Tonyhax does, so this game will work in the next update. I just figured I'd drop this explanation here ifi anyone finds it useful.

Fixed in 3e140b8a9103897442c2adb4eb6dd27a84479344

Available in tonyhax v1.4.4


Background became transparent in 1.0.4

It seems that something has changed from 1.0.3 to 1.0.4 that turned the solid widget background to transparent. I took these screen shots just by switching between the two versions using Bower:
This is what my 1.0.3 datepicker looked like inside a Bootstrap dialog:

And this is what my 1.0.4 datepicker looked like:

Here's the simple usage:
<input type="text" view="date"
    ng-blur="onDatePicked($event)"
    ng-model="edits.capture_time"
    date-time select-on-click />

The only styling performed:
[date-picker-wrapper] {
  width: 257px;
}

Will fix soon. Thanks

+1

+1


Rename 'get' to 'call'

Sorry to be nit-picky, but I have 'get' hard-wired in my brain to be a scoped accessor. :-/
Conceptually, I think of what you are using 'get' for actually represents call-ing the object to get its value.  If this was ruby, I'd want them to be actual lambdas; but I'm not sure that's a good idea in CoffeeScript.
Is that reasonable?

curious: why should it be a lambda? what would that accomplish?
my hesitation with using call is that in javascript call is something you do to a function to execute it. you can literally use (function() {}).call() to execute a function.
I chose get because it is an accessor. It's the accessor for the plain javascript object that the World wraps

Perhaps I'm confused. Could we use the term 'value' or 'contents' then?
Sent from my iPhone

On Jan 6, 2015, at 20:51, Daniel Ma<EMAIL_ADDRESS>wrote:
curious: why should it be a lambda? what would that accomplish?
my hesitation with using call is that in javascript call is something you do to a function to execute it. you can literally use (function() {}).call() to execute a function.
I chose get because it is an accessor. It's the accessor for the plain javascript object that the World wraps
—
Reply to this email directly or view it on GitHub.

ah, yes. value seems good to me


fix: Handle methodNotAllowed exception for groups

Closes: #849.
Endpoint for fetching groups (all, linked to product) returns 400 bad request for consumption tier.
The change introduces possibility to bypass and return empty result even if groups are not allowed, to continue full extraction.

Could you, please, link an issue \ description to know what is the reason of a PR, thanks!

Could you, please, link an issue \ description to know what is the reason of a PR, thanks!

Sorry, forgot to update.
Updated.

IMO your approach is not the best one: I would just add another call in the start of extractor activity to identify sku of apim service - could you please check, if such an endpoint exists?
So that flow would be:

extractor process triggered
var data = GET apim/service/data (unreal endpoint)
if service's sku is consumption, set it in ExtractorParameters and dont do any calls to unsupported endpoints (like groups)

yes agree, luckly there is such endpoint. thanks for pointing out.

closing the PR since the new approach is completely different.


Changes behaviour of timeout

Hey (no phun intended)
This PR changes the behaviour of timeouts. Instead of checking for timeout on TLSHandshake/dial this sets the timeout for http.Client which includes both. Changed the default value from 0 to 20 and went from ms to s which seems easier to handle for the human using hey.
Not sure if this is the way you want to go, if not you can just ignore this PR. :)
My editor also fixed some trailing whitespaces

I think renaming the binary is a good excuse for such a breaking change :)

Btw, is this your first time contributing to a Google project? If so, could you please review and sign the Google CLA? https://cla.developers.google.com/ to sign.

Signed!

Thanks!

Thank you (and all contributors) for a excellent piece of software. :)