DuplicateToArtboards.jsx Is malfunctioning in Illustrator CC 2023 (27.4.1)

See this video:
https://user-images.githubusercontent.com/33441569/233846064-721218be-7a3c-462b-85b5-603e87255e74.mp4
When Preserve Layers is disabled, the script just does nothing. Is this intended?
Really appreciate your work on all of the scripts available here.
Jay

This error is related to running the script through an action. The objects are copied, but they are copied to a temporary layer with artboard indexes, and when you close the script, that layer is deleted along with the objects.
Try this hotfix https://gist.github.com/creold/a40354a83c6323a9f78ab02efa9e77e2

Awesome! That worked great.
I have one more issue with one of your scripts: FitSelectionToArtboards.jsx
It only works if the geometry is completely outside of the artboards. If each artboard has geometry, the script does nothing.
See this video for a better demonstration:
https://user-images.githubusercontent.com/33441569/234197200-70128574-e87f-4152-8017-ccc224d2c842.mp4
Sorry for pestering! But a hot-fix for this script too would be nice! 😍


Add USB Start Up Delay and Nano Text Editor

Adds ENV Variable used to delay the start up of the usb making it seem like the device is disconnected.

This delay allows certain cars, such as Mazda, to finish initialization like importing contacts etc before starting the AA service.
See my comment on #87 for more details

It also adds the nano text editor to allow for an way to edit config files.

I don't think solved my issue, what did work is switching it phone first. I'm closing this one, but adding another to add the nano package


Random problem with insert on S3

Sporadically I get these errors:
[Wed Sep 30 2015 15:25:32 GMT+0000 (UTC)] INFO Exception in callback of async function: Error: failed [403]
at Object.Future.wait (/meteor/dev_bundles/0.4.18/lib/node_modules/fibers/future.js:398:15)
at Object.call (packages/meteor/helpers.js:119:1)
at [object Object].Meteor.methods._cfs_getUrlInfo (packages/cfs:file/fsFile-server.js:186:1)
at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1617:1)
at packages/ddp/livedata_server.js:1530:1
at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
at [object Object]._.extend.apply (packages/ddp/livedata_server.js:1529:1)
at [object Object]._.extend.call (packages/ddp/livedata_server.js:1472:1)
at EventEmitter.fsFileAttachData [as attachData] (packages/cfs:file/fsFile-common.js:77:1)
at EventEmitter.FS.File (packages/cfs:file/fsFile-common.js:17:1)
at EventEmitter.FS.Collection.insert (packages/cfs:collection/api.common.js:79:1)
at app/server/methods.js:151:24

The code at 151 is:
            Images.insert(data.image, function (err, fileObj) {
              data.image2 = fileObj._id;
              done();
            });

Looking at:
It looks like the problem is that the HTTP.call does not have a try/catch.
According to Meteor documentation: https://github.com/CollectionFS/Meteor-CollectionFS/blob/f28a3fcbfe86b999fcb2896363134fa9753d152e/packages/file/fsFile-server.js#L186
This function initiates an HTTP request to a remote server.
On the server, this function can be run either synchronously or asynchronously. If the callback is omitted, it runs synchronously and the results are returned once the request completes successfully. If the request was not successful, an error is thrown.
Solution: Retry -- See: https://meteorhacks.com/how-to-use-the-new-meteor-retry-package


Fix 500 on unintended endpoints and further refactor association router

Something drove me crazy after testing with my last patch - which is that certain serializers (with the same name) were created twice. This is logical if you think about what's being done. This PR adds a registry to fix the problem.
It also trades a few things in code organization. It gets rid of the "factory" method, and adds a new utility method for getting the parent class, which has to follow a certain format. Then the registry management becomes the main job of get_serializer_class
I still have 1 more suspected problem - which is that I believe RBAC is double-filtering. This might not be solved in this place, but adding a flag to querysets.

I've created https://github.com/ansible/django-ansible-base/issues/393 to discuss 2 remaining things I'm still not happy with. But I don't want those in scope here.

@AlanCoding to make a merge meeting for this PR sometime next week.


added camel-quarkus-javascript

Fixes #6360

The failing test is unrelated. Let's embed that in the next release.
@mweissdigchg Well done for this. Following prs with more tests could be of great value time permitting.


qovery-cli: 0.58.3 -> 0.58.6

Diff: https://github.com/Qovery/qovery-cli/compare/v0.58.3...v0.58.6
Changelog: https://github.com/Qovery/qovery-cli/releases/tag/v0.58.6
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 228175 run on x86_64-linux 1

1 package built:

qovery-cli


how to assign task to specific thread?

 My face recognition algorithm uses caffe, caffe is a thread-binding graphical library, that means I have to init and call algorithm in same thread, so I checked LockOSThread().
LockOSThread uses 1 thread, but my server owns 4 GPU.
In C/C++, I could create 4 threads, initialize algorithm in each thread, use sem_wait and sem_post to assign task, 1 thread use 1 GPU.
How to do the same thing in Go, how to tell my code this one uses thread0 and that one uses thread1 ?

Hi,
the Go project does not use its bug tracker for general discussion or asking questions. The Github bug tracker is only used for tracking bugs and proposals going through the Proposal Process.
Please see the Questions wiki page; it has a list of good places for asking questions.
Closing, since this is not a bug report.


[0.8] Properties observers registered too early

Properties observers seem to be set up too early.
If I declare a default value for a property, the property change callback is invoked before the component is ready.

This leads to the following output in the console :
openedChanged false undefined
ready

Do we really want to observe the transition from undefined to default value ?
PS: I updated the code to reflect today's changes in ca0953c but it behaved the same prior to @kevinpschaaf commits.

I am seeing the same thing, but not in a native browser like Chrome. So it appears the lifecycle path differs between Shadow DOM and Shady DOM. This simple test demonstrates the order of operation, run under a particular browser type:
lifecycle-tester.html:
<link rel="import" href="polymer/polymer.html">
<dom-module id="lifecycle-tester">
  <template>
    <content></content>
  </template>
</dom-module>

index.html:
<!doctype html>

  <meta charset="utf-8">

  <link rel="import" href="lifecycle-tester.html">

Under Chrome:
lifecycle-tester: created
lifecycle-tester: ready
lifecycle-tester: attributeChanged
lifecycle-tester: attached

Under Firefox:
lifecycle-tester: created
lifecycle-tester: attributeChanged
lifecycle-tester: ready
lifecycle-tester: attached

@robbear What you're talking about (lifecycle callbacks) is unrelated to whether property observers fire when the default value is set.
Some ordering is different on native webcomponents vs. polyfilled webcomponents. However, we make some ordering guarantees that you can rely on (created => ready => attached are always fired in that order).

The design notion here is that the element starts in a pristine state and you are informed of all changes that point on, including default values. Input values are also, by design, set before the ready method is called. By ready time the element's local dom has been created and the element itself has been configured with values.
We've also now normalized attached timing such that it is never called before ready.


Updated python script.

Journal abbreviations files contain non ascii characters and some journals do not have abbreviations. Instead of fixing those journal names and abbreviations, I simply remove them.
Signed-off-by: Emrah Er<EMAIL_ADDRESS>

What is the reason for simply removing that journals completely? Can't python handle UTF-8?

I'm not proficient in python. I used the abbreviations with some Bibdesk scripts. When I ran the script I got some errors and I thought non-ascii characters were the cause. You are right. I think the problem was the journals without abbreviations. Sorry for that. Just ignore my request.


Farmer application in /13-constrained-optimization.ipynb

In the markdown for the application, using only one bar for the $ works:
$120 instead of \$120, for example.
Also, in the code part, the constraints c4 and c5 are not included, I am not sure if it should be that way. Using them or not leads to the same optimal condition.

thanks!


autobuild on thrift

Original author: Nikhil Jain
Original issue: https://charm.cs.illinois.edu/redmine/issues/998

Since thrift is down, autobuild test for clang are not functional. Either bring thrift up, or move the build away to an active system.

Original date: 2016-03-10 21:31:20

We want this fixed to test the 6.7.1 release.

Original date: 2016-03-10 21:46:09

I just changed thrift to ambition. Hopefully it'll be fixed after tonight.

Original date: 2016-03-11 14:19:46

Fixed.


sbcl: 2.4.1 -> 2.4.2

Description of changes
SBCL 2.4.2.

changes in sbcl-2.4.2 relative to sbcl-2.4.1:
  * bug fix: restore the ability to inherit from both SEQUENCE and
    SB-MOP:FUNCALLABLE-STANDARD-OBJECT.  (lp#2050088, reported by Christophe
    Junke)
  * bug fix: COERCE will not convert lambda forms to functions if given a type
    naming a (strict) subclass of FUNCTION.
  * bug fix: LOG with a double-float and a ratio argument (in either order) do
    not lose precision through a single-float intermediate argument.
  * bug fix: LOG to the base 2 of integer powers of 2 are more likely to get
    the mathematically precise answer.
  * bug fix: LOG on ratios very near 1 with numerator or denominator being
    near a power of 2 will use log1p and so will lose less precision.
  * bug fix: the utf-8 external format with Unix line-endings updates its
    character size information when taking the fast path for a buffer of ascii
    characters.  (lp#2054169, reported by John Carroll)
  * bug fix: don't print the contents of a possibly no-longer-valid
    dynamic-extent cons in PRINT-OBJECT method for THREAD objects.
    (lp#2026195, reported by Jake Connor)
  * bug fix: place external entry points for functions consistently before any
    local functions.  (lp#2051169, reported by Fedorov Alexander)
  * bug fix: remove unactionable optimization notes for backquoted forms and
    ordinary calls to APPEND at high speed.  (lp#2051401, reported by Robert
    Brown)
  * bug fix: infinite loop in COPY-SEQ on zero-length arrays of element-type
    NIL.  (lp#2051759, reported by Devon Sean McCullough)
  * bug fix: fix compilation of non-top-level struct constructors.
    (lp#2052329, reported by Robert Poitras)
  * bug fixes in SB-SIMD:
    ** improve bounds checking in SB-SIMD.  (lp#2012010, reported by Patrick
       Poitras)
    ** fix SB-SIMD AVX f64.4-reverse (lp#2012986, thanks to Ari Projansky)
    ** fix SB-SIMD shuffles on AVX and SSE2 (lp#2012990, reported by Ari
       Projansky)
    ** fix lifetimes in sse+xmm0 VOPs (lp#2015329, reported by Ari Projansky)
  * optimization: a number of internal tables, particularly those related to
    Unicode support have been converted to use perfect hash mechanisms,
    improving both speed and space.
  * optimization: FIND, POSITION, ASSOC and RASSOC with constant sequence
    arguments containing symbols as keys are compiled to perfect hash lookups.
  * optimization: the compiler runs a jump-to-jump elimination pass on x86-64.
  * system integrity: compiling the system itself on x86-64/linux now produces
    bitwise-identical cross-compiled fasls whether the build host is cmucl,
    ccl, clisp or sbcl itself.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

@ofborg build sbcl.pkgs.iolib


Field offset in bits is not always divisible by 8

Field offsets are not always divisible by 8.
Running bindgen on signal.h give assertion error on struct __darwin_fp_control because second field __denorm has 1 bit offset.
Solution is to remove assertion and not generate getters/setters for such fields.

It looks like it is caused by explicit struct field layout, which is a quite common pattern to optimize memory usage:
struct __darwin_fp_control
{
    unsigned short              __invalid       :1,
                                __denorm        :1,
                                __zdiv          :1,
                                __ovrfl         :1,
                                __undfl         :1,
                                __precis        :1,
                                                :2,
                                __pc            :2
    // ...
}

@ekrich Did you figure out a way to support such structs in Scala Native? One option would be to read in the whole 32-bit/64-bit word and do the bit masking in Scala.

Seems like we cannot get real offset for such fields because it is implementation-defined

Multiple adjacent bit fields are usually packed together (although this behavior is implementation-defined)
https://en.cppreference.com/w/cpp/language/bit_field

Is there an issue for this in Scala Native?
Also I think it would be good to document this limitation.

@jonas In certain places the POSIX standard allows a type to differ because the underlying structure is based on the system or OS. They could not standardize all the way down. I believe the solution is provide a Ptr[Byte] as a generic pointer. I think this will also require some glue code in C if #ifdef conditionals for each platform. I haven't quite gotten that far yet.
Example: the ucontext_t struct contains mcontext_t which points to platform specific code. See http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/signal.h.html


Small improvements to crew retrieval page

Modified rarity filter options to display 'minimum 5*' instead of simply '5'
Modified the text to disable collection filter from 'Any' to 'None or any'.
Added option to filter crew by their amount of collections: 'Any 1 collection', etc
Sort rarity column in descending order first

This resolves #100

I've added this as a draft PR for now, because I'm unsure if we should separate the collection filters by collection name and quantity, or if it's fine to stay combined in a single dropdown like shown in the screenshot above. What do you guys think?

@ussjohnjay I think keeping it in a single dropdown is fine. I can't imagine a scenario where someone would want "crew in 3 collections specifically including Sherwood Forest", for example.

@ussjohnjay It occurs to me that these options would probably be more useful if they were "X or more collections".
I can't see a scenario where a user would want to see crew in any 3 collections but not a 4-collection crew at same time.

@ussjohnjay It occurs to me that these options would probably be more useful if they were "X or more collections".
I can't see a scenario where a user would want to see crew in any 3 collections but not a 4-collection crew at same time.

I agree - "X or more collections" in a single dropdown field would be awesome!

Closing this, as the improvements proposed here were included in #277.


Tutorial pt. 6 Routing, problem/concern

The following code below in pt. 6 of the Tutorial (Routing) doesn't work. Specifically, the getHero.then promise in the ngOnInit is async so it causes an error in the template. That is, when the first attempt to interpolate hero.name or hero.id occurs, hero is still undefined and you get all sorts of ugly red errors saying "cannot read property name/id of undefined". I found that moving the promise to the constructor works, but this doesn't seem like a good practice for debugging. What is a good solution?
import { Component, OnInit, OnDestroy } from '@angular/core';
import { ActivatedRoute } from '@angular/router';
import { Hero } from './hero';
import { HeroService } from './hero.service';
@Component({
selector: 'my-hero-detail',
templateUrl: 'app/hero-detail.component.html',
})
export class HeroDetailComponent implements OnInit, OnDestroy {
hero: Hero;
sub: any;
constructor(
private heroService: HeroService,
private route: ActivatedRoute) {
}
ngOnInit() {
this.sub = this.route.params.subscribe(params => {
let id = +params['id'];
this.heroService.getHero(id)
.then(hero => this.hero = hero);
});
}
ngOnDestroy() {
this.sub.unsubscribe();
}
goBack() {
window.history.back();
}
}
Please tell us about your environment:
Angular version: 2.0.0-rc.X

Browser: [all]

Language: [ES6 typescript]

ping @brandonroberts. Can you give some insight?

I'll have to check this and verify that the issue still exists. Unless the template is trying to access the hero before it's set I don't think this should be an issue.

I don't think this issue is relevant anymore. The template for the hero detail checks to make sure the hero property is set before displaying the details, so something else is going on.

yeah the hero detail uses the structural *ngIf directive to ensure hero property exists before displaying the detail template. So this *ngIf is the best practice for these situations then?

Yes. If you have some variables in the template that are resolved async
then you need to protect against failure in the case that they aren't there
yet.
On Aug 23, 2016 9:44 PM, "CaesarOG"<EMAIL_ADDRESS>wrote:

yeah the hero detail uses the structural *ngIf directive to ensure hero
property exists before displaying the detail template. So this *ngIf is the
best practice for these situations then?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular.io/issues/2038#issuecomment-241942275,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACk4yX6zAgRH6UFs3d7gQKPYiCMBzykks5qi7AGgaJpZM4Jd-yk
.

This last response really cleared the confusion in my head. Thanks @brandonroberts

@CaesarOG close this one since your issue is resolved.


Add additive scrambler

Fixes #281

Codecov Report
Attention: 23 lines in your changes are missing coverage. Please review.

Comparison is base (8b7fa74) 73.51% compared to head (9606449) 76.39%.

Files
Patch %
Lines

src/sdr/_sequence/_lfsr.py
82.30%
23 Missing :warning:

Additional details and impacted files
@@                Coverage Diff                @@
##           release/0.0.x     #284      +/-   ##
=================================================
+ Coverage          73.51%   76.39%   +2.88%
=================================================
  Files                 55       56       +1
  Lines               3277     3292      +15
=================================================
+ Hits                2409     2515     +106
+ Misses               868      777      -91

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


What should happen on keyguard reload?

Should the window get closed?
That would probably be the easiest as the keyguard looses the state it had before reload, e.g. for create the chosen identicon (private key) + passphrase and that is stuff that we don't want to persist in localstorage

should be firing. I like the idea @sisou! Sounds like a clean and predictable solution.

I believe with the current redirect RPC method, the keyguard receives its parameters via the URL query fragment (?q=...). Thus if the keyguard only changes the URL hash fragment, it should be able to preserve the RPC parameters on page reload and be able to start the request again, including the correct callback URL when the request is finished (or canceled). Needs testing though.

Tested this with the sign-transaction request type, it works as described in my last comment.


shock-client: throw an exception if shock service is down

This a stripped down pull request where only 1 commit for some changes against the shock client code were cherry picked.
The previous pull request was https://github.com/kbase/assembly/pull/309.

Thanks


Add K8sEndpointGroup

TBU

I managed to finish implementing our own Kubernetes authentications by porting https://github.com/kubernetes-client/java. However, I'm not sure the code is maintainable when there are new changes on the Kubernetes side.
On second thought, it would be much better to use a well-known Kubernetes client implementation instead. https://github.com/kubernetes-client/java is hard-coded with OkHttp but https://github.com/fabric8io/kubernetes-client has an integration layer for various client implementations.
I filed https://github.com/fabric8io/kubernetes-client/issues/5307 to support for Armeria backend. I will continue working on this PR once the Armeria backend for the Fabric Kubernetes client is implemented. It will make this PR simple and easy to review for maintainers.

There are leak reports in CI builds which turned out to be bugs in tests of https://github.com/fabric8io/kubernetes-client. I will disable the tests until the upstream fixes it.
https://github.com/fabric8io/kubernetes-client/pull/5852

I found another leak in tests https://github.com/fabric8io/kubernetes-client/pull/5854


import/no-extraneous-dependencies not working on windows

What I am doing:
Lint file with import/no-extraneous-dependencies enabled and which importing debug module, that is not presented in package.json dependencies
Expected behavior:
The error should be displayed
Actual behavior:
Linting finish successfully
OS:
Windows 10 x64 1809
Investigation
Find problem in function importTypes -> isSubpath. It not treating module as external because of working only with forward slashes as path separators. Looks like normalization for paths is needed.

debug is a core module. It doesn't have to be in package.json.

https://github.com/visionmedia/debug. Any way other module imports are not linted either. Reopen please.

I'm aware you can install it, but it's a core module - thus, the rule doesn't warn on it.
If you require debug/ instead, you'll get the installed one, and the linter will warn on it if it's not in package.json.
What other imports?

lru-cache, classnames

And rule erroring on debug import if run with bash console through wsl

A PR with a failing test case on windows would be great; then i can validate when it's fixed.

This is fixed here https://github.com/benmosher/eslint-plugin-import/commit/47f912e74eccbb6009ea5778a7cdb33e918dd495. Tests for no-extraneous-dependencies are passing on windows now.


I'm confused please help.

Hi, I'm working on our project I uploaded your code using the esp32-dev module. The code is working without error but nothing happens. I'm using inmp441, max98357, and speaker 8 ohm and just a common push switch button. I'm connecting everything according to your schematic as well. When I push a button it shows this message.(https://www.img.in.th/image/U8k02r) . Is this mean I'm doing it right? And I'm following your guide to change just WIFI_SSID and password is that right? Thank you for your answer :))

The code was not yet compatible with IDF version 4, now it should work again.
In case the microphone is not yet recording audio, in some versions on some chips you need to set
#define I2S_MIC_CHANNEL I2S_CHANNEL_FMT_ONLY_RIGHT
instead of left.
Remark also that defines can be set in platformio.ini or config.h : USE_I2S_MIC_INPUT & USE_ESP_NOW are set in platformio.ini


Slider Component border radius not displaying in safari browser

Overview
I am trying to apply custom style Stack  Overflow.
i) Slider component border radius not displaying in ios safari browser,
ii) And first time try to change the slider value, but colour is not continue in the slider.
This two issue reproducing in safari browser
border radius issue

slider colour not displaying when first time trying to slider

Reproduction steps
-i am trying this customizing the slider
.mat-slider.mat-slider-horizontal .mat-slider-wrapper {
  top: 18px;
}
.mat-slider.mat-slider-horizontal .mat-slider-track-wrapper {
  height: 12px;
  border-radius: 10px
}
.mat-slider.mat-slider-horizontal .mat-slider-track-background,
.mat-slider.mat-slider-horizontal .mat-slider-track-fill {
  height: 100%;
}
.mat-slider.mat-slider-horizontal .mat-slider-track-fill {
  background-color: blue;
}
.mat-accent .mat-slider-thumb {
  height: 30px;
  width: 30px;
  background-color: white;
  border: solid 2px gray;
  bottom: -20px;
  right: -20px;
}
.mat-slider-min-value:not(.mat-slider-thumb-label-showing) .mat-slider-thumb {
  background-color: white;
}

Example:
for sample reference [Stackblitz]
Version number
 "@angular/material": "^7.0.4",
  "@angular/cli": "~7.0.5",

Operating system and device
  MAC 10.14.11 Safari version 12.1.1
  Mobile IOS 13 , safari browser

Since you're applying your own styles on top of ours, it's up to you make it work everywhere. It looks like you probably need to add a transform: translateZ(0) to the element that has the border radius.

#crisbeto  Agreed i was written on own style for border radius. But in element level dynamically injected the transform properties for applying the colour. so i just added the colors in css level. For your reference, i have attached the video of chrome and safari browser behavior.
So, please advice me, where i have to add transform style properties and how to solve this issue.


netcdf-hdf5 parallel define size limit?

config.log.mvapich.txt
Environment Information

What platform are you using? (please provide specific distribution/version in summary)

[x] Linux

32 and/or 64 bit?

[ ] 64-bit

What build system are you using?

[ ] autotools (configure)

Can you provide a sample netCDF file or C code to recreate the issue?

[ ] Not at this time

Summary of Issue
I've been testing 4.7.4 with our cloud simulation model for the compressed hdf5 parallel I/O (mpiio). (HDF5 is 1.10.7, netCDF Fortran is 4.5.3, pnetcdf 1.9.0) It seems to work great until I switch to an option that takes the number of 3D arrarys from about 32 to about 250. Then it returns
DEFINE_NETCDF:  Error ending define mode        -101
NetCDF: HDF error
DEFINE_NETCDF: Error Closing File:
NetCDF: HDF error
It does create a file (about 2MB) that is unreadable by ncdump.
The same error occurs when variable compression is not enabled, so I suppose that zlib compression is not the issue.  There is no problem creating a 64-bit offset (pnetcdf) file or a serial-write file. (Note that I create pnetcdf files using the netcdf interface, but write the data with pnetcdf functions.) It doesn't seem to be a new issue, as it also occurs with my older installation of hdf5-1.8.9 + netcdf <IP_ADDRESS>
The file size with pnetcdf is only 713MB for my test configuration (grid dimensions of 120x120x51). I think the -101 means an error in the HDF level?
I'm setting the file mode with consecutive 'ior' statements:
cmode = IOR(nf90_netcdf4, nf90_classic_model)
cmode = IOR(cmode, nf90_mpiio)

 status = nf90_create(filename(ibeg:iend), cmode, ncid, comm = my_comm, info = my_info)

Any idea if this would be in the hdf5 part or something passed to it that it doesn't like? The same file creates fine as as serial (i.e., without the mpiio flag).
Thanks!
-- Ted Mansell
Steps to reproduce the behavior

Hi Ted,  you are correct that this appears to be something at the HDF5 level.  I'll take a look, although if you were comfortable providing your code (or a C equivalent)? If that's not practical, I will try to recreate this issue so that I might step through the debugger and see what exactly is happening at the HDF level.

Hi, Ward,
Well, I made a simple program to write a bunch of 3d arrays, and that runs fine. So the next step may be to add attributes and other things that are used in the cloud model.

I can confirm that there is no size limit, and NOAA produces some massive data files with many variables, using compression and parallel I/O. There is a test program which demonstrates and tests the parallel I/O with compression: nc_perf/tst_gfs_data_1.c. THis program is only built and run if netcdf-c is configured with --enable-benchmarks.

I can confirm that there is no size limit, and NOAA produces some massive data files with many variables, using compression and parallel I/O. There is a test program which demonstrates and tests the parallel I/O with compression: nc_perf/tst_gfs_data_1.c. THis program is only built and run if netcdf-c is configured with --enable-benchmarks.

Right, Ed. I started on a new test code to recreate what the model sets up, but other things came up. I hope to get back to it soon.

Right, Ed. I started on a new test code to recreate what the model sets up, but other things came up. I hope to get back to it soon.

I set this aside for a while, but I'm back on it, now with WRF, as well. I made a WRF IO option for NETCDFPAR (parallel io using the netcdf4 interface), separate from the default netcdf. It works. One of the issues I ran into was different processors trying to set different values for chunking, which was also happening in COMMAS.
Unfortunately, that didn't solve the original define error.

Can you send a small test program and demonstrates the problem?

@edwardhartnett  I tried to reproduce the issue with a simple code and lots of arrays, but it did not fail. I haven't gotten back to this in a while. My guess is there is something I'm missing in the my model code where a collective mpi action has conflicts, but I really don't know

OK, maybe you could close this issue and re-open it if this turns out to be related to netCDF.

Sure, good suggestion. I will do that.

OK, I made some progress on this and have a relatively small example that demonstrates my problem and can be found here (the readme has info on setup and running to get the enddef error):
https://github.com/MicroTed/ncpartest.git
Basically, it sets up a grid structure with a number of 0d, 1d, 2d, and 3d variables, which may or may not be time dependent. The dimensions are time (TIME), x axes (XC, XE), y axes (YC, YE) and z axes (ZC, ZE) (the C and E are for the center and edge positions of the grid points, on a Cartesian grid).
dimensions:
TIME = UNLIMITED ; // (0 currently)
XC = 80 ;
XE = 81 ;
YC = 40 ;
YE = 41 ;
ZC = 40 ;
ZE = 41 ;
And then the corresponding coordinates are defined with the same name:
    int TIME(TIME) ;
    float XC(XC) ;
    float XE(XE) ;
    etc.

So if these coord variables are NOT defined, then it works with any number of total variables. But there's a caveat to that, because if the coords vars ARE defined and I turn off setting attributes for each variable, it works again. I don't know if there is any connection there -- any thoughts on that?

In addition to testing with ifort, I also ran this test with gfortran-12, netcdf 4.8.0, hdf5 1.10.7, and got an extra error (overflow):
NetCDF: HDF error
Note: The following floating-point exceptions are signalling: IEEE_OVERFLOW_FLAG

@edwardhartnett @WardF  My workaround now is to reduce the number of variable attributes. Curiously, I can add all the string/character attributes, but adding just one integer attribute trips the error. Those integers are not really needed for anything at this time, fortunately. At least it can work!


Trix toolbar not working at all.

Hello
Thanks for developing this package.

I seen editor but not work.
Usage information:
te7a-houdini/laravel-trix 2.0.1
laravel/framework 7.10.3

Any error in browser console.
An investigation:
when I comment this line everything gone fine:
window.$ = window.jQuery = require('jquery');
What's problem with jquery?

Same issue here. Toolbar buttons don't work and there are no errors in the console.
@A1Gard Have you found a fix for this issue?

@A1Gard am not sure why this problem happened with jquery
@kiritokatklian is it happening with you also using jquery ?

@Te7a-Houdini Yes, it's being used through Bootstrap. In my case, commenting it out doesn't fix the issue.

So I was able to get it to work after commenting out axios, which apparently was preventing Trix from adding event listeners to the trix-toolbar element.
I tried to investigate what's causing the issue on axios side, but unfortunately I couldn't find anything.

@Te7a-Houdini So I've been playing around with Trix again and found out that it doesn't work well with VueJS. I'm assuming it's because they both listen to DOM changes. When you intentionally cause an error in VueJS (so it doesn't load properly), Trix works perfectly.
To fix this issue and have both working trix.js needs to load after VueJS has loaded by adding the defer attribute to the trix.js script and including @trixassets after your app.js (or wherever VueJS is imported). PR #36  addresses this issue.

fixed in #36


installation issue

Dear developers
I have problems to install velocyto through anaconda mini-conda, through the Sryder console. pip install velocyto did not go on python 3.9 or 3.11.
Collecting velocyto
Using cached velocyto-0.17.17.tar.gz (198 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'error'
Note: you may need to restart the kernel to use updated packages.
error: subprocess-exited-with-error
python setup.py egg_info did not run successfully.
exit code: 1
[6 lines of output]
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "C:\Users\u0153852\AppData\Local\Temp\pip-install-55o8yc8v\velocyto_f8958368a200418ab96f142c9b467509\setup.py", line 3, in
import numpy as np
ModuleNotFoundError: No module named 'numpy'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
Encountered error while generating package metadata.
See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
Can you suggest my mistake, please?

hello, I have the same problem here while trying to install it. I first created a virtual environment and activated it
> python3 --version
Python 3.9.6
> python3 -m venv virtualEnv
> source virtualEnv/bin/activate

I then proceeded by installing velocyto using pip
> pip install velocyto

I got the following error messagge
    ERROR: Command errored out with exit status 1:
     command: /Users/lrcq/Documents/devtraj/virtualEnv/bin/python3 -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/kx/jq__74vx39z9tptjlhbh6m400000gn/T/pip-install-l7nk6mlv/velocyto_39181c4ec1d14fac87aec8f2aeb4d34f/setup.py'"'"'; __file__='"'"'/private/var/folders/kx/jq__74vx39z9tptjlhbh6m400000gn/T/pip-install-l7nk6mlv/velocyto_39181c4ec1d14fac87aec8f2aeb4d34f/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /private/var/folders/kx/jq__74vx39z9tptjlhbh6m400000gn/T/pip-pip-egg-info-gmv_k1sc
         cwd: /private/var/folders/kx/jq__74vx39z9tptjlhbh6m400000gn/T/pip-install-l7nk6mlv/velocyto_39181c4ec1d14fac87aec8f2aeb4d34f/
    Complete output (5 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/kx/jq__74vx39z9tptjlhbh6m400000gn/T/pip-install-l7nk6mlv/velocyto_39181c4ec1d14fac87aec8f2aeb4d34f/setup.py", line 3, in <module>
        import numpy as np
    ModuleNotFoundError: No module named 'numpy'

So I proceeded by manually installing numpy and pysam into the virtualEnv
> python3 -m pip install --upgrade pip
Requirement already satisfied: pip in ./virtualEnv/lib/python3.9/site-packages (21.2.4)
Collecting pip
  Using cached pip-24.3.1-py3-none-any.whl (1.8 MB)
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 21.2.4
    Uninstalling pip-21.2.4:
      Successfully uninstalled pip-21.2.4
Successfully installed pip-24.3.1
> pip install numpy
> pip install pysam
> pip freeze
numpy==2.0.2
pysam==0.22.1

When I try then to install again velocyto I get the following:
pip install velocyto
Collecting velocyto
  Using cached velocyto-0.17.17.tar.gz (198 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [17 lines of output]
      Traceback (most recent call last):
        File "/Users/lrcq/Documents/devtraj/virtualEnv/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/Users/lrcq/Documents/devtraj/virtualEnv/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/Users/lrcq/Documents/devtraj/virtualEnv/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/private/var/folders/kx/jq__74vx39z9tptjlhbh6m400000gn/T/pip-build-env-3hk6f2a5/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 333, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=[])
        File "/private/var/folders/kx/jq__74vx39z9tptjlhbh6m400000gn/T/pip-build-env-3hk6f2a5/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 303, in _get_build_requires
          self.run_setup()
        File "/private/var/folders/kx/jq__74vx39z9tptjlhbh6m400000gn/T/pip-build-env-3hk6f2a5/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 521, in run_setup
          super().run_setup(setup_script=setup_script)
        File "/private/var/folders/kx/jq__74vx39z9tptjlhbh6m400000gn/T/pip-build-env-3hk6f2a5/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 319, in run_setup
          exec(code, locals())
        File "<string>", line 3, in <module>
      ModuleNotFoundError: No module named 'numpy'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

What am I missing?  currently running onto arm64 M3 with macOS Sonoma 14.5 :)

I am facing this issue too.
'numpy' installation completes without any issues, however 'pip install velocyto' fails citing 'ModuleNotFoundError: No module named 'numpy''
I installed 'numpy' with Conda and pip, velocity installation fails with the same error message.


ClassNotFoundException: org.slf4j.impl.Slf4jLogger from Service Module Loader

After login attempts from /cas-management to /cas
I have exception:

Caused by: java.lang.ClassNotFoundException: org.slf4j.impl.Slf4jLogger from [Module "deployment.cas.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)

Full stacktrace

CAS server version: 4.2.0
Container type/version: Wildfly 10

Thanks for the report. I'll try to look into this tomorrow.

Cant duplicate.
Downloaded WF 10 and ran the standalone server.
Deployed the CAS over under 4.2.1-SNAPSHOT to master.
No errors. Can get to 8080/cas just fine.

Used this to deploy: https://docs.jboss.org/wildfly/plugins/maven/latest/examples/deployment-example.html

Actually, I take that back. I do see an error in the browser that is almost the same as yours, but I can't trace this in the logs. Which file did you use to look up the stack trace?

This error has DEBUG level.
My config for Wildfly:
<subsystem xmlns="urn:jboss:domain:logging:3.0">
    ...
    <logger category="org.jboss.as.config">
        <level name="DEBUG"/>
    </logger>
    <root-logger>
        <level name="DEBUG"/>
        <handlers>
            <handler name="CONSOLE"/>
            <handler name="FILE"/>
        </handlers>
    </root-logger>
    ...
</subsystem>

Thanks. Which file in WF do the above changes go into?

/wildfly_path/mode/configuration/mode.xml
wildfly_path - path to Wildfly
mode - standalone or domain
See jboss.server.config.dir to find the path.
Wildfly output or server log has this variable:
2016-03-31 00:21:42,772 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties:
    [Standalone] =
    ...
    jboss.server.config.dir = /srv/wildfly/standalone/configuration

For example:
/opt/wildfly/standalone/configuration/standalone.xml
/opt/wildfly/domain/configuration/domain.xml

Found and fixed the issue. Tested with Jetty and WF 10.
The fix is to ensure logger fields are marked as transient, so they are ignored during serialization.

Thanks! Worked with my WildFly 10 too.
P.S. To use CAS 4.2.0 with WildFly 10 your must apply this patch's:

1658.patch
1659.patch
1666-4.2.0.patch (based on 1666.patch)

Point your overlay to 4.2.1-SNAPSHOT and you should have all those patches available. The actual release will be in a few weeks.


Text to speech

Are you planning to use any text to speech conversion

like Amazon polly

I'd considered baking it into the library #25 but it's so simple to add on I'm not sure it's worth it. Super simple sudocode example of how could do this:
sonus.on('final-result', result => {
  intent.process(result, => (response, prompt) {
    say.speek(response)
    if(prompt) {
      sonus.trigger(sonus, 0, 'some hotword')
    }
  }
})

what is this intent process and prompt.I need to implement session using hotword so as long as session is open i don't want hotrod to be associated with statement in session

It's just sudocode. You'd replace that with whatever actual intent processor you have. If you say the hotword while cloud recognition is in progress is will not begin another recognition.

Ok I am trying to trigger the hotrod once all the response is flushed out to the speaker if prompt is required from the user.
Player.on('flush' , function(){console.log("In flush block");
if(session)
sonus.trigger(sonus, 0, 'snowboy') ;
        });

Is this oK
Also wanted to know  if I can use hotword only during the start of the conversation and not in all subsequent interactions until i say stop

How to make sure when speaker has played out the response and then trigger hotword manually

Sonus.pause and resume are not working it is still picking what is said after user utterance

Are you use you are using Sonus.pause() correctly? You cannot call .pause() on your created Sonus object. To be clear:
const sonus = Sonus.init({ hotwords }, speech)

sonus.pause() // does nothing
Sonus.pause(sonus) // should work

I am doing following thing:
sonus.on('final-result', result => {
console.log("UserSpeech : ", result)
Sinus.pause(sonus);

bufferStream.pipe(Player)
         Player.on('flush' , function(){console.log("In flush block");
          //if(session)

        });
         Player.on('close' , function(){console.log("In player close block")
          Sonus.resume(sonus)
           sonus.trigger(sonus, 0, 'snowboy') ;
       });

and then in some function down the line  I am executing Sonus.resume(sonus) after that calling manual trigger of hotword
But it seems it is taking time to do pause and resume both
There is no possibility of capturing pauseOnComplete and resumeOnComplete events while pausing and resuming mic?
I need on functionality where mic listens nothing till I emit hotword manually which seems to be not the case as it is going into endless loop of recognising things   which are played out by speaker

Still doesn't work even after that change I made

I'll be online after work today and will have time to take a look at this and give you a hand. There's an unofficial Discord channel: https://discord.gg/35zesAR
I should be on at ~7:30 PST

So it is 7:30 am or pm

I have joined the channel .. Are u available on the channel

How to configure for multiple languages(Google Speech API) in sonus

@sharmmoh1983 please open separate issues for new questions. Right now there is no support for multiple simultaneous languages: API.md#languages


Problem when trying do edit metadata

Summary
white screen when clicking edit metadata: https://portal.minimal-gaia-x.eu/asset/did:op:De7A1AB5db11de81513B837f69dEC8581DDB1035
Current Behavior
white screen, nothing to see
Expected Behavior
metadata edit mask appears and metadata can be edited
Steps to Reproduce

go to data set: https://portal.minimal-gaia-x.eu/asset/did:op:De7A1AB5db11de81513B837f69dEC8581DDB1035
login metamask account: 0xa76Fa6837A6ffc9F123F2193717A5965c68B0cbA
click edit metadata

I am able to reproduce this behaviour.

I don't have the credentials to log in with that wallet so I can't test why it's not working


Extract metadata ovs unit tests and use schema constants

Coverage remained the same at ?% when pulling<PHONE_NUMBER>de8d1a3ac3b1420153d86237b2762e on EdDev:extract-metadata-ovs-unit-tests into 026ed90713784e4421adab06d38159e380a44545 on nmstate:master.


THREE.WebGLShader: Shader couldn't compile.

Hi.
Some Android phones, as Galaxy S5 Mini, throws this exeption on runetime:
THREE.WebGLShader: Shader couldn't compile.
 So i decided to make some like this:
function pixelShaderSupport() {
  console.log("Checking pixel shader...");
  var support = true;
  try {
    var textTry = '<a-scene><a-entity style="display: none;" class="animate" id="textTry" rotation="0 0 0" scale="1 1 1" position="1 1 1" bmfont-text="color: white; mode: pre; text: tmp" look-at="[camera]"></a-entity></a-scene>';
    $('body').append(textTry);
  } catch (error) {
    if (error)
      {
        console.log("Your device doesn't support the bmfont-text shader...");
        support = false;
      }
  }
  return support;
}

But is not throwing, i think because the shader itself is not running.
Any way to fix or to prevent test this exception?
Thanks,

According to MDN, "Using highp precision in fragment shaders will prevent your content from working on some older mobile hardware. You can use mediump instead, but be aware that this often results in corrupted rendering due to lack of precision on most mobile devices, and the corruption is not going to be visible on a typical desktop computer".
MDN also says that there is a function "getShaderPrecisionFormat()" that can check if highp precision is supported.
So I guess you'd need to fork the component and add some code that tests if precision is supported. You could also try using mediump instead of highp (although this may result in degraded quality or corruption).

Hi!
I made this test on early stage on my app to, in case of, redirect the user to a limited xp:

function pixelShader() {
var support = true;
try {
var canvas = document.getElementsByTagName('canvas')[0]
var gl = canvas.getContext("webgl")
var shaderType = [gl.VERTEX_SHADER,gl.FRAGMENT_SHADER]
var precisionType = [gl.LOW_FLOAT, gl.MEDIUM_FLOAT, gl.HIGH_FLOAT, gl.LOW_INT, gl.MEDIUM_INT, gl.HIGH_INT]
shaderType.forEach(function(shader){
precisionType.forEach(function(precision){
gl.getShaderPrecisionFormat(shader,precision)
})
})
} catch (error) {
if (error)
{
support = false;
}
}
return support;
}

Where do you think i could integrate this in your component? Let me try and if it looks fine i'll send you a PR.

Changing the precision used by the fragment shader can be done by adding a parameter here. Try testing with precision: "mediump".
var material = new THREE.RawShaderMaterial(SDFShader({
    precision: "mediump",
    map: texture,
    side: THREE.DoubleSide,
    transparent: true,
    color: data.color,
    opacity: data.opacity
}));

If that fixes the problem on mobile let me know and I'll try to help with integrating the test.
P.S.
I've just discovered that Three.js' WebGL renderer has a "capabilities" property that contains a method getMaxPrecision(). Might be useful.

Closing as this issue has been open for quite some time and I'm about to archive this project.


provide methods for IO other than stdout

As far as I can tell, Term.jl renderables can only be shown properly with the 1-argument print methods or with the 1-argument tprint methods.
It would be nice to be able to print the expected output to any IO.  The main reason I'd like to be able to do this is that it makes it more natural to overload Base.show(::IO, ::MIME"text/plain", ::T), as without this, the only way of writing an appropriate show method using Term.jl is with redirect_stdout.

This will happen with the next release: https://github.com/FedeClaudi/Term.jl/blob/524e2078292e3f078aa160b6c90d669b91bdffd5/src/tprint.jl#L22

It would be nice to be able to print the expected output to any IO. The main reason I'd like to be able to do this is that it makes it more natural to overload Base.show(::IO, ::MIME"text/plain", ::T), as without this, the only way of writing an appropriate show method using Term.jl is with redirect_stdout.

Do you have a concrete example of this? So that I can test this functionality before the next release

I've been doing stuff like this
function termrender(obj::Object)
    Panel(obj.stuff, title=obj.name)
end
Base.show(io::IO, ::MIME"text/plain", obj::Object) = redirect_stdout(() -> termrender(obj), io)

The redirect_stdout is what I was hoping to eliminate.

Come to think of it, I probably should do
function Base.show(io::IO, ::MIME"text/plain", obj::Object)
    if get(io, :color, false)
        redirect_stdout(() -> print(termrender(obj)), io)
    else
        show(io, obj)
    end
end

As checking if the IO stream supports color seems like a good minimal sanity check for whether it makes sense to try to use Term.jl on it, so you might want to consider doing this in a method you add.

With the next release, the general methods
tprint(x) = tprint(stdout, x)
tprint(io::IO, x) = tprint(io, x)
tprint(io::IO, ::MIME"text/html", x) = tprint(io, x)

should allow for the behavior that you have in mind.

As checking if the IO stream supports color seems like a good minimal sanity check for whether it makes sense to try to use Term.jl on it, so you might want to consider doing this in a method you add.

Term does more than just color though, it can be used for layouts, panels etc even when there's no color information.

Term does more than just color though, it can be used for layouts, panels etc even when there's no color information.

Oh yeah, it's not perfect by any means, but at least it's something.  I'm not aware of any way of testing everything that'd be general and robust enough (you'd still want to have the ability to write to buffers and stuff like that so trying to determine if something is a real TTY seems a bit much).

aye, though it would be good to add more checks for IO contexts and the likes, in the future I guess (unless someone whats to help in 😄 )

Please install the code under development with
] add https://github.com/FedeClaudi/Term.jl

to test.

Seems to work great (for both tprint and print), thanks!

awesome, enjoy!


nixpkgs Upstream Dependencies are Offline or Their Declared hash Differs from Actual hash

I first tried to write about that to
<EMAIL_ADDRESS>
but my letter got stuck to some spam filter or just did not go through due to some weird reason. So, the following is a Copy/Paste with Markup related modifications.
---citation--start---

nixpkgs dependencies availability test is about 300MiB in size due to a clone of the
https://github.com/NixOS/nixpkgs

and resides at a location at my web site
sha256:
f05cf8bb85527a14f22adf0e2b3a7fa56f63461b7580620e4d54204c4d2db1ba
The idea is roughly:
git clone https://github.com/NixOS/nixpkgs
cd nixpkgs
find . -name '*.nix' > list_of_nixfiles.txt

and then each of the nix-files is searched for pairs of fetch-url's and hash values and a gigantic bash-script is generated that contains lines of calls to the nix-prefetch-url
---a--demo--excerpt--start---
nix-prefetch-url --type sha256
http://bits.xensource.com/oss-xen/release/4.5.1/xen-4.5.1.tar.gz
0w8kbqy7zixacrpbk3yj51xx7b3f6l8ghsg3551w8ym6zka13336 ;
nix-prefetch-url --type sha256 sourceInfo.url sourceInfo.hash ;
nix-prefetch-url --type sha256
http://download.belastingdienst.nl/belastingdienst/apps/linux/ib2007_linux.tar.gz
13p3gv086jn95wvmfygdmk9qjn0qxqdv7pp0v5pmw6i5hp8rmjxf ;
---a--demo--excerpt--end---

I executed the gigantic bash script and my conclusion is that many up-stream packages, their files, are offline or their hashes do not match, specially those of the npm.
In those circumstances it is absolutely no wonder that there are various build problems. I propose that in addition to "stable" and "unstable" packages would be classified as "Nix-contained" and
"up-stream-dependent".
The "Nix-contained" packages would be buildable without downloading anything from any server other than the Nix project servers and various caches. I believe that package specific, up-stream dependent, package upgrade tools might be bundled with the "Nix-contained" packages, so that when the up-stream servers come online, the package upgrade could be manually made and the "Nix-contained" set of packages is supplemented with a new version of the package without removing the old version.
Currently it seems to me that the up-stream dependent package build scripts try to do 2 in one: build a Nix package and upgrade its dependencies. In the case of the "Nix-contained" packages the package building would work without downloading anything from upstream and all testing and experimentation that is related to the upgrade of the dependencies of a "Nix-contained" package, would be carried out by the package maintainer at a time, when he/she has the time to work on the package, not whenever the package is being automatically built.
Thank You for reading my letter and I hope to receive criticism that tells that I'm missing/omitting
a lot of important issues or have otherwise come up with a spectacular blunder.
Regards,
<EMAIL_ADDRESS>P.S. The "manual" upgrade of dependencies will probably be a requirement even due to computational limitations and security requirements. Formal verification might take a lot of CPU-power and it might not be optimal to run that every time a package is built.
---citation--end-----

@martinvahi I can see you message on the mailing list, as you also got a reply.
In the worse case you can see it on http://lists.science.uu.nl/pipermail/nix-dev/2015-November/018688.html
Closing.

Strange, I can not find it, but the link that You provided was very useful. I'll look into the proposed
nix-store -r $(grep -l outputHash $(nix-store -qR $(nix-instantiate '<nixpkgs>' -A foobar) | grep '.drv$'))

but it seems to me that nobody addressed the issue that some dependencies of the nixpkgs are occasionally offline and some of the nixpkgs packages upgrade their dependencies as part of the build task. Any upgrade of dependencies can actually break a package and needs testing and probably package code modifications. In that sense I do not think that this issue should be closed, id est this bug report here should be re-opened.

Strange, I can not find it, but the link that You provided was very useful.

IIRC the mailer doesn't send messages to people that are known to already have the message, e.g. the sender or additional recipients.

First of all, thank You all/both for Your answers. I took a second look at the mailing list digests and it seems that indeed, replies to my both letters are present, but my own letter seems to be omitted, as described by vcunat. However, what regards to the nixpkgs packages that download upstream dependencies as part of their build process, then it seems to me that I have to create some utility for myself that classifies the different nixpkgs packages, generates a list of pacakges that can be classified as "Nix-contained". The utility would act on the nixpkgs packages a bit like the PricewaterhouseCoopers acts on companies, giving them marks in different categories.
To avoid re-implementing a wheel, does there exist some utility that tries to do something similar already?

That's what the outputHash grep is for, I believe. Only fixed-output derivations can access network and thus download http://nixos.org/nix/manual/#fixed-output-drvs Usage of them for anything but fetches is rare, I think, except for the recently added texlive packages (all of them, i.e. thousands).

A citation from the manual:
It sometimes happens that the URL of the file changes, e.g., because servers are reorganised or no longer available. We then must update the call to fetchurl, e.g.,

Is there a way to add more then one fetch URL, so that when one of the servers is offline, then another URL is tried? If the hash of the downloadable file is already known, then if anonymity is discarded, it should not matter, which URL is used.
Second question is, is there some plugin mechanism so that for some type of network, for example, Tor or GNUnet or whatever else, the downloading of a pacakge could be delegated to some other application. The mechanism would be that first the URL is classified, a bit like files are classified to MIME types, and then according to the type of the URL the download task is handed over to a program that is able to handle the given type of URL. The URL might even be some Magnet link.

(reopen as the discussion moved to github)

May be a dirty workaround might be the use of some proxy, like
url = http://www.my_proxy_site.com/nix_proxy.php?hash_algorithm=foo&hash_value=bar&network=tor&hint_url_1=<the first url to try>&hint_url_2=<the second URL to try>&<etc.>

and for local proxies the .nix file is preprocessed by replacing
www.my_proxy_site.com/
with
localhost:<some port number>/

Probing for different, mirroring, URL-s would then be the task of the proxy.

@martinvahi: fetchurl supports using a list in urls instead of url.

Second question: you can code an arbitrary fetcher – we have fetchgit, fetchzip, fetchsvn, ... it's an arbitrary builder that is given access to network because the hash of output is specified in advance.

On my AMD64:
ts2@linux-0fiz:/nix$ nix-instantiate '<nixpkgs>' -A hello
error: file ‘nixpkgs’ was not found in the Nix search path (add it using $NIX_PATH or -I)

The whole excerpt:
ts2@linux-0fiz:/nix$ nix-env version
error: no operation specified
Try ‘nix-env --help’ for more information.
ts2@linux-0fiz:/nix$ nix-env --help
No manual entry for nix-env
ts2@linux-0fiz:/nix$ uname -a
Linux linux-0fiz 3.16.7-29-desktop #1 SMP PREEMPT Fri Oct 23 00:46:04 UTC 2015 (6be6a97) x86_64 x86_64 x86_64 GNU/Linux
ts2@linux-0fiz:/nix$ nix-instantiate '<nixpkgs>' -A hello
error: file ‘nixpkgs’ was not found in the Nix search path (add it using $NIX_PATH or -I)
ts2@linux-0fiz:/nix$ which nix-env
/home/ts2/inst/nix/bin/nix-env
ts2@linux-0fiz:/nix$ date
Sat Nov 21 22:56:31 EET 2015
ts2@linux-0fiz:/nix$ hello
Hello, world!
ts2@linux-0fiz:/nix$ which hello
/home/ts2/.nix-profile/bin/hello
ts2@linux-0fiz:/nix$

Well, my suspicion about the lack of tests before commits seems to hold. I downloaded the 2015_11_22 early morning version of the Nix src from GitHub and the compilation failed.
ts2@linux-0fiz:~/Projektid/progremise_infrastruktuur/lemmestega_seonduv/Nix_projektid/kompil/v2015_11_21_Nix$ ./configure --prefix=/home/ts2/inst/nix
configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /usr/bin/sed
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for the canonical Nix system name... x86_64-linux
checking for gcc... clang
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether clang accepts -g... yes
checking for clang option to accept ISO C89... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether clang++ accepts -g... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for pubsetbuf... yes
checking for chroot... yes
checking for unshare... yes
checking for statvfs... yes
checking how to run the C preprocessor... clang -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking sched.h usability... yes
checking sched.h presence... yes
checking for sched.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for sys/mount.h... yes
checking sys/syscall.h usability... yes
checking sys/syscall.h presence... yes
checking for sys/syscall.h... yes
checking for lutimes... yes
checking for sched_setaffinity... yes
checking whether it is possible to create a link to a symlink... yes
checking how to run the C++ preprocessor... clang++ -E
checking locale usability... yes
checking locale presence... yes
checking for locale... yes
checking err.h usability... yes
checking err.h presence... yes
checking for err.h... yes
checking linux/fs.h usability... yes
checking linux/fs.h presence... yes
checking for linux/fs.h... yes
checking for curl... /usr/bin/curl
checking for bash... /bin/bash
checking for patch... /usr/bin/patch
checking for xmllint... /usr/bin/xmllint
checking for xsltproc... /usr/bin/xsltproc
checking for flex... /usr/bin/flex
checking for bison... /usr/bin/bison
checking for perl... /usr/bin/perl
checking for sed... /usr/bin/sed
checking for tar... /bin/tar
checking for bzip2... /usr/bin/bzip2
checking for gzip... /usr/bin/gzip
checking for xz... /usr/bin/xz
checking for dot... /usr/bin/dot
checking for dblatex... /usr/bin/dblatex
checking for pv... /usr/bin/pv
checking whether Perl is recent enough... yes
checking for the Perl installation prefix... ${exec_prefix}/lib64/perl5/site_perl/5.20.1/x86_64-linux-thread-multi
checking for cat... /usr/bin/cat
checking for tr... /usr/bin/tr
checking for openssl... /usr/bin/openssl
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for OPENSSL... yes
checking for BZ2_bzWriteOpen in -lbz2... yes
checking bzlib.h usability... yes
checking bzlib.h presence... yes
checking for bzlib.h... yes
checking for SQLITE3... yes
checking for LIBCURL... yes
checking for SODIUM... yes
checking for LIBLZMA... yes
checking whether DBD::SQLite works... yes
checking whether WWW::Curl works... yes
checking for otool... no
checking that otool works... not needed
checking whether to build the Perl bindings... yes
checking for setresuid... yes
checking for setreuid... yes
checking for lchown... yes
checking for strsignal... yes
checking for posix_fallocate... yes
checking for nanosleep... yes
checking for sysconf... yes
checking if you have a recent GNU tar... yes
configure: creating ./config.status
config.status: creating config.h
ts2@linux-0fiz:~/Projektid/progremise_infrastruktuur/lemmestega_seonduv/Nix_projektid/kompil/v2015_11_21_Nix$ time nice -n20 make
  GEN    Makefile.config
  GEN    doc/manual/version.txt
  GEN    doc/manual/manual.xmli
  GEN    doc/manual/manual.is-valid
I/O error : Attempt to load network entity http://docbook.org/xml/5.0/rng/docbook.rng
warning: failed to load external entity "http://docbook.org/xml/5.0/rng/docbook.rng"
Relax-NG parser error : xmlRelaxNGParse: could not load http://docbook.org/xml/5.0/rng/docbook.rng
Relax-NG schema http://docbook.org/xml/5.0/rng/docbook.rng failed to compile
-:1: parser error : Document is empty

^
-:1: parser error : Start tag expected, '<' not found

^
doc/manual/local.mk:29: recipe for target 'doc/manual/manual.is-valid' failed
make: *** [doc/manual/manual.is-valid] Error 1

real	0m0.655s
user	0m0.202s
sys	0m0.150s
ts2@linux-0fiz:~/Projektid/progremise_infrastruktuur/lemmestega_seonduv/Nix_projektid/kompil/v2015_11_21_Nix$

Within my limited capabilities I might try to help with deliverables, but I can not do anything about the habits of other people. Right now I do not know, if the GNU Guix is any better, but I'll experiment with it. I guess that regardless of the state of the GNU Guix project it still takes some time, till the Nix project people get their social aspects sorted out. It is possible that I have misunderstood something again, but I have not noticed that there would be a Git repository for "stable" code or, "release candidates" code, something that new developers could download as a WORKING example to learn and dig into.

Check github.com/NixOS/nixpkgs-channels if you want git refs that match stable/tested versions.

@martinvahi: nix-1.10 compiles fine if you set up the environment correctly, i.e. nix-build -A nix works in nixpkgs. (And many people seem to be using it.) In your case you were missing some docbook stuff needed for documentation.

Thank You for the answers and thank You for the link. I'm just trying to figure out, how to use the link. The way I currently understand the "channels" concept, a channel is basically a "bookmark collection" that tells, where the packages are. However, when I look at the MANIFEST file of the nixpkgs-unstable, then it contains keywords like NarURL, NarHash and when I search for those keywords from the Nix manual, the keywords are not even mentioned at the manual. On the other hand, the aforementioned https://github.com/NixOS/nixpkgs-channels does not contain any MANIFEST file either, which hints that I should assemble my own MANIFEST file, if I want to use the https://github.com/NixOS/nixpkgs-channels.
Could You please write, if there are any solutions smarter than the one that I just planned?
http://nixos.org/releases/nixpkgs/nixpkgs-16.03pre71923.3087ef3/MANIFEST

Our manifest files are superseded by binary caches nowadays.
The nixpkgs-channels repository are just branches pointing into versions of nixpkgs repository that were put into the binary cache (after builds and tests succeeded). Therefore the two repositories are "used the same way". Our binary cache is one and shared by all channels/branches.

Thank You for the binary cache related reply. I gather that the Nix manual section that talks about channels is then out of date. Is there any way to contribute documentation without using DocBook? To put it directly, editing some archaic, custom semantics based, XML and setting up a  complex development environment just to write structured text with image based illustrations and links is a waste of my time, so DocBook is certainly not an option for me. LaTeX is acceptable, because I can edit that with a plain text editor and see the generated PDF or DVI with a single console command. The GNU TeXmacs is also attractive.
The way I remember the discussion from the Nix mailing list, people wanted to kill the wiki, because uninformed contributers write uninformed claims there. They also wanted to keep the documentation "near the source". The Fossil places the whole central repository, bugtrack, wiki with all its history, code submissions with all the history, users-and-passwords to a single file. It is also possible to "clone" the Fossil repository so that it contains everything public, but lacks the info about users and passwords. The "clone" can be placed to the documentation folder of the Nix package manager and the the Fossil is actually really stable, compiles to a single binary that can be hosted as a CGI-script or it can be run as a wiki-serving-web-server on localhost by giving the "clone" as one of its console arguments. As a matter of fact, I even host a separate Fossil repository(You might try "raudrohi", "sirel", "kibuvits") for all of my open source projects and client projects and at the end of the client project I give the client a copy of the Fossil repository file that contains all bug reports (with history), wiki (with history), central code repository, etc. That is to say, the Fossil is really great and might be a solution for the Nix documentation project. If people would just accept it.

I gather that the Nix manual section that talks about channels is then out of date.

There seems nothing wrong about the manual section. It's mentioned (in a few words) that channels contain a manifest, and they still do, I think, only it's not really relevant for nowadays usage.

Is there any way to contribute documentation without using DocBook?

I think @domenkozar wrote some parts in some markdown-like format, but most is in DocBook (which is a format quite often used for technical docs). There are various convertors, so you might well write in anything else and then jut export.

That is to say, the Fossil is really great and might be a solution for the Nix documentation project.

Switching from git to fossil seems extremely unlikely in near future. There would have to be much clearer advantages to go with another switch. And I remember fossil was considered when we were switching svn -> git(hub).

As of 2015_11_25 it seems to me that there is no point on working on the package collection related issues before the package maintenance part, the Nix, has been fixed at least to the extent thet the #718 has been fixed. I'm not sure, what the tag of the current flaw report should be, but a word "pending" might suit.

Personally, I would prefer if this discussion moved to the nix-dev mailing list. Github issues are really a poor forum for technical discussions.


Vickel: Watch glam[\W_]*+(?:a)?esthetics

Vickel requests the watch of the watch_keyword glam[\W_]*+(?:a)?esthetics. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

glam[\W_]*+(?:a)?esthetics has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Rejected by Makyen in Charcoal HQ. Reason: 'Went with a slightly different regex'


refactor(connlib): remove Result return values from callbacks

Currently, an error returned by Tunnel::poll_next_event is only logged. In other words, they are never fatal. This creates a tricky to understand relationship on what kind of errors should be returned from callbacks. Because connlib is used on multiple operating systems, it has no idea how fatal a particular error is.
This PR removes all of these Result return values with the following consequences:

For Android, we now panic when a callback fails. This is a slight change in behaviour. I believe that previously, any exception thrown by a callback into Android was caught and returned as an error. Now, we panic because in the FFI layer, we don't have any information on how fatal the error is. For non-fatal errors, the Android app should simply not throw an exception. The panics will cause the connlib task to be shut down which triggers an on_disconnect.
For Swift, there is no behaviour change. The FFI layer already did not support Results for those callbacks. I don't know how exceptions from Swift are translated across the FFI layer but there is no change to what we had before.
For the Tauri client, I chose to log errors on ERROR level and continue gracefully. That is equivalent to what happened previously, it is now just more obvious that we don't actually abort when any of these things fail. Panics are passed through as before because we stay in Rust land.

Resolves: #4064.

I think conceptually, we should adopt the following model:

Any exception / panic in a callback will shut down connlib. I'd consider that to be reasonable and not surprising.
If a client encounters a fatal error that needs to stop connlib, it should call disconnect.

(1) should only be considered a last-resort way of dealing with things, i.e. exceptions / panics shouldn't be the standard way of error handling.

With both this and #4159, I'm more confused about how the callbacks are intended to work.
I'll add to my comment in the Slack thread about 4159

Mind re-reviewing this after the conversation we had on Slack? :)


Investigate Compiler Performance

The current HKT encoding seems to be very heavy on the compiler, investigate if it is possible to improve, eg:
import { pipe, tuple } from "@effect-ts/core/Function"
import * as NA from "@effect-ts/core/NonEmptyArray"
import * as R from "@effect-ts/core/Record"

type License = "CC" | "MIT"

interface Hero {
  name: string
  license: License
}

function hero(name: string, license: License): Hero {
  return { name, license }
}

const toRecord = R.fromFoldable(NA.getAssociative<Hero>(), NA.Foldable)

const grouped = pipe(
  [hero("Johannes", "CC"), hero("Mike", "MIT")],
  NA.map((h) => tuple(h.license, NA.single(h))),
  toRecord
)

Takes about 10 seconds for VSCode LSP to keep up with changes

Conditional types and especially tuple recursion are the problem, the only practical solution is to remove support for transformers #552

closed with #556


Realistic airspeeds

Add an option to use simplified airspeeds.  By default it is enabled and game behavior is unaffected.
When disabled, aircraft ground speeds are affected by altitude.  The model is 1.6% increase in ground speed per 1000 feet altitude.  The speed shown in data blocks on the radar is always ground speed.
The 1.6% is based on http://williams.best.vwh.net/avform.htm#Mach with a slight increase to account for compression effects.  I didn't do the math to see how much of an effect compression would actually have at the speeds generally encountered in game.

Ooohhhh I like this... that will certainly do a lot to make it "feel right"!
@zlsa Going further with this, are the aircraft currently affected by the wind settings? They don't appear to be, based on what I can see. Being able to crank up a stiff 30-40 degree crosswind throws off all your timing down in the final corridor and really makes you think harder as each base leg could differ by 20+ knots groundspeed.... allowing wind to "push" the airplanes would be a really great feature!

Thanks :smile:
Aircraft are not affected by wind at this point, see #289.


[Event Request] Table 5050 Contact - OnShowCustVendBankBeforeRunPage

Please add a new publisher event to the function ShowCustVendBank as follows:
.
.
  1:
    ContBusRel.FINDFIRST;
  ELSE
    FormSelected := PAGE.RUNMODAL(PAGE::"Contact Business Relations",ContBusRel) = ACTION::LookupOK;
END;

//>> Start New Publisher Call
OnShowCustVendBankBeforeRunPage(Rec, FormSelected, ContBusRel, IsHandled);

IF IsHandled THEN
  EXIT;
//<< End New Publisher Call

IF FormSelected THEN
  CASE ContBusRel."Link to Table" OF
    ContBusRel."Link to Table"::Customer:
      BEGIN
.
.

New Publisher Event:
LOCAL [IntegrationEvent] OnShowCustVendBankBeforeRunPage(VAR Contact : Record Contact;FormSelected : Boolean;VAR ContBusRel : Record "Contact Business Relation";VAR IsHandled : Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Updated the leadership calendar copy and links

Changes

Updated the leadership calendar copy
Updated links in leadership calendar page and removed History link

Testing

Visit http://localhost:8000/about-us/the-bureau/leadership-calendar/ and test the links in the footer!

Review

@anselmbradford
@jimmynotjim
@sebworks

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Minor comment :+1: otherwise

:+1:


Issue with the Quick Start Guide in 5.8.0 version

hi,
I wanted to configure my IS version 5.8.0 with users and service providers of the Quick Start Guide. I run the corresponding scripts, however even if everything is working fine, although the users are visible under 'Users', no service providers are visible!

closed

Hi stefanonegri
We use Cameron credentials to create service providers therefore the service providers only visible if you log using Cameron credentials.
Thanks
wijith


allows for image repos to be set via Environment Variables

What type of PR is this?
/kind feature

What this PR does / why we need it:
Sometimes clusters will not have access to upstream image repos. This updates the manifests in the clusterloader2 "load" test to support setting the 2 image repos used via Environment Variables, like the others starting with '.CL', while still keeping the current repos set as defaults. This allows the use of mirrors image repos which may be available to clusters.
.CL2_REGISTRY_K8S_REPO for registry.k8s.io
.CL2_GCR_REPO for gcr.io
Which issue(s) this PR fixes:

Fixes # https://github.com/kubernetes/perf-tests/issues/2704
Special notes for your reviewer:

/ok-to-test

/retest

/retest

/retest

/retest


Do not capture whole test instance when provider is enough

The test listeners live for the entire test run duration. Capturing
a test instance in the listener prevents it from being GC'ed, and the
test instance can be quite large. Having hundreds of them can easily
cause OutOfMemoryError.
This commit reduces the retained size of the listener by only capturing
the test directory provider, which is much smaller.

@bot-gradle test RfR

OK, I've already triggered the following builds for you:

ReadyForRelease build

@bot-gradle test and merge
Looks like the failures were flakes.

No milestone for this PR. Please set a milestone and retry.

@bot-gradle test and merge

OK, I've already triggered a build for you.


[Bug] Default value of barCategoryGap and  barGap not as described in the document

Version
5.5.1
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?code=PYBwLglsB2AEC8sDeAoWszGAG0iAXMgL4A0as2ApgOaXQAmhSp5AHgIKsQDOT569AIZhBhANoAiALIwJJWBIAqAV0pyFAdUr11SgBbLdAMQBOEXQGVhl5dAkBdci3QBPTjybPY3Smcq9YMVR0dGhBAFtKQgkrKjl-DBcQKIUAI0ETeJDYIRFxAFZ5ACYABnkAZgA2eQBGMtg64vqAFkd0IkciIA&_source=echarts-doc-preview
Steps to Reproduce

Use the example of https://echarts.apache.org/zh/option.html#series-bar.barCategoryGap
Edit the example, set barCategoryGap as  '20%' , will found the bar width and gap changed,  set barCategoryGap as '31%', bar width and gap not changed
Add another series, set barGap as '30%', will found bar width and gap changed, set barGap as '20%', not changed

Current Behavior
Description is inconsistent with behavior。
In the document,  default value of barCategoryGap is '20%'， default value of barGap is '30%'.
Expected Behavior
I expect the description to be consistent with the behavior。
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

API for both barGap and barCategoryGap  says "this attribute is shared by multiple 'bar' series". This means they should be defined once in a single bar series.


Dedicated strike team to resolve unsafe code guidelines

Incorporate a strike team dedicated to preparing rules and guidelines for writing unsafe code in Rust (commonly referred to as Rust's "memory model"), in cooperation with the lang team. The discussion will generally proceed in phases, starting with establishing high-level principles and gradually getting down to the nitty gritty details (though some back and forth is expected). The strike team will produce various intermediate documents that will be submitted as normal RFCs.

cc @arielb1 @ubsan @eternaleye @rust-lang/lang

I am interested as well.

Something I'd've expected the RFC to mention:
What's the motivation for forming a separate "strike team" to take on this responsibility, instead of making it a priority for one or more of the existing teams*? Is it expected that the membership of the strike team will have minimal overlap with the existing teams? Otherwise, if it's mostly the same people, the amount of capacity they have available to dedicate to the effort will be a constant independently of what team rosters they appear on. Of course, the phrase "strike team" evokes swift and decisive progress, and everyone's in favor of swift and decisive progress, but naming aside why is this special-case organizational structure felt to be necessary and expected to be effective in this case? (And why not for other major priorities? What aspect of this one makes the difference?)
* The RFC writes "It is the contention of this RFC that a complete guidelines for unsafe code are far too big a topic to be fruitfully addressed in a single RFC. Therefore, this RFC proposes the formation of a dedicated strike team" -- but I don't see how these are connected. There's no reason in principle why the effort couldn't be structured as a multi-RFC process as described without a dedicated strike team, or for that matter why a strike team couldn't have creating a single "big bang" RFC as its objective.

@glaebhoerl The intent is that the strike team will include members not currently on subteams, and hopefully act in consultation with academics and other experts.
As @nikomatsakis says, the lang team is expected to be heavily involved in some of the higher-level aspects, but we need people who can devote significant time to working out the details as well, and don't have the resources on the lang team alone.
(I agree that the way the RFC explains this isn't very clear.)
FWIW, I'm also a bit uneasy about the expectation that the artifacts here will end up going through the normal RFC process as well. I think we should try to get some clarity on who and how the decisions are going to be made.
====
Separate concern: as someone who's spent some time on formal memory models (the concurrency side of C/C++11), I have significant respect for the problem space -- there are many open research problems in memory models, and many mistakes made over the course of years-long efforts by myriad experts. I think we need to go about this in a humble and open-ended way, with an emphasis on incremental, conservative gains. I think @nikomatsakis has done a good job of pushing in this direction by delineating the scope and highlighting some intermediate artifacts, but I'm hoping that we can reach further clarity on that front in this RFC thread.

FWIW, I'm also a bit uneasy about the expectation that the artifacts here will end up going through the normal RFC process as well. I think we should try to get some clarity on who and how the decisions are going to be made.

I would be open to changing this, but I still think it's a good idea. I think there are a lot of people who pay attention to RFCs, but don't follow the minute details -- they would probably want to know that a larger decision is on the cusp of being made.
On the other hand, maybe we can just advertise that another way, but it seems like we have an existing RFC channel, so why not use it?
One counter argument might be that we won't actually be ready to settle on a "high-level approach" (for example) until the detailed approach is nearly done, at which point there will be a lot of resistance to changing -- but that seems ok to me. If crucial flaws are found, great, we can fix them -- and if not, then we can continue moving forward.

@glaebhoerl

What's the motivation for forming a separate "strike team" to take on this responsibility, instead of making it a priority for one or more of the existing teams*? Is it expected that the membership of the strike team will have minimal overlap with the existing teams?

Yes, that is expected and the point.

Will there be a stabilisation period for changes to the unsafe code guidelines?

Will there be a stabilisation period for changes to the unsafe code guidelines?

It probably makes sense to try and follow the process for features as much as possible -- this would imply an FCP for the "RFC", and then a secondary stabilization period. In the interim, I would expect that we'll make strides on modifying the compiler to take advantage of these new guidelines when optimizing, as well as surveying code for compliance, so that we can have a good feeling for how things are working out.

Nominating for FCP.

lgtm. I think this would be improved with some language about the conditions for disbanding the strike team; once these things are accomplished, the team's work is done.

@brson is it? I look at C++, and their "strike teams" are never finished -- they have a team for gamedev, a team for the memory model, a team for everything. It seems to work out pretty well for them.

@brson is it? I look at C++, and their "strike teams" are never finished -- they have a team for gamedev, a team for the memory model, a team for everything. It seems to work out pretty well for them.

Once there's a spec covering the memory model, I don't see what significant ongoing work there will be that can't be folded into the existing project structure. Whether the team is expected to exist forever or to have a finite purpose and then end, I would like it to be addressed.

@brson Nowhere is the intention of this team to create a specification. There is no Rust specification.
(barring my personal project which is empty, because I haven't upstreamed any local changes yet)

@brson Nowhere is the intention of this team to create a specification, unless this team is supposed to start the Rust specification. There is no Rust specification.

Thanks for the correction @ubsan. Please consider my previous comment to apply to whatever documentation this team is going to produce.

Like @brson, I assumed that the purpose of this team was indeed limited in duration. That is, the team exists for the purpose of doing the sprint work to produce the initial documents described within. After that, smaller questions can presumably be resolved by the normal RFC process -- which would of course include input from the strike team members!

After thinking more about the difference in meaning between 'team', 'subteam', and 'strike team', I do find it attractive for us to get to a place where many teams are flourishing in some official capacity. It wouldn't be a bad thing - it would be really great - for the teams page to be filled with many, many active contributors. The bigger Rust gets (and it's going to get really big) the more people need to be empowered to make decisions. But still I am inclined to push back on expansions of the bureaucracy, and want us to make those changes carefully.

@brson I think the current bureaucracy is inefficient in part because some people are doing a lot of jobs at once. If we could just have more people doing less... We know that there are people in the community who want to help, but their skills aren't really fully utilized since everything needs to go through six people (and from personal experience, it just feels kind of hopeless when you're in that position).

Rendered version

This RFC is entering its final comment period. The main point on which we need to reach final consensus is the precise "success conditions" (and whether the team is disbanded). This question intersects considerably with the ongoing discussion around refinements to the RFC process, but if possible we shouldn't block getting going on this team on those broader questions.

The main point on which we need to reach final consensus is the precise "success conditions" (and whether the team is disbanded).

It seems to me that the "success conditions" would be producing the various documents cited in the RFC. That is, the team exists to produce the initial version of those documents.
I'm not sure what I think about longer-lived "subsubteams" yet -- I go back and forth -- but I do feel pretty sure that this RFC wouldn't be the right place to establish such a thing. I feel like that's creating permanent structure is a more fundamental change more, akin to https://github.com/rust-lang/rfcs/pull/1068, and hence worthy of being discussed separately.

@ubsan: We really need a spec and then csn define what are common and what are accepted variance for porting.

Huzzah! The @rust-lang/core team has decided to accept this RFC.
If this stuff is of interest to you, you probably want to subscribe to this internals category:
https://internals.rust-lang.org/t/about-the-unsafe-code-guidelines-category/3706


WebVTT rendering - shaka.text.Cue

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
4.4.0
Please ask your question
WHAT

How does the compiler/minifier determine which properties to uglify/minify and which to leave as is?
Is it possible to extend shaka.text.Cue?

The problem I am facing is that shaka.text.Cue doesn't seem to support VTTCue.line or VTTCue.snapToLines
in the minified version at runtime.

The screenshot above shows an instance of shaka.text.Cue with some uglified and some readable properties. To my humble eye, its unclear what the compiler latches onto as the determining factor.
WHY
I am trying to take control of the rendering of VTTCues because I am not getting quite the same behaviour as getCueAsHTML. The solution I have arrived at is to extend shaka.text.VttTextParser and register a parser using the shaka.text.TextEngine.registerParser API for the text/vtt mimeType.

Upgrade to a newer version of shaka-player, that was fixed a while ago.


Feature/integration tests

enables running the the app locally
gets to here (link )https://github.com/Kevin-Sim/SET08103/tree/master/labs/lab08#adding-github-actions-job-stages

I started doing the work for the integration tests and thought it would be better to do it on a different branch since its unrelated to the queries / unit tests work
I just did the first part of this https://github.com/Kevin-Sim/SET08103/tree/master/labs/lab08#adding-github-actions-job-stages - as per my PR comment


Add setting for voice search

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #3477

PR #3489

PR #3516
PR #3491
PR #3490

PR #3528   👈

This comment was auto-generated by Graphite.


Flutter Web App Performance on Mobile Chrome Browsers Using --web-renderer html

Steps to reproduce
I created a fresh Flutter project, generated a web build using the flutter build web --web-renderer html command, and hosted the app on GitHub Pages. When accessing the hosted app on physical mobile Chrome browsers(chrome://inspect/#devices), I analyzed the performance using Lighthouse in Chrome DevTools. The Lighthouse report indicated poor performance scores, especially in areas like Speed Index, First Contentful Paint (FCP), and Largest Contentful Paint (LCP).
This raises concerns about whether Flutter Web apps are optimized for mobile browsers when using the HTML renderer. Below are the specific details and observations related to the issue.

Create a new Flutter project:
flutter create web_test_project
cd web_test_project

Build the web app using the HTML renderer:
flutter build web --web-renderer html

Host the generated build/web folder on GitHub Pages.

Open the hosted app on a mobile Chrome browser.

Use Chrome DevTools' Lighthouse tool to generate a performance report.

Expected Results

The Flutter Web app should provide a reasonable performance score on mobile Chrome browsers.
Metrics such as Speed Index, FCP, and LCP should be optimized for mobile

Actual Results

Poor Lighthouse performance scores, especially for key metrics like:
Speed Index
First Contentful Paint (FCP)
Largest Contentful Paint (LCP)
High initial load time observed on mobile Chrome browsers.

Questions

Is the Flutter Web HTML renderer optimized for mobile Chrome browsers?
Are there recommended steps or configurations to enhance the performance of Flutter Web apps on mobile browsers?
Could this be an issue with the Flutter Web framework or the HTML renderer?

Code sample
Create a Fresh project using below command
flutter create web_test_project
What target platforms are you seeing this bug on?
Android
OS/Browser name and version | Device information
Android mobile chrome browser
Does the problem occur on emulator/simulator as well as on physical devices?
Yes
Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[√] Flutter (Channel stable, 3.22.0, on Microsoft Windows [Version 10.0.22631.4317], locale en-US)
    • Flutter version 3.22.0 on channel stable at C:\Program Files\flutter_windows_3.7.7-stable\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5dcb86f68f (7 months ago), 2024-05-09 07:39:20 -0500
    • Engine revision f6344b75dc
    • Dart version 3.4.0
    • DevTools version 2.34.3

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\Users\pgoyal\AppData\Local\Android\sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: C:\Program Files\Java\jdk-17\bin\java
    • Java version Java(TM) SE Runtime Environment (build 17.0.12+8-LTS-286)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[X] Visual Studio - develop Windows apps
    X Visual Studio not installed; this is necessary to develop Windows apps.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[√] Android Studio (version 2024.1)
    • Android Studio at C:\Program Files\Android\Android Studio1
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.11+0--11852314)

[√] Android Studio (version 2022.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = C:\Program Files\Android\Android Studio
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[√] VS Code (version 1.95.3)
    • VS Code at C:\Users\pgoyal\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.100.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22631.4317]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 129.0.6668.103
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 131.0.2903.86

[√] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

@pgoyal-android
The html web renderer has been deprecated as part of https://github.com/flutter/flutter/issues/145954.
The --web-renderer html flag is now not available in master version, so even if now you are seeing performance related issues with this renderer, it will be unlikely to be fixed. So I suggest you to migrate or use canvaskit renderer to see if you still get same reported behavior or not. If not, please file a new issue stating the same.
I will close this issue, per above explaination. If you disagree, write in comments and I'll reopen it.

@darshankawar Thank you for the update regarding the deprecation of the html web renderer. Following your recommendation, I tested my Flutter web app with the canvaskit renderer. However, I noticed the following:
1.Test Setup and Observations:
I hosted a dummy Flutter web application on this URL without using the --web-renderer html flag.
Analyzed the performance using Lighthouse on a physical mobile device running Chrome, accessed via chrome://inspect/#devices.
The performance score on mobile Chrome browsers did not show significant improvement compared to the html renderer.

Desktop vs. Mobile Performance:

When analyzing the same hosted app using a laptop browser (Chrome), Lighthouse consistently reported performance scores above 90.
On mobile devices, the score remains average, indicating that the hardware resource limitations of mobile devices might be a contributing factor.

Core Concern:
My question remains: Is Flutter Web optimized for mobile Chrome browsers, given the hardware constraints of mobile devices?

Additional Data:
I have attached the Lighthouse scores for mobile and desktop Chrome browsers for reference.

If further analysis or clarification is required, please let me know. Thank you for your support!
Mobile chrome browser score

Laptop chrome browser score

Note : I am currently on Flutter (Channel stable, 3.22.0, on Microsoft Windows) version.