Radial annotator - Confidences

I am in 3i project in production. Every time, I am trying to set up Confidence for a taxon (Browse Nomenclature). It takes about 3 seconds to get Radial annotator to refresh the page and find recently used confidences.
Please optimize the search and refresh the page faster.

I can't replicate.  There is a half second pause.  Does this still exist?  Browser?

most likely this related to the data accumulation in the 3i database. Now the delay is more than 5 sec. It seems that query is not optimized.

I am doing the exact same thing you are, your project,  in production.
On Sun, May 26, 2019, 8:10 AM Dmitry Dmitriev<EMAIL_ADDRESS>wrote:

most likely this related to the data accumulation in the 3i database. Now
the delay is more than 5 sec. It seems that query is not optimized.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SpeciesFileGroup/taxonworks/issues/974?email_source=notifications&email_token=AAAFQSAPE7ATIKVTRZGO463PXKD43A5CNFSM4HL4TN6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWIFPVA#issuecomment-495998932,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAFQSDN5CUPOZ2UPUHN4WDPXKD43ANCNFSM4HL4TN6A
.


Avoid checking in binary wheels

And I'd suggest deleting the current one.

Good finding, thanks 👍


chore: Add flank website code

Fixes #1220
Test Plan

How do we know the code works?

The website workflow (publish_mkdocs_site) passes
The web page under https://flank.github.io/flank/ is properly generated using mkdocs-material

[ ] Change workflow on pull_request to push before merge

Codecov Report

Merging #1222 into master will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #1222      +/-   ##
============================================
+ Coverage     79.69%   79.71%   +0.01%
  Complexity      696      696
============================================
  Files           232      232
  Lines          4314     4318       +4
  Branches        731      731
============================================
+ Hits           3438     3442       +4
  Misses          489      489
  Partials        387      387

@jan-gogo could we do something with a table of contents at the right?
CLI should have 3 subsections (Flank configuration, iOS example, Android example)
CI Integration should not be a subsection of CLI
CircleCI, Bitrise should be a subsection of CI
Other sections should not be a subsection of CLI (except described above) or Download
Resources section is not displayed
WDYT?

I guess, this should be merged soon due to potential conflicts between README.md from master and docs/index.md. Other improvements may be done in further PRs.

I guess, this should be merged soon due to potential conflicts between README.md from master and docs/index.md. Other improvements may be done in further PRs.

I made just one improvement about making subsections of CI

This is nice improvements, so I suggest to change title prefix from chore: to docs: to have it on release notes


Get route name before munging request

This ought to correct a problem where we incorrectly report route names
for admin routes.

This change is

LGMT when green


Cleanup async state when multi-threaded shuffle readers fail

Closes https://github.com/NVIDIA/spark-rapids/issues/10631
We had some reports of file descriptors left open from the multi-threaded shuffle reader, likely due to a wave of other exceptions. I started to look at it and found that it did not handle cases when tasks were cancelled correctly, nor errors such as stream close. I added code in the task completion callback to close out any accumulated future or to-be-processed batch.
I also fixed an issue where we would leak a batch if a stream closes after we materialize the batch, but before we read the next header. I found that one because I was testing this by introducing exceptions manually.
I am going to add a test in RapidsShuffleThreadedReaderSuite shortly.

build

build

build


feat(propagation-utils): end pub-sub process span on promise settled

When promises are returned from a mapping function we now
end the span when that promises resolves rather than doing
so immediately.
This makes sure that the processing span wraps the entirety of the
processing

Which problem is this PR solving?

The pubsub propagation module would end spans prematurely when promises were involved.

An example of what this looks like:

Short description of the changes

Handle promises from mapping functions

Checklist

[ ] Ran npm run test-all-versions for the edited package(s) on the latest commit if applicable.

@nordfjord thank you for the contribution :)
can you please run npm run lint:fix to revert all the linter changes? It will really help to focus on the logical changes while reviewing and make CI happy.
Also please add relevant unit tests for this change. Either in the propagation-utils package or in the aws-sdk instrumentation package which is consuming these utils. Thank you!

Thanks for taking the time to review this. I think this is ready for another review now.

Not quite sure what was going on but I had to remove the --require @opentelemetry/contrib-test-utils part from the package.json test script so that the tests would pass.
I've verified that yarn test works locally now.

catch {} is not supported in node 8. Will merge this after https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1065.


Fix closures again

Closes #934
Oh god, the rules for parsing closures are even more messed up than I thought - whether or not there is an inner block or depends not only on if there are braces, but also if there is a return type for the closure (!) and if there are statements in the block.
r? @marcusklaas

With that branch I know get https://gist.github.com/mcarton/a86a76782e310953a15085d06d182644
By the way, did you notice you had copy-pasted the same closure twice in your tests?

With that branch I know get https://gist.github.com/mcarton/a86a76782e310953a15085d06d182644

Hmm, guess I need to test with the whole input, not just one closure

By the way, did you notice you had copy-pasted the same closure twice in your tests?

The second 'copy' has an extra semicolon, which changes how the closure is parsed

By the way, did you notice you had copy-pasted the same closure twice in your tests?

The second 'copy' has an extra semicolon, which changes how the closure is parsed

Subtle :smile:
Just noticed the new error is in another file (https://github.com/Manishearth/rust-clippy/blob/578cc3dc71134594da58a606acce1ef03883fee3/src/utils/hir.rs) by the way. rustfmt is now happy with the file that originally failed.

Hmm, I can't repro this with just that file, which is interesting and a little disturbing. The problem is obvious and the fix easy, but I'm concerned it isn't isolateable.

ah, it's probably one of the submodules

bah, except there aren't any submodules :-s

It only fail with Clippy’s rustfmt.toml

I can repro on Clippy master. I think with the commit you referenced, it has been formatted already or something?

The file I referenced is different from the one in Clippy master yes

OK, that commit fixes the problem I could find. Hopefully it fixes your branch also.

Yep :tada:


How long does it take to make the newly uploaded blob file be available to all CDN locations?

Assume its a new file. The file No two file in the container has the same name. When I upload this file, how long does it take to make the newly uploaded blob file be available to all CDN locations? I guess it doesn't happen instantly. So what is the exact about of time? Thank you!

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

ID: 38ede72f-b8be-6455-36b8-e891451f42a0
Version Independent ID: f97e246c-4076-c4bb-e1df-34d05edea0fd
Content: Quickstart - Integrate an Azure storage account with Azure CDN
Content Source: articles/cdn/cdn-create-a-storage-account-with-cdn.md
Service: azure-cdn
GitHub Login: @mdgattuso
Microsoft Alias: magattus

we don't proactively push new files to the CDN when they're uploaded. When a request hits a CDN PoP, the CDN checks it's cache to serve the content, if the content is not there or it's TTL is expired it goes and pulls the content from the origin, then caches it and serves it.

@arefinsami, Does that answers your question? Let me know if you have any further questions.

Thank you very much for the quick response. That answers my question.


Invalid config options

Hi! I like the idea of your plugin but it doesn't work that way for me.
I tried your sample code and get the following error:
ERROR   -  Config value: 'plugins'. Error: Plugin value: 'hooks'. Error: Expected type: <class 'dict'> but received: <class 'list'>

My config:
# Plugins
plugins:
  - mkdocs-simple-hooks:
      hooks:
        - on_pre_build: "docs.hooks:copy_readme"

I am using the latest plugin version (0.1.1), mkdocs  1.1.2, python 3.7 64bit
If i debug into your plugin there seems to be something wrong how the hook config value is read:
[{'on_pre_build': 'docs.hooks:copy_readme'}]
> special variables
> function variables
> 0:{'on_pre_build': 'docs.hooks:copy_readme'}
> len():1

Do you know what could be wrong in my configuration? It seems that the codes workes for you?

Sorry wrong github tab. :-(


Fix Affiliation Creation Logic for Entities Requiring Passcode

Description:
Currently, when creating an affiliation, the request fails if the entity requires a passcode and the user does not provide one. This affects users who are not staff, as the current system does not prompt for a passcode. Without a valid passcode, the request is rejected, preventing users from proceeding.
Steps to Reproduce:
Attempt to create an affiliation for an entity that requires a passcode.
Do not provide the passcode in the request.
Observe that the request is rejected.
Proposed Solution:
Implement a check in the frontend/backend to verify if the entity requires a passcode.
Use a GET call to check for the passcode requirement before creating the affiliation.
If a passcode is required, prompt the user to enter it during the affiliation process.
Add a screen or modal for passcode entry.
Alternatively, instruct users to create the affiliation through the business dashboard if there is a passcode exist

@nsmenon8890 This ticket is ready to test, please let me know if you need more detail

Testing completed and working as expected.


Multiple layers torque can be assigned to a map using the wizards

In #2981, we implemented a change that prevents multiple torque layers from being added to a map. Before, a dialog was displayed, and the layer wasn't added to the map (causing some issues). Now, when a map has a torque layer and we try to add another torque layer, the latter is converted to a simple layer and added to the map.
But it's still possible to have a map with multiple torque layers. This can be accomplished by using the wizards. Here's how:

Add a torque layer (layer1) to a new map.
Add another torque layer (layer2) to the map. It will automatically be converted to a simple layer.
Select the new layer (layer2) and click on the Torque wizard.

You will now see that both layers display the following message:

But the fact it that there're two torque layers in that map. If you visualize that map, you will notice that both torque animations are being played. :-1:
Right now, when you click the Torque wizard, we activate it on the layer and we use that information to re-render the tabs and the corresponding wizard, which renders the error message when there're more than one torque layers in that map.
I think, a good solution to this problem would be to directly disable the "torque" wizards if the map already has a torque layer. We could grey them out and display a tooltip or dialog when the users hovers/clicks on them, instead of displaying this info on the wizard itself.
cc: @javisantana @iriberri @saleiva

+1 to your solution

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


NTR: second-harmonic imaging microscopy

NTR: second-harmonic imaging microscopy
definition: Second-harmonic imaging microscopy (SHIM) is based on a nonlinear optical effect known as second-harmonic generation (SHG). SHIM has been established as a viable microscope imaging contrast mechanism for visualization of cell and tissue structure and function.[1] A second-harmonic microscope obtains contrasts from variations in a specimen’s ability to generate second-harmonic light from the incident light while a conventional optical microscope obtains its contrast by detecting variations in optical density, path length, or refractive index of the specimen. [Wikipedia: https://en.wikipedia.org/wiki/Second-harmonic_imaging_microscopy]
descendant_of: light microscopy (CHMO:0000102).

This looks good, the only major update is to use 'light microscopy' as the parent
Definition: A light microscopy assay that uses a nonlinear optical effect known as second-harmonic generation (SHG) for visualization of a specimen. It obtains contrasts from variations in a specimen’s ability to generate second-harmonic light from the incident light while a conventional optical microscope obtains its contrast by detecting variations in optical density, path length, or refractive index of the specimen.
Definition source: [Wikipedia: https://en.wikipedia.org/wiki/Second-harmonic_imaging_microscopy].
This is being added to assays as we speak


Finite deck & more cards

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

218 of 218 (100.0%)  changed or added relevant lines in 21 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
990

Relevant Lines:
990

💛  - Coveralls


Change caching of global window inputs to be guarded by experiment

As there are potential performance concerns, put the removal of caching of global window inputs added by #30991 behind an experiment.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Why I am reciving too much emails
While I unsubscribed
El mié, 17 abr 2024, 6:11 p. m., scwhittle @.***>
escribió:

As there are potential performance concerns, put the removal of caching of
global window inputs added by #30991
https://github.com/apache/beam/pull/30991 behind an experiment.
Thank you for your contribution! Follow this checklist to help us
incorporate your contribution quickly and easily:

Mention the appropriate issue in your description (for example: addresses
#123), if applicable. This will automatically add a link to the pull
request in the issue. If you would like the issue to automatically close on
merging the pull request, comment fixes # instead.
Update CHANGES.md with noteworthy changes.
If this contribution is large, please file an Apache Individual
Contributor License Agreement
https://www.apache.org/licenses/icla.pdf.

See the Contributor Guide https://beam.apache.org/contribute for more
tips on how to make review process smoother
https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier
.
To check the build health, please visit
https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
[image: Build python source distribution and wheels]
https://github.com/apache/beam/actions?query=workflow%3A"Build+python+source+distribution+and+wheels"+branch%3Amaster+event%3Aschedule
[image: Python tests]
https://github.com/apache/beam/actions?query=workflow%3A"Python+Tests"+branch%3Amaster+event%3Aschedule
[image: Java tests]
https://github.com/apache/beam/actions?query=workflow%3A"Java+Tests"+branch%3Amaster+event%3Aschedule
[image: Go tests]
https://github.com/apache/beam/actions?query=workflow%3A"Go+tests"+branch%3Amaster+event%3Aschedule
See CI.md https://github.com/apache/beam/blob/master/CI.md for more
information about GitHub Actions CI or the workflows README
https://github.com/apache/beam/blob/master/.github/workflows/README.md
to see a list of phrases to trigger workflows.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/beam/pull/31013
Commit Summary

8659684
https://github.com/apache/beam/pull/31013/commits/8659684c5b1106e495827c2083e6e50ac09e7705
Change caching of global window inputs to be guarded by experiment

File Changes
(1 file https://github.com/apache/beam/pull/31013/files)

M sdks/python/apache_beam/runners/common.py
https://github.com/apache/beam/pull/31013/files#diff-350e908b1c77bb2c78ff5a16f77e7da591ea87dd3911a296be8c598162896b19
(92)

Patch Links:

https://github.com/apache/beam/pull/31013.patch
https://github.com/apache/beam/pull/31013.diff

—
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/31013, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX62FTCYYUQSWKXQHP5RTCTY5ZUZJAVCNFSM6AAAAABGLHVOXKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI2DQMRQGA3TONA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

R: @tvalentyn


Add ability text alignment recognition

This text is right-aligned.

@ozayr  sure i will add this feature in next release

@ozayr  text alignment feature is added

done


[Feature]: Implement OpenAI Clip in an application usable

Description
Create an application wich use OpenAI Clip :rocket:
Expected behaviour
The team have to :

[x] Create an application which use OpenAI Clip
[x] The application should be easily usable

Environment
/
Proposed solution
/

You can see the application on this link: https://huggingface.co/spaces/LayBraid/OpenIA-Implementation


Option to add social buttons in the nav bar

Config option allowing users to add social icons with links in the nav bar.

Acceptance

[ ] social config field which allows to specify popular social options

[ ] GitHub
[ ] Discord
[ ] LinkedIn
[ ] Facebook
[ ] X (Twitter)
[ ] Instagram
[ ] YouTube

Notes
social field should follow the following shape:
type Social = Array<{
	href: string;
	label: "github" | "discord" | ... other options
}>

@olayway  Can you please assign this issue to me ?

@pranay911 as i wrote on discord
Welcome and great you want to contribute 🎉
Thanks for asking and I suggest you have a look at the current source for where discord icon comes from. Usually you can find these svg icons in a bunch of open source and free icon toolkits. have a quick google 😄

FIXED


Create ShivaniMayekar.md

Description for Shivani Mayekar Profile.

Hi! Thank you for your interest. Please be sure your entry is a single line and has only three columns. Thank you!

Hi! Thank you for your interest. Please be sure your entry is a single line and has only three columns. Thank you!

Hello I have made changes and kept it in single line. Thank you!


Create metadata fee should be calculated (For now it's hard coded)

https://github.com/solana-labs/governance-ui/blob/73237169fad7cf486c834e304535294fe9dd19a5/utils/instructionTools.ts#L736-L755
Metadata.getMinimumBalanceForRentExemption is still returning wrong price on 22.July.2022.
I also tried to make Buffer with the params and get length from that but it doesn't have enough length as actual on chain data.
It looks like we need to submit a script to the Metaplex team to reproduce this error and resolve it jointly.

https://github.com/metaplex-foundation/metaplex-program-library/issues/600

Hey Buidleeeeeeeeeeeeeeers🙌
This issue is related to Epics Quest🚨
You get 1,000 $EPCT if you solve this💰
Please join this Quest from here👇
https://alpha.epics.dev/quest/UXVlc3Q6MTM=
WAGBI🔨
Have a good day☀


Error with Postgreslq image

I'm trying install de Netbox, but the netbox-postgresql-0 pod is ImagePullBackOff status.
Describing the pod we got the message:
Warning  Failed     61s                  kubelet, docker-desktop  Failed to pull image "docker.io/bitnami/postgresql:11.11.0-debian-10-r0": rpc error: code = Unknown desc = context canceled
Warning  Failed     61s                  kubelet, docker-desktop  Error: ErrImagePull
Normal   BackOff    60s                  kubelet, docker-desktop  Back-off pulling image "docker.io/bitnami/postgresql:11.11.0-debian-10-r0"
has anyone faced it?

This definitely looks like an issue on your end I'm afraid. The bundled PostgreSQL chart is just the bog-standard Bitnami PostgreSQL chart, and the image is its default image.


[release-0.2] Bump golang.org/x/net from 0.8.0 to 0.17.0

Manual backport from main, see commit
a861522c6224e6495b1a43d2c1762efbdace581c and PR #97

close in favor or #99


fix(slugrunner): pass minio details to slugrunner during run command

pass minio details to slugrunner during pod created during run command

Current coverage is 83.29%

Merging #585 into master will increase coverage by +0.01% as of 9fa880d

@@            master    #585   diff @@
======================================
  Files           36      36
  Stmts         2375    2377     +2
  Branches       343     343
  Methods          0       0
======================================
+ Hit           1978    1980     +2
  Partial        117     117
  Missed         280     280

Review entire Coverage Diff as of 9fa880d

Powered by Codecov. Updated on successful CI builds.


Update handlebars

@gotwarlost the version of handlebars used inside Istanbul is a vulnerable dependency, please update.
I couldn't find your contact to disclose this vulnerability.
Just ping me in private, if you need more details.
<EMAIL_ADDRESS>

Fixed in https://github.com/gotwarlost/istanbul/commit/48dc2de37c2b5cc318ee600e8adad8bccde8cd1a.


Css linting not showing errors/warnings

VSCode Version: 1.8.0 insiders
OS Version: Windows and Mac OS X

Steps to Reproduce:

Create an empty ruleset in a css file

In VSCode 1.7.1 and earlier, you would see the below

In the Insiders there are no squigglies and the Problems view is empty as well

duplicate of #15504


Non-ASCII-8BIT special characters are being replaced with blank characters (ADDON-33494)

What happened:
Add-on is replacing non-ASCII-8BIT special characters (like swedish, polish, russian, japaneese etc) with blank characters (or '?' in internal logs).
Example:
2021-02-26T08:18:29.227618927Z stdout F 2021-02-26 08:18:29 +0000 [info]: aaaąąąbbbźźźcccżżżddd
Is visible in Splunk in this way:
2021-02-26T08:18:29.227618927Z stdout F 2021-02-26 08:18:29 +0000 [info]: aaa   bbb   ccc   ddd
(GitHub is replacing 3 blank spaces with one, but I hope you feel the vibe)
Add-on container internal logs that are processing this event in the following way:
(...) 2021-02-26T08:18:29.227618927Z stdout F 2021-02-26 08:18:29 +0000 [info]: aaa???bbb???ccc???ddd
What you expected to happen:
Non-ASCII-8BIT characters should be visible and processed properly.
How to reproduce it (as minimally and precisely as possible):
(in pod)
echo '2021-02-26T08:18:29.227618927Z stdout F 2021-02-26 08:18:29 +0000 [info]: aaaąąąbbbźźźcccżżżddd' >> name-splunk-kubernetes-logging-(POD).log
Anything else we need to know?:
Fix in pull request #567 - Change default encoding to UTF-8
Workaround:

Clone the main Splunk Connect for Kubernetes repo:
git clone https://github.com/splunk/splunk-connect-for-kubernetes.git
In 'configMap.yaml' that is located in the Helm chart folder, add 2 encoding statements - encoding + from_encoding - with proper libraries (written in capital letters), just after line 75 -  (https://github.com/splunk/splunk-connect-for-kubernetes/blob/79d17645af594762c9421cc184d59201a7ccb0a6/helm-chart/splunk-connect-for-kubernetes/charts/splunk-kubernetes-logging/templates/configMap.yaml#L75):
vi splunk-connect-for-kubernetes/helm-chart/splunk-connect-for-kubernetes/charts/splunk-kubernetes-logging/templates/configMap.yaml

(...)
<source>
encoding UTF-8
from_encoding UTF-8
@id containers.log
(...)

Perform helm install, by using the local project content you modified:
helm install  -f <VALUES_FILE>.yaml splunk-connect-for-kubernetes/helm-chart/splunk-connect-for-kubernetes
All the non-native speakers' nightmare letters and sentences should be visualized properly in Splunk
(like Grzegorz Brzęczyszczykiewicz. Chrząszczyrzewoszyce, powiat Łękołody
https://www.youtube.com/watch?v=AfKZclMWS1U).

As per fluentd docs:
https://docs.fluentd.org/input/tail#encoding-from_encoding
fluentd encoding can be set up by using the following parameters:
encoding
from_encoding
'- If encoding is specified, in_tail changes string to encoding.
This uses Ruby's String#force_encoding.

If encoding and from_encoding both are specified, in_tail tries to
encode string from from_encoding to encoding. This uses Ruby's
By default (it) emits string value as ASCII-8BIT encoding.'

Environment:
(environment is irrelevant for this issue TBH)

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.2-34+350770ed07a558", GitCommit:"350770ed07a558ba1ce8202a6f9ea849f9a75f06", GitTreeState:"clean", BuildDate:"2021-02-11T20:09:31Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.2-34+350770ed07a558", GitCommit:"350770ed07a558ba1ce8202a6f9ea849f9a75f06", GitTreeState:"clean", BuildDate:"2021-02-11T20:10:29Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
Ruby version (use ruby --version):
(in pod)
ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux]
OS (e.g: cat /etc/os-release):
Ubuntu 20
Splunk version:
8.1.2
Splunk Connect for Kubernetes helm chart version:
1.4.4 - 1.4.6

There is a similiar merged PR for the openshift logging component: https://github.com/openshift/origin-aggregated-logging/pull/622
They actually have a filter that runs just after reading any source and before more filters are run because not every source type supports setting encoding.

so if I add
<filter **>
  @type record_modifier
  char_encoding utf-8
</filter>

right after the pipeline, would it be resolved?
but i would have to make it optional with default to be off for performance issue, yea?

my suggestion: https://github.com/splunk/splunk-connect-for-kubernetes/pull/570

@BartekZm Thank you for detailed instruction! I merged #570.


Ensure format only accepts strings. Add test to fix worked.

Closes #2 .

Thanks for contributing @aaronFranssell!
If I'm reading draft 7 correctly, it looks like the format attribute should be ignored if an instance type isn't compatible:

The value of this keyword is called a format attribute.  It MUST be a
string.  A format attribute can generally only validate a given set
of instance types.  If the type of the instance to validate is not in
this set, validation for this format attribute and instance SHOULD
succeed.

https://tools.ietf.org/html/draft-handrews-json-schema-validation-01#section-7.1
I think the better approach here is to move the validate_format call into validate_string since all of the supported formats only apply to strings. That way we won't get multiple errors for cases like this:
> puts JSONSchemer.schema({
  'type' => 'string',
  'format' => 'email'
}).validate({}).to_a
{"data"=>{}, "schema"=>{"type"=>"string", "format"=>"email"}, "pointer"=>"", "type"=>"format"}
{"data"=>{}, "schema"=>{"type"=>"string", "format"=>"email"}, "pointer"=>"", "type"=>"string"}

There is currently (undocumented) support for custom formats, which makes this a little more complicated. I think it makes sense to separate validate_format into separate methods for custom and draft-defined formats and call them in separate places. Let me know if you'd rather not continue with this and I'll add a fix myself.
Not sure what's up with the test suite. I'll look into it.

Test suite is fixed on master.

Thanks for fixing the test suite!
Looking at the code, I see what you mean about this being a more complex fix/refactor. If you are OK with it, then I think you should be the one to implement the fix. I may have more time in the next couple of weeks if you aren't able to get to it...


[Doc] Harvester DOC enhancement

Is your feature request related to a problem? Please describe.

Customer SREs are expecting more details from Harvester DOC.
Describe the solution you'd like

Harvester DOC enhancement:

Dedicated chapter to introduce K8S CSI, PVC, VOLUME, LH basic etc.,  and link to LH doc
Add LH troubleshooting chapter (to link LH doc)
List all Harvester used CRDs
How to collect all upgrade related detailed logs, how to better trouble-shooting
How to use kubectl to start/stop/create/delete VM, and other frequently used resources
OS layout, partitions ...
...

Describe alternatives you've considered

Additional context

Please include Harvester Network Configuration in your documentation enhancement.  Specifically, how to assign externally accessible IP addresses to VMs.

Documents have been widely and continuously updated, close as finished.
Fell free to open new issues on specific topics.


Find my mouse --> twice left ctrl  -->  twice right ctrl

Description of the new feature / enhancement
Changeable trigger Find my mouse button
Scenario when this would be used?
When i play Game twice left is easy to touch . Find my mouse is a good function
Supporting information
No response

/dup #14651


There is a pprint function in the example script, I wonder if that's a typo...

There is a pprint function in the example script, I wonder if that's a typo...

Originally posted by @schungx in https://github.com/rhaiscript/rhai-sci/pull/11#issuecomment-1207418837

Fixed typo in new PR


Infinite loop when trying to exit

When ESC is pressed the terminal enter a loop thats appear to cleaning and renders the terminal.

When I refactored the control, this problem was resolved.


Owned board hidden movement

Resolve #86

Drat.  After more testing, I would like to change the playback display when flipping owned pieces.  Therefore, I have converted this PR to a draft.

Dale, are you still reviewing this?

I just had some questions in the review before merging (see above about back stepping. That's why I didn't pull the trigger on the merge.
-Dale

I just had some comments in the review before merging (see above about back stepping) so I wanted to see if you were good with them. That's why I didn't pull the trigger on the merge.

Did you see https://github.com/CyberBoardPBEM/cbwindows/pull/87#discussion_r975936237?

I just had some comments in the review before merging (see above about back stepping) so I wanted to see if you were good with them. That's why I didn't pull the trigger on the merge.

Did you see #87 (comment)?

Yes and I replied with this:

so this code is the move back a step processing. It goes back to one move before the move we're stepping back to so it can replay it to get to the desired state. This code is tricky and my memory is definitely fuzzy here but this comment:

    // OK...we know there is at least one move to do PRIOR to the move
    // we are stepping up to. Find it so we can turn off silent mode for
    // that move.

seems to suggest that the argument bAutoStepHiddenMove value should be overridden with FALSE so that move is visible.

So the code changes seems to reverse what the code did before (by default initialization) and I feel this may be wrong so--as a minimum-- I expected you to react to that as it seems wrong.
-Dale


ERROR ITMS-90668 - Uploading application to App Store

Hello guys, I'm having trouble submitting my application that uses the Card.io component in the App Store.
The following error is presenting the Application Loader:

ERROR ITMS-90668: "Invalid Bundle Executable. The executable file 'Demo.iOS.app/Frameworks/CardIOSharp.framework/CardIOSharp' contains incomplete bitcode. To compile binaries with complete bitcode, open Xcode and choose Archive in the Product menu."

Any idea how to solve this issue?
Note: I am using the Xamarin component (https://components.xamarin.com/view/cardioios)

@marlonconstante How are you building the framework? Is the Enable Bitcode set to YES in Xcode target configuration? Sorry not familiar with Xamarin's build process.
You can see the original source at https://github.com/card-io/card.io-iOS-source which has the Project Config with Bitcode enabled by default for the framework build.

@bluk I am using the Xamarin component (https://components.xamarin.com/view/cardioios), which is official, right?
I believe that is the case then generate a new build with this option bitcode enabled to solve the problem, correct?

@marlonconstante The Xamarin component is being built by a 3rd party and isn't official from anyone associated with card.io AFAIK. Judging from the link, the publisher says it's Xamarin Inc, so maybe someone from Xamarin is repackaging? I would personally be a little bit cautious since it's an unknown 3rd party building something that handles credit cards as a binary library.
You may want to see if you can just try disabling bitcode entirely in your build process. That may work for now since Bitcode isn't required by Apple. Normally for Xcode projects or Cordova/React Native based projects, you can modify the Xcode project settings to Enable/Disable. I'm not sure how you would do that with Xamarin unfortunately.

Note that I am experiencing exact same problem, note the following, when I backed down to version <IP_ADDRESS> the problem goes away.
Note too that I have emailed Xamarin support directly to try to get a resolution for this issue on more recent version of cardio. Once known I will update this post.

Just checking in on this. Have you heard anything from Xamarin about what's going on here?

I had this issue when uploading to the App Store. I just installed the latest version (<IP_ADDRESS>) of the component from Xamarin via https://components.xamarin.com/view/cardioios#
I had to directly download as the integrated Xamarin component store wasn't working for me. Again.
This version was posted after the comment by @mlimbocker , so they may be all set already.

Hey folks, I work on the Xamarin component and we had a few requests from customers around this issue.  v<IP_ADDRESS> was released to address this issue :)
To the Card.IO team:  If you're interested in taking over ownership of the bindings to the SDK's, we'd be more than happy to help transition the bindings and code over.  The current code is all open-sourced and located here: https://github.com/xamarin/XamarinComponents/tree/master/XPlat/CardIO
Thanks!

@Redth would you please describe how you fixed it? We have the same problem binding another library.

@alxbog  the tl;dr is that we had an xcode project referencing this library which we bound, but forgot to disable BITCODE on our own xcode project.  ymmv...


Fixing #1030

This isn't funny. From here forward, anyone who makes an issue or pull request regarding the developer list will be blocked from the repo.

@twizmwazin can we keep the second part of the PR? (first you need it to compile tho)

No. That's dumb.

@twizmwazin I know, i was just joking


Make instance-id and/or instance-name clickable in sliver list

When the IP address is empty, there's not much to click on in the sliver list, so make one or more of the other fields clickable.

Done.


tests for fixing full fine tuning

Description of the change
Unit tests for full fine tuning should not have any tuning config set . This PR fixes the unit tests by unsetting the PT config that was getting set for FT
How to verify the PR

Unit tests pass
No adapter_config is created which is how Full fine tuning should be

Was the PR tested

[ ] I have added >=1 unit test(s) for every new method I have added.
[ ] I have ensured all unit tests pass

@anhuong I have refactored tests in next PR https://github.com/foundation-model-stack/fms-hf-tuning/pull/163 to not use any argument parsing from a large dict, but rather have explicit parameter passing in each test. This will avoid errors in how args are created. Each test has more control over args passed. If you are in agreement, we can merge this and then just complete the refactor - I have not been able to finish it yet


fix(ci): skip package cache on golangci-lint action

PR summary
While running golangci/golangci-lint-action@v3 in CI we are getting number of warnings about "File exists" which is a known issue with golangci-lint and related to use of cache.
It seems that this prevents of actual linting beyond of the first version in lang matrix even though the tests are passing green. Disabling the cache seems to be a recommended workaround.
Fixes: #445
Note: An existing issue is required before opening a PR.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the
Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[x] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

That seems to do the trick, the warnings are gone: https://github.com/IBM/cloudant-go-sdk/actions/runs/7613203259


Component guidelines

:+1: :100: :1234:

Looking good! :fallen_leaf:

Deferred
Implement tests from #33 instead of a readme

Both the guideline doc and the tests were implemented in #33.


How to use with file-type

npm install file-type
add to main/src/index.ts

import * as fileType from 'file-type';

console.log(fileType);

Try add node:buffer to externals

Or, better, try set build.ssr: true

@cawa-93

if I set ssr: true, and call file-type

import {fileTypeFromBuffer} from 'file-type';

console.log(fileTypeFromBuffer);

I get this error
[main] App threw an error during load
19:51:05 [main] Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/vinchilive/Documents/dev/firestarter/vite-electron-builder/node_modules/file-type/index.js from /Users/vinchilive/Documents/dev/firestarter/vite-electron-builder/packages/main/dist/index.cjs not supported.
Instead change the require of index.js in /Users/vinchilive/Documents/dev/firestarter/vite-electron-builder/packages/main/dist/index.cjs to a dynamic import() which is available in all CommonJS modules.

if I add 'node:buffer', to external it seems to do the trick, but if I edit the code sometimes the app is crashing on save

19:54:40 [main] [32568:0110/195440.662687:ERROR:process_singleton_posix.cc(1201)] Failed to extract pid from path: /Users/vinchilive/Library/Application Support/vite-electron-builder/SingletonLock

actually the second case is happening on the clean repo as well

looks like the issue is in the dynamic import of electron-devtools-installer
.then(() => import('electron-devtools-installer'))
.then(({default: installExtension, VUEJS3_DEVTOOLS}) =>

if I do it statically the error is gone
import installExtension, { VUEJS3_DEVTOOLS } from 'electron-devtools-installer'

if (import.meta.env.DEV) {
  app.whenReady()
    .then(() => {
      installExtension(VUEJS3_DEVTOOLS, {
        loadExtensionOptions: {
          allowFileAccess: true,
        },
      })
    })
    .catch(e => console.error('Failed install extension:', e));
}

and imports are working fine with other packages, this one do not crash the app:
import('file-type').then(({fileTypeFromBuffer}) => {
  console.log(fileTypeFromBuffer)
})

@vinchilive

if I set ssr: true, and call file-type

import {fileTypeFromBuffer} from 'file-type';

console.log(fileTypeFromBuffer);

I get this error
[main] App threw an error during load
19:51:05 [main] Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/vinchilive/Documents/dev/firestarter/vite-electron-builder/node_modules/file-type/index.js from /Users/vinchilive/Documents/dev/firestarter/vite-electron-builder/packages/main/dist/index.cjs not supported.

It seems to upstream issue.
At the moment, the ESM is not supported in the electron. So main package completly transpile to commonjs. And in runtime you got:
f = require('file-type');

But, As far as I can see, the file-type does not provide the module in cjs, but only in esm.

@cawa-93
1. if I set `ssr: true,` and call file-type

import {fileTypeFromBuffer} from 'file-type';

console.log(fileTypeFromBuffer);

I get this error
[main] App threw an error during load
19:51:05 [main] Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/vinchilive/Documents/dev/firestarter/vite-electron-builder/node_modules/file-type/index.js from /Users/vinchilive/Documents/dev/firestarter/vite-electron-builder/packages/main/dist/index.cjs not supported.
Instead change the require of index.js in /Users/vinchilive/Documents/dev/firestarter/vite-electron-builder/packages/main/dist/index.cjs to a dynamic import() which is available in all CommonJS modules.

2. if I add `'node:buffer',` to `external` it seems to do the trick, but if I edit the code sometimes the app is crashing on save

19:54:40 [main] [32568:0110/195440.662687:ERROR:process_singleton_posix.cc(1201)] Failed to extract pid from path: /Users/vinchilive/Library/Application Support/vite-electron-builder/SingletonLock

node -v
v17.2.0

It's like a separate sciatica. However, I cannot reject it. Did you specify that this is specific to m1? https://github.com/cawa-93/vite-electron-builder/issues/554 may be relevant. In any case, this deserves a separate issue.

ssr: {
    noExternal: ['file-type'],
  },

that one helped, thanks 👍
as for the issue with the app crashing I tested and reproduced it on 2 M1 macs and tested and cannot reproduce it on intel mac. I agree that it is a separate issue so we can close this one


Add INTEL_WHL and INTEL_ICL to uarch get name function

Follow up from #99. Forgot to add INTEL_WHL and INTEL_ICL to the GetX86MicroarchitectureName function.

good catch ! many thanks again for the effort !


Add support for source_names and source_ignore

Thhis adds support for source_names and source_ignore as requested in #17

@KaSroka  Thank you very much for you support! Both PRs merged and a new release created.


setting of gyp variables via command line

As far as I understand the gyp documentation, I should be able to set a gyp variable using
  node-gyp configure -DLNNZ_VERSION=10

And in my binding.gyp file:
  'variables': {
    'LNNZ_VERSION%': '11'
  },

I would expect that the value of LNNZ_VERSION is 10 with the above invocation. Am I doing something wrong, or is this not supported by node-gyp?
Background: depending on the version of Oracle installed on the system, there is either a lnnz10 or a lnnz11 library. And the build must use the correct one ...
The only other solution would be to create a dynamic link 'lnnz' and use that as dependency
Any input?

How can this be done when installing a package with npm install?

Just pass it along as a flag to npm. Unhandled options from npm get turned into gyp flags. See https://github.com/TooTallNate/node-speaker#audio-backend-selection for an example.
$ npm install foo --LNNZ_VERSION=10

Let me know if that doesn't work as expected.

Oh cool, thanks! Just didn't know it :-) I'll try it and tell you if it works ;-)

Ok, that worked :-) Thank you @TooTallNate! :-D


Create SECURITY.md

To let the repository confirm<EMAIL_ADDRESS>as its security contact.

Thank you so much for your contribution! However, we noticed that the SECURITY.md file you provided might not be fully complete. We have updated our entire security policy (#234 or https://github.com/go-sonic/sonic/blob/master/SECURITY.md). We really appreciate your efforts, and we're now closing this pull request. Thanks again!


[BUG] chat embed_chatflow config_sessionId not working

Describe the bug
when trying to use the html embed for chat (both widget, and fullpage html).,
i am sending the chatflow config additional information

specifically sessionId, is not working.
the conversation doesn't show the conversation specific to referenced sessionId

To Reproduce
Steps to reproduce the behavior:
test html embed chat, both full page and widget.

chatflow config with sessionId.
see if only sessionId specific information is shown.

Expected behavior
html embed chat should show only the message history of specified sessionId.

1120_SNSmktgAgent Agents.json
Flow
If applicable, add exported flow in order to help replicating the problem.
Setup

Installation [render, bubble]
Flowise Version [latest 11.27 latest versions deployed]
OS: [e.g. macOS]
Browser [safari]

Additional context
Add any other context about the problem here.

This is a feature not a bug to do with override variables.
You now have to configure them in your global variables, you can't just declare them on the fly. so I add a couple empty objects for things I want to declare in api calls and then in my chatflow config I can toggle them to allow for overwriting

thanks for the reply... may i ask are you sure you're not referring to override config for APIs? (b/c yes, i am also using global vars. here)

i'm running into trouble specifically for chat embed. (am looking at flowise doc, but doesn't distinctly specify that vars can be used for chat embed config)
that being said, i don't mind testing your approach.
how do you call the vars for the below? i'm looking to changed the sessionId.

I dont think we are able to do so since the beginning, you can only set a sessionId that any chat conversation happened on the chat, will be saving to that sessionid, however you are not able to display the chat by specifying a specific sessionId for security purpose

thanks alot for your comment.
if that is the case, is there anyway i can:

use the same agentflow, and use the chat embed (or if i must API), and have multiple users have their own "conversation session" or "conversation threads?


Crashing server now.. have another log...

do you even test this stuff on server enviroment?
crash-2022-11-09_10.46.09-server.txt
reverting back to .6.2 again.. honestly kevin.. still the only version that doesnt crash client or server

Yes I am. I'm not even getting these errors. How do I recreate it?
0.6.2 is more broken than this one. Here is a gif of 0.6.2:

yes there is a duplication error, yes, we ALL know that. but it DOESNT CRASH CLIENT OR SERVER. Listen man.. you could wrap a pile of textfiles in a zip and claim its a new update, doesnt mean you fixed anything. I agree .6.2 has errors but it WORKS.. nothing afterwards works in server enviroment.

Honestly erazare, maybe you should learn how to code and fix it yourself if you aren't happy with it. I know how hard DAQEM works on this and he does test it out.

Honestly erazare, maybe you should learn how to code and fix it yourself if you aren't happy with it. I know how hard DAQEM works on this and he does test it out.

oh believe me Amy, the thought has crossed my mind. however I do not wish to steal from the developer. I could have rewritten .6.2 rebranded it and re-released it as soon as this started and no one would be the wiser. that's not my ethics. stop SIMPing to the developer. we all agree its a great concept, no one is denying anything or trying to disturb anyone, but broken is broken, if you intend to keep the project fix it.. nothing simpler.. can't fix it abandon it and someone WILL fix it.

Yes I am. I'm not even getting these errors. How do I recreate it?
0.6.2 is more broken than this one. Here is a gif of 0.6.2:

how do you recreate it? get on a server with say.. one or two others, play for about 3mins and you will see the rubber-banding as the client has trouble communicating with the server, then the client drops, the server gets stuck waiting for a response and then it drops. I might have been rash to suggest you are not testing, but i dont believe that you are testing this in a multiplayer envioroment.

Here is some proof of multiplayer testing for you ;)


Extensions not loading

I can't use any extension. But after re-installing them they'll be available till the next restart!

VSCode Version: Version: 1.36.1 (system setup)
OS: Windows_NT x64 10.0.19042

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

It seems you are using pretty old version of VS Code. Can you please update VS Code and try again?
If you still see the issue, please provide us the steps to reproduce.

It seems you are using pretty old version of VS Code. Can you please update VS Code and try again?
If you still see the issue, please provide us the steps to reproduce.


Dependency: ACPI 6.6: APEI

Does anything RISC-V specific need to be added to e.g. GHESv2 or elsewhere.

Yes, both ACPI and UEFI spec needs some updates for RISC-V.

Yes, there is a need to define an ID in SectionType of Section Descriptor. This wold be to differentiate between Error from different type of sources. There is Generic/IA32/IA64/ARM processors defined. We will need one for RISCV. Also, Ventana is working on an high priority software events specification. This would need identification number to differentiate between SDEI of ARM and SSE of RISCV. We at Ventana are working on a proposal for SSE specfication and RAS software architecture.

Need to clearly understand what parts of APEI can be implemented without depending on the ongoing RAS work (i.e. apply to existing hardware). Can fw-first error handling be made a requirement for BRS or not or if it is conditional on certain HW features being implemented.

RAS is not currently in scope.


Launch elevated instances via shell:AppFolder

This uses shell:AppsFolder to launch elevated instances of the app via
ShellExecuteEx and runas in elevate-shim.exe. The app to launch is
discovered via the GetCurrentApplicationUserModelId API.
e.g. shell:AppsFolder\WindowsTerminalDev_8wekyb3d8bbwe!App
This will fallback to launching WindowsTerminal.exe if it fails to
discover the app user model id to launch.
This also fixes a bug in elevate-shim where the first argument of
WinMain was lost (e.g. new-tab).
Curiously, AppLogic::RunAsUwp() is never called and
AppLogic::IsUwp() is always false when running debug builds locally
(e.g. WindowsTerminalDev). It's not clear if this is an artifact of
development packages or something else.
Validation Steps Performed
Various manual debug/execution scenarios.
Verified the fallback path by running the unbundled app by extracting
the CascadiaPackage_<IP_ADDRESS>_x64.msix from the 'drop' build artifact.
Fixes #14501

@microsoft-github-policy-service agree

I'm not particularly attached to the specifics of the implementation; it was an iterative process to get here.
There may be a potential for (un)escaping issues in the command line conversion when it removes (replace w/ empty string) shell:AppsFolder... from the cmdline args. i.e. arg0 from __wargv is not the same as what is found in the full cmd line string.
This is also assuming the string returned from GetCurrentApplicationUserModelId doesn't have spaces in it.
It also wasn't clear if terminal is always an AppX package, in which case the fallback to invoking WindowsTerminal.exe isn't necessary.

@zadjii-msft
Just had an idea while working on something entirely unrelated.  Turns out that elevate-shim.exe can successfully call GetCurrentApplicationUserModelId.  This means this change can be entirely isolated to the shim and not have to deal with any command line argument parsing.  It significant simplifies the shim to only a decision on how it generates the cmd to pass to shell execute.
I'll get an updated pull request out.

Is shell:AppsFolder documented as an API? It's described in Find the Application User Model ID of an installed app for interactive use though, and there is FOLDERID_AppsFolder in KNOWNFOLDERID.

I know that PowerToys uses it, but I don't know whether it's been publicly documented. That's something we should definitely pursue. Thank you :)

"Release notes" link in bot posts is 404'd.


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(scripts): add posttest@npm run prepare && markdown-doctest
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Rebuild with latest libultrahand. (for your consideration)

Hey masagrator, thought you might want to look over this.
I've made the bare minimum modifications to get your project working with the latest libultrahand.
I've also made your MiniListItem a preset in libtesla you can use within the ListItem class itself so you don't need to redefine it.
I know the size does increase a bit, but there are some ways to make it smaller (like using more methods from libultra instead of using filesystem).
Anyways, if you have any questions or comments feel free to ask / share.  Wasn't sure if this update would interest you or not, but it does add some quality of life fixes to the libtesla.

I've made a number of updates to the libraries.  Feel free to look at the changes now.  I believe it should be compilable without any modifications, but one thing i did include was the ability to override the theme and wallpaper.

the only things changed now are the submodule, make file, and and MiniListItem implementation.

Ive added a NO_FSTREAM_DIRECTIVE to the Makefile since I know you may not want to force all projects to use fstream over cstdio.

I've stripped json libraries from needing to be compiled with libtesla for overlays to be built.  One can still import jansson, but the compiler will strip the class away if none of the json_funcs methods are being used.


[KEP-3488]Placeholder PR

Hello @cici37  :wave: please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday March 12th 2024 18:00 PST. Thank you!

I didn't assign any tech reviewer in this PR since it didn't touch any tech context. Please let me know if it's needed. Thanks

/milestone 1.30


Atom Echo M5 install failure

if I try through website (https://esphome.io/projects/index.html) it works fine, however when trying to upload config to the ESPHome for hte install I'm getting following error:
INFO Reading configuration /config/esphome/esphome-web-0a06ec.yaml...
INFO Updating https://github.com/esphome/esphome.git@pull/5230/head
INFO Updating https://github.com/jesserockz/esphome-components.git@None
INFO Generating C++ source...
INFO Updating<EMAIL_ADDRESS>INFO Updating<EMAIL_ADDRESS>INFO Updating submodules (components/esp-sr, components/esp-adf-libs) for<EMAIL_ADDRESS>INFO Updating<EMAIL_ADDRESS>INFO Updating<EMAIL_ADDRESS>INFO Updating<EMAIL_ADDRESS>INFO Compiling app...
Processing esphome-web-0a06ec (board: m5stack-atom; framework: espidf; platform: https://github.com/pioarduino/platform-espressif32.git#51.03.07)
--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
 - framework-espidf @ 3.50105.0 (5.1.5)
 - tool-cmake @ 3.21.3
 - tool-esptoolpy @ 4.8.1
 - tool-mklittlefs @ 3.2.0
 - tool-ninja @ 1.7.1
 - tool-riscv32-esp-elf-gdb @ 12.1.0+20221002
 - tool-xtensa-esp-elf-gdb @ 12.1.0+20221002
 - toolchain-esp32ulp @ 2.35.0-20220830
 - toolchain-xtensa-esp32 @ 12.2.0+20230208
Reading CMake configuration...
-- git rev-parse returned 'fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).'
-- Building ESP-IDF components for target esp32
Processing 1 dependencies:
[1/1] idf (5.1.5)
-- Configuring incomplete, errors occurred!
See also "/data/build/esphome-web-0a06ec/.pioenvs/esphome-web-0a06ec/CMakeFiles/CMakeOutput.log".

fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/build.cmake:266 (message):
  Failed to resolve component 'jsmn'.
Call Stack (most recent call first):
  /data/cache/platformio/packages/framework-espidf/tools/cmake/build.cmake:308 (__build_resolve_and_add_req)
  /data/cache/platformio/packages/framework-espidf/tools/cmake/build.cmake:603 (__build_expand_requirements)
  /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:604 (idf_build_process)
  CMakeLists.txt:3 (project)

========================== [FAILED] Took 1.74 seconds ==========================```

Looks like it might be the same error as https://github.com/esphome/wake-word-voice-assistants/issues/43

just a note that even after adding the workaround, when trying to use the local wake word getting:
[10:23:07][E][micro_wake_word:032]: Could not allocate the streaming model's tensor arena.
[10:23:07][E][micro_wake_word:268]: Failed to initialize a wake word model.
[10:23:07][E][micro_wake_word:161]: Failed to load the wake word model(s) or allocate buffers
[10:23:07][E][component:164]: Component micro_wake_word set Error flag: unspecifie****

worked out that using the bluetooth_proxy causes that to happen, if I disable bluetooth_proxy it starts workign fine even with local wake word - would be good to see if we can edit the code to allow the bluetooth proxy to be used with it


Fix getGarbageLength to return correct size

What this PR does / why we need it?
Fix getGarbageLength to return correct size
Any background context you want to provide?
What are the relevant tickets?
https://github.com/yorkie-team/yorkie-js-sdk/pull/714

Fixes #
Checklist

[x] Added relevant tests or not required
[x] Didn't break anything

FYI, I've changed instrumentation test to run on a single device as it was failing too often


Package and Upload Eventing Auth Manager Helm Chart in CI Pipeline

Description
Package and upload EAM helm chart to the GCR repository as a part of CI so that it can be referenced in the management-plane-config like this as a dependency.
Acceptance Criteria

[ ] a helm chart in the GCR repository
[ ] automated packaging and uploading helm chart as a part of CI

We may automate the releasing of a new EAM docker image automatically in DEV environment.


init commit for getresponse

adding oAuth provider for getResponse

Tests
[x] Get all lists
[x] lists[i].totalSubscribers is equal to contacts from getList
[x] Get all contacts for a given list
[x] Add new subscriber to list
[x] Create a new suppression list with results


Update pubspec.yaml

Upgrade flutter_web_auth_2_platform_interface dependency

Thanks for the PR! This is basically a superfluous change as the ^ identifier allows the use of 2.0.1 anyways.
However, it might be good to indicate a stricter constraint.


Sushiswap (Polygon) Subgraph QA- not indexing

Subgraph Reviewed | https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/name/messari/sushiswap-polygon&tab=protocol |
-- | -- | --
Date Reviewed | July 5th 2022 |
Schema Version | 1.3.0 |
Subgraph Version | 1.0.0 |
Methodology Version | 1.0.0 |

Protocol |   |
-- | -- | --
Section | Value | Status
All | All | NOT OK

OVERALL COMMENTS
-Indexing has stopped, no values are being shown
-Subgraph needs to resume indexing before passing QA
-Chain should be called Polygon and not Matic.

next time when this happens, can you specify the block number where it failed, and copy the error message here?


Extension issue

Issue Type: Bug
Extension Name: jupyter
Extension Version: 2020.12.414227025
OS Version: Darwin x64 19.6.0
VSCode version: 1.52.1

{
	"messages": [],
	"activationTimes": {
		"codeLoadingTime": 465,
		"activateCallTime": 14,
		"activateResolvedTime": 1464,
		"activationReason": {
			"startup": false,
			"extensionId": {
				"value": "ms-toolsai.jupyter",
				"_lower": "ms-toolsai.jupyter"
			},
			"activationEvent": "onLanguage:python"
		}
	},
	"runtimeErrors": []
}

Hi @toprakfirat
Could you please provide some additional details on the issue you are experiencing?
Helpful information includes steps to reproduce, expected behavior vs. actual behavior, pictures or screen recordings when applicable. (https://www.screentogif.com)

Hi @toprakfirat
Could you please provide some additional details on the issue you are experiencing?
Helpful information includes steps to reproduce, expected behavior vs. actual behavior, pictures or screen recordings when applicable. (https://www.screentogif.com)


Combined dependencies PR

Combining multiple dependencies PRs into one.

Instructions for merging

Use a merge commit, so that GitHub will mark all original PRs as merged.
If your repository does not have merge commits enabled, please temporarily enable them in settings. Tick Allow merge commits in the repository settings.
When ready, merge this PR using Create a merge commit.

Combined PRs

build(deps-dev): Bump typedoc from 0.22.15 to 0.22.16 (#857) @dependabot
build(deps-dev): Bump @typescript-eslint/eslint-plugin from 5.26.0 to 5.27.0 (#856) @dependabot
build(deps-dev): Bump @typescript-eslint/parser from 5.26.0 to 5.27.0 (#855) @dependabot

Built with rnorth/gh-combine-prs and seems to be not working correctly, missing parser bump


Issue-demo token removed

Automated Review Comments
Issues in backend/app.js:

(7, 'Line exceeds 80 characters')

I got it.


Portainer - can't exec into containers with Traefik

When using Portainer with Traefik I can't exec into any containers. If I try, I get Failure timeout waiting for exec session ready. If I bypass Traefik and connect directly to the IP of Portainer I can successfully exec into containers.
To reproduce, open Portainer, click Containers, click the Console Quick Action next to any container then click Connect.
Anyone else have this issue? BTW, I'm using Docker for Mac on macOS 10.14.

Sorry! I thought this stack had Portainer included but I must have added it myself. Please ignore.


Object.prototype.toString.call incompatibility for ProxyArray

I'm trying to port our code from Nashorn to Graal JS. We're using docxtemplater which calls Object.prototype.toString.call on an array that I've passed from Java which is an implementation of ProxyArray. However, as you can see in the code, they explicitly check what is returned from that call - expecting [object Array]. But Graal JS returns [foreign PolyglotProxy] for my array. This is true both with and without  js.experimental-foreign-object-prototype. The result being - the library doesn't work correctly.
Nashorn returns correctly [object Array] for it's own proxy-like thing.
I'm not sure what can I do apart from constructing a whole "real" JS array (which is a performance hit of course). Any ideas?

Hi @boris-petrov
thanks for your report. I agree, this is wrong. We also report [object Object] or [object Array] for JS-Proxy objects, so no reason to deviate from that for polyglot objects with a separate type.
I'll work on fixing this.
Best,
Christian

Hi @boris-petrov
this is fixed in the master branch of Graal.js by https://github.com/graalvm/graaljs/commit/74e1629379c30c9000dd3f28b96184d588dc1940
It will land in the GraalVM 20.2 release, and will be in the preview builds on https://github.com/graalvm/graalvm-ce-dev-builds/releases in the next few days.


These isn't a public api to get the parent of a MortarScope.

Is it designed to be so? And how can I get the parent of a MortarScope?

Yeah, we should probably add that. In the meantime you can hack around the lack by introducing your own peekaboo class in the mortar package. E.g.
package mortar;

public class ScopeSpy {
  public static MortarScope parentScope(MortarScope mortarScope) {
    return mortarScope.parent;
  }
}


Allow examples to work on Windows

..and do not copy renv directory into local cache

I've unblocked this as even though problems remain (e.g. https://github.com/openpharma/staged.dependencies/pull/74#issuecomment-898366180) with these changes install_deps works on the examples on Windows

And with latest push https://github.com/openpharma/staged.dependencies/pull/74#issuecomment-898366180 should be resolved


constant linker errors with monadic-html

In my project https://github.com/antonkulaga/GEOmetadb-scala/tree/3770f7a6f05aa052e4d00a106779d1eb765a3e8d I am getting constant linker errors with monadic-html like:
Linker: Compute reachability: 4438219 us
Referring to non-existent method scala.xml.NodeBuffer.$$amp$plus(java.lang.Object)scala.xml.NodeBuffer
  called from group.research.aging.geometa.web.MainJS$.delayedEndpoint$group$research$aging$geometa$web$MainJS$1()scala.Unit
  called from group.research.aging.geometa.web.MainJS$delayedInit$body.apply()java.lang.Object
  called from scala.scalajs.runtime.SemanticsUtils$.scala$scalajs$runtime$SemanticsUtils$$genericCheck(scala.Int,scala.Function0,scala.Function0)scala.Unit
  called from scala.scalajs.runtime.SemanticsUtils$.arrayIndexOutOfBoundsCheck(scala.Function0,scala.Function0)scala.Unit
  called from java.lang.System$.checkIndices$1(scala.Int,scala.Int,scala.Int,scala.Int,scala.Int)scala.Unit
  called from java.lang.System$.copyRef$1([java.lang.Object,[java.lang.Object,scala.Int,scala.Int,scala.Int,scala.Boolean)scala.Unit
  called from java.lang.System$.arraycopy(java.lang.Object,scala.Int,java.lang.Object,scala.Int,scala.Int)scala.Unit
  called from scala.collection.immutable.VectorPointer.copyOf([java.lang.Object)[java.lang.Object
  called from scala.collection.immutable.Vector.copyOf([java.lang.Object)[java.lang.Object
  called from scala.collection.immutable.VectorPointer.stabilize(scala.Int)scala.Unit
  called from scala.collection.immutable.VectorIterator.stabilize(scala.Int)scala.Unit
  called from scala.collection.immutable.Vector.initIterator(scala.collection.immutable.VectorIterator)scala.Unit
  called from scala.collection.immutable.Vector.iterator()scala.collection.immutable.VectorIterator
  called from scala.collection.immutable.Vector.iterator()scala.collection.Iterator
  called from scala.collection.IterableLike.foreach(scala.Function1)scala.Unit
  called from scala.collection.AbstractIterable.foreach(scala.Function1)scala.Unit
  called from scala.collection.generic.TraversableForwarder.foreach(scala.Function1)scala.Unit
  called from scala.collection.mutable.ListBuffer.foreach(scala.Function1)scala.Unit
  called from scala.App.main([java.lang.String)scala.Unit
  called from group.research.aging.geometa.web.MainJS$.main([java.lang.String)scala.Unit
  called from core module module initializers

Originally I thought it was a build misconfiguration ( https://github.com/lihaoyi/mill/issues/272 ), but now I think something is wrong with monadic-html itself.

Linking to https://github.com/lihaoyi/mill/issues/277


Refactor touch events

This is a work item for #685.
Pages:

[x] https://developer.mozilla.org/en-US/docs/Web/Events/touchcancel
[x] https://developer.mozilla.org/en-US/docs/Web/Events/touchend
[x] https://developer.mozilla.org/en-US/docs/Web/Events/touchenter (delete)
[x] https://developer.mozilla.org/en-US/docs/Web/Events/touchleave (delete)
[x] https://developer.mozilla.org/en-US/docs/Web/Events/touchmove
[x] https://developer.mozilla.org/en-US/docs/Web/Events/touchstart

The target interfaces here are document and element, so this is a case where there is not one redirect, but a split. We could decide to redirect to either document or element, though.
Tasks

[x] Document events interface page

[x] Element events interface page

[x] Document:touchcancel

[x] Translated pages moved

[x] Element:touchcancel

[x] Document:touchend

[x] Translated pages moved

[x] Element:touchend

[x]  Document:touchenter -- removed as it is not part of the spec

[x] Document:touchleave -- removed as it is not part of the spec

[x] Document:touchmove

[x] Translated pages moved

[x] Element:touchmove

[x] Document:touchstart

[x] Translated pages moved

[x] Element:touchmove

[x] BCD PR

Reviewer Estelle

@estelle Everything has been done but the BCD PR. You can start reviewing.

https://www.quirksmode.org/mobile/tableTouch.html - not sure if you already wrote the bcd and haven't submitted for PR, but that URL can help

Here is the pull request: BCD Pull Request #3534

@irenesmith , I hope you don't mind me adding a few nit-picking comments, but I think it's worth trying to be consistent as much as we can.

titles should have a space between interface name and event name: Document: touchend event not Document:touchend event
the blue boxes should use <th> not <td> for the first column (sorry this wasn't in the post)
"Event handler" in the blue box should be "Event handler property"

Moving this back to in progress because i have some fixes to make.
@wbamberg, Thank you for your comments. Actually, I noticed the Event handler property myself late yesterday and, since I have to move the Element-related ones anyway, I will fix the other things as well.
@estelle, if you haven't already had a look, hold off until I get a chance to fix the things Will pointed out and to also move the events from Element to HTMLElement. Thanks!

BCD data is now showing up properly on the pages.

@irenesmith , can you comment on the status of this story? Is it waiting for review, or finished?

This one has been reviewed, updated, and the BCD information is appearing as it should.

Thanks for the update @irenesmith ! I just noticed that these pages are missing specification sections, can you add these?

Spec links have been added


Backup AWS Credentials are restore them before CopyToS3

Toni,
Does it make sense to save the original AWS credentials and then restore them before doing  a copy to S3? I don't see a reason to keep the assumed credentials before the copy. The credentials of the individual/process that launched prowler are most likely to be the one used to perform other tasks, such as copy to S3. Optionally, we could add a new option, i.e.,
-Bn  Custom output bucket used with original prowler role, requires -M  and it can work also with -o flag.
(i.e.: -M csv -B my-bucket or -M csv -B my-bucket/folder/)

I always have tried to keep Prowler consistent with the way that the cli works in terms of configuration settings and precedence

Command line options – Overrides settings in any other location. You can specify --region, --output, and --profile as parameters on the command line.
Environment variables – You can store values in your system's environment variables.
CLI credentials file – ~/.aws/credentials on Linux or macOS, or at C:\Users\USERNAME.aws\credentials on Windows
CLI configuration file – The credentials and config file are updated when you run the command aws configure. The config file is located at ~/.aws/config on Linux or macOS, or at C:\Users\USERNAME.aws\config on Windows.
Container credentials
Instance profile credentials

Additionally, Prowler handles:

With credentials gotten from any of the previous 6 steps, Prowler can assume a role that the previous user or role has permission to assume in the same account or another one.

This is ready to go. It was tested and it appears to work fine.

Awesome, thanks @sectoramen!


Show color palette of listed themes

When choosing a theme seeing color palette is important if theme is not a well known one.  Add an option to show color palette on terminal.  Pastel project would be helpful in implementing this.

This will be a really nice feature. We'll need cache the github repo contents instead fetching on demand because colortty needs to get individual files to know the colors in them.

Released as 0.2.0


[spirv] 'memref.alloc' op unexpected allocation without upper bound shapes

What happened?
Hi, I'm getting the following error during the compilation of an IR:
<stdin>:810:21: error: 'memref.alloc' op unexpected allocation without upper bound shapes
<stdin>:26:3: note: called from
<stdin>:820:10: error: failed to run translation of source executable to target executable for backend #hal.executable.target<"vulkan", "vulkan-spirv-fb", {spirv.target_env = #spirv.target_env<#spirv.vce<v1.6, [Shader, Float64, Float16, Int64, Int16, Int8, StorageBuffer16BitAccess, StorageUniform16, StoragePushConstant16, StorageBuffer8BitAccess, UniformAndStorageBuffer8BitAccess, StoragePushConstant8, GroupNonUniform, GroupNonUniformVote, GroupNonUniformArithmetic, GroupNonUniformBallot, GroupNonUniformShuffle, GroupNonUniformShuffleRelative, GroupNonUniformClustered, GroupNonUniformQuad, VariablePointers, VariablePointersStorageBuffer, DotProduct, DotProductInputAll, DotProductInput4x8BitPacked, DotProductInput4x8Bit, CooperativeMatrixNV], [SPV_KHR_16bit_storage, SPV_KHR_8bit_storage, SPV_KHR_storage_buffer_storage_class, SPV_KHR_variable_pointers, SPV_NV_cooperative_matrix]>, api=Vulkan, NVIDIA:DiscreteGPU, #spirv.resource_limits<max_compute_shared_memory_size = 49152, max_compute_workgroup_invocations = 1024, max_compute_workgroup_size = [1024, 1024, 1024], min_subgroup_size = 32, max_subgroup_size = 32, cooperative_matrix_properties_nv = [#spirv.coop_matrix_props<m_size = 8, n_size = 8, k_size = 32, a_type = i8, b_type = i8, c_type = i32, result_type = i32, scope = <Subgroup>>, #spirv.coop_matrix_props<m_size = 16, n_size = 16, k_size = 16, a_type = f16, b_type = f16, c_type = f16, result_type = f16, scope = <Subgroup>>, #spirv.coop_matrix_props<m_size = 16, n_size = 16, k_size = 16, a_type = f16, b_type = f16, c_type = f32, result_type = f32, scope = <Subgroup>>]>>}>
<stdin>:26:3: note: called from
<stdin>:820:10: error: failed to serialize executables
<stdin>:26:3: note: called from

Steps to reproduce your issue
To reproduce the issue, run the following command over the given IR (https://gist.github.com/vivekkhandelwal1/b458ba8e74936b2445693663ff89a967):
./build/tools/iree-compile --iree-input-type=tm_tensor --iree-vm-bytecode-module-output-format=flatbuffer-binary --iree-hal-target-backends=vulkan --iree-llvmcpu-embedded-linker-path=/build/compiler/bindings/python/iree/compiler/tools/../_mlir_libs/iree-lld --mlir-print-debuginfo --mlir-print-op-on-diagnostic=false --iree-llvmcpu-target-cpu-features=host --iree-stream-resource-index-bits=64 --iree-vm-target-index-bits=64 --iree-vm-bytecode-module-strip-source-map=true -iree-vulkan-target-triple=ampere-unknown-unknown --iree-util-zero-fill-elided-attrs vulkan_reproducible.mlir

What component(s) does this issue relate to?
MLIR, Compiler
Version information
No response
Additional context
No response

I'm curious what's the Python original input of this dispatch looks like. From what I can see, the following:
%23 = linalg.fill ins(%true : i1) outs(%20 : tensor<1x1x1x?xi1>) -> tensor<1x1x1x?xi1>
  %24 = linalg.generic {indexing_maps = [affine_map<(d0) -> (d0)>], iterator_types = ["parallel"]} outs(%22 : tensor<?xi1>) {
  ^bb0(%out: i1):
    %26 = linalg.index 0 : index
    %extracted = tensor.extract %23[%c0, %c0, %c0, %26] : tensor<1x1x1x?xi1>
    linalg.yield %extracted : i1
  } -> tensor<?xi1>
  %25 = linalg.generic {indexing_maps = [affine_map<(d0) -> (d0)>, affine_map<(d0) -> (d0)>], iterator_types = ["parallel"]} ins(%24 : tensor<?xi1>) outs(%21 : tensor<?xf32>) {
  ^bb0(%in: i1, %out: f32):
    %26 = arith.uitofp %in : i1 to f32
    linalg.yield %26 : f32
  } -> tensor<?xf32>
  flow.dispatch.tensor.store %25, %15, offsets = [0], sizes = [%14], strides = [1] : tensor<?xf32> -> !flow.dispatch.tensor<writeonly:tensor<?xf32>>{%14}

tensor.extract %23 can be folded into %true. So %24 is %true, and then %25 is 1.0. The whole dispatch does not need to exist at all--what's missing is just a pattern to fold tensor.extract(linalg.fill(%v)) into %v.
Is this dispatch a proper translation of the original Python model intent? Wondering whether there is something wrong there.

@antiagainst I'm still blocked by this issue for the same dispatch, and I've been trying to debug it on my end. Is there anything I can try to resolve or work around it for now while a patch is underway?

@suryajasper did you read the comment I have in the above?

Yes, I was able to get the dispatch compiling by folding the tensor.extract op as you mentioned, but I wanted to know the best way to go about implementing this fix for compiling the entire MLIR. Would that involve writing a preprocessing pass to canonicalize every instance of the tensor.extract(linalg.fill(%x)) pattern, or is there a simpler or more elegant solution I'm overlooking?

To me what the above pattern is really cleaning up and canonicalize the IR from earlier stages. I think it makes sense to add it as a canonicalization pattern for linalg.fill directly, given that this is widely applicable and won't interfere with other functionalities much I believe.

@antiagainst just opened a PR with the patch I added. I don't have permissions to assign reviewers, so I just wanted to follow up here. Do you think you could take a look and let me know if there's anything I should change or can generalize further?

Thanks! I guess I wasn't being clear on my suggestions. I commented on the pull request directly. Let me know whether that makes sense! :)

Wanted to update that I have a PR pending in LLVM with the canonicalization pattern that resolves this issue: https://reviews.llvm.org/D156008

@suryajasper thanks! commented there. :)

Hey @antiagainst I was wondering if you had a chance to look over the most recent changes to the LLVM revision. Just following up since there are a few tasks on our side being blocked by the memref issue so it would be great to get the patch in as soon as possible.

Sorry, didn't realize the label got switched to "changes planned". Just fixed the FileCheck prompts in the test mlir and requested review.

Squashed the commits on the revision, so now full patch is visible

Landed upstream. I'll close this one given on further work needed other than bring it in with a future LLVM integration.


[3.0] Moved IdentifierGenerator to Property.

@guilhermeblanco a lot of this seems to be incomplete though - especially the 'FIXME' skipped tests :S

@Ocramius We're pairing to address things here... =)

Gotcha
On 13 Jul 2017 6:06 PM, "Guilherme Blanco"<EMAIL_ADDRESS>wrote:

@Ocramius https://github.com/ocramius We're pairing to address things
here... =)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/pull/6551#issuecomment-315124632,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakJRpu4lp8Koo2ErOeUeOvKKPcX52ks5sNkB0gaJpZM4OXHuK
.

@Majkl578 I've reverted the PR since it I didn't realize until now that there're 100 tests failing. =
Once you reach all tests passing, then I'll look again.


cnspec: 11.30.0 -> 11.31.1

Diff: https://github.com/mondoohq/cnspec/compare/refs/tags/v11.30.0...v11.31.1
Changelog: https://github.com/mondoohq/cnspec/releases/tag/v11.31.1

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 357807

x86_64-linux

:white_check_mark: 1 package built:

cnspec


Documentation - Server

Hello :)
Nothing major. The documentation mentions using http-server, but then gives live-server in the code sample.
Cheers

This should now be fixed on the es6 and es6-tutorial branches.
Please let me know if you're still experiencing any issues.


feat(nx-plugin): Release automation

One particular open question: Currently I have things set up with the license and release generators such that they set defaults for themselves on first run, so that when the package generator runs the per-package related code, it pulls from that. Should we instead extract out those operations such that we have license-core/license-package and release-core/release-package, with the defaults set on the -package generators? That would make the behavior of re-running one of these generators a bit less odd (ie, applying parameters from however you last ran it rather than re-prompting).
That would bring up a further question though: who would be responsible for applying the defaults from the nx.json? When running the generators via the command line, nx itself would do that. Maybe we make the TS interface such that those options are optional, and if not specified then it looks for defaults? The other option, which is more conventional for nx, would be to have the license and release options on every parent generator (eg, instead of just package, it would also be on lib-ts, app-node, etc like name, description, etc are) - though that would mean not just adding it to the schema of each (which is kinda cool since that means we could override the default behavior when we generate a package), but also means we'd need to set these as default values for each generator, which while elegant from an execution standpoint (we never have to inspect the nx.json ourselves) means a lot of extra configuration.
Side note: I filed https://github.com/nrwl/nx/issues/10890 with nx a while back to note that this behavior could be improved by providing a utility in devkit to say "this generator runs this other generator, please raise its arguments and handle things like defaults and prompts for me"
Resolves #55

Another thought: Should I look into setting up some workflow that runs on every commit to main to create canary releases? The idea would be that it would, say, bump every package version one minor version and add something like -dev.<n> and release it to npm under the canary tag so that we could install and test in another project. I wouldn't want to use release-please though as I'd want it to auto-publish instead of requiring a PR merge. Theoretically we could pull in lerna and do a lerna publish --canary --preid dev though I'd need to do a bit of testing (make sure it works appropriately given release-please uses lightweight tags and not annotated tags, plus ensuring its behavior of updating other packages which may be dependent on it makes sense)

Sorry, bump one patch version, not minor version.
Looking through the lerna source, it appears that it should work properly - I'm inclined to add canary publishing to this PR tomorrow. That should also make it easier for us to test our changes since we'll have a dev version pushed to npm! Also happy to hear suggestions about semver and tag names. -dev? -next? -beta? @canary? @next?

Ok so one thing worth noting about doing the canary without annotated tags. In my testing repo, the previous commit was tagged, and we get this:
npx lerna publish --canary --preid dev
lerna notice cli v5.3.0
lerna info versioning independent
lerna info canary enabled
lerna info Looking for changed packages since 14770f3^..14770f3

Found 8 packages to publish:
 - @eternagame/bootstrap => 1.0.1-dev.161+14770f3
 - @eternagame/eslint-plugin => 2.0.1-dev.161+14770f3
 - @eternagame/jest-utils => 2.0.1-dev.161+14770f3
 - @eternagame/lint-staged-utils => 1.0.1-dev.161+14770f3
 - @eternagame/nx-plugin => 2.0.1-dev.161+14770f3
 - @eternagame/nx-spawn => 2.0.1-dev.161+14770f3
 - @eternagame/tsconfig => 2.0.1-dev.161+14770f3
 - @eternagame/vite-utils => 2.0.1-dev.161+14770f3

There's a couple reasons for this:

Lerna is looking for annotated tags, but release-please has github make the tags as part of creating a github release, which uses lightweight tags. We'd need to convert the tags to annotated as part of the release process by running something like git for-each-ref refs/tags/ --format '%(objecttype) %(refname:short)' | while read tagtype tag; do [ $tagtype = commit ] && git tag -a $tag $tag -m $tag -f; done (cf https://stackoverflow.com/questions/21031201/how-can-i-list-all-lightweight-tags)
In independent mode, lerna searches for the last tag like @<scope>/<pkg>@* whereas release-please makes them <pkg>-*.  I think we can get release-please to use that format by setting tag-separator to @ and manually setting component to the full package name with scope for each package in the release-please-config. The question is whether or not we want to. I know we originally discussed preferring the format like<EMAIL_ADDRESS>(which also suggests setting include-v-in-tag to false), though the current tagging of bootstrap-v1.0.0 seems a little more friendly... Maybe that's just me?

Decisions discussed in call:

For simplicity, don't worry about a "correct" build number. No one will really care
-dev and @canary
Use the default release-please tags

Code reviewed on call.


gccgo: bogus incompatible types in binary expression error

gccgo rejects to compile the following program:
package a
var a, b = 0, a^0/8i

go.go:2:15: error: incompatible types in binary expression

Both gc and go/types compile it.
gcc version 6.0.0 20150702 (experimental) (GCC)

@paranoiacblack


redis password/auth not in plugin sample condig

Redis password/AUTH seems to be supported, but the sample config is missing an example of how to provide it correctly. Unfortunaletly I am not that familiar with go, si I couldn't figure it out myself.

true, it's not very well documented, I have change to fix it, thanks for pointing it out :+1:


Fix canvas not updating when deleting layers or redoing/undoing layer changes

Fixes issue: #979
Added a call to Workspace.Invalidate() in DocumentLayers.DeleteLayer() and DocumentLayers.Insert() to always update the canvas when a layer is deleted or inserted.
Another alternative would be to invalidate the workspace from the LayerAction that deletes the layer, and from Undo()/Redo() in DeleteLayerHistoryItem if that is preferred?

Thanks! I think this is okay since other methods like DocumentLayers.MoveLayerUp() are doing the same


Support for execute code in Docker container as well

It will be very nice to have support for executing code in Docker container for security reason.

Dublicate https://github.com/evgenyigumnov/rustsn/issues/19


Redact after transform

Problem
Previously, columns in the patient records table were redacted before they were transformed. In the following snippet, df is the patient records table; suppress_low_numbers is the redaction function; series_report is a statistical transformation (it calculates descriptive statistics); and series_graph is a visual transformation (it plots either a bar chart or a histogram).
https://github.com/opensafely-actions/cohort-report/blob/d9237b52874cad29e8dc6884c1e7b1718cec188b/cohortreport/report.py#L79-L87
The redaction function is essentially a group by/count (series.value_counts()) of the values in a column. If the count of any group in the column -- including the "null" group -- is less than a threshold, then the column is redacted. If not, then the column is returned. Consequently, columns with many, low count groups will be redacted; columns that are drawn from continuous distributions often have this characteristic and so often are redacted. Clearly, this is undesirable.
Solution
Now, columns in the patient records table are transformed before they are redacted. More specifically:

~TODO the statistical transformation, where descriptive statistics were calculated, is now more explicit. Previously, series.describe() was used, which calculates different descriptive statistics depending on the data type (dtype) of the series. Now, "safe" descriptive statistics are used; that is, descriptive statistics that don't require redaction.~

the visual transformation has been split into group, redact, and plot functions. A column that is drawn from a continuous distribution will be grouped (binned) and if a group is less than a threshold, the group (not the column) will be redacted. (This design decision was made through discussion with @robinyjpark and @alexwalkerepi.)

The above has also allowed us to:

replace Plotly with Matplotlib (#7). Plotly does not appear to support histograms with pre-binned data; Matplotlib does, with the weights argument to Axes.hist. Remember, too, that a histogram isn't a bar chart.
switch the axes on the bar charts (#26).
~TODO include additional descriptive information (#27)~

Some additional "nice to haves" are:

a table and a chart for each column in the patient records table, even when a group is redacted; it is easier to interrogate the HTML report on L4
saving charts as PNG images; it is easier to interrogate charts on L4
a cleaner API
less code (468 insertions, 1310 deletions)

Fixes #40
Fixes #50

I've said that this PR fixes #50. You might want some evidence for that claim 🙂 So, let's compare the size of the HTML document before and after these changes. Specifically:

618d190 6.3M
a1e5912 7.7K, with three PNG files of 7.7K, 6.9K, and 6.1K


fix(Pipelines): allow scheduling for only pipelines without parameters

A short, meaningful PR description. Explain the goal of the PR and the ideas behind it.
Changes
Please list / describe the changes in the codebase for the reviewer(s).

display schedule section only when the pipelines has no parameters.

How/what to test
Screenshots / screencast
Pipeline without parameters

Pipeline with parameters

WDYT of adding a permission schedule on the pipeline and using this on the frontend ?

Voila  @qgerome !
Screencast from 07-18-2023 12:41:42 PM.webm


kubectl top does not work

I am trying to use kubectl top node and kubectl top pod on a Kubernetes cluster created using kubo-deployment release 0.13.0.  In all other respects the cluster appears to be working correctly.
When I issue the command kubectl top node, I get the following error:
Error from server (InternalError): an error on the server ("Error: 'net/http: HTTP/1.x transport connection broken: malformed HTTP response "\x15\x03\x01\x00\x02\x02"'\nTrying to reach: 'http://<IP_ADDRESS>:8082/apis/metrics/v1alpha1/nodes?labelSelector='") has prevented the request from succeeding (get services http:heapster:)
This looks to me like an https response, and when I do kubectl top node --heapster-scheme=https, I get the following response:
error: You must be logged in to the server (the server has asked for the client to provide credentials (get services https:heapster:))
This is perhaps more promising, but I don't know how to correct have kubectl top authenticate to heapster.
For kubectl get pod, I get the following response:
W0204 14:10:09.688668   28189 top_pod.go:192] Metrics not available for pod auctionw1i1/default-http-backend-8d5449cd7-pbdh4, age: 37m15.688644441s
error: Metrics not available for pod auctionw1i1/default-http-backend-8d5449cd7-pbdh4, age: 37m15.688644441s
The response is the same even if I specify --heapster-scheme=https
Any suggestions on how to get this working?

@hrosenbe Thanks for raising the issue - we've been able to recreate the issue.  I'll ask for it to be prioritised.

I have a similar issue. With my admin account, I can issue kubectl top nodes and top pods and they work fine. However developers that have a more restrict RBAC role, receive a error message like this:
"17951 top_pod.go:192] Metrics not available for "
Would you know what kind of permissions does a role need to issue this command?

The same issue in my cluster.
`[root@cfcr-install ~]# kubectl top nodes
Error from server (InternalError): an error on the server ("Error: 'net/http: HTTP/1.x transport connection broken: malformed HTTP response "\x15\x03\x01\x00\x02\x02"'\nTrying to reach: 'http://<IP_ADDRESS>:8082/apis/metrics/v1alpha1/nodes?labelSelector='") has prevented the request from succeeding (get services http:heapster:)`

By default, Heapster is configured to talk over HTTPs, so you’ll need to set the flag that forces that (--heapster-scheme='https').
That said, it’s still unlikely to work unless your kubeconfig is using certificate credentials rather than bearer token credentials. Heapster seems to reject the inbound request if you’re using a bearer token. If you have a certificate signed by the kubo_ca it may work though - I haven’t had a chance to test it yet.

This should be fixed as of cloudfoundry-incubator/kubo-release@ce0a8e8667f0a8a8ca68fd56304211555bda20c8.


"Invalid language object" on<EMAIL_ADDRESS>

Hi there. I tried testing this library with the latest version of node-tree-sitter (0.21.1) and I'm getting an error Invalid language object when calling parser.setLanguage(Swift).
Related issue: https://github.com/tree-sitter/node-tree-sitter/issues/193
It looks like the 0.21.1 node package made some breaking changes by switching over to the napi interface for running native code, which means this repo needs to regenerate the bindings.
I tried running tree-sitter generate on the repo in a fork but was running into some strange missing symbol errors that I haven't been able to figure out yet. Happy to open a pull request with those changes but it was literally just me running the command.

Fixed in #404


Using React component classes

My polymer2 branch now has support for using ES6 classes with mixins.
Feel free to help upgrade the rest of the components to ES6 style

Everything changed, not so easy to review...

Are there changes in behavior, or is it the same?
Which features are tested?
Anything which needs to be done before it could be merged and used in production apps?

Extension of #344

I cloned the repo then pushed. Didn't fork, why commit stories might be out of sync.
I documented most of the changes in a migration doc in root folder. Most everything should work.

No changes in behavior. Been working on network graph example only. Can draw connections between nodes as before.

By migration doc, do you mean 'Polymer2-migration-notes.md'? That file is empty. Anyways,
To you intend for this to branch to merged into this repository?
Do you intend to help maintain it if it gets merged?
If so there are a lot of things that needs to be fixed. But before we go to details, there are two major things that must be dealt with. For this to be at all possible to merge, it needs to:

Help to remove Polymer dependency (or at least not make it worse)
Not break existing functionality

1
This branch seems to add more dependencies on Polymer. And furthermore changes the version to a yet-to-be-released version. Do the React components still work with old Polymer? Can the components be used without Polymer? Does it get us closer to working without Polymer somehow?
2
I tested the examples/demo-network.html (in latest Chrome). Several pieces of basic functionality seems to be broken. For instance:

No panning of graph with either touch or mouse
No context menu when right clicking on either

The other examples are completely broken, the intial graph does not even render. I tried to update to reflect the changed locations of some .js, and it still did not render.
This to me suggests that not much testing of existing features was done...

The essential (for my needs) functionality works for the network demo.
IMO it needs a complete rewrite from scratch. Ideally much of the functionality extracted and not  tightly integrated with React or any such framework. Yes, a mess mixing Polymer and React his way. Would be better done using custom elements or web components.
I'm fed up with web development tbh. Still working  knee deep in garbage most of the time. Lost my motivation. Can't look at code any more... Need a break for at least 6 months. This code is garbage as well, sorry. Not sure if you are the original author. Can't stand to look at anymore garbage...

Ok, I am glad you were able to massage the code to fit your purposes!
Not a problem that you are not interested in maintaining, I just need to know, since I have to maintain it :)
I am not the original author no, I took over because we use it in flowhub/noflo-ui.
The code might be shit (as is typical), but the code is used and useful, which is more important. More problematic is that there are no tests, and documentation of expected functionality is missing.
I don't believe in rewrites from scratch. Prefer to make it better iteratively. Some desired cleanups are docuemented in #314. Reducing framework dependencies is key. The benefits are small for this usecase, and the costs high due to their invasiveness (Polymer is real bad here) and API churn..

Hey, sorry, was in a bad mood when I replied before ;) I submitted migration notes now. Should be easy to migrate the Polymer classes to Rails classes I think. But yeah, I'm out of the game for a while.. would rather be a farmer than a developer at this point :p

Shit happens :) Thank you for the migration notes!


Implement nodeCheck into ami-check

We should implement some code that ensures that the hosting node is ready to do network connections on the network connectivity check. If the check runs too fast, then a node may not be able to connect to the target and that would cause a false alarm.

Someone has already done this. Showing up in Master already


SD-JWT: Parse EUDIW issued credential

Final part in a series of PR to improve SD-JWT interoperability.
Parse EUDIW issued credential and add option to verify the JWS when public key is not provided in the header.

Has been merged