cvs_fast_export: 1.55 -> 1.56

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cvs-fast-export/versions.
meta.description for cvs_fast_export is: "Export an RCS or CVS history as a fast-import stream"
meta.homepage for cvs_fast_export is: "http://www.catb.org/esr/cvs-fast-export/"
meta.changelog for cvs_fast_export is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56/bin/cvs-fast-export passed the binary check.

/nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56/bin/cvssync passed the binary check.

/nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56/bin/cvsconvert passed the binary check.

/nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56/bin/.cvs-fast-export-wrapped passed the binary check.

/nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56/bin/.cvsconvert-wrapped passed the binary check.

/nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56/bin/.cvssync-wrapped passed the binary check.

2 of 6 passed binary check by having a zero exit code.

6 of 6 passed binary check by having the new version present in output.

found 1.56 with grep in /nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56

found 1.56 in filename of file in /nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56

directory tree listing: https://gist.github.com/394f14b87c0789a28ca69216b75b19c9

du listing: https://gist.github.com/a302587256893a6bd21eff6e061bb4f8

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
cvs_fast_export

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cvs_fast_export https://github.com/r-ryantm/nixpkgs/archive/b6cbf005d7126580884a12b8540bb4c5f56e5c8a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56
ls -la /nix/store/b8nmsisblsvihc7wibfd7mmcb4d499as-cvs-fast-export-1.56/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

cvs_fast_export

Maintainer pings
cc @dfoxfranke for testing.

Result of nixpkgs-review pr 120989 at b6cbf005 run on x86_64-linux 1

1 package built successfully:

cvs_fast_export

8 suggestions:

warning: build-tools-in-build-inputs
makeWrapper is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/version-management/cvs-fast-export/default.nix:23:3:
   |
23 |   buildInputs = [
   |   ^

warning: build-tools-in-build-inputs
git is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/version-management/cvs-fast-export/default.nix:23:3:
   |
23 |   buildInputs = [
   |   ^

warning: build-tools-in-build-inputs
yacc is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/version-management/cvs-fast-export/default.nix:23:3:
   |
23 |   buildInputs = [
   |   ^

warning: build-tools-in-build-inputs
docbook-xsl-nons is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/version-management/cvs-fast-export/default.nix:23:3:
   |
23 |   buildInputs = [
   |   ^

warning: build-tools-in-build-inputs
flex is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/version-management/cvs-fast-export/default.nix:23:3:
   |
23 |   buildInputs = [
   |   ^

warning: build-tools-in-build-inputs
docbook_xml_dtd_45 is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/version-management/cvs-fast-export/default.nix:23:3:
   |
23 |   buildInputs = [
   |   ^

warning: build-tools-in-build-inputs
asciidoc is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/version-management/cvs-fast-export/default.nix:23:3:
   |
23 |   buildInputs = [
   |   ^

warning: build-tools-in-build-inputs
bison is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/version-management/cvs-fast-export/default.nix:23:3:
   |
23 |   buildInputs = [
   |   ^

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

1 package built:

cvs_fast_export


[*] Changes registry in package-lock to default

[*] Adds npmrc files to enforce default registry

the npm i is failing - "no such directory" for the node modules

the npm i is failing - "no such directory" for the node modules

will look into it, not sure what could be causing that 🤔

@ReallySmall not sure what to do with this one, works fine for me and can't replicate Andy's issues

Let me delete node modules/package-lock and try again. Probably something to do with my local as it was me causing the nexus issue

Let me delete node modules/package-lock and try again. Probably something to do with my local as it was me causing the nexus issue

ok @Matt-Beldon-CDS it took half an hour to re-install all the modules but it worked fine haha. That's my bad for not googling the error


Allowed optional exclusion of protection IDs from shield module

As noted, this allows a module user to supply values which can be excluded from association with the AWS Shield managed WAF ACL. I don't have a good way to supply them without hard-coding, so in example I've placed the relevant ID to be excluded into the application json.
Ideally I'd be able to use a data source like data.aws_shield_protections but as I'm currently using an external data source to get this information there are limits to what I can achieve without adding extra complication.

Couple of errors - a number of checkov failures and one step failed entirely and won't give me details to tell me why

I've re-run the failing step and it's been successful, but as the SCA failures aren't due to code added in this PR I'm going to fix them at a later date.


Spelling Error in Readme

There is a spelling error in the Readme
Summary

Getting Started
Runing the tests
Deployment

Should be:
Summary

Getting Started
Running the tests
Deployment

thanks @AllanRegush 👍 . I added the label bug and good first issue to it

is this taken?

@tory-brown go for it 👍 - I have assigned it to you 🤓

Oh wait, I think it has been fixed already 🤦♂ - sorry
I am sure there are many more spelling mistakes. Someone spelt my name wrong, that still needs fixing, let me try to find it

I found it @tory-brown , let me raise a new Issue and close this one. I will assign the new one to you

@tory-brown I assigned a ticket to you https://github.com/EddieJaoudeCommunity/support/issues/136 any questions let us know in ticket #136


Add MQTT climate two-point target temperature support

Description:
Add two-point (low + high) target temperature support to the MQTT climate platform.
Background: This is so that esphome's native API and MQTT api have the same feature-set.
Mostly based on the existing target temperature stuff in here. The class could use some refactor at some point to reduce the huge amount of code duplication going on.
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io TODO

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Is this the same as https://github.com/home-assistant/home-assistant/pull/20962?

Probably yes, I am not aware another PR have opened for this same feature.

Hey. I didn't see this pull request until it was mentioned in the 0.92 release notes. I have two questions:

What is the intended use of these options and why would I set them? I have an idea of what they are based on nothing but intuition. The climate component docs aren't that descriptive.

Would it be prudent to add template config options for the new temp high/low state topics?

Please open an issue if you suspect a bug. If you need help please use our help channels:
https://home-assistant.io/help/#communication-channels
Merged PRs should not be used for support or bug reports. Thanks!


My domain is being blacklisted

Hello
My personal testing domain:
zcryp.to
has been placed on the blacklist but there is no malicious intent or any scamming whatsoever. Just using this domain to practice web dev skills and for hosting nextcloud. Please remove from blacklist so that I can still use your chrome extension and navigate to my domain
Thanks

Please make the necessary and prompt action to resolve this issue. Why am I encountering this kind of issue  whereas I'm not so adept with this online activity. I'm just learning it bit by bit. Thanks...


Redirects are only advisory not handshake error.

Diagnostic clients must use this connection and cannot be blocked.

I'm working on a test but this area of code is very hard to hit with a unit test.  Verified currently with an integration test

test this please


Display Helium in full screen apps

Be awesome if when you set an app to fullscreen you can still have Helium floating; making it almost sticky to the screen rather than a space.

That admittedly would be cool, but I don't believe it is possible to have an app overlap a fullscreen app in OS X. If you find info that says otherwise, feel free to let me know.

+1
Maybe resist this @JadenGeller? I almost exclusively run apps in fullscreen mode and I know I'm not the only one.

It looks like someone added the feature already! https://github.com/JadenGeller/Helium/pull/100

Ah that's fantastic! I'm on Version 1.6 (12) - when abouts can I expect that to make its way live?

@SamHH I actually went ahead and built it myself. If you're trusting I could send you it.


Add Swix to the Swift Source Compatibility test suite

Here it is.
These tests should be good enough. I think.
Edit
Ah, I see. You're working now on the package-manager branch. Take your time... :)
Maybe I'll drop a PR to help you implementing/porting/testing stuff ^^

I would love help with the port/with the package-manager branch.
Looking at the requirements for inclusion to the Source Compatibility:

Have maintainers who will commit to resolve issues in a timely manner

I can't commit to this.

The package-manager branch is moving to Swix 3 and refactoring a bit (renaming vector to Vector, etc)

Well, and also moving to the Swift Package Manager.


Add method equivalent of x[component]=None

Add a new method which allows setting a default value to a component.
The following lines are equivalent:
x.setComponentToDefault(comp)
x[comp] = None
but the first one is more explicit and raises fewer eyebrows during
code review.

Current coverage is 84.40%

Merging #2 into master will increase coverage by +0.01% as of 21e2a5b

@@            master     #2   diff @@
=====================================
  Files           21     21
  Stmts         2601   2603     +2
  Branches         0      0
  Methods          0      0
=====================================
+ Hit           2195   2197     +2
  Partial          0      0
  Missed         406    406

Review entire Coverage Diff as of 21e2a5b

Powered by Codecov. Updated on successful CI builds.

I'm struggling with this MR for some time already, so I have a few concerns to discuss:

We already have .setComponentByPosition() that works exactly the same as .setComponentToDefault() (since it has value defaulted to None). Do we need both?
For mapping types there is also .setComponentByName() and .setComponentByType() methods, should they have counterparts like .setComponentByNameToDefault() for API consistency? On the other hand that makes API even more hairy.
To set all defaulted components to their defaults all at once we can use .setDefaultComponents(). But that would not touch non-defaulted components of mapping types and would not grow sequences (like seq[10] = None adds 10 elements to a sequence and initialize them with a pyasn1 type). We could probably invent a method like .populateStructureWithElements(start, stop) which is very close to what you have proposed.

I absolutely hate the comp[key] = None way of initializing things, however I'm having troubles coming up with a much better API call. Here None is a sentinel, would it make things more clear if we would have  a more explicit and dedicated sentinel like comp[key] = defaultValue or pass it to a callable like setDefault(comp[key])...?
What do you think would be the most logical, convenient and concise API? I appreciate your thoughts and feedback!

I considered .setComponentByPosition() before, but find it just as surprising as = None. The reason in both cases is that the code like:
x.setComponentByPosition('foo', None)
x['foo']['bar'] = y

and
x['foo'] = None
x['foo']['bar'] = y

raise the same question: "You just set it to None, it's going to explode at runtime, right?"
.setComponentToDefault() may be doing exactly the same thing under the covers, but is more explicit. Even without ever seeing pyasn1 interface before, a random developer will figure out what's going on in:
x.setComponentToDefault('foo')
x['foo']['bar'] = 1

(this is not theoretical situation by the way, I develop code for openstack which is publicly reviewed and got that question a few times)
I admit, I haven't seen .setComponentByType() before, and it is tricky. But then again, I don't know if it matters much in this case. If you're selecting the component by type, you need the complete type already. Which means you're just one step from getting your own default anyway.
The problem with hand-crafting the named default is that I need to get the tags from the component description, but when setting by type I must already have them. Unless I'm missing something it's essentially:
t = create_some_type_in_potentially_long_way
x.setComponentByType(t.getTagSet(), t)

Which doesn't include None and is already quick and clear.
Regarding the third point, I have no opinion. Is the mass-initialisation popular? It seems like if you wanted more than one default object, you'd customise them afterwards, so it's not a huge difference to initialise each element before customisation. But maybe other people have a use for it?...
I like both the defaultvalue alternatives. Although in the assigning case, I'd prefer:
x['foo'] = make_default_value()

so that it's clear that it's a different value each time (even if internally you do always return the same static sentinel (which actually makes a lot of sense)).

Actually I realised that setDefault(x['foo']) won't work - it would be setDefault(None). Then again setDefault(x, 'foo') would work for types too - setDefault(x, t.getTagSet()), just needs to check for string/integer/tagset argument.
But... it would stick out badly in the whole design - everything else is very OOPy, but this would be a completely separate method.
So I guess I like the default sentinel the best. I'm happy to implement that if you agree. Or look at other ideas if not.

As far as I know, mass initialization is not popular. The use case I'm aware of behind:
x['foo'] = None

is to be able to do:
x['foo']['bar'] = 123

To be more precise, the above does not actually set a default value. Rather, when we do x['foo'] = None, we ask x to take pyasn1 object that is associated with 'foo' (through componentType = NamedTypes()) and set it as a value object for x['foo']. If that type object does not have a default (Integer(1) vs Integer()), then you still could not read from x['foo'] (i = x['foo'] would fail unless type for foo is defined with default Integer(1)) but you can go on with further initialization.  Here I'm talking of a scalar component type for simplicity, initialization does not make much sense for scalars.
While I generally prefer the explicit sentinel/function solution over explicit .setComponentToDefault(), the alternative idea would be to permit reading from an unset component, so that:
x['foo']['bar'] = 123

would automatically initialize x['foo'] on component miss prior to performing x['foo']['bar'] assignment. That change would propagate deep into AbstractConstructedAsn1Item. For instance:
x.getComponentByPosition(123)  # -> None
x.setComponentByPosition(123)  # -> initialize component 123
x.setComponentByPosition(123, 'foo')  # -> initialize component 123 and set value 'foo' into it

would turn into:
x.getComponentByPosition(123)  # -> initialize component 123
x.setComponentByPosition(123)  # -> initialize component 123
x.setComponentByPosition(123, 'foo')  # -> initialize component 123 and set value 'foo' into it

On the other hand, assigning to [uninitialized] inner components of a dictionary-like object x['foo'] may look more surprising than x['foo'] = set_value_object_for_component(); x['foo']['bar'] = 123, no?

So basically perl's autovivification? Not a huge fan, but also I'm worried about any existing codebase. If you go that way, then any case of:
if not x['foo']: ...
if x['foo'] is None: ...

starts failing. I've got a number of those even in a tiny project, so I'm sure other people will be upset too. Even if it could be done with some false'y placeholders so that real setting is delayed, the is None comparisons will fail anyway :(

I agree, implicit vivification is evil. BTW, defaultdict in Python can do similar things.
Unless you get better ideas, I'd stick to a function returning a sentinel value (we would probably want to retain current behavior (e.g. x['foo'] = None) for backward compatibility).
If you implement that, I'd be happy to merge your implementation.
Thank you for a great debate!

A bit more code for this one, hope this one is good enough :)

One more question: would it make sense to use base.noValue object as a sentinel? Like this:
x.setComponentByPosition(0, noValue)
x['foo'] = noValue

To hint users that noValue is not a constant (which it is), we could make it callable (and returning self):
x.setComponentByPosition(0, noValue())
x['foo'] = noValue()

My concerns are:

We are adding an arguably duplicate entity (noValue vs DEFAULT_VALUE_SENTINEL)
We do not really want to set default value, but we want to set a "wireframe" object that could be populated afterwards (the whole concept of pyasn1 object being either an ASN.1 type or  ASN.1 type  instance is confusing). In that regards may be noValue is more obvious?

What do you think?
Sorry for being so nitpicking - I'm trying to make the whole thing less obscure to users... ;-\

Does this have the same result though? I'm thinking about something like:
Inner ::= SEQUENCE {
    ... }
Outer  ::=  SEQUENCE  {
    ... ,
    inner [1] Inner OPTIONAL  }

wouldn't outer['inner'] = noValue result in actually setting no value on that component, rather than an empty Inner?

Currently, instantiating pyasn1 scalar class with noValue makes it "ASN.1 type" meaning that such object can't participate in operations other than creating "ASN.1 type instances".
asn1_type_object = Integer(noValue)
asn1_type_object += 1                  # -> failure
asn1_type_instance_object = asn1_type_object.clone(123)
asn1_type_instance_object += 1  # -> 124

So if component has associated scalar type:
outer['scalar_foo'] = 123           # -> sets ASN.1 type instance object for component
outer['scalar_foo'] = noValue    # -> sets ASN.1 type object for component

you end up with foo being ASN.1 type after setting it to noValue.
However, if inner component is a constructed ASN.1 type, current implementation won't let you assigning noValue to it. But it accepts None sentinel to create a single (non-recursive) inner ASN.1 type object.
outer['constructed_foo'] = None      # -> sets ASN.1 type object for component
outer['constructed_foo'] = noValue  # -> currently, failure

So I propose to unify this and use noValue sentinel for both scalar and constructed types.
outer['constructed_foo'] = None      # -> sets ASN.1 type object for component ( would be legacy)
outer['constructed_foo'] = noValue  # -> sets ASN.1 type object for component

Does it make sense?

I've implemented the above approach in https://github.com/etingof/pyasn1/commit/fa78f1b0b3cd8c9628f8862ce1c19b7597a08be6.
I'd appreciate your feedback! Thanks!


Does the ONNX Variant allow variable input length

Hi Guys, thank you for the library. I am running into this error after I exported the onnx file with 16000 length. However the audio I wanna process can be of variable length.
Cell In[23], [line 18](vscode-notebook-cell:?execution_count=23&line=18)
     [15](vscode-notebook-cell:?execution_count=23&line=15) encoder_path = "melspec.onnx"
     [16](vscode-notebook-cell:?execution_count=23&line=16) encoder_session = ort.InferenceSession(encoder_path)
---> [18](vscode-notebook-cell:?execution_count=23&line=18) features = encoder_session.run(
     [19](vscode-notebook-cell:?execution_count=23&line=19)     None,
     [20](vscode-notebook-cell:?execution_count=23&line=20)         {
     [21](vscode-notebook-cell:?execution_count=23&line=21)             "input": input_signal.numpy(),
     [22](vscode-notebook-cell:?execution_count=23&line=22)         },
     [23](vscode-notebook-cell:?execution_count=23&line=23) )

File [/opt/homebrew/Caskroom/miniconda/base/envs/nemo/lib/python3.10/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py:220](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/Caskroom/miniconda/base/envs/nemo/lib/python3.10/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py:220), in Session.run(self, output_names, input_feed, run_options)
    [218](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/Caskroom/miniconda/base/envs/nemo/lib/python3.10/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py:218)     output_names = [output.name for output in self._outputs_meta]
    [219](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/Caskroom/miniconda/base/envs/nemo/lib/python3.10/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py:219) try:
--> [220](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/Caskroom/miniconda/base/envs/nemo/lib/python3.10/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py:220)     return self._sess.run(output_names, input_feed, run_options)
    [221](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/Caskroom/miniconda/base/envs/nemo/lib/python3.10/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py:221) except C.EPFail as err:
    [222](https://file+.vscode-resource.vscode-cdn.net/opt/homebrew/Caskroom/miniconda/base/envs/nemo/lib/python3.10/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py:222)     if self._enable_fallback:

InvalidArgument: [ONNXRuntimeError] : 2 : INVALID_ARGUMENT : Got invalid dimensions for input: input for the following indices
 index: 1 Got: 1536768 Expected: 16000
 Please fix either the inputs or the model.

Thank you for the reply, I finally fixed it by making both axes dynamic. I think this does need to be fixed in the save_onnx function most probably
torch.onnx.export(
    melspec,
    x,
    output_path,
    verbose=True,
    input_names=["input"],
    output_names=["output"],
    opset_version=17,
    dynamic_axes={
        "input": {
            0: "batch_size",
            1: "sequence_length",
        },  # Marking both axes as dynamic
        "output": {
            0: "batch_size"
        },
    },
)


Permit creation of long-lasting access tokens

I'd like to be able to create access tokens that last for a long time - in the region of months or years - in a similar way to Github's access tokens.
For example, when integrating a Travis build of your application with Cloud Foundry (like https://docs.travis-ci.com/user/deployment/cloudfoundry), it's necessary to enter your account password to have your Travis server authenticate to Cloud Foundry, and this is then stored in your .travis.yml file for later deployments. This password can be encrypted, but it has the password lifecycle... so if your password changes (say regular forced changes), your builds fail until you update your .travis.yml.

Nothing prevents you from creating clients that receive tokens with Integer.MAX_VALUE seconds expiration time. Example of uaa.yml config is
oauth:
  clients:
    my-client:
      access-token-validity: 1209600
      refresh-token-validity: 1209600
      authorities: zones.write,cloud_controller.admin
      authorized-grant-types: authorization_code,client_credentials,refresh_token
      autoapprove: true
      override: true
      redirect-uri: https://p-identity.identity.cf-app.com/dashboard/
      scope: openid
      secret: my-client-secret

Thanks for the comment @fhanik. Perhaps I'm confused about the relationship between the UAA and other parts of Cloud Foundry. How would I, as an application developer deploying apps to a Cloud Foundry installation, make use of that? Is there a cf command for it?

hi @ind1go
On Cloud Foundry (cf-release) the UAA job is there to handle authentication and authorization for all Cloud Foundry components.
For an application to leverage that, you have a couple of options

If your the administrator of the CF itself, then you have permissions to create these clients.
They can be created in the CF deployment manifest or using the uaac command (ruby gem called cf-uaac)

You could deploy your own UAA instance as an application
https://github.com/cloudfoundry/uaa#deploy-to-cloud-foundry


Fixed Home page font

#514
Fixed design and fonts in Home page.
Before:

After:

Can you please attach screenshots of the design on mobile? Is the responsiveness included in the update?


feat: upgrade tablab version from 1.0.0-alpha.4 to 1.0.0-alpha.5

Upgrades peer dependency on tablab
Installs tablab as a dev dependency
Updates tests for compatibility with the latest version of tablab

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
44

Relevant Lines:
44

💛  - Coveralls


Support for tensorboard

As someone that is not too experienced with Tensorflow and ML, it would be awesome if you could include support for TensorBoard with the repo.

@SophieMBerger there is actually a TensorBoard Callback passed during the training process have a look here.
You can have a look on the graph and the training logs with following terminal command:
tensorboard --logdir=<path to log dir>


Fix scss interpolation error

Fixes nolimits4web/swiper#4553
Currently the implementation of scss interpolation causes a build error. This PR updates the syntax to prevent that.

@nolimits4web Is there any chance I could get some eyes on this since this bug prevents CI from working? Hopefully this PR is simple enough that is doesn't need much of your time.

Thanks! But why it doesn't work for you and works for everyone else as far as I know. Even CodeSandbox works fine https://codesandbox.io/s/swiper-react-pagination-forked-c8rq0?file=/src/App.js . Maybe you have some sass/scss outdated?

Hi @nolimits4web! 👋🏻
I can't speak as to why we are the ones seeing this. The only thing I know to pass along is that this is the recommendation for using colors within string interpolation!
https://github.com/sass/sass/issues/1687
Apparently, (this was new info for me) this stems from the fact that colors in SCSS are objects! TIL!
The other question I have is there a potential issue that you'd forsee in using the updated syntax since it is the recommendation that the sass repo recommends?
They do present another alternative which is to put the keys in the source list within quotes, but I haven't looked at that list to see how the code is currently written.

Merged, thanks!


get_cell_autotile_coord returns the same value for two different cases

Godot version
3.3.2 mono official
System information
w10 64
Issue description
get_cell_autotile_coords returns Vector2.Zero in two different cases:

empty tile
the first tile of the atlas

How then will the user be able to distinguish between the two cases?
Steps to reproduce
...
Minimal reproduction project
No response

get_cell_autotile_coords returns Vector2.Zero in two different cases:
empty tile
the first tile of the atlas

How then will the user be able to distinguish between the two cases?

Before obtaining sub coords with tile_map.get_cell_autotile_coord(x, y) make sure that for var tile_id = tile_map.get_cell(x, y) these are true:

tile_id != TileMap.INVALID_CELL,
tile_map.tile_set.tile_get_tile_mode(tile_id) != TileSet.SINGLE_TILE.

what seems more logical to me would be that a negative vector would be returned for empty tile


Enable linter script with same profile as edgex-go

Linter script is currently broken.
Enable linting as per edgex-go.

@bnevis-i PR opened, could you help review? https://github.com/edgexfoundry-holding/device-onvif-camera/pull/55


Update get-access-to-and-back-up-a-former-user-s-data.md

clarify which admin center need to be used

issue #600

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@twernermsft @cmcatee-MSFT @aruhdam - PR has been copy edited and is ready for final review. This is based on issue #600. Looping in Cern and Madhura in this PR since I am not sure if Tom is still the doc owner for this document content.
Thank you.
cc: @kenwith @AndreaBarr

Change is not needed. Article is correct as written. We no longer use the "Office 365" or "Microsoft 365" designation when talking about the main admin center. Note that "admin center" is NOT capitalized.


Crash when loading / viewing an existing nodegraph into graph editor - related to swizzle node upgrade process

I try to load an existing nodegraph into graph editor.
Crashes when double clicking to open the node graph.
If I work around a crash in node display then I end up on a throw "cyclic dependency detection"
If I remove the swizzle nodes from the graph, everything is fine.
I suppose swizzle nodes upgrade process ends up in creating cycles ?

This sounds like a good catch, @jhubertubisoft!
Do you have an example MaterialX document that demonstrates this behavior?  We've tested our upgrade process with a wide variety of documents containing swizzle nodes, but it sounds like there's an edge case that was not covered in our tests, and an example would be very helpful.

A simpler way to test where the issue may reside is to run the mxvalidate.py script (in the Python Scripts folder) on the document which performs the upgrade and checks for validity. You can post your sample file here to look at as well.
If this does not pass then the upgrade logic sounds like the issue. Otherwise it could be an editor issue.

unpack_normal.zip
Here is one on the files I have trouble with.

This certainly looks like a bug somewhere in the swizzle upgrade code to me - comparing before/after snippets for the 1.38 -> 1.39 upgrade for this document look like this...
1.38
    <swizzle name="swizzle_float_vector4" type="vector4" xpos="4.492754" ypos="1.250000">
      <input name="in" type="float" nodename="constant_float" />
    </swizzle>

1.39
    <combine4 name="swizzle_float_vector4" type="vector4" xpos="4.492754" ypos="1.250000">
      <input name="in1" type="float" nodename="swizzle_float_vector4" output="outx" />
      <input name="in2" type="float" nodename="swizzle_float_vector4" output="outx" />
      <input name="in3" type="float" nodename="swizzle_float_vector4" output="outx" />
      <input name="in4" type="float" nodename="swizzle_float_vector4" output="outx" />
    </combine4

It looks like the generated combine4 node is connecting its inputs to itself - which certainly doesn't look quite right. I didn't get chance to look at the code itself yet.

Good catch, @ld-kerley, and that looks like a straight-up bug in our version upgrade logic.  This would definitely be worthwhile to address for 1.39.1, and I can also take a look if you don't get to it first.

I've written up a fix for this and am validating it now.  Thanks for posting this issue, @jhubertubisoft, and it is indeed a case we'd never encountered in our repository before.
The novel case was a swizzle node with no channels string set, causing it to act like a convert node, propagating a scalar value to all channels of the destination type.

The fix for this issue has been posted as #1945.

Excellent. Thanks everybody for the quick answer / fix. Have a nice day.


NPU Turbo Mode support

Is there currently a way to pass the NPU Turbo mode parameters to LLMPipeline()?

You may use one of the following codes to set the npu_turbo mode:
core.set_property("NPU", ov::intel_npu::turbo(true));
or
core.compile_model(ov_model, "NPU", {ov::intel_npu::turbo(true)});
For more information, please refer to npu_turbo%3B-,npu_turbo,-The%20turbo%20mode) in Supported Features and properties in NPU Device.

@addisokw based on this guide and as per info provided by Wan, I believe the proper way to set npu_turbo mode with LLMPipeline() is shown below. Please have a try on your side and see if it works, hope this helps.
plugin_config = { "NPU_TURBO": True }
pipeline_config = { "PREFILL_CONFIG": plugin_config, "GENERATE_CONFIG": plugin_config }
pipe = ov_genai.LLMPipeline(model_path, "NPU", pipeline_config)

This appears to have worked. Thanks!


add theme-lint, remove some gems

No immediate need to merge, but getting this started.
Why:  Move theme i18n linting to the package.json so folks don't need circle Ci testing / ruby tests.
Other notes:

Good candidate for hooks.  Run a linting task post build.

To do:

Make Circle Ci happy
Thorough check of Jekyll build for docs

Note: Add a command for npm run tests that will run lint and can be expanded to run more test in the future.

Related topic https://github.com/Shopify/slate-tools/issues/5. Might be better to integrate this into slate-tools directly?

@chrisberthe I'm down with the idea of integrating theme linting into one of the package.  It will be linting the dist/ directory.  Does slate-tools sounds like the best spot?  Or should it be a core slate command?
Maybe slate-tools and it can be an optional pre-deploy / post-build task?
Let's try it out as slate-tools, and if it works out we'll modify this PR accordingly.

@chrisberthe want to approve your own changes? 😜
They look good to me ✅


Create slides for CTSA: Text Analytics and Data Sharing WG Meeting (March 15)

I presented to this group around mid-2020 the planned architecture of the NLP Sandbox. This month presentation will focus on giving a review of the work performed by the NLP Sandbox Team so far with a focus on demonstrating the current implementation.
The slides prepared for this presentation will be reused for the S4 presentation that I will give in April on the NLP Sandbox.
Presentation duration: 20 minutes

The slides are available here (NLPSandbox.io Google folder)


[dv/adc_ctrl] Moving assertions to RTL or interface for reusability

Detailed discussion here:
https://github.com/lowRISC/opentitan/issues/11744

Triaged for adc_ctrl. I think this is not necessary for M2.5, so I'm labeling it https://github.com/lowRISC/opentitan/labels/Type%3AIcebox. @cindychip if you disagree, PLMK

At this stage - moving assertions to RTL is not going to be done as an ECO so should be considered for future release.
@moidx / @vogelpi / @andreaskurth

Can someone clarify which assertions this refers to? There are some assertions for the adc_ctrl fsm that are written in a module at https://github.com/lowRISC/opentitan/blob/master/hw/ip/adc_ctrl/dv/sva/adc_ctrl_fsm_sva.sv, but could be moved to an interface, which is simple. Other assertions are in the tb.sv file, and I imagine these are the assertions relevant to this issue.

I think it's probably both the assertions inside tb.sv as well as the ones inside adc_ctrl_fsm_sva.sv. But I seriously think we have more important things to do right now. Let's not bother about this now.


Add testnet support to binance store

https://python-binance.readthedocs.io/en/latest/overview.html#using-the-spot-futures-or-vanilla-options-testnet

Thanks @Fongeme
Note: The testnet only works for vanilla options, implemented in lib python-binance v0.7.11.
I will update it to the latest version soon.


[FEATURE] Implement SfColorPicker in SfProductCard

Describe how this feature will help us improve
This issue is blocked by https://github.com/DivanteLtd/storefront-ui/issues/851
With new design, we need to implement SfColorPicker in SfProductCard
Additional context
Mobile: https://www.figma.com/file/N0Ct95cSAoODNv7zYS01ng/Storefront-UI-Design-System?node-id=264%3A566
Desktop: https://www.figma.com/file/N0Ct95cSAoODNv7zYS01ng/Storefront-UI-Design-System?node-id=771%3A306

related #949

(Unblocked because #851 is implemented now (merged with PR #1012))


Autologin user with no password on select

Autlogin users with no password when selected. (implies that if the first user in the list has no password it will be logged in without being able to select another user)

I found where the error is but the code is such a mess that it can't be fixed :(


Redirect users to the game screen if the game was started

https://github.com/sopra-fs23-group-40/Client/commit/f28472cc1bd13301685f72588c925ad16943c336


Set a Static Proxy Port

I downloaded and started poking around this app recently.
I noticed that every time I open the app and click the proxy server icon, the port is different. Sometimes it's 8080, sometimes it's 49526, sometimes it's something else.

I use Bluestacks as my Android emulator, updating the proxy address every time I want to use GFChipCalc means I need to close Bluestacks, run a command in CMD to update the proxy settings, and relaunch the game. It's quite inconvenient.
Is there a way to tell GFChipCalc to use a specific port each time? (just like how GFLAlarm does it)

@dullahan8 If you're already using GFAlarm, it might be worth considering setting that up to output a json file that can be fed into GFChipCalc instead. In GFAlarm, go to Settings->File Save and check "Save Equip Info." You can find that output file in <gf_alarm_root>/Info/ and feed it into GFChipCalc via the "Open Inventory" button.

Oh very cool. This makes things easy thanks!


Predictive Analysis Demo Map uses unreleased service

e8effa285e7e4cfcab3b004a3cfc8e55   "Predictive Analysis Demo Map"  used unreleased content:
e7d140d8de9f4fe5a40a9887e866e50a   Country Boundaries Raster Image Service.
50c15cdd37cd49dcb5caa8e4f6ef4854 Country Boundaries Map Service
Owned by @ircampbell .
@nfeuerstein can you review and release?

@lfunkhouser I added these to demo review group.

@lfunkhouser I updated the summary and description for the map service and added to Demo Review.

released by DemoIntelligence

Verified.


Specify apache-beam==2.43.0

This is yet another version patch which further underscores the importance of moving recipe parsing out of the FastAPI container, which will be accomplished with #204.
I believe this reported failure https://github.com/pangeo-forge/C-iTRACE-feedstock/pull/5#issuecomment-1374381446 was caused by the apache-beam version mismatch (between parsing and worker containers) resolved by this PR.
The "better" solution is probably to fix this in pangeo-forge-runner but ideally this will be the last such patch that needs to go in before merging #204, at which point the need for this type of fix should basically disappear, so don't want to spend too much effort on what should be a very temporary bandaid solution.

merging https://github.com/pangeo-forge/pangeo-forge-orchestrator/pull/204, at which point the need for this type of fix should basically disappear

For future reference to anyone (myself included) reading this thread, the reason that #204 will fix this problem, is because recipe parsing will happen in a container inheriting from the same base image as is used for the Dataflow workers.
Though as I write this, I realize we'll need to be cautious that any runtime installations of pangeo-forge-runner and/or pangeo-forge-recipes into the parsing container, match those used for Dataflow workers, so no mismatch issues like this come up.

Hmm so this can't be patched quite so simply because this is irresolvable
pip install "pangeo-forge-runner==0.7.0" "apache-beam[gcp]==2.43.0"

I'll think of a better way to do this.

I'll think of a better way to do this.

Now installing from https://github.com/pangeo-forge/pangeo-forge-runner/pull/50, which pulls in recipes 0.9.4 and beam 2.43.0.


Define bool size as 8 bits instead of 16

When a user tries to use SGDK with a C++ project #define bool becomes illegal.
By default, m68k GCC defines bool with 8 bits size. If you match this size C++ users would use the library easily without recompiling it. Furthermore, 8 bits to store two values is enough for everyone, and also probably the code could be smaller.

I initially set it to u16 as usually that is the fastest type to use but for boolean operation i think it shouldn't make a big difference, We rarely use bool for arithmetic so that should be fine.
Updated bool to u8 now :)


[BUG] Uncaught ReferenceError: $ is not defined

txAdmin/FXServer versions: 5104
Describe the bug
Uncaught ReferenceError: $ is not defined
To Reproduce
Steps to reproduce the behavior:

Start the server
Login to server GUI using localhost:40120
Opening Console

Expected behavior
The web should work, but without jQuery It doesn't
Additional context
Server hosted on Win11 64bit.
Fixed the issue on my own fork: https://github.com/rubencosta13/txAdmin-master

Showing 322 changed files with 97,456 additions and 0 deletions.
Your repository is not even a fork, so hard to compare what you did

@tabarra.
Sorry, so the file that I edited was located on: https://github.com/rubencosta13/txAdmin-master/blob/master/web/basic/setup.html
To be precise, line: 17

There were more files.


No commulative vocabulary cheat sheet

Once upon a time I made myself a cheat sheet on paper I could refer to when doing exercises without having to have ten tabs open (as everything is introduced in different lessons), and now that I restarted the lessons I have no idea where that sheet is, which is proving especially annoying with higher sumti places.
...or rather, too annoying: Having to look something from a list is mildly annoying, just the right amount to prompt memorisation, going back a couple of lessons, querying la sutysisku (not to mention writing a report on github) OTOH completely interrupts learning flow. And simply guessing doesn't work because (from what I can tell) the lessons are randomised, you're not getting probed in weak spots.
Not sure how to best do it. Options include

Including a growing "old vocabulary" section ordered by word type and alphabetically in the existing vocabulary pages, to be opened in another tab
Pretty much the same but on the exercise page, always visible but you have to visually search/scroll
A "show definitions" button on the exercise page, then only displaying vocabulary used in that exercise. Don't give it a keyboard shortcut, make me move my arm to the mouse. (Side note: "Retry" could use a shortcut. Backspace?)


error: Cannot read property 'path' of undefined

Please see this issue: https://github.com/Nexus-Mods/Vortex/issues/6710
The problem is in this line (compiled): var gamePath = this._api.getState().settings.gameMode.discovered[__1.GAME_ID].path;
This is a fairly common mistake that happens to us as well: The "discovered" object stores manually configured settings for a game (e.g. if you manually set up tools). These settings don't get removed if a game is no longer discovered but the path gets set to undefined.
So if a game was once installed, got configured, then uninstalled you may have an entry for the game in discovered but the path is undefined.
The line further down you use that gamePath in path.join, which doesn't like undefined as a parameter.

I've removed the two places that should've caused this to happen on quite the scale it did, sorry about that :( v0.3.5 should be a bit safer.
There's still a lot of places using that same method for getting the install path so I will need to progressively add null-checking to them as I go through.

So I'm understanding this properly @TanninOne I should be able to replicate this by 'unmanaging' my game (i.e. delete all its profiles) and then trigger a deploy (or whatever starts the problematic code)?

No, afaict the only way to reproduce is by manually configuring something for the game (e.g. a tool on the dashboard) and then uninstalling the game (from steam).
That way the next time Vortex starts it will no longer have the game path set.

Alright thanks, I'll break out the Hyper-V and see if I can replicate it just so I can check any other spots I might have done this


Feature/swat 4136 - crash with GoogleMapSDK

Identify and solve crash

Think we can get rid of the extra files?

yes, we removed extra file and commit the same.

We create separate repo for test. link of repo is as follow


Column View

What feature or improvement do you think would benefit Files?
I can't seem to find this feature, but if it's there already, please point me in the right direction.
Love this app by the way...perfect for what I'm looking for. When in column view, can there be a setting that auto adjusts the width of the column to the longest filename OR else auto adjust AND shrink the folder contents so the app interface doesn't get any larger? Hope that makes sense. Thank you.
Requirements
I'm just the user! You're the dev!
Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.3527
Comments
No response

Thanks for using Files, the option is in the layout picker on the toolbar


Integration uses async_forward_entry_setup which is deprecated

Describe the bug
As per logs below, not a bug as such, but integration uses outdated HA APIs for platform setup as per below log entry.
Reproduction steps
Install and setup integration
Expected behaviour
N/A
ATCO Code
N/A
Integration Version
N/A
Home Assistant Version
2024.12
Fresh Install?
Not specified
Home Assistant Logs
2024-12-23 20:21:42.472 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'first_bus' calls async_forward_entry_setup for integration, first_bus with title: Bus Stop Norwich Road North and entry_id: e6f79ea72f2b14f16cbfe6ba216bd8d9, which is deprecated, await async_forward_entry_setups instead at custom_components/first_bus/__init__.py, line 14: hass.async_create_task(. This will stop working in Home Assistant 2025.6, please create a bug report at https://github.com/BottlecapDave/HomeAssistant-FirstBus/issues

Hello. I believe this was fixed a while ago in in v2.0.1. Therefore you should update the integration to the latest version to see this warning disappear.


Disconnected and reconnected smart card not detected in session

I use /sec:tls and /smartcard to forward a Yubikey to the remote session, and then use it to login to my Windows session. Assuming that the server has the policy "lock on smart card removal" and the "Smart Card Removal Policy" service running, removing the smartcard from the local machine automatically locks the session. However, the smartcard is not detected when reinserted and it's not possible to unlock the remote system again. The only choice is to reconnect.
Steps to reproduce the behavior:

Ensure the server has the "lock on smart card removal" policy and that the "Smart Card Removal Policy Service" is running
Connect using /sec:tls and /smartcard, and use the smartcard for authentication at WinLogon
Once authenticated, remove the smartcard from the local system and observe that the Windows session will lock
Reinsert the smartcard
The smartcard is not detected by the remote system, and can't be used to unlock again

Expected behavior
Reinserting the smartcard should allow unlocking the remote system without having to reconnect
Application details

FreeRDP version 3.0.0
/v:{server} /u:{username} /sec:tls /smartcard
OS version connecting to: Windows Server 2022

Environment

OS: macOS
Version/Distribution: Sonoma 14.1
Architecture: arm64

Additional context
Originally cited as here #8179; the issue as closed due to the main problem being fixed.

@akallabeth After testing, the current behaviour indeed seems to match mstsc. Sorry for the noise.


Document.index_new is producing the wrong url

Calling Document.index_new/4 or Document.index_new/5 produces the wrong url because it appends a double backslash (e.g. "/movies/movie//"). This can cause problems with AWS authentication since it affects the request signature.
Seems like a minor fix so I would be glad to make a PR if needed.

@walterbm happy to get a PR from you! :)

@werbitzky great! I created a PR #39 to fix the issue.

Fixed by https://github.com/werbitzky/elastix/pull/39


On OpenBSD cabs* are in libm, but no -lm in linker calls, giving linking errors

On OpenBSD 7.2 (arm64, Raspberry Pi 4), while running make, there is no -lm in linker calls, e.g.
gmake -j 4 -C ctest all
gmake[1]: Entering directory '/tmp/OpenBLAS-0.3.21/ctest'
gfortran -O2 -Wall -frecursive -fno-optimize-sibling-calls  -march=armv8-a -fno-tree-vectorize -L/usr/lib -lm -o xscblat1 c_sblat1.o c_sblas1.o ../libopenblas_armv8p-r0.3.21.a -lpthread -lgfortran -lpthread -lgfortran -L/usr/lib  -lc
cc -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION=\"0.3.21\" -march=armv8-a -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I.. -DADD_ -DCBLAS -o xdcblat1 c_dblat1c.o c_dblas1.o ../libopenblas_armv8p-r0.3.21.a -L/usr/lib  -lc  -lpthread -lpthread
cc -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION=\"0.3.21\" -march=armv8-a -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I.. -DADD_ -DCBLAS -o xccblat1 c_cblat1c.o c_cblas1.o ../libopenblas_armv8p-r0.3.21.a -L/usr/lib  -lc  -lpthread -lpthread
cc -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION=\"0.3.21\" -march=armv8-a -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I.. -DADD_ -DCBLAS -o xzcblat1 c_zblat1c.o c_zblas1.o ../libopenblas_armv8p-r0.3.21.a -L/usr/lib  -lc  -lpthread -lpthread
gfortran -O2 -Wall -frecursive -fno-optimize-sibling-calls  -march=armv8-a -fno-tree-vectorize -L/usr/lib -lm -o xscblat2 c_sblat2.o c_sblas2.o c_s2chke.o auxiliary.o c_xerbla.o constant.o ../libopenblas_armv8p-r0.3.21.a -lpthread -lgfortran -lpthread -lgfortran -L/usr/lib  -lc
cc -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION=\"0.3.21\" -march=armv8-a -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I.. -DADD_ -DCBLAS -o xdcblat2 c_dblat2c.o c_dblas2.o c_d2chke.o auxiliary.o c_xerbla.o constant.o ../libopenblas_armv8p-r0.3.21.a -L/usr/lib  -lc  -lpthread -lpthread
cc -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION=\"0.3.21\" -march=armv8-a -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I.. -DADD_ -DCBLAS -o xccblat2 c_cblat2c.o c_cblas2.o c_c2chke.o auxiliary.o c_xerbla.o constant.o ../libopenblas_armv8p-r0.3.21.a -L/usr/lib  -lc  -lpthread -lpthread
cc -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=4 -DMAX_PARALLEL_NUMBER=1 -DBUILD_SINGLE=1 -DBUILD_DOUBLE=1 -DBUILD_COMPLEX=1 -DBUILD_COMPLEX16=1 -DVERSION=\"0.3.21\" -march=armv8-a -UASMNAME -UASMFNAME -UNAME -UCNAME -UCHAR_NAME -UCHAR_CNAME -DASMNAME= -DASMFNAME=_ -DNAME=_ -DCNAME= -DCHAR_NAME=\"_\" -DCHAR_CNAME=\"\" -DNO_AFFINITY -I.. -DADD_ -DCBLAS -o xzcblat2 c_zblat2c.o c_zblas2.o c_z2chke.o auxiliary.o c_xerbla.o constant.o ../libopenblas_armv8p-r0.3.21.a -L/usr/lib  -lc  -lpthread -lpthread
gfortran -O2 -Wall -frecursive -fno-optimize-sibling-calls  -march=armv8-a -fno-tree-vectorize  -o xscblat3 c_sblat3.o c_sblas3.o c_s3chke.o auxiliary.o c_xerbla.o constant.o ../libopenblas_armv8p-r0.3.21.a -lpthread -lgfortran -lpthread -lgfortran -L/usr/lib  -lc
ld: error: undefined symbol: cabs
>>> referenced by c_zblat2c.c
>>>               c_zblat2c.o:(zmvch_)
>>> did you mean: fabs
>>> defined in: /usr/lib/libc.so.96.2
cc: error: linker command failed with exit code 1 (use -v to see invocation)
ld: error: undefined symbol: cabsf
>>> referenced by c_cblat2c.c
>>>               c_cblat2c.o:(cmvch_)
cc: error: linker command failed with exit code 1 (use -v to see invocation)

(there is also something weird with -L/usr/lib added for no good reason)
note that if I manually add -lm to the command line it passes:
pi$ cd ctest
pi$ gfortran -O2 -Wall -frecursive -fno-optimize-sibling-calls  -march=armv8-a -fno-tree-vectorize -o xscblat3 c_sblat3.o c_sblas3.o c_s3chke.o auxiliary.o c_xerbla.o constant.o ../libopenblas_armv8p-r0.3.21.a -lpthread -lgfortran -lpthread -lgfortran -lc -lm

Manually adding -lm to LDFLAGS does not work, as they get prepended like this:
gfortran -O2 -Wall -frecursive -fno-optimize-sibling-calls  -march=armv8-a -fno-tree-vectorize -L/usr/lib -lm -o xscblat3 c_sblat3.o c_sblas3.o c_s3chke.o auxiliary.o c_xerbla.o constant.o ../libopenblas_armv8p-r0.3.21.a -lpthread -lgfortran -lpthread -lgfortran -L/usr/lib  -lc

and have no effect.

Ah, we already have a  special case for BSD on ARM in Makefile.system, but it is currently for FreeBSD only. I will fix this tomorrow.

By the way, cmake build succeeds here, so it must be doing something better.

cmake better

Does it run any ctests?

On Thu, 15 Dec 2022, 06:36 Andrew, @.***> wrote:

cmake better
Does it run any ctests?

I don't know, the default cmake build is much less verbose than the
standard one.
If I wanted more feedback on cmake builds, I would have provided more docs.
E.g. I had to look up how to set up install prefix.
For ctesting - in the way the default build does it - I don't even know
where to look.
It doesn't seem to be the usual cmake thing- tests after build done, less
so - still I wouldn't know how to run them.
—

Reply to this email directly, view it on GitHub
https://github.com/xianyi/OpenBLAS/issues/3862#issuecomment-1352621069,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJXYHFVHP2WPGHTWVBU75DWNK363ANCNFSM6AAAAAAS62BXHQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

cmake build already adds -lm for all of FreeBSD/OpenBSD/NetBSD/DragonFly/Darwin regardless of architecture in script cmake/os.cmake. And yes, CMAKE is a bit harder to debug - though by setting CMAKE_VERBOSE_MAKEFILE=ON one at least gets more verbose information. Tests are built by default, but invoked only by calling the ctest program from the cmake suite in the build directory.

Tests are built by default

there are failures due to some tests simply missing somehow. (not built, or just not present - no idea)
No trace of these sin2 etc anywhere.
$ ctest
...
93% tests passed, 8 tests failed out of 115

Total Test time (real) =  14.92 sec

The following tests FAILED:
        105 - xscblat2 (Failed)
        106 - xscblat3 (Failed)
        108 - xdcblat2 (Failed)
        109 - xdcblat3 (Failed)
        111 - xccblat2 (Failed)
        112 - xccblat3 (Failed)
        114 - xzcblat2 (Failed)
        115 - xzcblat3 (Failed)
Errors while running CTest
Output from these tests are in: /tmp/OpenBLAS-0.3.21/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.

$ ctest --rerun-failed --output-on-failure
Test project /tmp/OpenBLAS-0.3.21/build
    Start 105: xscblat2
1/8 Test #105: xscblat2 .........................***Failed    0.01 sec
/tmp/OpenBLAS-0.3.21/build/ctest/test_cblas_helper.sh[1]: cannot open /tmp/OpenBLAS-0.3.21/ctest/sin2: No such file or directory

    Start 106: xscblat3
2/8 Test #106: xscblat3 .........................***Failed    0.01 sec
/tmp/OpenBLAS-0.3.21/build/ctest/test_cblas_helper.sh[1]: cannot open /tmp/OpenBLAS-0.3.21/ctest/sin3: No such file or directory

    Start 108: xdcblat2
3/8 Test #108: xdcblat2 .........................***Failed    0.01 sec
/tmp/OpenBLAS-0.3.21/build/ctest/test_cblas_helper.sh[1]: cannot open /tmp/OpenBLAS-0.3.21/ctest/din2: No such file or directory

    Start 109: xdcblat3
4/8 Test #109: xdcblat3 .........................***Failed    0.01 sec
/tmp/OpenBLAS-0.3.21/build/ctest/test_cblas_helper.sh[1]: cannot open /tmp/OpenBLAS-0.3.21/ctest/din3: No such file or directory

    Start 111: xccblat2
5/8 Test #111: xccblat2 .........................***Failed    0.01 sec
/tmp/OpenBLAS-0.3.21/build/ctest/test_cblas_helper.sh[1]: cannot open /tmp/OpenBLAS-0.3.21/ctest/cin2: No such file or directory

    Start 112: xccblat3
6/8 Test #112: xccblat3 .........................***Failed    0.01 sec
/tmp/OpenBLAS-0.3.21/build/ctest/test_cblas_helper.sh[1]: cannot open /tmp/OpenBLAS-0.3.21/ctest/cin3: No such file or directory

    Start 114: xzcblat2
7/8 Test #114: xzcblat2 .........................***Failed    0.01 sec
/tmp/OpenBLAS-0.3.21/build/ctest/test_cblas_helper.sh[1]: cannot open /tmp/OpenBLAS-0.3.21/ctest/zin2: No such file or directory

    Start 115: xzcblat3
8/8 Test #115: xzcblat3 .........................***Failed    0.01 sec
/tmp/OpenBLAS-0.3.21/build/ctest/test_cblas_helper.sh[1]: cannot open /tmp/OpenBLAS-0.3.21/ctest/zin3: No such file or directory

0% tests passed, 8 tests failed out of 8

cmake build already adds -lm for all of FreeBSD/OpenBSD/NetBSD/DragonFly/Darwin regardless of architecture

cmake is advertised as a great improvement over autoconf, yet it does not provide an analog of AC_SEARCH_LIBS 🤦🏽♂

sin2 et al. are the input files for the respective test, provided in the source tree.

Do you provide them in the release tarballs? (Cause I did my build from a release tarball)

Release tarballs are created automatically by github, so far I have not seen anything missing from them. (I download&reupload them after calculating their checksums, as github sometimes rebuilds these after unrelated changes, thereby changing timestamps and checksums)

Release tarballs are created automatically by github, so far I have not seen anything missing from them. (I download&reupload them after calculating their checksums, as github sometimes rebuilds these after unrelated changes, thereby changing timestamps and checksums)

https://github.com/xianyi/OpenBLAS/releases/download/v0.3.21/OpenBLAS-0.3.21.tar.gz
was not created by GitHub - perhaps by GitHub Actions or something like this, then it's not mutable, IMHO. Potentially mutable is e.g.
https://github.com/xianyi/OpenBLAS/archive/refs/tags/v0.3.21.tar.gz

Anyhow, after manually copying these missing files to build/ctest/, all tests run by ctest in build/ (the place I ran cmake in) pass.


increased circulating gamma-glutamyl transferase level

Add new term:
increased circulating gamma-glutamyl transferase level (a child of abnormal circulating enzyme level MP:0001570)
DEF: elevated blood level of the enzyme that catalyzes the transfer of gamma-glutamyl functional groups from molecules such as glutathione to an acceptor that may be an amino acid, a peptide or water (forming glutamate); GGT plays a key role in the gamma-glutamyl cycle, a pathway for the synthesis and degradation of glutathione as well as drug and xenobiotic detoxification; GGT is present in many organs throughout the body, with the highest concentrations found in liver, and elevated in the blood in most diseases that cause damage to the liver or bile ducts
SYN: increased circulating GGT level
SYN: increased circulating gamma-GT level
SYN: increased circulating gamma-glutamyl transpeptidase level
https://en.wikipedia.org/wiki/Gamma-glutamyltransferase, https://labtestsonline.org/tests/gamma-glutamyl-transferase-ggt
Annotations from J:166890

Added new term:
increased circulating gamma-glutamyl transferase level MP:0031114


Include external queries option

KICS comes with a wide set of queries, which is great.
I want to request a feature that would ease people to create more queries.
ATM, for someone to add query, files must be added to KICS directory hierarchy.
If the user want to upgrade KICS he needs to remember to copy/move all the files
he'd added to the new copy of KICS.
If we have an option for KICS to include external queries it would simply the process.
Allowing a person or an organization to keep their customization between upgrades/changes, or to manage them on their GIT.
Please notice that in case the user uses this option, we also want to suggest he'd contribute those queries to KICS, so everyone can enjoy them. Linking to the contribution page.

I'm adding here as a note that custom queries should enable the user to add external data. That will be accessed by import data: as suggested by @mukeshpilaniya in https://gitter.im/kics-io/community?at=6099011d20d4f02631b25f60
Reference for implementation:
https://github.com/open-policy-agent/opa/blob/82cca627647165804f8cf042cfd7f84dd13ddecc/rego/rego.go#L873
https://github.com/Checkmarx/kics/blob/master/pkg/engine/inspector.go#L136-L141
cc: @oribendetcx @nunoocx


RFC: Add section property to IGListSectionController

IGListKit should remove the -[IGListCollectionContext sectionForSectionController:] method from IGListCollectionContext and replace it with a section property on IGListSectionController.
Reasons

sectionForSectionController: has nothing to do with the collection displaying the section/list. This method alone requires that the IGListAdapter be the collectionContext object.
A section controller's actual section index cannot change without the IGListAdapter knowing, and at that point it would be a new section controller anyhow.
The property allows the collectionContext object to really be anything and not something that owns a mapping from section controller to an index.

The reasons that this method was originally added are all solved by adding a section property and as mentioned, that property is known at creation time.
Options

Add this as a property to the init method of IGListSectionController
Add this as @property (nonatomic, readwrite, assign) NSInteger index;

The init option is great because it means the property can be readonly, but it does mean that all subclasses have to be careful to include the property also.
The readwrite property is nice because then the IGListKit infra can own setting it. The downside is everyone knows that property can be written to. Maybe this is declared in IGListSectionController.h as readonly and in IGListSectionControllerInternal.h it is redeclared as readwrite?
Context
Speaking with @rnystrom in person about ways to break up implicit dependencies on UICollectionView and this method stood out as one that could be culled and would easily break up a hidden dependency on IGListAdapter.

Makes sense to me.

Maybe this is declared in IGListSectionController.h as readonly and in IGListSectionControllerInternal.h it is redeclared as readwrite?

Yep. This is what we already do for .isFirstSection and .isLastSection

Let's do this in 3.0

On board w/ this, ++ 3.0

Will do. Finally back from a pretty crazy week. Gonna start this week and should have PR pretty quickly.

How would this handle updating the index of all section controllers, if I inserted a section at index 0?

^^ I assumed that's always what this was about, just a convenience wrapper

The overall goal was to remove sectionForSectionController: from IGListCollectionContext in order to clean up the protocol to be only methods that go through to the backing list view. With that goal, the sectionForSectionController: method doesn't fit because it was going through to the sectionMap property of IGListAdapter which is not necessarily something that would be present on all IGListCollectionContext conforming objects that handle the presentation of a list.

How would this handle updating the index of all section controllers, if I inserted a section at index 0?

How would this handle updating the index of all section controllers, if I inserted a section at index 0?

In a similar fashion isFirstSection and isLastSection (https://github.com/Instagram/IGListKit/blob/c19379eeda6f254c0ba365dbe1110f4ffe37acf0/Source/IGListAdapter.m#L480-L481), but instead use the map to determine the section index right before calling didUpdateToItem: (https://github.com/Instagram/IGListKit/blob/c19379eeda6f254c0ba365dbe1110f4ffe37acf0/Source/IGListAdapter.m#L498-L500).

But if the object wasn't updated, then we wouldn't tell the section controller.

You could set the section index right up there where you set isFirstSection by adding a counting variable for the for-loop.

just to follow back up with this, i kind of melded both suggestions: move setting the isFirstSection and isLastSection into the IGListSectionMap object's update method since it already has all the context, and then within the iteration during the update set the sectionIndex. this effectively unifies the location as @Adlai-Holler suggested and removes the necessity for an extra indexing variable which could theoretically get out of sync with the canonical mapping.


trying to install the development setup

You can help me to understand, why i'm getting this error mensagens when i try to run this repo? i have made everything that was indicate on Development Setup section.
[149/229] Linking CXX executable Examples\Cpp\Cpp-Examples.exe
FAILED: Examples/Cpp/Cpp-Examples.exe
cmd.exe /C "cd . && C:\PROGRA~1\JETBRA~1\CLION2~1.3\bin\mingw\bin\G__~1.EXE -g  Examples/Cpp/CMakeFiles/Cpp-Examples.dir/main.cpp.obj -o Examples\Cpp\Cpp-Examples.exe -Wl,--out-implib,Examples\Cpp\libCpp-Examples.dll.a -Wl,--major-image-version,0,--minor-image-version,0  C:/Users/danig/Documents/GitHub/x-IMU3-Software/x-IMU3-API/Rust/target/release/ximu3.lib  -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 && cd ."
Warning: corrupt .drectve at end of def file
C:\Program Files\JetBrains\CLion 2023.1.3\bin\mingw\bin/ld.exe: Examples/Cpp/CMakeFiles/Cpp-Examples.dir/main.cpp.obj: in function `ximu3::DataLogger::getResult()':
C:/Users/danig/Documents/GitHub/x-IMU3-Software/x-IMU3-API/Cpp/DataLogger.hpp:25: undefined reference to `XIMU3_data_logger_get_result'
C:\Program Files\JetBrains\CLion 2023.1.3\bin\mingw\bin/ld.exe: Examples/Cpp/CMakeFiles/Cpp-Examples.dir/main.cpp.obj: in function `ximu3::NetworkAnnouncement::getResult()':
C:/Users/danig/Documents/GitHub/x-IMU3-Software/x-IMU3-API/Cpp/NetworkAnnouncement.hpp:26: undefined reference to `XIMU3_network_announcement_get_result'
C:\Program Files\JetBrains\CLion 2023.1.3\bin\mingw\bin/ld.exe: C:/Users/danig/Documents/GitHub/x-IMU3-Software/x-IMU3-API/Rust/target/release/ximu3.lib(ximu3-9d51039fde32745d.ximu3.0eefa5cf-cgu.6.rcgu.o):ximu3.0eefa5cf-cgu:(.xdata[$cppxdata$_ZN107_$LT$alloc..boxed..Box$LT$$u5b$I$u5d$$GT$$u20$as$u20$core..iter..traits..collect..FromIterator$LT$I$GT$$GT$9from_iter17he6755c612336f861E]+0x2c): undefined reference to `__CxxFrameHandler3'
C:\Program Files\JetBrains\CLion 2023.1.3\bin\mingw\bin/ld.exe: C:/Users/danig/Documents/GitHub/x-IMU3-Software/x-IMU3-API/Rust/target/release/ximu3.lib(ximu3-9d51039fde32745d.ximu3.0eefa5cf-cgu.6.rcgu.o):ximu3.0eefa5cf-cgu:(.xdata[$cppxdata$_ZN17crossbeam_channel7channel15Sender$LT$T$GT$4send17h1836224e2fcb7d55E]+0x10): undefined reference to `__CxxFrameHandler3'
C:\Program Files\JetBrains\CLion 2023.1.3\bin\mingw\bin/ld.exe: C:/Users/danig/Documents/GitHub/x-IMU3-Software/x-IMU3-API/Rust/target/release/ximu3.lib(ximu3-9d51039fde32745d.ximu3.0eefa5cf-cgu.6.rcgu.o):ximu3.0eefa5cf-cgu:(.xdata[$cppxdata$_ZN17crossbeam_channel7channel15Sender$LT$T$GT$4send17h62e50a5a41aefd23E]+0x14): undefined reference to `__CxxFrameHandler3'

I expect the issue is that you are using the latest master branch with the static library of the most recent release (v1.1.4).  The master branch is currently ahead of the release.  You need to either...

build the static library for the latest master branch yourself, or...
checkout the master branch at the most recent release.

When u say "build the static library for the latest master branch yourself", are u saying that i have to run cmake .  o the root directory ? because i have already did that and when all have finished and i try to build the same error message was prompt again
Sorry i kind of nub yet, so if u could detail more the step that i have to make to get the static library rebuild i will appreciate

The static library is the C:/Users/danig/Documents/GitHub/x-IMU3-Software/x-IMU3-API/Rust/target/release/ximu3.lib in the compiler error you shared.  I assumed that you copied this file from the v1.1.4 release assets as instructed by the following warning message, displayed when you run the root CMake for the first time.
CMake Warning at CMakeLists.txt:20 (message):
  Please provide the missing library file and then reload the CMake project.
  https://github.com/xioTechnologies/x-IMU3-Software/blob/main/x-IMU3-API/Rust/target/release/README.md

If this is what you did then the issue would be that the master branch is ahead of the release, and includes calls to functions that do not exist in the static library.  Hence the linker errors.  The solution would be to checkout the master branch at the commit corresponding to the release.
If you wish to instead build the library yourself then you must compile the Rust-API and then reload the CMake as per the instructions.  The Rust-API is separate from CMake.  We build it by clicking Build in CLion, but you can also build from the command line by running cargo build --release in the Rust directory.

Thanks for the help, rebuilding the ximu3 library made it possible to run the GUI, and now I have the executable running fine, I'll start to make changes to try to implement the movement for the 3d object


Jenkins slave is not coming up.

I am running jenkins master as mesos container using this project (https://github.com/rji/jenkins-standalone). Jenkins gets registered properly but when i am trying to setup a jenkins job, it is not getting assigned any slave. It just says - (pending—Waiting for next available executor) Not sure how to debug it. I am using Mesos v0.23.0. Mesos Master logs says:
I0903 17:18:31.912482 27456 master.cpp:2884] Processing DECLINE call for offers: [ 20150903-110359-1143087020-5050-27447-O31365 ] for framework 20150903-110359-1143087020-5050-27447-0003 (Jenkins Scheduler) at scheduler-6a8c9582-bd3b-47b7-a880-1d3eef857dec@<IP_ADDRESS>:50332
I0903 17:18:32.911624 27458 master.cpp:4290] Sending 1 offers to framework 20150903-110359-1143087020-5050-27447-0003 (Jenkins Scheduler) at scheduler-6a8c9582-bd3b-47b7-a880-1d3eef857dec@<IP_ADDRESS>:50332
I0903 17:18:32.913389 27460 master.cpp:2884] Processing DECLINE call for offers: [ 20150903-110359-1143087020-5050-27447-O31370 ] for framework 20150903-110359-1143087020-5050-27447-0003 (Jenkins Scheduler) at scheduler-6a8c9582-bd3b-47b7-a880-1d3eef857dec@<IP_ADDRESS>:50332
I0903 17:18:33.912559 27459 master.cpp:4290] Sending 2 offers to framework 20150903-110359-1143087020-5050-27447-0003 (Jenkins Scheduler) at scheduler-6a8c9582-bd3b-47b7-a880-1d3eef857dec@<IP_ADDRESS>:50332

And jenkins-master logs says:
ep 03, 2015 5:09:31 PM com.sonyericsson.hudson.plugins.metadata.contributors.JobContributorsController <init>
INFO: Started
Sep 03, 2015 5:09:31 PM jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
Sep 03, 2015 5:09:33 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Download metadata
Sep 03, 2015 5:09:33 PM org.jenkinsci.plugins.mesos.MesosCloud restartMesos
INFO: Mesos master changed, restarting the scheduler
Sep 03, 2015 5:09:33 PM org.jenkinsci.plugins.mesos.JenkinsScheduler <init>
INFO: JenkinsScheduler instantiated with jenkins http://test-host:31089/ and mesos zk://zookeeper-host:2181/mesos
Sep 03, 2015 5:09:33 PM org.jenkinsci.plugins.mesos.JenkinsScheduler$1 run
INFO: Initializing the Mesos driver with options
Framework Name: Jenkins Scheduler
Principal: jenkins
Checkpointing: true
Sep 03, 2015 5:09:33 PM org.jenkinsci.main.modules.sshd.SSHD start
INFO: Started SSHD at port 36018
Sep 03, 2015 5:09:33 PM org.jenkinsci.plugins.mesos.JenkinsScheduler registered
INFO: Framework registered! ID = 20150903-110359-1143087020-5050-27447-0003
Sep 03, 2015 5:09:33 PM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Sep 03, 2015 5:09:33 PM hudson.WebAppMain$3 run
INFO: Jenkins is fully up and running
Sep 03, 2015 5:09:36 PM hudson.model.UpdateSite updateData
INFO: Obtained the latest update center data file for UpdateSource default
Sep 03, 2015 5:09:36 PM hudson.model.DownloadService$Downloadable load
INFO: Obtained the updated data file for hudson.tasks.Maven.MavenInstaller
Sep 03, 2015 5:09:37 PM hudson.model.DownloadService$Downloadable load

There is no error in mesos slaves logs as well.

Mesos is sending Jenkins offers, but it's refusing them.
Maybe you are asking for more RAM/CPU than is available, or you have constraints that
can't be met?

@rasputnik Is there any specific port which is required to be announced by the slaves.

Didn't have to do anything specific on my setup (though I did use host networking rather than bridge on my docker config).
If you have intervening firewalls you could be onto something, but I'd start with checking your mesos layer as the first message looks a lot like jenkins is turning down offers.

@rasputnik Can you refer me which jenkins docker image you are using to bring the jenkins scheduler. There is no firewall which should prevent the communication between mesos-master and mesos-slaves.

I'm running jenkins standalone , the workers are in a docker container with

a jdk
maven
git

that's it.

@rasputnik Thank you for the help. I will debug it further to figure out the issue why jenkins is not accepting the mesos offers.

@rasputnik Thank you for all your help. I figured out that I wasn't setting the Label Expression while configuring the job. Thats why it wasn't running on mesos cluster.


Github Actions test that runs with the latest ESMValCore master

Python 3.6, 3.7 and 3.8 pass with the latest ESMValCore master picked up nightly, see results - we'll have to add Python 3.9 when we have a functional environment for ESMValTool too (we have it for Core)
EDIT: I have added Python 3.9 anyway, worst case it'll fail until we sort out the environment;
NOTE: the reason why there are so many commits is that it took me a day to realize that once you jump from one step to another, in GA, directory presence is not preserved (ie it always gets you back to the main test directory), so I tried with the new working-directory option they implemented, but that's total pish and very buggy :grin:

@bouweandela @nielsdrost could I get a review here chaps plese :beer:

@bouweandela @nielsdrost could I get a review here chaps plese :beer:

cheers @bouweandela :beer:

cheers @bouweandela :beer:


Different row view for unapproved vulnerabilities

Mark with a different color all rows of unapproved vulnerabilities or use another column with a label

added new column with vulns status


Switching modes make above line chomped

General information
Please report the following information as possible as you can:

Terminal program: WezTerm 20230513-073621-bdb173f1
Operating system: macOS Ventura 13.4 (22F66)
ZSH framework: zinit
ZSH version: zsh 5.9 (x86_64-apple-darwin21.3.0)
ZVM version: def0f842b27c0b51f2f059d976fa24f4856839f2

Basic examination

[x] I have read through the README page
[x] I have the latest version of zsh-vi-mode
[x] I have tested with another terminal program

Problem description

Switching modes make above line chomped.
Reproduction steps

Open a new interactive ZSH without configuration zsh -d -f -i.
Sourcing zsh-vi-mode.zsh and eval "$(starship init zsh)".
Quickly type <ESC>i in insert mode or normal mode.

Expected behavior
Switching modes should be smooth correctly without above line chomped.

This issue is related to #124 as well.


add another solution with spread operator

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason:   Your solution does not follow the instructions of the challenge.  The following line in the instructions state to use slice and splice, which means they both should be used.

Use the array methods slice and splice to copy each element of the first array into the second array, in order.

Thank you and happy coding.


DOC: fix typos

Closes #136

Codecov Report

Merging #137 (63104f5) into master (434a11c) will decrease coverage by 1.20%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #137      +/-   ##
==========================================
- Coverage   99.33%   98.12%   -1.21%
==========================================
  Files           5        4       -1
  Lines         600      588      -12
==========================================
- Hits          596      577      -19
- Misses          4       11       +7

Impacted Files
Coverage Δ

scikeras/utils/transformers.py
100.00% <ø> (ø)

scikeras/_utils.py
95.76% <0.00%> (-4.24%)
:arrow_down:

scikeras/wrappers.py
98.23% <0.00%> (-0.62%)
:arrow_down:

scikeras/__init__.py

Continue to review full report at Codecov.

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


desktop-file-utils: 0.23 -> 0.24

Motivation for this change
https://hpjansson.org/blag/2019/07/26/desktop-file-utils-0-24-released/
Things done

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

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

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

Add Budgie, Deepin, Enlightenment and Pantheon to list of registered desktop environments

Finally a release with this!!!!! Only happened years ago now.


add skeleton loader for projects page

Fixes Issue
Closes #149

Screenshots
Project page behaviour:
Before

After:

Sorry that i added these two more commits but my changes differed from #158 at that two lines and I just corrected them

@JakubChorzepa in my screen i'm seeing that skeleton image placeholder is having more height than the real project card. could you fix this issue? thanks 😊

We need to have consistent card sizes

I didn't set exact same height becoause actual setting fixed size will be only for this specific since the image on Projects.tsx has only specified width value but height i changing depending on image aspect ratio

I didn't set exact same height becoause actual setting fixed size will be only for this specific image since the image on Projects.tsx has only specified width value but height i changing depending on image aspect ratio

what's the solution for it @JakubChorzepa ?

I think would be setting fixed size on image wrapper on projekt card and setting image to have full width and height and to object fit on image. Then to copy this behavior to skeleton component

For me, color is much more bright.
Something like this is much nicer

https://flowbite.com/docs/components/skeleton/#card-placeholder

I think would be setting fixed size on image wrapper on project card and setting image to have full width and height and to object fit on image. Then to copy this behavior to skeleton component

yes make sense. could you try please it?

For me, color is much more bright.
Something like this is much nicer
https://flowbite.com/docs/components/skeleton/#card-placeholder

Yeah i used that page and i dont know why I changed that color 😄, will get it to this one

I think would be setting fixed size on image wrapper on project card and setting image to have full width and height and to object fit on image. Then to copy this behavior to skeleton component

yes make sense. could you try please it?

Will do that changes tomorrow, I mean on european time becoause I don't have access to computer rn

Sure ☑

Also, the number line appears to be excessive. With some padding, 4 or 5 lines will look ideal. What do you say?

Yeah 4 lines with padding will look better

@JakubChorzepa resolve conflicts

The light mode color is perfect, In Dark mode, I think still it little too bright.

Ok I'll change it


[OSF Institutions] Update SAML IdP Entity ID for Ferris - Prod Server [ENG-308]

Purpose
Finally, after verifying that both TestIdP-TestSP and TestIdP-ProdSP work, we are moving to to ProdIdP-ProdSP release in this PR.
Deployment Notes
Prod Server

[x] No domain/cert

CAS

[x] Update the first non-comment line below in institutions-auth.xsl for Ferris State University.

<!-- Ferris State University (FERRIS) -->
<xsl:when test="$idp='login.ferris.edu'">
    <id>ferris</id>
    <user>
        <username><xsl:value-of select="//attribute[@name='mail']/@value"/></username>
        <familyName><xsl:value-of select="//attribute[@name='sn']/@value"/></familyName>
        <givenName><xsl:value-of select="//attribute[@name='givenName']/@value"/></givenName>
        <fullname/>
        <middleNames/>
        <suffix/>
    </user>
</xsl:when>

Shibboleth

[x] Add the following attribute mapping to attribute-map.xml

<!-- Ferris State University -->
<Attribute name="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress" id="uid" />
<Attribute nameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" name="http://wso2.org/claims/emailaddress" id="mail" />
<Attribute nameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" name="http://wso2.org/claims/lastname" id="sn" />
<Attribute nameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" name="http://wso2.org/claims/givenname" id="givenName" />

[x] Add ferris-prod-metadata.xml JIRA LINK under conf/. The name and path for ferris-prod-metadata.xml may be different on prod settings.

[x] Add or modify the Ferris provider in shibboleth2.xml. The path may have a different name in prod settings.

<!-- Ferris State University (FERRIS) -->
<MetadataProvider type="XML" path="ferris-prod-metadata.xml" />

[ ] OSF: populate institutions Prod OSF

Test Servers

Q: Should I revert our test server to point back to your test IdP server again?
A: Your test server can still point to our prod server - I don't think it really matters

[x] So we keep test server as it is?

QA Notes
No
Documentation
No
Side Effects
No
Ticket
https://openscience.atlassian.net/browse/ENG-308

Cherry-picked in as 595f54266f5dd504fc8f55e67648e14cc71b2afe, consider this merged


Curl command to test secured service is failing

This is a Bug Report
Securing the Service section of k8 documentation has below code towards the end of the topic.
kubectl exec curl-deployment-1515033274-1410r -- curl https://my-nginx --cacert /etc/nginx/ssl/nginx.crt
...
<title>Welcome to nginx!</title>
...

But this fails without specifying '-k' parameter to curl.
Proposed Solution:
Add a '-k' parameter to curl command.
Page to Update:
https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/#securing-the-service

My take on this is that the current page is accurate about that task, but not clear.
I've suggested that the fix will be to split that task out into its own page, verify that the instructions work, and possibly tweak wording for clarity.
/priority backlog
/language en


android hardware back button closes app despite visible back button

Short description of the problem:
I have a normal tabs app. I call this.nav.rootNav.push() to navigate to a page outside the tab view. The new page shows the back button, like I would expect it to. If I press the hardware back button, the app closes instead of returning to the tab view.
Note: If I pressed the back button in the navbar, it would have returned to the tab view like normal.
What behavior are you expecting?
I would expect the hardware back button to go back.
Steps to reproduce:

Create app with tabs
Create new page
Navigate to new page from tab using this.nav.rootNav.push(NewPage)
Press the android hardware back button and app closes

Which Ionic Version?  2.x
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.1.1
Gulp version:  CLI version 3.9.1
Gulp local:   Local version 3.9.1
Ionic Framework Version: 2.0.0-beta.7
Ionic CLI Version: 2.0.0-beta.29
Ionic App Lib Version: 2.0.0-beta.16
ios-deploy version: 1.8.6
ios-sim version: 5.0.8
OS: Mac OS X El Capitan
Node Version: v5.5.0
Xcode version: Xcode 7.3 Build version 7D175

This should be fixed as of this commit: https://github.com/driftyco/ionic/commit/9f293e85496404364c08a8275c04f52d19dacea6
Thanks for creating this issue and pointing out the problem.


feat: add get_conventional_message fn to return the prepared message without committing

I'm working on a toy project to learn Rust. To support running it as a git hook, I need to be able to write the commit message to COMMIT_EDITMSG instead of actually creating a commit. This PR just adds a new function, get_conventional_message, that returns a string of what the commit message would be if you called conventional_commit with the same args.
I understand if this is out of the scope of this project, since it doesn't seem made to be a library.

@oknozor done! i'm not the best at documentation, so only a couple lines, but it's something? lol

@its-danny no worries, if people actually uses cocogitto as a library I will make an effort to document the crate a bit :)

@its-danny Your changes we be shipped on crates.io with the next release. I am actively working on this but it might take some time.
Meanwhile you can use :
cocogitto = { git = "https://github.com/oknozor/cocogitto", branch = "feat/add-bump-profiles " }


backdrop android full width bug after change orientation

backdrop android full width bug after change orientation v11.5.6

Please follow the issue template, thanks! :)


Unify JAX and Pallas unit test workflows to overcome the 20-workflow limit in CI

This is currently done in a sort of 'brute-force' way by stitching together the two test files and use a workflow input to conditionally run one of the tests. It is meant to be a quick solution to enable Pallas test in the new unified workflow.
A more systematic approach can be done in the future.

Just for documentation purpose, this is what the actual run looks like

So there will be two 'cancelled' jax/pallas test each spawning from the workflow from for the other software. For example, there will be a 'cancelled' pallas test as part of the jax test, and vice versa. These can be distinguished from the actual ones by checking if it contains the GPU model suffix.


Fix npe in TopKOperator when topKResult is null.

Description
Fix the possible npe in TopKOperator when the children device operators of TopKOperator all have no result.

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

Comparison is base (1a52ca3) 49.00% compared to head (55daa6f) 49.04%.
Report is 2 commits behind head on master.

Files
Patch %
Lines

.../db/queryengine/plan/analyze/TemplatedAnalyze.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master   #11627      +/-   ##
============================================
+ Coverage     49.00%   49.04%   +0.03%
- Complexity    24884    24900      +16
============================================
  Files          2810     2810
  Lines        176002   176005       +3
  Branches      21116    21116
============================================
+ Hits          86253    86322      +69
+ Misses        89749    89683      -66

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


Autocomplete failed to find definition

Type: Bug
I Created an Angular project and added a new interface called Appointment. When I type "App" and try to auto-complete and include it into the current file, nothing is suggested.
I would expect "Appointment" interface selection to be made available and upon selecting it, it is added to my code along with its import.

VS Code version: Code - Insiders 1.92.0-insider (34f8428e4b0e3bf822f4b9e8b4e3e0cab69ef2ce, 2024-07-04T05:48:51.656Z)
OS version: Linux x64 6.9.9-1-default
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 9 5900X 12-Core Processor (24 x 3998)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
62.72GB (45.11GB free)

Process Argv
. --crash-reporter-id 210d9130-10f4-4cf9-ad76-187d60112fd6

Screen Reader
no

VM
0%

DESKTOP_SESSION
plasma6

XDG_CURRENT_DESKTOP
KDE

XDG_SESSION_DESKTOP
KDE

XDG_SESSION_TYPE
x11

Extensions (51)

Extension
Author (truncated)
Version

Bookmarks
ale
13.5.0

ng-template
Ang
18.1.2

biome
bio
2.3.0

npm-intellisense
chr
1.4.5

path-intellisense
chr
2.9.0

vscode-markdownlint
Dav
0.55.0

vscode-eslint
dba
3.0.10

java-decompiler
dgi
0.0.4

java-debug
DSn
0.0.2

EditorConfig
Edi
0.16.4

rest-client
hum
0.25.1

ionic
Ion
1.89.0

java-properties
ith
0.0.2

plantuml
jeb
2.18.1

angular-file-changer
joh
0.0.4

vscode-peacock
joh
4.2.2

sort-typescript-imports
mic
1.4.1

vscode-docker
ms-
1.29.1

playwright
ms-
1.1.7

cpptools
ms-
1.21.3

js-debug-nightly
ms-
2024.7.2417

live-server
ms-
0.4.14

angular2-inline
nat
0.0.17

platformio-ide
pla
3.3.3

java-ide-pack
pve
1.2.1

java
red
1.32.0

vscode-commons
red
0.0.6

vscode-community-server-connector
red
0.26.16

vscode-rsp-ui
red
0.24.11

vscode-xml
red
0.27.1

vscode-yaml
red
1.15.0

markdown-preview-enhanced
shd
0.8.13

vscode-checkstyle
she
1.4.2

java-generate-setters-getters
soh
8.0.1

tailwind-fold
sti
0.2.0

sass-indented
syl
1.8.30

find-then-jump
tra
2.0.5

sort-lines
Tyr
1.11.0

vscode-boot-dev-pack
vmw
0.2.1

vscode-spring-boot
vmw
1.56.0

vscode-gradle
vsc
3.15.0

vscode-java-debug
vsc
0.58.0

vscode-java-dependency
vsc
0.24.0

vscode-java-pack
vsc
0.27.0

vscode-java-test
vsc
0.41.1

vscode-lombok
vsc
1.1.1

vscode-maven
vsc
0.44.0

vscode-spring-boot-dashboard
vsc
0.14.0

vscode-spring-initializr
vsc
0.11.2

markdown-pdf
yza
1.5.0

vscode-aspell
zap
0.1.4

(8 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vsc_aa:30263845
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
2i9eh265:30646982
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythonregdiag2:30926734
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfnew:30980852
pythonait:30973460
01bff139:31013167
a69g1124:31018687
dvdeprecation:31040973
dwnewjupyter:31046869
nb_pri_only:31057983
nativerepl1:31104042
refactort:31084545
pythonrstrctxt:31093868
1iic9185:31091668
flightc:31102344
wkspc-onlycs-t:31102394

I imported the Appointment interface and it still fails to autocomplete.

Realized I was typing in the type before the variable name.
If I type:
appointment: App

then do autocomplete, it will do what I was expecting.
Can I suggest an improvement, to provide a field name upon autocomplete completion?
If I type: "App" and then autocomplete, I get
appointment: Appointment;

You don't get auto imports in that case because you're typing out a new field name, not a type
Looks like it is working as expected in type contexts
Autocompleting App to appointment: Appointment is a better fit for an extension rather than core VS Code imo


Optimized WorldWind graphics are not set to CLAMP_TO_GROUND

They default to ABSOLUTE and not CLAMP_TO_GROUND

The placemark (dot) is already set to clampToGround. The problem is that there is no way to set its vertical origin.  I opened an issue in WW sdk:
https://github.com/NASAWorldWind/WebWorldWind/issues/120

Snapshot  showing the issue. The dot is floating on the air when the altitude mode is clampToGround.

The EMP map was reusing the imageOffset of the mil standard icon when switching to a dot placemark. Setting the dot image offset to .5, .5 fixed the issue. The issue was not in  WebWorldWind.

Test case:
Use the branch 2.6.0
Use WW.
Plot a mil std single point  (any). Zoom out until the icon switches to a dot. Tilt the map. The test is a success if the dot is on the terrain (not floating in mid air).

Reinetgrate

Merged into the release 2.6.0 branch. closing this issue.


XDG and shared-mime-info for .robot files

Hi, we'd like to add custom icons for .robot files in KDE Breeze icon set. However, this requires that the .robot files have their own shared-mime-info, such as text/robotframework or something similar.
However, one can't create an MIMEtype for an extension we don't control, of course.
Here's more information about shared-mime-info: https://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec/
If I understand this correctly, RF would need to install it's own MIMEtype during pip install, with xdg-mime. There are probably alternative ways too.
This would also fix an issue of .robot files being handled as .patch files by default because of the *** Header *** parts of the file.
Any interest in this? :smile:

Continues here https://github.com/robotframework/robotframework/issues/4746


feat(core): Now we can create decorators with additional metadata

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

import { Reflector } from '@venok/core';

export const ExampleDecorator = Reflector.createDecorator<string, string>({
    transform: options => options + options
});

What is the new behavior?
Now we can create decorators with multiple metadatas
import { Reflector } from '@venok/core';

export const Controller: Controller = Reflector.createDecorator<string | string[] | ControllerOptions, [string, any][]>(
  {
    type: "class",
    transform: (options) => {
      const defaultPath = "/";

      const [path, host, scopeOptions, versionOptions] = isUndefined(options)
        ? [defaultPath, undefined, undefined, undefined]
        : isString(options) || Array.isArray(options)
        ? [options, undefined, undefined, undefined]
        : [
            options!.path || defaultPath,
            options!.host,
            { scope: options!.scope, durable: options!.durable },
            Array.isArray(options.version) ? Array.from(new Set(options.version)) : options.version,
          ];

      return [
        [CONTROLLER_WATERMARK, true],
        [PATH_METADATA, path],
        [HOST_METADATA, host],
        [SCOPE_OPTIONS_METADATA, scopeOptions],
        [VERSION_METADATA, versionOptions],
      ];
    },
  },
);

Does this PR introduce a breaking change?

[x] Yes
[ ] No

After a night of reflection, I decided to put it in a separate method because of:

problems with typing
atypical behavior for some types
complexity of implementation (for the user)

Also for Reflector.createDecorator and Reflector.createDecoratorWithAdditionalMetadata the type field was added for options (for more details, see the docs).