not working in Ubuntu 20.04.3 LTS

it throws this error:
tk-Message: 19:21:25.297: Failed to load module "canberra-gtk-module"
(Psyc:68811): Pango-ERROR **: 19:21:25.580: Harfbuzz version too old (1.2.7)

Any chance to work?

@nephew92
new zip for debian-11 support, you can try
https://github.com/PlanetRenox/psyc-d11/tree/master/download

I got this error in Ubuntu 21.10
[1]    81909 segmentation fault (core dumped)  ./Psyc

I got this error in Ubuntu 21.10
[1]    81909 segmentation fault (core dumped)  ./Psyc

the same I have in 22.04...

The above link is 404

Has thi

I got this error in Ubuntu 21.10
[1]    81909 segmentation fault (core dumped)  ./Psyc

the same I have in 22.04...

Has this been resolved? I am getting the same error


AnimatorTransitions ignored

AnimatorTransitions are currently ignored by the transition condition conversion, which causes issues with CGE and similar avatar setups.
AnimatorStateTransitions (Implemented)
AnimatorStateTransition always originate from an Animator State (or AnyState) and have timing parameters.
AnimatorTransitions (Needs Implementing)
AnimatorTransition always originate from a StateMachine or a StateMachine entry. They do not define timing parameters.
They both Inherit from AnimatorTransitionBase.

I have a fix for this in my fork, I can submit a pull request if you like.

Merged :)


Parse service hostname from proto annotations

Adding testing using mocks, and testing of the ProtoParser itself.

PTAL

Codecov Report

Merging #2328 into master will decrease coverage by <.01%.
The diff coverage is 89.47%.

@@             Coverage Diff             @@
##             master   #2328      +/-   ##
===========================================
- Coverage      86.8%   86.8%   -0.01%
- Complexity     5168    5174       +6
===========================================
  Files           454     454
  Lines         20511   20520       +9
  Branches       2209    2210       +1
===========================================
+ Hits          17805   17812       +7
- Misses         1932    1933       +1
- Partials        774     775       +1

Impacted Files
Coverage Δ
Complexity Δ

...a/com/google/api/codegen/config/DiscoApiModel.java
68.57% <ø> (-0.88%)
10 <0> (-1)

...odegen/transformer/DiscoGapicInterfaceContext.java
65.04% <100%> (+0.34%)
28 <1> (+1)
:arrow_up:

...egen/transformer/go/GoGapicSurfaceTransformer.java
99.52% <100%> (ø)
38 <0> (ø)
:arrow_down:

...nsformer/nodejs/NodeJSGapicSurfaceTransformer.java
100% <100%> (ø)
27 <0> (ø)
:arrow_down:

.../transformer/py/PythonGapicSurfaceTransformer.java
98.29% <100%> (ø)
43 <0> (ø)
:arrow_down:

...degen/transformer/java/JavaSurfaceTransformer.java
98.44% <100%> (ø)
60 <0> (ø)
:arrow_down:

.../transformer/ruby/RubyGapicSurfaceTransformer.java
99.63% <100%> (ø)
44 <0> (ø)
:arrow_down:

...a/com/google/api/codegen/config/ProtoApiModel.java
90% <100%> (+0.25%)
18 <2> (+1)
:arrow_up:

...ansformer/csharp/CSharpGapicClientTransformer.java
97.77% <100%> (ø)
52 <0> (ø)
:arrow_down:

.../java/com/google/api/codegen/util/ProtoParser.java
76.47% <100%> (+7.23%)
9 <4> (+4)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

Nodejs test CI test failing because of https://github.com/googleapis/gapic-showcase/issues/25.


fix(vite): fix HMR preamble race condition

Closes #7863.
This PR fixes a couple issues:

Resolves a race condition between the React Refresh preamble script and the app code by ensuring that the preamble is imported first in the same script tag as the app code.
Allows the LiveReload component to behave the same as the existing Remix compiler from a consumer perspective. You can now choose not to render it, forcing you to perform a full refresh to see changes, and you can also render it after Scripts. I've updated the ordering of LiveReload and Scripts in the Vite tests to show this is the case.

Also, I could have sworn that using <LiveReload /> without <Scripts /> worked for HMR in esbuild-based compiler, but I guess not. So this would get us parity (and then some) with the current Remix compiler.


Remove rules for diffs that are no longer used/needed

The custom Makefile contains several rules to generate custom diffs:
(A) A diff between the local -edit file and the version from the master branch on GitHub. Exists in two versions: one with the imports removed (reports/diff_edit_noimports.txt), one with the imports merged (reports/diff_edit_imports.txt).
(B) A obo-diff.txt (unclear why it is called like that, it is generated from OWL/RDF files), produced by comparing the latest local build with the latest release, after removing (1) all non-CL stuff (thereby producing something akin to a “base” file) and (2) all annotations except rdfs:label (so that we only really compare logical axioms, plus labels).
(C) the “release-base-diff”, a standard ROBOT diff made by comparing the latest base release with the locally produced base.
(D) the “content summary”, also made by comparing the latest base release with the locally produced base, but produced by a custom Python script and OAK’s diff.
(C) and (D) are produced and published upon every release. However, (A) and (B) are never automatically produced and only generated if someone explicitly invokes the corresponding rules. I think it is doubtful that (A) and (B) are needed at all (especially (B), which is made quite redundant by (C) and (D)), and I’d be inclined to remove the corresponding rules entirely.

I agree - if they are not invoked by GHActions we can remove them - if they are needed we can add a better version back in the future. I doubt anyone is really using it?

Leaving them for now as there is always a chance that an editor is generating those diffs locally (especially the diffs against the master branch) to test the impact of their changes before even submitting a PR.
But if nobody shows up in, say, one or two months to say that they use those rules, then I’ll submit a PR to remove them.


Mars server list as config argument

Tested on mini-cci stack and it does not break current MARS adaptor.


chore: Reduce number of variables for small memory optimization

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

6 of 6 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 86.412%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.02%

Covered Lines:
2035

Relevant Lines:
2355

💛  - Coveralls

Merging to force rebuild of image


find_provider_for_node deprecation warnings

Cookbook version
3.1.1 - Latest released version
Chef-client version
12.21.3
Platform Details
Centos 7
Scenario:
Clean chef-client run
Steps to Reproduce:
Run chef-client
Expected Result:
No deprecation warnings from chef-client
Actual Result:
  Chef::Platform.find_provider_for_node is deprecated at 1 location:
    - /opt/chef/embedded/lib/ruby/2.3.0/forwardable.rb:189:in `execute_each_resource'
   See https://docs.chef.io/deprecations_chef_platform_methods.html for further details.
  Chef::Platform.find_provider is deprecated at 1 location:
    - /opt/chef/embedded/lib/ruby/2.3.0/forwardable.rb:189:in `execute_each_resource'
   See https://docs.chef.io/deprecations_chef_platform_methods.html for further details.
  Chef::Platform.find is deprecated at 1 location:
    - /opt/chef/embedded/lib/ruby/2.3.0/forwardable.rb:189:in `execute_each_resource'
   See https://docs.chef.io/deprecations_chef_platform_methods.html for further details.

Triggered by https://github.com/chef-cookbooks/windows/blob/master/libraries/windows_helper.rb#L55

This has been resolved in the newest releases. Try out the new version and feel free to open this back up if you're still seeing it.


Typo in goneovim.txt

Should be .config not .condig i think.
https://github.com/akiyosi/goneovim/blob/3c8b47e59dabcce9c4be6556fa2050f7a7447942/runtime/doc/goneovim.txt#L329-L330

Thank you!
Fixed with https://github.com/akiyosi/goneovim/commit/4d49ecf2d9c908c011ca1a55a193645e00238532


Fix Coingecko configuration for Gnosis Chain

Fixes the Coingecko native coin name for Gnosis Chain

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 91.259%

Files with Coverage Reduction
New Missed Lines
%

src/routes/transactions/entities/tests/human-description.builder.ts
1
90.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
4817

Relevant Lines:
5156

💛  - Coveralls


When following step 3 to ssh i am unable to get in because it is asking for a password which i do not know

I'm sorry, but I don't have any context on this issue. Can you describe what your deployment looks like?
I'm closing this issue for now while in fact-finding.

I'm also getting the issue


Who to contact for security issues

Hello 👋
I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@michaellrowley) has found a potential issue, which I would be eager to share with you.
Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.
Looking forward to hearing from you 👍
(cc @huntr-helper)

Hi JamieSlome
SECURITY.MD has been added to the project.
Please contact me by email<EMAIL_ADDRESS>


Allow port-forward to target a port name

The extension does not allow targeting port names - this would be convenient.

This would be a really nice idea, especially if we can find a good UX for it.  Of course we can easily allow names but I wonder if we can also allow users to browse for port names on the pod...  Thanks for the suggestion!


iOS init option type

So, all examples and code samples call .init() with string options passed on the iOS part, but they're specified as Boolean on README.md. Checking source code I can see that both ways are handled, but shouldn't we either

pick one way and go with it
or
be explicit that both ways work
?

@fredgalvao feel free to update the docs on this one.

@macdonst  Which approach is the desired one though?

@fredgalvao I believe in defensive programming. So if I'm expecting a boolean true I also except the String "true" to be valid. Same thing for false.


ScienceUtils does not have charset pinned down

This is related to https://github.com/clulab/eidos/pull/806 and likely also to #359.  Code in ScienceUtils, namely
  private def loadAccents:Set[Char] = {
    val acf = getClass.getClassLoader.getResourceAsStream(ACCENTED_CHARACTERS)
    assert(acf != null, s"Failed to find resource file $ACCENTED_CHARACTERS in the classpath!")
    val reader = new BufferedReader(new InputStreamReader(acf))

and
  private def loadUnicodes:Map[Char, String] = {
    val map = new mutable.HashMap[Char, String]()
    val is = getClass.getClassLoader.getResourceAsStream(UNICODE_TO_ASCII)
    assert(is != null, s"Failed to find resource file $UNICODE_TO_ASCII in the classpath!")
    val reader = new BufferedReader(new InputStreamReader(is))

do not have the Charset pinned down and it is left up to the operating system and user to decide.  In this case we made the files and know the encoding, so it should definitely be specified here.
See also https://docs.oracle.com/javase/7/docs/api/java/io/InputStreamReader.html.

@kwalcock: I am happy to fix this. But which Charset should we use?
Thanks!

Notepad++, which is never wrong, says UTF-8, and this code seems to work:
      val reader = new BufferedReader(new InputStreamReader(is, StandardCharsets.UTF_8))

I notice that the reader in loadUnicodes does get closed (unless there is an exception), but the one for loadAccents does not.  I will use the case to justify my paranoid programming practices in other code ;-)

Notepad++, which is never wrong

@kwalcock working with you is so much fun :)


Move olx.render.* and related typedefs to ol/render/*

Changes according to #7838, subtask of #7947
externs/olx.js is basically empty now. I did not remove it, because this would require additional changes which are out of scope for my task.

Rebased with master to resolve conflicts

Rebased with master to fix conflicts

ol/render~State still had an error. I put the fix into the very first commit. Tests are passing now.

Thanks for the work on this @pfirpfel.


Build Topic Details Page Blueprint + Supporting Updates

Jira
http://vjira2:8080/browse/BDS-1890?filter=-1
Summary
Topic Details Page buildout + supporting updates.

Details
This work includes:

Adding 3 new placeholder images used on the Topic Details page that include the actual image's dimensions (living documentation)
Adding a new Edit button to the Toolbar (used by the Topic Details page) + reordering the buttons to match comps
Fixing the Hero Title to properly use an <h1> (addressing this issue flagged by the Drupal team)
Lightly refactoring the details page hero so pages with 2 columns line up properly
Adding the ability to disable sticky positioning on the new Toolbar component (on by default)

Updating the Topic Details page template to automatically disable the sticky toolbar to avoid UI layering issues with TOC + Toolbar

Updating the details page template to support displaying:

A side nav (TOC)
Page controls (on the top / bottom of the page)

Updating the breadcrumbs to related Blueprint demos so demos to the difference sections are linked
Creating the new Topic Details page blueprint
Fixing layout issues relating to overflow scrolling + TOC not working on actual pages
Updating our existing float utility classes to now support breakpoints
Tightening up the styling of the new TOC component to more closely match the design comps

Adding a temporary workaround to @bolt/core styles not actually supporting bold font weights!

How to test

Just a quick high-level review is needed so we can get this in for the v2.17.0 release. Let me know if there's any items we can defer + follow-up on with our next release.

PR was released with v2.17.0


Discussion: Inputs and outputs for workflow modules

Currently, the inputs for OpenScPCA-nf modules are channels that contain the following tuple:
[project_id, project_dir]
This makes for a pretty nice compact and universal input, and for modules that depend on nothing but "raw" data it is is pretty easy to work with. It is therefore currently the module workflow's responsibility to filter the inputs down to the portion of the data that is needed for each analysis.
However, that structure may not be workable in the case that one module depends on the output of another module. We have not yet described standards for what a module workflow might emit for consumption by other module workflows, but it seems unlikely that the output would be of the form [project_id, project_dir].
There are a couple reasons for this:

For efficiency, workflows are likely to split input projects into multiple streams, and joining them back into a single output could be difficult

For example, the simulate-sce workflow largely performs its simulations on a single sample at a time. While it would be possible to rejoin the results into a single directory, this would mean we would need to have a process that downloads the data for all samples within each project and then emits the folder with all of them in it. This would result in a lot of copying without much benefit.

The contents of an output directory may not be as predictable as inputs, and it may be better to have more fully specified input channels which contain more information about the kind of data that is needed for each workflow.

A motivating example
I already mentioned the simulate-sce module workflow, and it was the main reason I started thinking about this problem in the first place (though as I write this I may have a simpler/better solution, discussed below). The simulate-sce module workflow does not currently emit anything, but we might want it to, in order to use the results from that workflow in downstream workflows. For example, the merge-sce workflow could be used to create simulated merged data.
However, the merge-sce workflow currently expects [project_id, project_dir] as input, and as discussed, this might be a pain to produce from the simulation workflow, which works on a sample-by-sample basis.
An easier output might be something of the form [project_id, sample_id, sample_dir], but then the consuming workflow (merge-sce in this case) might have to perform some form of merging on the input channel if it wants things organized by project. This isn't necessarily terrible to do: we could do that with something like groupTuple() function.
This assumes that we want to pass along the whole directory, which we probably don't need to do all the time. This simulate-sce function produces both SCE and AnnData objects: different workflows might want to consume one or the other of these, and sometimes both? The merge workflow really only needs the SCEs, and of those, only the processed files. So we could instead have a workflow emit  multiple channels: a set with [project_id, sample_id, sample_sce] , where we might separate out processed and earlier stage files, and separately [project_id, sample_id, sample_anndata], though because AnnData are likely be split by RNA and other features, sample_anndata might actually be a array of files at times (or in the case that there is more than one library for a sample), though Nextflow generally handles this pretty reasonably.
Other outputs
One can also imagine that some workflows might not output sample-level info at all, or might have multiple files per sample. Another likely scenario is that a workflow outputs some results that need to be combined with other data for a downstream analysis. An example of this might be cell typing or doublet detection: for efficiency we would not want the output of these analyses to be another whole set of annotated SCE files, but instead a table of annotations that we could use to join with the original data in a downstream step.
For outputs like these, we would want to emit them on a sample-by-sample basis, to allow the workflow to use a join() or combine() operation (likely join(), assuming one output per sample, as these are more efficient than combine()).
Thoughts toward a standard
We want to keep the inputs and output from module workflows relatively consistent to make interactions between them as easy as possible. So we should favor relatively short, simple tuples within the channels where we can, especially given the fact that Nextflow does not  use named tuples for channel elements. (What happens within a module can get more complex as needed.)
It seems likely that most analyses will have at least some component that is run on a sample-by-sample basis, so it seems likely to make sense to make that the main unit of organization. If we always have the first two elements of the cross-workflow channels be [sample_id, project_id] (in that order to facilitate join operations).
Following those two identifiers, we would have a slot for the main data, which we should probably prefer to be a file or array of files. Workflows that produce multiple kinds of outputs that are not expected to be used together often (such as SCE and AnnData output) can emit more than one channel, with different sets of files. Any emit statements should use descriptive names, such as sample_processed_sce_ch to indicate the contents of the final element(s) of the tuple.
Putting this together, we might have a workflow that looked something like the following (though a real workflow would be more complex!):
process do_annotation {
  input:
	tuple val(sample_id), val(project_id), path(sample_sce)
  output:
    tuple val(sample_id), val(project_id), path(annotation_tsv)
}

workflow annotate {
  take:
    sample_sce_ch // [sample_id, project_id, sample_sce]

  main:
    do_annotation(sample_sce_ch)

 . emit:
    sample_annotation_ch = do_annotation.out // [sample_id, project_id, sample_annotation.tsv]
}

A later workflow could then combine the channels above for a later analysis that used the annotations:
workflow use_annotations {
  take:
    sample_sce_ch // [sample_id, project_id, sample_sce]
    sample_annotation_ch // [sample_id, project_id, sample_annotation]

  main:
    combined_ch = sample_sce_ch.join(sample_annotation_ch)
    ...
}

The main limitation I see with this plan is that it may not be uncommon for a workflow to also want access to the sample metadata sheet for the project or other project-level data like bulk sequencing. We could pass this in as a separate channel, or include the project_dir in each channel as well, with the expectation that most workflows would disregard that element, or simply pass it along unmodified.
Or just run the workflow twice
While I was originally thinking about this as a way to have a single-shot run of the workflow that would either include or not include the simulation step, followed by running everything else, it may be much simpler to just have two workflows for that use case: One to run the simulation and a second to run afterward to just work with either the real or simulation data buckets as the input. Having written all this, I think this is the way we should probably go, but there may still be value in starting to codify some expectations about workflow outputs for some of the more complex cases.

It seems likely that most analyses will have at least some component that is run on a sample-by-sample basis, so it seems likely to make sense to make that the main unit of organization. If we always have the first two elements of the cross-workflow channels be [sample_id, project_id] (in that order to facilitate join operations).

I think this is very likely and that most things will work on a per sample level. I think the merging is actually the exception here. Also I think if we were going to have anything that relied on merged objects downstream they would be mostly separate from processes that take individual samples so we probably wouldn't have to join this output with per sample output.
That being said I do think using something with [sample_id, sample_sce, project_id] would allow us the flexibility to join things and group things as necessary within individual workflows.

While I was originally thinking about this as a way to have a single-shot run of the workflow that would either include or not include the simulation step, followed by running everything else, it may be much simpler to just have two workflows for that use case: One to run the simulation and a second to run afterward to just work with either the real or simulation data buckets as the input. Having written all this, I think this is the way we should probably go, but there may still be value in starting to codify some expectations about workflow outputs for some of the more complex cases.

Another option that I don't know how I feel about but could be worth thinking about is having a single sample workflow and a grouped workflow. So the main.nf will run any analyses performed on individual samples. Then you have a separate group-analysis.nf that does the merging and then performs analysis on merged objects. I would imagine that would be things like differential expression, NMF, etc. While the single sample workflow contains things like cell typing.
Alternatively, if you update to make the input/output to everything on a per sample level then you can have a flag that runs the workflow with simulated data and runs the simulate step and if not used it will use real data and skip the simulate step. But this would only work if you move any grouping of projects to within each module.
Just jotting down some thoughts, but generally I think we might continue to make updates as we add more modules and see what works best.


Fix findMember for param accessors again.

The situation is much more complex than initially thought. Param accessors can be referred to by name, using ThisType prefixes. Moreover, non-private param accessors are truly the public vals, so they must be accessible from anywhere.

We fix widenIfUnstable, so that ThisType are not widened (among others).
We provide convenience accessors for the symbols of Idents and Selects.
We add a new flags.isAllOf(required, butNotAnyOf = excluded) method.
With all that, we fix ClassSymbol.findMember for the above issues.

/cc @shardulc

Rebased (without changes) to get the new versionPolicyCheck.


Decouple Post-Post Processing

The post-processing after decoding is in indexers; we should separate it out for future enhancements.

post-processing is gone and will be implemented as array methods.


removeIcon for Label conflicts with children

Steps
I'm trying to use a label with removeIcon:
Test

Expected Result
Add 'x' Icon, which listen to onRemove.
Actual Result
Warning: Failed prop type: Prop `removeIcon` in `Label` conflicts with props: `children`. They cannot be defined together, choose one or the other.

Version
0.73.1

removeIcon is the shorthand prop, it's not possible to combine shorthand props with children. You should use content prop there:
   {}}
  />
   {}}
  />

BTW, it's not required to use removeIcon prop, it will be added by default if onRemove callback is present. However, you can use for some tricks like this:
   {}}
    removeIcon={{ color: 'red', name: 'delete' }}
  />


Performance Improvements Tutorial - Integration with Swoole

Description of your feature
Swoole integration tutorial need (https://github.com/swooletw/laravel-swoole)

Information

hyn/multi-tenant version: 5.x
laravel version: 5.x

Hi there,
Personally, I don't think we need to provide a tutorial related to this.
Laravel Swoole is simply a package to make Laravel use the Swoole extension, I don't think there's anything you need to do with this package in order to make that work accordingly.
However, it's a package I have not used with our package and if you want to document a tutorial for it, feel free.


Stream selectors, .map operator (audio support)

Implements stream selection and mapping multiple streams to one output.
Example:
i = ffmpeg.input("video_with_sound.mp4")
audio = i[:"a"].filter_("aecho", 0.8, 0.9, 1000, 0.3)
video = i[:"v"].hflip().vflip()
single_output = ffmpeg.output(video, audio, "my_output.mp4")
# or
single_output = video.output("my_output.mp4")
single_output = single_output.map(audio)

ffmpeg -i video_with_sound.mp4
-filter_complex
'[0:v]hflip[s0];[s0]vflip[s1];[0:a]aecho=0.8:0.9:1000:0.3[s2]'
-map '[s1]' -map '[s2]' my_output.mp4

Closes #26 and #42

I agree with all your comments. I will probably get to it after holidays. See my reply to your immutability comment.

Btw, we should probably update the readme after this gets merged to show how to do audio right off the bat since a lot of people seem to run into the same issue again and again.


fix: Reset widget to default value after setter method has been applied

Description
This PR migrates the resetWidget logic to the web worker.
PR fixes following issue(s)
Fixes #27442
Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Bug fix (non-breaking change which fixes an issue)

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/build-deploy-preview skip-tests=true

Fixed here https://github.com/appsmithorg/appsmith/pull/29151


A.03.01.inspire.search.attributes

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment

XPATH expression is missing
Test type can be 'automated'
Adapt last sentence to:
'This test is an abstraction of the tests A.3.7 INSPIRE search criteria, A.3.8 Language search criteria and A.3.9 Additional search criteria'

Proposed Change
Add XPATH reference

See #52: this is a summary (abstraction) test case, covered by tests elsewhere. This need not be directly implemented - are we planning to remove these summary cases?

The only test cases that should be specified are those that need to be executed (manually or automated). Summary text may be included in the description of the conformance class / ATS.


Fixed #33408 -- Fixed adding primary keys/unique fields on SQLite.

Regression in 2f73e5406d54cb8945e187eff302a3a3373350be.
Thanks Alan Crosswell for the report.
ticket-33408

@n2ygk Does it work for you?

@felixxm Looks good!
(dot-venv) django-oauth-toolkit$ pip install git+https://github.com/felixxm/django.git@issue-33408
...
Successfully installed Django-4.1.dev20220103200100
(dot-venv) django-oauth-toolkit$ DJANGO_SETTINGS_MODULE=tests.settings pytest
...
==================================================== 378 passed, 5 warnings in 222.54s (0:03:42) ====================================================

Just a few DJ5.0 deprecation warnings

@felixxm Looks good!

Thanks for the confirmation :+1:

@charettes Thanks :+1:


[JA] Feedback for: /fundamentals/getting-started/web-starter-kit/setting-up.html

This page appears to be mostly untranslated.
(I simulated the effect of my PR #1002 for clarity, but it's not yet live)

I've marked it for re-translation for the next round.


Change email content-type to text/html

Because i'd like to use html in formdiesginer email templates.
Refs MH-50

This needs to be parametrized somehow; we can't have all mails sent by DFD suddenly being HTML when they've been plain-text before.

somehow parametrized

That's nicer! Thanks. :)


Feature request: base64url encode and decode

Base64URL is a modification of the main Base64 standard, the purpose of which is the ability to use the encoding result as filename or URL address. The Base64URL is described in RFC 4648 § 5, where it is mentioned that the standard Base64 alphabet contains invalid characters for URLs and filenames.

The first problem is that the main standard uses “+” as the 62rd character and “=” as padding character. Both characters have a special meaning in the URI address: “+” is interpreted as space, while “=” is used to send data via query string as “key=value” pair. As you understand, using these symbols may lead to various errors.

The second problem — the main standard uses “/” as the 63rd character, which both for URL addresses and for file system locations, represents the directory separator. Therefore in this case errors are guaranteed.

To avoid the errors above, it was proposed to use a “safe alphabet” for URL addresses and filenames. Thus, the Base64URL was born. It uses the same algorithm as the main standard, but differs in the following:

Replaces “+” by “-” (minus)
Replaces “/” by “_” (underline)
Does not require a padding character
Forbids line separators
For example, the main standard will encode <> to PDw/Pz8+Pg== while Base64URL will convert it to PDw_Pz8-Pg. As > you can see, only special characters have been changed, while the letters and digits have remained intact.

source: https://base64.guru/standards/base64url

I can't get any useful information from your title. Please make sure to write complete scenarios and examples when submitting feature requests.

I can't get any useful information from your title. Please make sure to write complete scenarios and examples when submitting feature requests.

replenished

Well I think you can convert base64 to base64url yourself...? I don't see a common use for it.

Well I think you can convert base64 to base64url yourself...? I don't see a common use for it.

ok


Sonar analyze: component, update, details not covered

Overview of the issue
When launching Sonar Analyze, under Sonar, these files are not covered:

component.ts
update.component.ts
details.component.ts

When we use npm test, it seems to be covered
I'll update the template later if needed
Motivation for or Use Case

Reproduce the error

Related issues

Suggest a Fix

JHipster Version(s)

JHipster configuration

Entity configuration(s) entityName.json files generated in the .jhipster directory

Browsers and Operating System

[ ] Checking this box is mandatory (this is just to show you read everything)

I'm adding a bounty on this, as it is really important for us, in our current project with @nonomoho
So if someone can help

You mean the update and details components for entities, right? For me it looks like they are also not covered when doing npm test, although there is unit test for that.

yes exactly @atomfrede it's for entities
but I remember I saw the same thing yesterday for health too:

health.service.ts is covered
health.component.ts not
Both got spec.ts

Yes. .component.ts are nowhere to find in the coverage reports also there is a spec for that which is executed. Very strange indeed.

You can find their coverage under corresponding .vue files like user-management-edit.vue contains the coverage of JhiUserManagementEdit.

I think it's related to https://github.com/SonarSource/SonarTS/issues/477

Oh thanks @vishal423
We can see @sahbi-ktifa already answered to the ticket lol

In a project I'm working on we use only .vue files without distinct .component.ts files. And our sonar analysis has the correct coverage information.
Could we consider to use only .vue files to fix this issue ?

Using only .vue file for fixing this Sonar Analyze is not a good idea.
We split into TS file, to be consistent with Angular part, and it will probably help to migrate to Vue 3.
There is already an opened ticket for that: https://jira.sonarsource.com/browse/MMF-1441
So the real issue is on their side.

Using only .vue file for fixing this Sonar Analyze is not a good idea.
We split into TS file, to be consistent with Angular part, and it will probably help to migrate to Vue 3.
There is already an opened ticket for that: https://jira.sonarsource.com/browse/MMF-1441
So the real issue is on their side.

@pascalgrimaud it seems that it is not a priority for them :(


Remove manual pkgconfig provides from non-toolchain specs

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/tools/cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

In Mariner 2.0, manual Provides: pkgconfig(*) statements are no longer necessary. These provides are generated automatically by RPM. The effect of these manual provides is benign when written properly with proper versions in the proper subpackages, but can cause build tooling confusion when done incorrectly. So, we should remove the manual provides statements.
This work was completed for the toolchain in #2155. This PR extends that work to non-toolchain specs.
Change Log

Remove manual pkgconfig(*) provides from non-toolchain specs.

Does this affect the toolchain?

NO
Test Methodology

Pipeline build looks good, generated pkgconfig provides look good in changed specs

Could you double check that the tooling updates I did are still happy? (Check the end of the package build phase, where it lists all the .rpm files it built. If there are any conflicts it will list any conflicting .rpms in red).
I don't think there should be any issues though.


Add Option to leave apps mounted

Currently, child apps are unmounted whenever the user navigates away from them.  If there was an option to leave an app mounted, only the initial load would be necessary.
I'm not sure how to set up passing options into the loader, but my team has manually cloned this repo into our project and turned off unmounting, so I could help with that.

Just a quick observation/consideration: unmounting and then remounting an app shouldn't cause any additional load since the child file should already be in the browser cache. Long load times may be a problem within the child app (eg. waiting for data retrieval before rendering anything to the page) and not necessarily with it being a singlespa child.

I apologize, I may have misspoken in my initial statement. What you said is correct. The long load times have to do with data retrieval from api calls. That still presents the problem though: we do not want to re-retrieve the same data from an API every time we mount the app, and by leaving the apps mounted, the data stays where it is.

This is fixed by PR #28

Unfortunately due to our specific use case, it's not viable to do all data retrieval in the parent app.

@bfaulk96 we'd have to discuss this feature in greater depth, but I'd like to understand a bit more. It seems like you are trying to solve what is ultimately an API/Application problem by changing the fundamental design of single-spa. When an application isn't mounted single-spa prevents events from hitting the application by design, leaving an application mounted will almost certainly cause some larger performance issues.
There are a few options I see immediately and @filoxo mentioned one of them.

Have the slow data request done by the single-spa-config/parent-application
Have the data request cached by the browser
Make the data request during the lifecycle functions only if the data isn't already cached by the project.
Have a shared data store that the child applications have access to

What performance issues do you foresee? What if, in a future single-spa update, you add the ability to keep the first N apps mounted? That way, you could keep say, 5 apps mounted, but after 6 the oldest would be unmounted? Either way, can we silently add this workaround to this helper library for now? It won't affect anyone else, and improves performance for our use-case.

What performance issues do you foresee?

Events are being sent to an application that doesn't need them. Those events could easily trigger side effects that would be very difficult to debug

What if, in a future single-spa update, you add the ability to keep the first N apps mounted? That way, you could keep say, 5 apps mounted, but after 6 the oldest would be unmounted?

Again we're talking about making a major change to the design of single-spa to support a use case that is already supported, I don't (yet) see an advantage to this approach versus the common approaches I've mentioned above

Either way, can we silently add this workaround to this helper library for now? It won't affect anyone else, and improves performance for our use-case.

single-spa-angular-cli isn't my project so that's up to @robinComa but IMHO I don't see how adding this feature will benefit you beyond the other options and I can easily see how it could negatively impact others in the future. There are ways to get the exact same performance improvements you want without fundamentally changing single-spa and they exist right now in javascript

Leaving apps mounted even after their activity function says they shouldn't be mounted goes against single-spa's ideology. The problem you're describing with a slow network request needing to be cached can be solved in a lot of other ways -- I think those methods are preferred.

Thanks for the speedy and thorough replies, @TheMcMurder and @joeldenning. I think I understand where you're coming from.

This project is deprecated (see #36). Use single-spa-angular@3, instead.


Logs Ethstats client is growing Gbs

Is necessary deploy ethstats client as process instead of container to manage the logs

It was solved #120


[Failing Test]: java:container:pullLicense fail at install pyyaml affecting all XVR Tests

What happened?
Seems affected by https://github.com/yaml/pyyaml/issues/601
Fail when trying to install pyyaml from source:
07:45:28   Downloading PyYAML-5.4.1.tar.gz (175 kB)
07:45:28      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 175.1/175.1 kB 5.7 MB/s eta 0:00:00
07:45:28   Installing build dependencies: started
07:45:32   error: subprocess-exited-with-error
07:45:32
07:45:32   × Getting requirements to build wheel did not run successfully.
07:45:32       Traceback (most recent call last):
07:45:32         File "/home/jenkins/jenkins-slave/workspace/beam_PostCommit_XVR_Direct/src/sdks/java/container/build/virtualenv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
07:45:32           main()
07:45:32         File "/home/jenkins/jenkins-slave/workspace/beam_PostCommit_XVR_Direct/src/sdks/java/container/build/virtualenv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
07:45:32           json_out['return_val'] = hook(**hook_input['kwargs'])
...
07:45:32           self._add_defaults_ext()
07:45:32         File "/usr/lib/python3.11/distutils/command/sdist.py", line 312, in _add_defaults_ext
07:45:32           self.filelist.extend(build_ext.get_source_files())
07:45:32                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
07:45:32         File "<string>", line 201, in get_source_files
07:45:32         File "/usr/lib/python3.11/distutils/cmd.py", line 103, in __getattr__
07:45:32           raise AttributeError(attr)
07:45:32       AttributeError: cython_sources
07:45:32       [end of output]

Issue Failure
Failure: Test is continually failing
Issue Priority
Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Could not reproduce locally, with / without cython 0.x or 3.x in persistent python environment. Seems this only happens on Jenkins

I see, it's failing on Python3.11 but pass for Python3.8 locally. Reproduce step: ./gradlew :sdks:java:container:pullLicenses -PpythonVersion=3.11.


[BUG] - Loading 1 average HERCULES data

Describe the bug
Siemens HERMES/HERCULES data with 1 average (& 4 subspectra) leads to a crash during OspreyLoad.

Solved [#390 ].


AQCU-1006: Fixed an issue where readings with no time were causing errors.

Should be merged with https://github.com/USGS-CIDA/AQCU/pull/670

Coverage increased (+0.0005%) to 99.04% when pulling 07b7291958f12813cbd45e33ed37f24c746a1dd4 on zmoore-usgs:wrong-readings into b173918160941f8f2f8fde273c0fc3a02916449a on USGS-R:master.


WIP: added supporting namespace package

[won't fix] support pkg_resources style namespace package (adding namespace_packages in setup.py)
[x] fix installing via symlink
[x] refactor variable names

hi @takluyver any chance this gets merged soon?

What does this need doing?

Better variable naming to make the code clearer (see my comment above)
The code that finds the module needs to be more robust against invalid combinations

e.g. if you specify module=foo.bar, it could currently package up foo.py and ignore the 'bar' part entirely.

@aodag mentioned that it doesn't yet work with installing by symlink.
We also need to check it with the --pth-file option.
I don't want to support the pre-standardisation (pkgutil or pkg_resources) namespace packages, so the test & sample for pkgutil should go. People who need to do namespace packages for Python 2 can stick with setuptools.
Probably a few more tests, including building wheels and sdists

@aodag did you implement all the things @takluyver mentioned? I’d like to package a sphinx extension, and since flit exists, using setup.py kinda hurts.

I was hoping to look at this properly before releasing 1.1, but I think I'm unfairly holding up the release waiting to get time for that, so I'm going to try to get the release out and come back to it.
At a brief glance, this is getting closer, and I'm still pleased to see how few changes it seems to need, but I think it could be a bit clearer.

Hi! Should I have a go at the tests or are you making progress?

I'm not quite sure what to do with this; I've got it 'working' in the sense that the tests pass and I'm reasonably happy with the code that's there. But I'm not confident that it will reliably do the right thing in all the different cases (install with pip, install symlink, wheel, sdist with setup.py, sdist with PEP 517...).
I ~never use namespace packages myself; my experiences with them have always been that they're an unnecessary complication, creating new ways for things to go wrong for little benefit. So I don't have much motivation to do all the testing to satisfy myself that this will work properly. And I don't have much enthusiasm for maintaining it if it doesn't work.

They are needed if you want to install things inside of a module hierarchy (extensible_package.ext.myplugin).
Namespace packages are a part of python and whenever a tool doesn’t support them and breaks in interesting and hard to debug ways when encountering them, I blame the tool, not namespace packages. They are innocent: They’re just directories! I think it’s rather straightforward to support them if they aren’t treated as an afterthought.

For most of their history, though, they've been directories with a special marker file that does something hardly anyone really understands. And then they break in hard to understand ways. I spent ages trying to debug a problem which affected IPython when you installed one backports.<something> package and it broke another one. It could all have been avoided if they had just been backports_<something> instead.
Now they're 'just a directory', but that can cause its own problems, if you try/except an import and it succeeds because some random directory is found as a namespace package. And I've no idea if new-style namespace packages play well with old-style namespace packages.
So, in summary, I think things would be a bit simpler if namespace packages had never been invented and we just had to use _ as a delimiter in package names.

For most of their history, though, they've been directories with a special marker file that does something hardly anyone really understands. And then they break in hard to understand ways.

Yes. Therefore I also think that old-style namespace packages should die.

Now they're 'just a directory', but that can cause its own problems, if you try/except an import and it succeeds because some random directory is found as a namespace package.

I had that problem a few times, but never with namespace packages.  Prepending to PYTHONPATH should also be done with care.

So, in summary, I think things would be a bit simpler if namespace packages had never been invented and we just had to use _ as a delimiter in package names.

I think you’d think differently if new-style namespace packages had been available forever. If Guido in 1991 had said something like

Python packages are directories that may have python files in them. You can optionally use __init__.py to write initialization code.

This is the way it is now, and I think it’s a rather simple concept hampered by lack of tool support for that kind of packages.

So just resurrecting this in the hope of this feature getting merged in the near future
I have to agree with @aodag:

Namespace packages are a part of python and whenever a tool doesn’t support them and breaks in interesting and hard to debug ways when encountering them, I blame the tool, not namespace packages.

I have foo.core, foo.client and foo.server packages stored in three separate source trees, and their build/install needs to be cleaned up. Ideally I'd use flit but without the namespace support I'm stuck for now.
Afraid I'm not knowledgable enough about all the corner cases in python packaging to do more than update the fix-namespace branch with current master, which I've done on my fork: https://github.com/rupertnash/flit/tree/fix-namespace
Tests pass except for py35 which dies at package install time:
action: py35, msg: installpkg
cwd: /Users/rnash2/work/vestec/flit-update/flit
cmd: /Users/rnash2/work/vestec/flit-update/flit/.tox/py35/bin/python -m pip install --exists-action w .tox/.tmp/package/1/flit-1.3.tar.gz
Processing ./.tox/.tmp/package/1/flit-1.3.tar.gz
  Missing build time requirements in pyproject.toml for file:///Users/rnash2/work/vestec/flit-update/flit/.tox/.tmp/package/1/flit-1.3.tar.gz: 'setuptools' and 'wheel'.
  This version of pip does not implement PEP 517 so it cannot build a wheel without 'setuptools' and 'wheel'.
  Could not find a version that satisfies the requirement pytoml (from versions: )
No matching distribution found for pytoml
You are using pip version 10.0.1, however version 19.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

@takluyver Any chance this PR get merged? We need this to adopt Flit at my company, as we have several regular subpackages of a company namespace package spread across several distributions:
.git/
company/
|-- subpackage_a/
    |-- __init__.py
tests/
pyproject.toml

.git/
company/
|-- subpackage_b/
    |-- __init__.py
tests/
pyproject.toml

Client code:
from company.subpackage_a import object_x
from company.subpackage_b import object_y

We should not use ugly prefixes like in C when we have namespace support like in C++ or Python in my opinion.

@takluyver I saw that you have recently merged the src layout PR (https://github.com/takluyver/flit/pull/260) and plan to make a new release soon (Flit 2.0). Do you plan to merge this PR as well for the new release? It would be awesome.

@takluyver Are there any plans to merge this?
I'll also add that, like properties/descriptors, they are useful for preserving interfaces/allowing dependent code to be unchanged. Flit is great, and I'd really like to be able to use it for the subcomponents of my project that I'm splitting out.
I'm happy to help if there's something that needs to be done to make this work.

Sorry that I've been letting this linger for ages. I'll accept that namespace packages are a thing lots of people want, even if I'm not a fan myself.
I've just commented in #453 that I prefer the approach in this PR - where you specify that you're packaging the concrete subpackage rather than the shared namespace package. However, this PR no longer merges, due to major refactorings that have happened in the meantime. That's entirely my fault for ignoring it for so long.
Could I ask someone to port this model to the new code structure? Whether that's a rebase of this branch, building on @martenlienen's work, or a new branch entirely. I think most of the changes in this branch will simply go to the corresponding files in flit_core (which is part of this repository), but there may well be bits that require some more thought. I will do my best to get this in before too much time passes.
(Just in case there's any doubt, we'll only do the standardised PEP 420 namespace packages, not the older style. That was my preference already back in 2018, and hopefully by now it's entirely uncontroversial.)

#468 is a rebase of this.


Implement Support for Native Types

Cairo 1 has introduced a new type system.
In particular, the corelibs have the following native types that should be supported by abiwan:

[ ] felt252
[ ] bool
[x] integers
[ ] strings

This item belongs to payment request #BCE367 on OnlyDust:

from thomas-quadratic to thomas-quadratic
7 items included
$500 for 1 day of work

We added support for boolean and felt252, can you please update the description accordingly ?

We support all native types and there is no string type in Cairo


Cannot find the ressdata directory

Hi
I can't seem to get gt-box-editor to read tessdata folder.
I select the path to C:\Program Files\Tesseract-OCR\tessdata
I have the version I have installed is 3.01-1
tesseract-ocr-setup-3.01-1.exe
Thanks in advance.

HI Zdenop,
Iam install in my Pc operator system using Windows 10  Qt-box-editor v 1.12rc1 When open Tif its not display left hand side window text letter  x-axis and y-axis.
can you send the screen shots how to create trained data file in Windows 10 screen shots.
Thanks and appreciate


Add a Buffer to the viewport Iframe Lazy loader

Perhaps use a buffer, so the iframe begins to load about 200 pixles below the viewport

Super easy, see "in-view-options" and the attribute "offset"
https://github.com/thenikso/angular-inview

Is this still applicable with the new card formats?


feature request: option to plot velocity field with streamplot instead of quiver

Thickness of the streams could be used to indicate flow strength. I often find these more clear than "quiver"-style vector arrows.

Example:


Python support

Prior art: https://github.com/benfred/py-spy#how-does-py-spy-work
Notes on native stacks (this would also be how we could add kernel space stacks): https://www.benfrederickson.com/profiling-native-python-extensions-with-py-spy/
To generate C bindings: https://github.com/xlab/c-for-go

Maybe this will helps you to implement profiling for Python: https://github.com/bloomberg/memray

CPython 3.12 will add support perf maps, which will allow to profile Python like NodeJS/Java
https://docs.python.org/3.12/howto/perf_profiling.html#perf-profiling
Shared on Discord: https://discord.com/channels/877547706334199818/877547706334199821/1036782373121032204

Implemented by the one and only, @kakkoyun!


Incorrect link

Linkt to the vehicle telematics simulator webpage does not work.

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

ID: 6a5d5aa8-4dc5-bf3c-01f0-5a2ba3cf8dac
Version Independent ID: 5204144c-280c-6cf8-f7f0-4c16177e45b3
Content: Deep dive into how to predict vehicle health and driving habits - Azure
Content Source: articles/machine-learning/team-data-science-process/cortana-analytics-playbook-vehicle-telemetry-deep-dive.md
Service: machine-learning
GitHub Login: @bradsev
Microsoft Alias: bradsev

@grzjab Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@grzjab Great catch! Sorry we missed that one. I'll find the right link if there is one and update directly.
#in-progress
@bradsev FYI

@deguhath This vehicle telemetry link is a 404. Is there a new link for this?
https://atlassaprod.blob.core.windows.net/connectedcar/CarEventGeneratorSoln.zip
@bradsev

@grzjab Good find! Thanks again for reporting this. It appears this content is deprecated, so we'll be retiring it. @deguhath

#please-close

@MicrosoftDocs/azure-cxp-triage Please assign this to @deguhath
Bradsev is no longer with the company.

@cjgronlund can this be closed? or do we need to wait for a reply from @deguhath  before closing?

@MicahMcKittrick-MSFT what's the reason to close this ticket while the link for https://atlassaprod.blob.core.windows.net/connectedcar/CarEventGeneratorSoln.zip is still broken?


steamPackages.fhs: load vendored steam libraries

Motivation for this change
closes #86257
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 120829 at 85798149 run on x86_64-linux 1

1 package skipped due to time constraints:

lutris

5 packages built successfully:

kodiPackages.steam-launcher
protontricks
steam
steam-run
steamcmd

What's holding this up?

people testing it and confirming that it solves the use case

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/fix-steam-black-library-store/14965/3

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/fix-steam-black-library-store/14965/4

Short term this will help: https://github.com/ValveSoftware/steam-runtime/issues/462#issuecomment-917311581

ping @jonringer

this got fixed a longer time ago already and now is the default


Report failing file names in comparisons

The files being diffed (especially for .pipe variants) are temp files, so their names are pretty nondescript. This improves error output, using ANSI escape sequences to make the lines stand out.

I'm mostly unsure about portability of those escape sequences. Is this a good idea?

GitHub seems to have missed the memo, but CI is full green.


const correctness everywhere

Not good that input parameters are often non constant (f.e. xc calc for paw). Constant parameters are impossible because one need to get a pointer and pass to constructor of Spheric_function

this is getting in order


Update the README to explain the lib

Give some refs on the papers used and the various algorithms

Kind of duplicate with https://github.com/vrancurel/nttec/issues/138, no?


Try other liquids

For recipes with OJ, try:

Blood orange juice
Grapefruit juice
Apple juice

For all recipes (milk/OJ), try:

Water
Ice cubes

Grapefruit juice taste overpowers other taste when using the same amount as milk


Fatou.jl

https://github.com/chakravala/Fatou.jl

[ ] try running some examples from Fatou.jl and generating pictures
[ ] do they run with TrackedFloats?
[ ] are there parameters we can tweak to introduce NaNs & change the picture?
[ ] what does the TF log say about the NaNs?

Tried running Fatou with FloatTracker. Adding support for complex numbers works well, but Fatou explicitly checks for something of type Complex{Float64}, which we cannot handle. Problematic code is in Fatou.jl:327:
323 function orbit(K::Define{FT,QT,CT,M,N,P,D,im},z0::Complex{Float64}) where {FT,QT,CT,M,N,P,D}
324     M ? (z = K.seed) : (z = P ? plane(z0) : z0)
325     zn = 0x0000
326     while (N ? (K.Q(z,z0)::Float64>K.ϵ)::Bool : (K.Q(z,z0)::Float64<K.ϵ))::Bool && K.N>zn
327         z = K.F(z,z0)::Complex{Float64}
328         zn+=0x0001
329     end; #end
330     # return the normalized argument of z or iteration count
331     return (zn::UInt16,(D ? disk(z) : z)::Complex{Float64})
332 end

I'm going to give up on this for now. It could be an interesting library to fuzz, but we'd have to work out how to make it past this block.


Autocomplete Next

We're not quite ready to tackle a new autocomplete yet, but I wanted to start the conversation as there are several folks interested in working on autocomplete: @mark-hahn, @lee-dohm, @joefitzgerald, @abe33.
Once we finish with API related things, I was planning on:

Looking at autocomplete-plus code
Checking out all of the existing providers out there.

How many are out there? What are the popular ones?

Looking at code @mark-hahn and @lee-dohm produced recently
Looking at other editors. How do they do it? Do they have APIs?
Are there autocomplete daemons out there we can use (e.g. https://github.com/nsf/gocode for Go)

Then I would come up with a plan of attack for the new version. In my mind, we have a couple options:

Extend autocomplete with an API
Take over autocomplete-plus with some modifications and API changes
Write something completely new

I am not sure what the best way forward is right now. I do feel, though, that the hard part is not the UI that pops up the completion box, it's having great language support, and a nice API for adding completions.
It would be great if you guys could help me / us work through the research phase. Off the top of my head, I'm thinking these would be a big help:

Your opinions and suggestions for the provider API.
Your architectural suggestions (I know @mark-hahn wrote one recently)
Comments explaining the pitfalls and your frustrations of the current autocomplete-plus API. Maybe suggestions on improvements.
Links to autocomplete providers for languages (either generic providers or for other editors)
Explanations / links to APIs in other editors
General autocomplete API related frustrations and desires

Resources

Discuss thread: https://discuss.atom.io/t/what-can-we-do-to-improve-autocomplete/13001
@mark-hahn + @lee-dohm's autocomplete: https://github.com/mark-hahn/autocomplete-generic
https://github.com/atom-community/autocomplete-plus
https://github.com/HaxeIDE/atom-autocomplete-plus-async

Providers

Ruby provider: https://atom.io/packages/rsense
Rust provider: https://atom.io/packages/racer
Go generic provider: https://github.com/nsf/gocode
Python generic provider: https://github.com/davidhalter/jedi
JS: https://github.com/marijnh/tern ; https://github.com/majutsushi/tagbar/wiki#javascript
Coffee: https://github.com/lukaszkorecki/CoffeeTags ; https://github.com/mntmn/tern-coffeescript

Autocomplete+ providers
https://github.com/atom-community/autocomplete-plus/wiki/Autocomplete-Providers

@benogle I know it's now January and you're nearing completion of the 1.0 API. If your focus starts to shift to this, please ensure you discuss with @nathansobo and take a look at the work we're doing in atom-community/autocomplete-plus#189 and atom-community/autocomplete-plus#184.

Will do

Are there any updates on the direction for autocomplete going forward? (ie. is Atom going to adopt autocomplete-plus now?)

Are there any updates on the direction for autocomplete going forward?

It is definitely in progress, we shipped two new autocomplete-plus providers this week, autocomplete-html and autocomplete-css
I would guess it would start to ship with Atom in the next couple weeks or so

... And we're more than happy to facilitate transition of the repo from https://github.com/atom-community to https://github.com/atom, as well as autocomplete-snippets and autocomplete-paths - if desired.

Tara Rum Pum, Bump

This is happening. I cant commit to a specific date, but autocomplete-plus will be the main deal soonish.

:+1:

Markup closing would be a great core feature for the autocompleter: https://github.com/mrhanlon/less-than-slash

Markup closing would be a great core feature for the autocompleter: https://github.com/mrhanlon/less-than-slash

That wouldn't be a core feature but it sounds like a great provider. Would be cool if the current package converted to become an autocomplete-plus provider.

@joefitzgerald Ah, I'll suggest there. Maybe wrong word choice, meant: would be nice if "Atom just behaved this way by default" rather than it belongs in this package specifically. This seemed like the right place among the roadmap tasks.

A wish would be 'inline-autocomplete', i.e. an UI-less mode where a keypress will rotate among the alternatives (similar to how it works in Textmate).
This package supports this, but it's not as nicely integrated with Atom as the regular autocomplete package, and since this is a core feature of an editor I'd much prefer using an official package.
https://atom.io/packages/inline-autocomplete

-1 for inline-autocomplete.
Because I use autocomplete to not only get autocomplete but to also get the type of the variable, for example, identify if it's a Map<string,mixed or Map<string,string.
Auto-Complete-Plus provides a label attribute that serves this purpose grealy.

@steelbrain I'm thinking of an optional, opt-in, mode. You wouldn't be forced to use it.

A wish would be 'inline-autocomplete',

I think this should be a separate package. For the people who want this behavior, they can disable the default, and install an inline-autocomplete package.

Just throwing in my +1 on an AutoComplete system that can stand-up against PHP Storm's. For example, working in a Laravel app, if I start typing:
Route
it gives me options on what class to import and even tells me when I have imported classes that are not in use in the current doc, which is fantastic. This is the ONLY feature that is keeping me from moving to Atom full-time -- right now it's just for frontend work.

@zslabs out of the box, it wont provide PHP intelligence. We will be bundling autocomplete-plus in the near future. You can install it today and get a much better experience over the built-in autocomplete. You may get some mileage out of @steelbrain's atom hack package. Also, I do know facebook will be soon releasing nuclide soon, which will include hack tooling, likely with autocomplete providers for PHP.

A note to everyone following this issue: there is a plan for bundling autocomplete-plus with core outlined in https://github.com/atom-community/autocomplete-plus/issues/351


Update generated ESLint config file for ESLint 9

Feature Request
Update ESLint config to support the ESLint 9 structure.
What are the alternatives?
I have managed to get ESLint to recognize the WXT globals by importing it as:
import globals from 'globals';
import wxtimport from './.wxt/eslintrc-auto-import.json' assert { type: 'json' };

export default [
    {
        languageOptions: {
            globals: {
                ...globals.browser,
                ...wxtimport.globals,
            },
        },
    }

Additional context
ESLint 9 has deprecated the .eslintrc* files in favor of eslint.config.js, eslint.config.mjs, and eslint.config.cjs and changed the config structure
https://eslint.org/docs/latest/use/configure/configuration-files
Looked through how it's generated and got lost trying to follow the trail 🤣

Or, a much simpler alternative, just output a second file file along-side the existing file with the following content:
// .wxt/eslint-v9-config.js
import globals from 'globals';
import v8Config from './.wxt/eslintrc-auto-import.json' assert { type: 'json' };

export default {
        languageOptions: {
            globals: {
                ...globals.browser,
                ...v8Config.globals,
            },
        },
    }

And tell people to extend that file for v9 and up. Eventually, I'd like to just generate one file, but this could be a short-term solution.

Thanks for pointing me in the right direction. I don't mind giving it a shot myself. I ended up in the getUnimportOptions function trying to find where it happens 🙃
I've looked at how the globals package does it, that package just has an index.js script that exports the globals.json file. I think we can do something similar here that way it's not backwards breaking.
I'll see about doing this a little later when I have some free

Released in v0.18.11


[Feature]: Optimizing Cross-Cluster Backup and Recovery

Is your feature request related to a problem? Please describe.
The current cross-cluster backup and recovery operation is somewhat complicated, requiring a lot of manual intervention from users.
Describe the solution you'd like.
Assuming there are two clusters, Alice and Bob.
Set alias names for each cluster:
milvus-backup alias set alice -c alice_backup.yaml
milvus-backup alias set bob -c bob_backup.yaml

List the configuration information of the clusters:
milvus-backup alias list

This will show the configuration information for both clusters.
Check the configuration information of the Alice cluster:
milvus-backup check alice

Check the configuration information of the Bob cluster:
milvus-backup check bob

Create a backup for the Alice cluster:
milvus-backup create -n alice/backup_1

This creates a backup for the Alice cluster with the name backup_1.
List all backups for the Alice cluster:
milvus-backup list alice

List all backups for all aliases:
milvus-backup list

Copy a backup from the Alice cluster to the Bob cluster:
milvus-backup copy alice/backup_1 bob/backup_1

This copies the backup_1 from the Alice cluster to the Bob cluster and creates a backup named backup_1. If backup_1 already exists in the Bob cluster, an error will be reported.
Restore the Bob cluster using a backup:
milvus-backup list bob

You should see the backup copied from the Alice cluster.
Restore the Bob cluster from the backup:
milvus-backup restore bob/backup_1

Describe an alternate solution.
No response
Anything else? (Additional Context)
No response

good suggestion and design!


Bumping up cni/cniplugins libraries versions to v1.0.0

@rajatchopra Please take a look. Was able to build with no issues or and dependency problems.

When running go mod vendor I am getting:
go: downloading github.com/containernetworking/cni v1.0.0
go: downloading github.com/containernetworking/plugins v1.0.0
go: downloading github.com/onsi/ginkgo v1.16.4
go: downloading github.com/onsi/gomega v1.15.0
go: downloading gopkg.in/yaml.v2 v2.4.0
go: downloading golang.org/x/net v0.0.0-20210428140749-89ef3d95e781
go: downloading golang.org/x/sys v0.0.0-20210809222454-d867a43fc93e
go: downloading github.com/nxadm/tail v1.4.8
go: downloading gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7
go: downloading github.com/fsnotify/fsnotify v1.4.9
go: downloading github.com/Microsoft/hcsshim v0.8.20
go: downloading github.com/buger/jsonparser v1.1.1
go: downloading golang.org/x/text v0.3.6
go: downloading github.com/sirupsen/logrus v1.8.1
go: downloading github.com/Microsoft/go-winio v0.4.17
go: downloading github.com/pkg/errors v0.9.1
go: downloading go.opencensus.io v0.22.3
go: downloading github.com/containerd/cgroups v1.0.1
go: downloading github.com/golang/groupcache v0.0.0-20200121045136-8c9f03a8e57e
go: downloading github.com/gogo/protobuf v1.3.2
go: finding module for package github.com/containernetworking/cni/pkg/types/current
go: downloading github.com/containernetworking/cni v1.0.1
github.com/flannel-io/cni-plugin tested by
	github.com/flannel-io/cni-plugin.test imports
	github.com/containernetworking/cni/pkg/types/current: module github.com/containernetworking/cni@latest found (v1.0.1), but does not contain package github.com/containernetworking/cni/pkg/types/current

Please rebase so that CI verifies this PR

@rajatchopra @manuelbuil looks like our build system not able to run tests from cni library. If we're using containerized builds we probably have to give them more rights/privileges. I do see the following error when I try to run tests in the container:
mount --make-rshared /var/run/netns failed: "operation not permitted"

@AleksandrNull Thanks! Could you please rebase one more time? We improved our tests :)


gildas: 20190601_b -> 20190701_a

Motivation for this change
Update Gildas to the latest upstream.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

OfBorg build on x86_64-linux failed because  went out of memory. I've built the package on a local x86_64-linux (Debian) successfully.


sepolia: add Fjord activation

unix time<PHONE_NUMBER>
Wed May 29 16:00:00 UTC 2024
Note that the failed diff check is expected, as we add Fjord to the Sepolia superchain.

We're waiting for confirmation from @kahuang on whether to exclude PGN Sepolia from activating Fjord.

@kahuang confirmed we can let Fjord activate on PGN Sepolia.


Python publishing name conflict - PyPI package pulumi-local already in use

We're unable to publish the Python package due to this issue for now.
We'll disable Python publishing and remove Python docs in the README, await on this issue filed with the maintainers of the pulumi-local package:

https://github.com/localstack/pulumi-local/issues/13

Is it possible to use another name for Python SDK, like pulumi-local-provider?
I want to use this provider in Python, I have to download the generated Python SDK, and patch the line pep440_version_string = importlib.metadata.version(root_package) to something like pep440_version_string = '0.1.2' because it is not installed from PyPI.


Internationalization

I think that if we want PoH becomes global, we should have the platform translated to different languages.
Does someone knows if this is already on the roadmap? if not, I can take the task of preparing the web to handle different languages and, if I still have some time, translate it to Spanish.

I suggest using linguo for the required translations

Unfortunately this likely won't be implement in the short or medium term because verifying submissions means running the submission against machine learning algorithms to detect duplicates. This includes verifying the audio of the video.


Update to v1.x

Description
Hi. Will this image need to be adapted to work with anonaddy 1.x + ?
Are there plans of doing so?

Yes I will work on it, keep you posted.

@crazy-max , is there any update on this?

Yes opened #240, I'm looking at the branding to check if everything is aligned. Will mark for review asap.

@crazy-max , Please merge #240 as it looks like @willbrowningme has approved it.

Can you update it to the latest version after rebranding to Addy.io?
If I then just pull the image will it work or do I need to migrate it somehow. I don't want to lose all my aliases and other stuff

@crazy-max  seems like your 1.0.4 image doesn't include the breaking changes of addy.io 1.0.0 , specifically the one regarding main.cf that needs to be updated.
For now, i have mounted a fixed version of this file, but it needs to be fixed in your image.


feat: introduce confirmation when deleting unit test [INS-3330]

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Cupertino navigator push don't have a hide bottom tab option.

Cupertino navigation examples show how to navigate in cupertino. but there is no options provide when push to next page and hide bottom tab bar.
These to push method are different:
// this one can hide, but not same behaviour with original iOS transition
Navigator.of(context, rootNavigator: true).push(
      new CupertinoPageRoute(
        builder: (c) {
          return new ChatPage(sess: session);
        },
      ),
    );

// this one can not hide, but have same behaviour with original iOS transition
// however how to hide that tab bottom in this transition style?
Navigator.of(context).push(
      new CupertinoPageRoute(
        builder: (c) {
          return new ChatPage(sess: session);
        },
      ),
    );

Can you describe a bit your desired behavior or an example in iOS where you see the desired pattern?
The only scenario I'm aware of in iOS is going to a fullscreen dialog from a page from tabs such as tapping on the 'profile' button in the App Store. A bottom-up transition is triggered in this case.
The equivalent code would be
Navigator.of(context, rootNavigator: true).push(
  new CupertinoPageRoute(
    fullscreenDialog: true
    builder: ...
  ),
);

Thanks for reply. I know what you mean, it's a push up from bottom transition with fullscreen options true. But what I means is, when not provide rootNavigator option, the transition in cupertino navigator will have a transition animation with the page  title ( I mean the big title in page and become the previous title in next screen).  But if we using rootNavigator as true, then there is not such animation. You will say without animation is also work on transition, yes it is, and works very well. But sometimes we want the vivid title animation between first and detail page (first one I decribe has, but can not hide bottom bar which is the problem).

I'm still not sure what is the desired effect.
I understood the part that you want to perform the transition at a higher level than the CupertinoTabScaffold.
Do you want a horizontal transition or a vertical transition?
I'm also not sure that either transition is present natively on iOS where a page transition above a bottom tab bar either horizontally or vertically AND has the nav bar's subcomponents transition between the outgoing and incoming nav bars.
Do you have an example of the effect you're looking for in a system iOS app?

@xster Thanks for your patiance, I made a screen record to show what I mean. https://drive.google.com/open?id=1W61EJZmnMBu5B8aiKagYZU2YL9tCYHR6
As you can see, The first push from father screen to child screen, it has a title animation. But the bottombar can not hide after pushed. The second push has no animation but can hide the bottombar. What I want is, push with animation and same time has the option to hide bottom bar.

Can you give access to your file? I can't see the video.

@xster Sorry, can this be seen? https://drive.google.com/file/d/1W61EJZmnMBu5B8aiKagYZU2YL9tCYHR6/view?usp=sharing

I think I understand what you mean. So a bit like the transition in WeChat where the conversation page does a horizontal transition above the tab bar.
If it's achievable in iOS, I think it's reasonable to let the Flutter API match. I'll close this bug for now but you can follow the progress on #22084.


Issue with Case Sensitive File Systems environment

In nfcmanager.h case issue:
There is
#import <CoreNFc/CoreNfc.h>
should be:
#import <CoreNFC/CoreNFC.h>

Hi, this issue has been fixed, thanks for spotting!


Support new format for notification messages

bmv2 now support 64-bit device ids. As a result the format of these
messages has changed to accomodate the larger ids. This means that the
PD code that parses these messages had to be updated. This doesn't
affect the PD interface at all.

See https://github.com/p4lang/behavioral-model/pull/432

Codecov Report

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

@@           Coverage Diff           @@
##           master      #91   +/-   ##
=======================================
  Coverage   97.14%   97.14%
=======================================
  Files          10       10
  Lines        1681     1681
=======================================
  Hits         1633     1633
  Misses         48       48

Continue to review full report at Codecov.

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


*: Add copyright notice to code files

This PR adds copyright notices to gittuf's code files.
Based on https://www.linuxfoundation.org/blog/blog/copyright-notices-in-open-source-software-projects
cc @adityasaky

I got confirmation this is fine. @patzielinski can you rebase and check if any new files need the header?


WIP: Add is_definition.

WIP: Add is_definition.
test: Add separate relationships statement to repro.

Test plan
Going to see if the code navigation works as expected in an SG instance with the new relationships statement in repro, which allows adding a relation to a symbol which lacks a definition.

Looks like this does have the desired effect. 🎉

IIUC, the hover is empty because I set the documentation to be blank. So I don't quite get what is_hover would solve... If A is a definition for B, isn't the desired behavior that you show hover docs of A when you hover over B?

Let's merge this for now so that I can start using it in scip-ruby. We can add is_hover later too.


Deploy your app for free 🚀

Hey @KnisterPeter, I'm just stopping by to say great work and to make a recommendation! Will you need to host your app in the future? If so, I'd highly recommend using DeeloCloud. It's built for developers, it's super easy to use, and you won't have to manage servers - which means you can focus on building!
Here's how it works in a few steps:
After signing up at https://deelo.cloud:
1.) Select the repo and branch where your app lives. In this case, it would be KnisterPeter/react-ssr-renderer.
2.) Select the runtime template of the app you wish to deploy.
3.) Hit deploy. 🚀
4.) In a few minutes your app will be live.
5.) Each time you push code to your branch, your app will pick up the changes and re-deploy.
And boom, just like that you got yourself free hosting! Enjoy.

Spam


Make Phone number not click dialable in mobile

Since we don't have a voice option, we want to discourage people from voice calling the phone number, it also incurs charges. Can we make it so on iPhones it doesn't have a URL click to call option?

I pushed a very small commit to master that adds:
<meta name="format-detection" content="telephone=no">
This works to prevent the link on my iPhone. I'm not sure if it's universal.

This issue is fixed in 81f77d54e13c49a70d8d7b9acc0d79c696cd455d.


Move swarmctl, swarmd, and swarm-bench to examples

swarmctl and swarmd are not the recommended way to run swarmkit, and it
has been requested several times that they be moved to an 'examples'
directory so users are less likely to try them. I don't know what
swarm-bench does but it looks like it should probably go there too.
protoc-gen-gogoswarm has been left in cmd because it's not an example,
its an essential command to the build process (i think). The Makefile
has been altered accordingly. A README has been added to examples to
explain this change
Signed-off-by: Drew Erny<EMAIL_ADDRESS>

I'd suggest leaving swarm-bench in cmd or moving it to a different subdirectory like tools (since it's a benchmark, not an example), but I don't think it matters much.

I'd appreciate someone taking a minute to double-check my Makefile changes to see if they're sane. They seem a little convoluted to me, but make seems a little convoluted to me so ¯_(ツ)_/¯

If you did create a tools directory, protoc-gen-gogoswarm could move there too.

Sure, those sound like solid changes. It's easier to move protoc-gen-gogoswarm and swarm-bench around than it is to move swarmd and swarmctl because the former don't have a bunch of dependencies to update.

[Current coverage][cc-pull] is 53.95%

Merging [#1062][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.04%

@@             master      #1062   diff @@
==========================================
  Files            75         75
  Lines         11686      11686
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6310       6305     -5
- Misses         4477       4481     +4
- Partials        899        900     +1

[][cc-pull]

Powered by Codecov. Last updated by [5667c2d...04680bb][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/5667c2d89c53ba3cc7ee3c6107a2aad003df7455...04680bbb8ecd6353088246b09af3435bea13c190
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/1062?src=pr

LGTM, but let's wait for other people to weigh in before merging. The examples / tools split was just something I thought up and I'm not sure whether that's what we want to go with. People may prefer cmd for the other programs.

Note #1098. Once it is merged, BUILDING.md will need to be updated as part of this.

Should I do that work as part of this PR or as part of a second one?

whoops finger slipped wrong button.

Depends which is merged first.

fwiw I'm more in favor of putting this in a cmd folder rather than examples. This is the reference command line for swarmkit which could after all, be used standalone. Also it is easy to miss for those used to Go projects on Github which have their command line generally under cmd.

Is there any interest in rebasing this PR and merging it, or should we close?


Need to click search twice

When I am looking at the menu across the top of the screen e.g. when viewing an individual post, it seems I need to click Search twice to actually view the Search page.
Metasmoke is unstable right now, but I believe this is reproducible since a week or two at least.

Take a look at your address bar as you do this. Does it change to /search on the first or second click? If it changes on the first, then you are already navigating, but search is just so slow that it seems like you have to click again. It's taking 10+ seconds to load for me at the moment.

I was unable to repro just now, but it seemed to happen a lot in the past. I know about slowness and my browser shows how things are slowly in progress when the click "takes." I don't think this is about slowness.

I got a repro this morning - definitely seemed like a click handler not firing, but it wouldn't reproduce in subsequent tests.


[AutoPR] servicefabric/resource-manager

Created to accumulate context: servicefabric/resource-manager

(message created by the CI based on PR content)

@zikalino can this be merged? we want to publish a new version with this changes

@zikalino why was this pr closed and not merged?


[OWL-171] build API interface

added:      http/api.go
modified:   cfg.example.json
modified:   g/cfg.go
modified:   http/http.go

Please fix the indention of "g/cfg.go".


CLOUD-991: First check the existance of the instancegroup

@keyki pls review

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1599/


🧑💻: Adding Hovering effect in Directory Hub

Title
It looks better and give a better user expierence
Enhancement Aim
A beautiful looking UI
Changes
Hovering in the Directory Hub
Screenshots 📷
NA
Guidelines

[X] I have read the guidelines
[ ] I have the link to my latest merged PR

Full Name
Ashish Patnaik
Participant Role
GSSOC

@Ashish-Patnaik can you provide some screenshots what are you gonna do in hovering UI?

I can't provide screenshots as I did not not work on your project but I worked on other website where I made these types of effect I will provide a video of a attractive card animation that I made
https://github.com/user-attachments/assets/ac8e2257-6261-4a1c-9da3-d2fcb2730a87
https://github.com/user-attachments/assets/2fcfe149-7f56-451c-ba06-2a0cf6b8e18b

@Ashish-Patnaik the thing is there is no proper website for the project as the website is being created using Google Sites and it doesn't provide much customization.
If you want to create a new website from scratch you can raise a new issue I will assign it to you with higher levels, if you want to.


Error while executing the script in Arch Linux

wine: could not open working directory L"unix\home\nil\.fusion360\bin\", starting in the Windows directory.
I have multiple errors like this.

you will need to provide more information:
At what point during the process does this occur? during installation? during first startup?
What OS are you running?

Same issue, happens during installation, right at the beginning.

Same issue here

I see similar in installation, but after fixing #273 it seemed to proceed and install ok anyway (seemingly) despite these errors - dialogs popping up to install extensions I'd selected that I hadn't seen before - but then on launch:
wine: could not open working directory L"unix\\home\\$USER\\.fusion360\\", starting in the Windows directory.
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: File not found.

What OS are you running?

Linux (Arch), as OP.

Ah,

wine: could not open working directory

is resolved (if it's even a problem) by running from within wineprefixes/default/drive_c.
The rest seems to be the actual error though.

Works after removing everything (because uninstall was broken too) and running ../../../bin/install.sh from the drive_c directory. (i.e. manually mkdir -p wineprefixes/default/drive_c first.)

@OJFord Do you have more details on how you fixed this? I can't seem to recreate.

I seem to be running into this issue on kubuntu 23.10 myself. @OJFord could you expain what you're talking about in a bit more detail? i'm not sure if I follow

I don't recall any more details, but fwiw I gave up on trying to run Fusion on Linux, not for this issue specifically, but just the general flakiness of getting it to run at all and then not performing well anyway.


TypeError: cannot unpack non-iterable NoneType object

from fpgrowth_py import fpgrowth
itemSetList = [['276', '303'],
 ['0', '109', '293', '160', '171'],
 ['204', '49'],
 ['204', '105'],
 ['49', '303', '105', '204', '276'],
 ['261', '255', '154', '74'],
 ['145', '261', '154']]
freqItemSet, rules = fpgrowth(itemSetList, minSupRatio=0.5, minConf=0.5)

TypeError: cannot unpack non-iterable NoneType object

have solved. just turn down 'minSupRatio' or delete the values returned, eg. freqItemSet, rules


:error_no_group when function is called from a separate app

I keep getting
** (exit) exited in: :gen_server.call({:error_no_group, :riak})
** (EXIT) no connection to riak

I have an app_users and app_db and app_api, my tests in app_users are running fine but if I have a test in app_api that calls app_users code I get a no connection to riak. app_db is the only interface to riak and app_users has a dependency to it and app_api has a dependency to app_users. The only app with pooler in the deps setting is app_db which handles connection pooling to the database.
What am I mixing up?

I managed to get rid of the error by applying app_db as an application dependency on app_api. Doesn't look clean to me because I don't want the api to be app_db aware

I am also getting same error, I am trying to use Elixir Riak client in an umbrella app.

Very difficult to understand what exactly the problem is. I'm closing it for now as outdated, but feel free to reopen if disagree.


Migrating to GitHub?

What steps will reproduce the problem?
1. Visit json.simple page on googleCode
2. Wonder if it is moving to GitHub.
3. Goto Github: https://github.com/fangyidong/json-simple
4. Still wonder a bit...

What is the expected output? What do you see instead?
Expect to see an announcement from the author.

What version of the product are you using? On what operating system?
N/A

Please provide any additional information below.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 4 Aug 2015 at 3:48

Closing unneeded issues from google export of code (and the project is on github :grinning:


Fix documentation for the gevent transport

The gevent transport is called GeventHTTPTransport in the docs but its real name is GeventedHTTPTransport

Thanks! :icecream:


DONT MERGE2

Can one of the admins verify this patch?

@kaa-leeroy add to whitelist

@kaa-leeroy test this fully please

@kaa-leeroy test this fully please

@kaa-leeroy test this fully please


remove 'blanket SHALL' in section intros

Steering summary
sections start with an overall SHALL but subsections contain SHOULD, MAY, which causes ambiguous requirements and/or an additional superfluous audit test. suggest to remove the blanket SHALL at the start (either remove sentence or capitalization).

4.3 OCI Functional Wallet Features

The following functional requirements (FRs) SHALL be respected by all Digital Wallet Providers.

same goes for 4.4 - the generic intro is superfluous when all sub-criteria have their own granular requirement wording

Triage:

[x] Is Issue appropriate for OCI Architecture
[x]  Assign Size
[x]  Assign Priority
[x]  Assign Label (if needed)
[x]  OCI affected Artifacts Identified
[ ]  Assign Triage - Artifact Version Target (v x.x.x Milestone)
[ ]  Assign Triage - Interop Profile Version Target (v x.x.x Milestone)
[ ]  Create sub-project (if needed)

Affected Parties (help determine Sunrise/Sunset):

[ ] Trading Partners
[ ]  Issuers
[x]  Wallet Solutions
[ ]  PI Verification Solutions

Affected OCI Artifact

[ ] Schema Document
[ ] Identity Schema
[ ] ATP Schema
[ ] Issuer Conformance Criteria
[x] Wallet Conformance Criteria
[ ] VRS Solution Conformance Criteria
[ ] Wallet API Specification
[ ] Governance Document
[ ] Conformance Program
[ ] OCI Website
[ ] Internal Process

Change Category (Guides Steering Review)
- Steering/Industry Review

[ ] Business-Level (May affect business operations)
[ ] OCI Governance, Policy or website feature

- Steering/Industry Notification

[x] Technical-Level (Does not affect business operations)
[ ] OCI Internal Process or Infrastructure

Communication

[ ] Website
[ ]  Newsletter
[ ]  email:
[ ]  Other:

replace "expectations" wording in PR with sth that states, "The following is a high-level overview of the technologies used by Digital Wallet Providers as part of this specification:"

July, 27: to be released in Digital Wallet Criteria v3.3.0,  interop profile v3.2.0


Explain unsupported

Let's make "Unsupported" clickable either by linkifying it or adding an info icon. Clicking should open a tooltip explaining why the given contract route is not available. It's not very intuitive why "Origin Vault" is always unsupported with DAI, USDC, and USDT as the output. Similarly, everything else is unsupported when the output is Mix.

done in #1050


Release Google.Cloud.Batch.V1Alpha version 1.0.0-alpha24

Changes in this release:
New features

Two new proto files added to the build (commit 605583b)

Created release for Google.Cloud.Batch.V1Alpha-1.0.0-alpha24


Can't find FaceSwap anymore, what happend? [bug]

Describe the bug
Well, the title is self explanatory

Reproduction
No response
Expected behavior
No response
Operating System
Linux
Comfy Mode
In a custom virtual env (venv, virtualenv, conda...)
Console output
No response
Additional context
No response

Hi,
Thanks for the report, yes I actually removed them from the "setup" because they were a pain to maintain on windows (became impossible without using other approaches with Py11 afaik).
But other OSes work actually fine so I need to add instructions to properly install them. I personally still use all the optional nodes on windows and macos.

I will write better instructions did not have the time yet tbh.
That said I really recommend the alternatives listed in the readme as they are more up to date!


install does not work on linux

Yes, you can use homebrew on linux too.
chirino@hiram-awesome:~/sandbox/java-operator-sdk$ brew install mvndaemon/homebrew-mvnd/mvnd
==> Installing mvnd from mvndaemon/mvnd
==> Downloading https://github.com/mvndaemon/mvnd/releases/download/0.1.1/mvnd-0.1.1-darwin-amd64.zip
Already downloaded: /home/chirino/.cache/Homebrew/downloads/011e0aefe9d0e517f32eb61793f657a979e4e4444491c418d558d0468b2cdd9a--mvnd-0.1.1-darwin-amd64.zip
🍺  /home/linuxbrew/.linuxbrew/Cellar/mvnd/0.1.1: 96 files, 41.8MB, built in 1 second
chirino@hiram-awesome:~/sandbox/java-operator-sdk$ file /home/linuxbrew/.linuxbrew/Cellar/mvnd/0.1.1/libexec/bin/mvnd
/home/linuxbrew/.linuxbrew/Cellar/mvnd/0.1.1/libexec/bin/mvnd: Mach-O 64-bit x86_64 executable, flags:<NOUNDEFS|DYLDLINK|TWOLEVEL|PIE>
chirino@hiram-awesome:~/sandbox/java-operator-sdk$ /home/linuxbrew/.linuxbrew/Cellar/mvnd/0.1.1/libexec/bin/mvnd
bash: /home/linuxbrew/.linuxbrew/Cellar/mvnd/0.1.1/libexec/bin/mvnd: cannot execute binary file: Exec format error
chirino@hiram-awesome:~/sandbox/java-operator-sdk$ uname -a
Linux hiram-awesome 4.19.128-microsoft-standard #1 SMP Tue Jun 23 12:58:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Here's an example of a Formula that does download different binaries depending on the platform:
https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/go.rb

thanks! it's working great!

thanks! it's working great!


Is there a way to set the timezone for pipelines?

The server that is running pipelines is running with UTC time. when i view tasks in the web front end it tells me the tasks were completed X hours in the future.

Hi @JonLundy, thanks for helping make pipelines better! Timezone management is currently not configurable and is one of the next improvements we want to make. #57 is an implementation issue for adding this.

Closing this one, this issue is being addressed in #57, I just pushed a PR for it.