Strange error

ancient@nickolaypc ~/load % git clone https://github.com/atom/atom.git
Cloning into 'atom'...
remote: Counting objects: 165240, done.
remote: Compressing objects: 100% (150/150), done.
remote: Total 165240 (delta 101), reused 10 (delta 10), pack-reused 165080
Receiving objects: 100% (165240/165240), 281.12 MiB | 6.66 MiB/s, done.
Resolving deltas: 100% (117457/117457), done.
git clone https://github.com/atom/atom.git  23.68s user 7.74s system 46% cpu 1:07.05 total
ancient@nickolaypc ~/load % cd atom
ancient@nickolaypc ~/load/atom (git)-[master] % script/build
Node:	v7.1.0
Npm:	v3.10.9
Installing script dependencies
Installing apm
../src/onig-string.cc: In constructor ‘OnigString::OnigString(v8::Local<v8::String>)’:
../src/onig-string.cc:25:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   hasMultiByteChars = (value->Length() != utf8_length_);
                        ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~
../deps/libgit2/deps/zlib/inflate.c: In function ‘inflateMark’:
../deps/libgit2/deps/zlib/inflate.c:1507:61: warning: left shift of negative value [-Wshift-negative-value]
     if (strm == Z_NULL || strm->state == Z_NULL) return -1L << 16;
                                                             ^~
child_process.js:145
    throw new TypeError('Incorrect value of args option');
    ^

TypeError: Incorrect value of args option
    at Object.exports.execFile (child_process.js:145:11)
    at Object.exports.exec (child_process.js:108:18)
    at Object.<anonymous> (/home/ancient/load/atom/apm/node_modules/atom-package-manager/script/postinstall.js:10:16)
    at Module._compile (module.js:573:32)
    at Object.Module._extensions..js (module.js:582:10)
    at Module.load (module.js:490:32)
    at tryModuleLoad (module.js:449:12)
    at Function.Module._load (module.js:441:3)
    at Module.runMain (module.js:607:10)
    at run (bootstrap_node.js:420:7)
npm ERR! Linux 4.8.7-1-MANJARO
npm ERR! argv "/usr/bin/node" "/home/ancient/load/atom/script/node_modules/.bin/npm" "--global-style" "--loglevel=error" "install"
npm ERR! node v7.1.0
npm ERR! npm  v3.10.5
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node script/postinstall.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node script/postinstall.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the atom-package-manager package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node script/postinstall.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs atom-package-manager
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls atom-package-manager
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ancient/load/atom/apm/npm-debug.log
npm ERR! code 1
child_process.js:511
    throw err;
    ^

Error: Command failed: /home/ancient/load/atom/script/node_modules/.bin/npm --global-style --loglevel=error install
../src/onig-string.cc: In constructor ‘OnigString::OnigString(v8::Local<v8::String>)’:
../src/onig-string.cc:25:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   hasMultiByteChars = (value->Length() != utf8_length_);
                        ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~
../deps/libgit2/deps/zlib/inflate.c: In function ‘inflateMark’:
../deps/libgit2/deps/zlib/inflate.c:1507:61: warning: left shift of negative value [-Wshift-negative-value]
     if (strm == Z_NULL || strm->state == Z_NULL) return -1L << 16;
                                                             ^~
child_process.js:145
    throw new TypeError('Incorrect value of args option');
    ^

TypeError: Incorrect value of args option
    at Object.exports.execFile (child_process.js:145:11)
    at Object.exports.exec (child_process.js:108:18)
    at Object.<anonymous> (/home/ancient/load/atom/apm/node_modules/atom-package-manager/script/postinstall.js:10:16)
    at Module._compile (module.js:573:32)
    at Object.Module._extensions..js (module.js:582:10)
    at Module.load (module.js:490:32)
    at tryModuleLoad (module.js:449:12)
    at Function.Module._load (module.js:441:3)
    at Module.runMain (module.js:607:10)
    at run (bootstrap_node.js:420:7)
npm ERR! Linux 4.8.7-1-MANJARO
npm ERR! argv "/usr/bin/node" "/home/ancient/load/atom/script/node_modules/.bin/npm" "--global-style" "--loglevel=error" "install"
npm ERR! node v7.1.0
npm ERR! npm  v3.10.5
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node script/postinstall.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node script/postinstall.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the atom-package-manager package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node script/postinstall.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs atom-package-manager
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls atom-package-manager
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ancient/load/atom/apm/npm-debug.log
npm ERR! code 1

    at checkExecSyncError (child_process.js:488:13)
    at Object.execFileSync (child_process.js:508:13)
    at module.exports (/home/ancient/load/atom/script/lib/install-apm.js:10:16)
    at Object.<anonymous> (/home/ancient/load/atom/script/bootstrap:27:1)
    at Module._compile (module.js:573:32)
    at Object.Module._extensions..js (module.js:582:10)
    at Module.load (module.js:490:32)
    at tryModuleLoad (module.js:449:12)
    at Function.Module._load (module.js:441:3)
    at Module.require (module.js:500:17)
script/build  200.41s user 16.72s system 81% cpu 4:26.86 total
1 ancient@nickolaypc ~/load/atom (git)-[master] %

Trying to build from AUR...

../deps/v8/src/identity-map.cc:5:30: fatal error: src/identity-map.h: No such file or directory
 #include "src/identity-map.h"
                              ^
compilation terminated.
make[1]: *** [deps/v8/tools/gyp/v8_base.target.mk:486: /tmp/yaourt-tmp-ancient/aur-nodejs-lts-boron/src/node-v6.9.1/out/Release/obj.target/v8_base/deps/v8/src/identity-map.o] Error 1
make[1]: Leaving directory '/tmp/yaourt-tmp-ancient/aur-nodejs-lts-boron/src/node-v6.9.1/out'
make: *** [Makefile:67: node] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Makepkg was unable to build nodejs-lts-boron.
==> Restart building nodejs-lts-boron ? [y/N]
==> -----------------------------------------
==>

@50Wliu @damieng

You need to build with Node v6 (or lower). We don't support v7 yet.
You might want to subscribe to https://github.com/atom/apm/pull/637 for Node.js v7 support.

Sorry, but how do i install node v6, if i am using pacman? I don't have any in official-repos nor AUR.

We don't officially support any Arch distributions of Atom, so I don't really know the exact answer to your question. For Arch we only really support building directly from official source distributions.
Regardless, check out nvm, which is a Node.js version manager. You can trivially install for example Node.js v6.9.1 via nvm install v6.9.1 (or similar).

@thomasjo, ok (i did both npm install and nvm install v6.9.1):
Wrote Dependencies Fingerprint: /home/ancient/load/atom/node_modules/.dependencies-fingerprint a3bf8553578811f6377fa84b89d511b70c89dad0
module.js:597
  return process.dlopen(module, path._makeLong(filename));
                 ^

Error: Module version mismatch. Expected 48, got 51.
  at Error (native)
  at Object.Module._extensions..node (module.js:597:18)
  at Module.load (/home/ancient/load/atom/script/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at tryModuleLoad (module.js:446:12)
  at Function.Module._load (module.js:438:3)
  at Module.require (module.js:497:17)
  at require (internal/module.js:20:19)
  at Object.<anonymous> (/home/ancient/load/atom/script/node_modules/runas/lib/runas.js:4:11)
  at Object.<anonymous> (/home/ancient/load/atom/script/node_modules/runas/lib/runas.js:47:4)
  at Module._compile (module.js:570:32)
  at Object.Module._extensions..js (module.js:579:10)
  at Module.load (/home/ancient/load/atom/script/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at tryModuleLoad (module.js:446:12)
  at Function.Module._load (module.js:438:3)
  at Module.require (module.js:497:17)
  at require (internal/module.js:20:19)
  at Object.<anonymous> (/home/ancient/load/atom/script/lib/install-application.js:5:15)
  at Module._compile (module.js:570:32)
  at Object.Module._extensions..js (module.js:579:10)
  at Module.load (/home/ancient/load/atom/script/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at tryModuleLoad (module.js:446:12)
  at Function.Module._load (module.js:438:3)
  at Module.require (module.js:497:17)
  at require (internal/module.js:20:19)
  at Object.<anonymous> (/home/ancient/load/atom/script/build:38:28)
  at Module._compile (module.js:570:32)
  at Object.Module._extensions..js (module.js:579:10)
  at Module.load (module.js:487:32)
  at tryModuleLoad (module.js:446:12)
  at Function.Module._load (module.js:438:3)
  at Module.runMain (module.js:604:10)
  at run (bootstrap_node.js:394:7)
  at startup (bootstrap_node.js:149:9)
  at bootstrap_node.js:509:3

script/build  14.51s user 0.74s system 109% cpu 13.915 total

@handicraftsman Atom just got accepted in the community repo in Arch. It is currently at v1.12.2 if you want to skip the AUR build.
https://www.archlinux.org/packages/community/x86_64/atom/

@yitzchak That package doesn't use the correct version of Electron and is a constant source of semi-random issues because of that.

@damieng That's too bad. Thanks for letting me know, though.

This time it built.
I am using i686 system :wink:

Gonna switch to XFCE soon


Events not registering on dynamically added objects

Describe the bug
Description:
I am experiencing an issue where events on dynamically added spheres are not being registered. In my setup, I have a box that, when clicked, adds a new sphere to the scene. While the initial spheres respond to click, pointer-enter, and pointer-leave events as expected, the newly added spheres do not trigger these events.
Sample Code:
<script setup lang="ts">
import { ref, reactive } from 'vue';
import { Sphere, Box, OrbitControls } from '@tresjs/cientos';

const addHotspot = () => {
  const newHotspot = reactive({
    position: [-2, 0, 0],
  });
  hotspots.push(newHotspot);
};

const hotspots = reactive([
  {
    position: [-2, 0, -2],
  },
  {
    position: [0, 0, -2],
  },
  {
    position: [2, 0, -2],
  },
]);

const grow = (event) => {
  event.object.scale.set(1.5, 1.5, 1.5);
};

const shrink = (event) => {
  event.object.scale.set(1, 1, 1);
};
</script>

<template>
  <OrbitControls />
  <TresPerspectiveCamera />
  <TresAmbientLight :args="['white', 0.5]" />
  <Box :position="[0, 0, 0]" :scale="[1, 1, 1]" @click="addHotspot">
    <TresMeshNormalMaterial />
  </Box>
  <Sphere
    :args="[0.5, 32, 32]"
    v-for="(hotspot, index) in hotspots"
    :position="hotspot.position"
    @click="console.log('click', index)"
    @pointer-enter="grow"
    @pointer-leave="shrink"
  >
    <TresMeshNormalMaterial />
  </Sphere>
</template>

Expected Behavior:
The click, pointer-enter, and pointer-leave events on the newly added spheres should function identically to those on the initial spheres, triggering the respective console logs and scaling effects.
Reproduction
https://stackblitz.com/edit/tresjs-minimal-reproduction-aa972s?file=src%2Fcomponents%2FTheExperience.vue,package-lock.json
Steps to reproduce
No response
System Info
No response
Used Package Manager
npm
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hey @RuthySheffi, thanks for the issue and reproduction.
Possibly related, there seems to be an issue with events not being added to v-if'd nodes:
Reproduction
https://stackblitz.com/edit/tresjs-minimal-reproduction-waagvz?file=src%2Fcomponents%2FTheExperience.vue
Expected
When visible, the on-screen mesh should log to the console when clicked.
Bug
When visible and clicked, the mesh does not log to the console.
Code
<!-- eslint-disable no-console -->
<script setup lang="ts">
import { shallowRef } from 'vue';
import { useLoop } from '@tresjs/core';

const tOrF = shallowRef(false);

useLoop().onBeforeRender(({ elapsed: _elapsed }) => {
  tOrF.value = !!(Math.floor(_elapsed) % 2);
});
</script>

<template>
  <TresMesh v-if="tOrF" @click="console.log">
    <TresSphereGeometry />
    <TresMeshNormalMaterial />
  </TresMesh>
</template>

Note that the code above logs to console if the v-if is removed.
Meta
@garrlker

Possibly related
#758


Add support for multi-segment entity set names separated with slash

Entity set name like "salesforce/project" is not currently supported.

can we please fix and incorporate this asap as I really need to have this working ideally today.

As I wrote you in the mail, it looks like the fix will require a bigger revision of the command formatter, so unfortunately it can't be done within so short time.


Feature - local libraries

Fixes #40

Coverage increased (+0.3%) to 78.783% when pulling be9811656ab92cdad4684e700e1b6d687d0e9354 on feature-local-libraries into 2bd32e2d3d4dd2399f1d5689f39af972a1bd6924 on master.

Coverage increased (+2.2%) to 80.683% when pulling fddd2b735d596369b492e8231affeedbfe9e445e on feature-local-libraries into 2bd32e2d3d4dd2399f1d5689f39af972a1bd6924 on master.

Coverage increased (+2.3%) to 80.753% when pulling 0ffa79935735157ef820cc302210035963b9b923 on feature-local-libraries into 2bd32e2d3d4dd2399f1d5689f39af972a1bd6924 on master.


Disable branch protection check

LLVM allows direct pushes but not force pushes. Just never try a force
push.

Stack from ghstack (oldest at bottom):

(to be filled)


Switch off force-ssl-redirect flag

@jwierzbo when it will be merged ? waiting for release like for christmas


CB-6844: Start freeipahealthagent after backups during install

Moved the starting of the freeipa healthagent to after backups.
Also minor unrelated change for logging.
This should not be merged until a new AMI for FreeIPA is published.

Need to reopen to get cert tracking

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Is this still relevant?

Yes im working on it now

These changes are going into another PR.


[Bug] Error in event enhanced incremental logic

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
There have been reported cases where the incremental logic in the event enhanced model results in failures due to the unique key not being unique. This results in a duplicate row detected during incremental run and thus a corresponding runtime failure.
Relevant error log or model output
Expected behavior
The incremental logic in the package works as expected.
Possible solution
No response
dbt Project configurations
No specific configs added
Package versions
Latest
What database are you using dbt with?
postgres, redshift, snowflake, bigquery, databricks
How are you running this dbt package?
Fivetran Quickstart Data Model
dbt Version
Latest
Additional Context
No response
Are you willing to open a PR to help address this issue?

[ ] Yes.
[ ] Yes, but I will need assistance.
[ ] No.

@fivetran-joemarkiewicz The two sources that flow into amplitude__event_enhanced each have multi-field primary keys, so I believe we need to capture all of them since event_type is effectively left joined onto event.
In the stg_amplitude__event_type model, we create  unique_event_type_id but don't use it downstream. Adding it to this line in place of event_day should create a unique key for merging on.
I tested this out with our test data, and while it ran on the incremental run successfully, it is very limited and I was not able to recreate the original issue. This might be a good candidate for an alpha release.

Closing this issue as it's been addressed in the above PR.


Check version changes for triggering releases

Description
Add the GitHub action Version Check to trigger release for the cli and schematics package conditionally if the version changed in the package.json. I've also removed the dependency via needs between both packages.
Related Issue
#59
Motivation and Context
Currently, the release of the cli package has a dependency with the schematics package via needs command on the action. This means that the release of the cli will only be done if the release of the schematics is successful. In our last release we only changed the version of the cli package, and the schematics action did still try to release again using the same version, getting an error. This, in turn, it's preventing the release of the cli package, blocking the release workflow.
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Wonderful @neodmy !! Thanks for the improvement. I only have one question before approving:
As we have removed the needs attribute from publish-npm-cuckoojs-cli to wait for publish-npm-cuckoojs-schematics, I wonder if it may run in parallel. This could be wrong when there is an update on the schematics package that needs to be published before publishing the cli package (the problem we had when we published the packages for the first time).

You are right. Apparently the GitHub jobs run in parallel by default. It would only happen when releasing a new version for both packages with the same action though, providing the schematics' dependency on the cli package has also been upgraded.
I guess we need to keep that dependency on the cli action


Add Auto Release Workflow

Description
Add Auto Release Workflow
Issues Resolved
https://github.com/opensearch-project/k-NN/issues/760
Check List

[x] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Is this something we need to have working identically for all plugins? Do we need a campaign in https://github.com/opensearch-project/opensearch-plugins?

We already have a campaign for this https://github.com/opensearch-project/opensearch-plugins/issues/201


Convert overworld from 3D to 2D: Camera

Camera should follow the player
Camera should zoom in during conversations
Camera should zoom out if the player runs away from a conversation

I've split the 'camera zooming' functionality into #352.
This functionality is actually really, really hard in 2D. There is no concept of a "camera target" and no concept of "switching cameras". It seems like more of a 'nice-to-have' than anything essential.


KAFKA-10566: Fix erroneous config usage warnings

Fix warn log messages caused by making HashMap copies of configs prior to using. This is not an ideal solution, but because the Maps are passed through Configurable.configure(Map) it's not possible to use another type (such as the RecordingMap type) directly.

@rajinisivaram @omkreddy perhaps one of you could review?

@rajinisivaram @omkreddy did you have any thoughts about this? What I've done here isn't exactly pretty, but it was the simplest thing I could think of which would remove the erroneous warnings.
As an aside: I spent quite some time looking at how the AbstractConfig tracks usage in order to log about unknown config. TBH it's a pattern which, as here, doesn't always work well, because what's passed to Configrable is a Map so it's easy for people to forget that they need to track usage if they need to configure a plugin with something other than AbstractConfig.values().
In some ways it would be better to be able to validate config parameters at the point of creating the AbstractConfig, but that would require lots of public API change to be able to build the overall ConfigDef (including all the plugins defined in the "root config"). As well as addressing the logging of unknown configs in a less flaky way, that would open the door for describeConfigs to be able to describe configs for plugins as well as the broker, for example. But it would be a lot of work if those were the only benefits. Thoughts?

@rajinisivaram @omkreddy @ijuma @mjsax please could someone take a look at this fix?

Maybe @chia7712, @dajac or @mimaison could take a look at this?

Is it similar to https://issues.apache.org/jira/browse/KAFKA-10090?

@chia7712 I think there's overlap, but I think this one removes additional warnings because it also propagates usage tracking in SslFactory. (It also provides a non-public abstraction to as least make it easier to identify the places where we end up doing this usage tracking, which might be useful should we ever figure out a better way of doing this).


Music glossary

It would be nice to have a search-engine-friendly glossary of music-related terms on the website

I have started this. The glossary needs to be expanded, though.


Downstream setting problem

Sorry for the simple question, I'm just wondering when following the instruction to run the downstream task, whether the result directly comparable to the result reported in SUPERB benchmark(e.g. strictly use the same train-val-dev split, downstream configuration...), or there may be some subtle difference?

Hi!
Thank you for the interest. It will be directly comparable since it is exactly the same code we used to run the SUPERB experiment without any refactoring.
Sincerely,
Leo.

Hi,
The instructions and configs are identical to the SUPERB benchmark (i.e. strictly using the same train-val-dev split, downstream configuration... etc.)
However, you may want to explore and tune the learning rate (since every "upstream and downstream pair" may prefer different learning rates). For example, in our SUPERB paper, for every upstream model, we explore five different learning rates for each downstream task. Thus, if you are getting slightly different results than the SUPERB numbers, you are most likely using a different learning rate than us.
Please let us know if you have any further problems reproducing our results. I will close this issue for now, if you have any questions you can re-open it.
Thanks,
Andy


Update to 6.1.2

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


help

在吗 ？代码运行出错  ValueError: An operation has None for gradient. Please make sure that all of your ops have a gradient defined (i.e. are differentiable). Common ops without gradient: K.argmax, K.round, K.eval.

Please write your execution environment.
Did you use the Dockerfile provided in the repository?


HttpClientBackend: fixed binary subparts' headers of a multipart request

Before submitting pull request:

[x] Check if the project compiles by running sbt compile
[x] Verify docs compilation by running sbt compileDocs
[x] Check if tests pass by running sbt test
[x] Format code by running sbt scalafmt

This fixes https://github.com/softwaremill/sttp/issues/773
Also depends on fixes to sttp-model https://github.com/softwaremill/sttp-model/pull/45

Released in 3.0.0-RC10, thanks!


Update ground vehicle to glTF 2.0 final.

This gets rid of the old glTF 1.0 vehicle, and updates the 2.0 version to one generated with the latest Khronos Blender exporter.  The new model now uses the standard glTF 2.0 forward vector of +Z.  Also the wheels are parented to the body now.

@emackey, thanks for the pull request! Maintainers, we have a signed CLA from @emackey, so you can review this at any time.
:warning: I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:


Increase test coverage

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.89%. Comparing base (7ca7410) to head (5bf035f).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   88.61%   94.89%   +6.28%
==========================================
  Files           5        5
  Lines         202      196       -6
==========================================
+ Hits          179      186       +7
+ Misses         23       10      -13

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


Remove a hack to change linkage from public_external to shared.

The linkage change let the compiler generate code for public functions which are imported from the stdlib - and are also available in the swiftCore library.
This got worse since we use public linkage for @_versioned internal functions in the stdlib.
Getting rid of the linkage change reduces code size a lot: up to 40% for some projects.
I didn’t see any significant impact on benchmark performance.

@swift-ci Please smoke test and merge

This is safe because we always copy a function before we specialize it, right?

(In the resilient world we won't be able to do this, since the implementation in the stdlib could change.)

Talked with Jordan offline. For now this change is safe.

@eeckstein Should we at least add a TODO or FIXME comment in the source code regarding resilience?

@swiftix I'll file a radar. The things what we have to do are not in the source file.


Feat/update guidance lib

Description
llama-index library wasn't updated with the newer version of guidance lib. We updated the codes and now it can run with guidance==0.1.10.
Fixes # (issue)
https://github.com/run-llama/llama_index/issues/9797
Type of Change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

I ran the make format; make lint just now and fixed any lint issues with it.


Migration: Async function returns shouldn't be marked uncheckable

Future<int/*1*/> f(int/*2*/ x) async => x;

At the moment, we create an uncheckable edge from int/*2*/ to int/*1*/. This is not correct. Clearly we can check this edge. As long as this bug exists, its possible to make 2 nullable just because 1 is marked exact nullable.
I'm not sure if its realistically possible if even at all likely, for node 1 to become marked exact nullable anyway.
Other concerns are what might happen when non-null intents get involved.

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


CLI Program

It would be cool to have something similar to create-react-app, that gives you a default app...
Possible Solutions

create a yeoman generator
create a bunch of filesystem stuff

Other Notes

use inquirer to toggle options on and off
offer webpack / rollup / budo ?

done and done: https://github.com/JRJurman/tram-one-express


[ISSUE #710]🚀Support pull message result handle-3🎨

(cherry picked from commit 7d2662a0e6a4fa8265f3fca762d96f63ff05a3a7)

Which Issue(s) This PR Fixes(Closes)

Fixes #710
Brief Description

How Did You Test This Change?

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥


How to add react-bootstrap via npm?

So I'm trying to add the react-bootstrap library and I'm unhappy with the solutions I've seen so far. I've read https://github.com/mxstbr/react-boilerplate/issues/238 but I would really prefer to use npm to install bootstrap-css-only rather than downloading bootstrap.min.css manually into a styles folder.  Also I'm looking for some guidance for how to best use the (global) react-bootstrap CSS with CSS Modules and PostCSS and Webpack.  I see that there is a bootstrap-css npm package (https://www.npmjs.com/package/bootstrap-css) but I'd rather use the original global CSS.  I've seen many different articles addressing these things separately but nothing within the context of react-boilerplate.  It would be super helpful for me to see a clear walkthrough on that.
I tried to add bootstrap-css-only and react-bootstrap as a dependencies but I got this error when running npm install:
                      Asset     Size  Chunks             Chunk Names
reactBoilerplateDeps.dll.js  2.86 MB       0  [emitted]  reactBoilerplateDeps
chunk    {0} reactBoilerplateDeps.dll.js (reactBoilerplateDeps) 2.53 MB [rendered]
  [887] dll reactBoilerplateDeps 12 bytes {0} [built] [1 error]
     + 887 hidden modules

ERROR in ./~/bootstrap-css-only/css/bootstrap.min.css
Module parse failed: /home/.../node_modules/bootstrap-css-only/css/bootstrap.min.css Unexpected token (5:83)
You may need an appropriate loader to handle this file type.

Did you see #595. I believe it addresses a similar problem.

Thanks gihrig, that was close to what I'm looking for.  Here is how I ended up solving the error.
package.json
  "dllPlugin": {
    ...
    "exclude": [
      "bootstrap-css-only",
      ...
    ],
    ...
  },
  "dependencies": {
    ...
    "bootstrap-css-only": "3.3.6",
    ...
  },

internals/config.js
const ReactBoilerplate = {
  /* ... */
  dllPlugin: {
    defaults: {
      /* ... */
      exclude: [
        'bootstrap-css-only',
        /* ... */
      ],

      /* ... */
};

As far as integration between the global css of bootstrap and the css-modules / PostCSS local css, there appears to be two options.  Either you can use :global in the css module to affect/override global styles, or you can create local styles to override the global ones and use classnames to combine both into one element, like so:
import styles from './styles.css';
import classNames from 'classnames';

Seems like an entry to docs/css explaining the use of global css libraries in general would be a welcome addition.
A PR would be awesome!
@mxstbr Agree?

Agree!

@bobkocisko Would you consider writing this up as a docs/css/recipe and opening a PR?
It would be nice if it could be general in nature for adding any similar global library. It would be fine to use react-bootstrap as the example.

Ok I'll try to get to it this weekend.
On Thu, Jul 21, 2016 at 12:40 AM, Glen Ihrig<EMAIL_ADDRESS>wrote:

@bobkocisko https://github.com/bobkocisko Would you consider writing
this up as a docs/css/recipe and opening a PR?
It would be nice if it could be general in nature for adding any similar
global library. It would be fine to use react-bootstrap as the example.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mxstbr/react-boilerplate/issues/741#issuecomment-234155194,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACoMHkhT204bs6Pex4FYfhA5DOAhGzwjks5qXvhPgaJpZM4JO4d6
.

https://github.com/mxstbr/react-boilerplate/pull/777

Pull request, take 2: https://github.com/mxstbr/react-boilerplate/pull/802


Throughput is only respected on table creation

Closes #311

Coverage increased (+0.1%) to 82.395% when pulling f98f34e65103d8320d8da6f061339b867029eb4e on fishcharlie:throughputdocs into d25b045050f9a54bf646fb7f89c531a6e21e16fa on automategreen:master.

Coverage increased (+0.1%) to 82.395% when pulling f98f34e65103d8320d8da6f061339b867029eb4e on fishcharlie:throughputdocs into d25b045050f9a54bf646fb7f89c531a6e21e16fa on automategreen:master.


FMW Infra

Hello,
I was able to successfully run the chef-solo client and have a weblogic instance running with the generic weblogic installer (fmw_<IP_ADDRESS>.0_wls.jar).
My question is, would the cookbooks be able to run with the Fusion Middleware Infrastructure (fmw_<IP_ADDRESS>.0_infrastructure.jar) as well?

Nice,
indeed see this readme for some fmw examples
or change your current install_type to infra instead of the default wls
  "fmw_wls": {
    "source_file":         "/software/fmw_<IP_ADDRESS>.0_infrastructure.jar",
    "install_type":        "infra"  <------
  }

Thank you very much Edwin! It worked wonderfully!


NY Times data

Not sure if this is incorporated in the scraper dataset, but NY Times is publishing their data on github.  Maybe common source, but just thought i'd bring it up.
https://github.com/nytimes/covid-19-data

Yes, it's already in the scraper and cross-checked/de-duped against everything.
https://coronadatascraper.com/#crosscheck
https://coronadatascraper.com/#sources


wasm: fix getHeaderMapValue() in case of early client disconnect.

Previously, getHeaderMapValuei() would incorrectly return BadArgument
when called in the access log phase after an early client disconnect,
because the code assumed that a HeaderMap can point to a nullptr only
when called from a callback in which given map is not available.
Fixes proxy-wasm/proxy-wasm-rust-sdk#82.
Signed-off-by: Piotr Sikora<EMAIL_ADDRESS>

/backport


Fix some issues related to wrong Browser.pointer value

Close #6977.

Introduce Browser.iOS property.

// https://stackoverflow.com/questions/57765958/how-to-detect-ipad-and-ipad-os-version-in-ios-13-and-up
// @property iOS: Boolean; `true` for iPhone/iPad.
export var iOS = /iPad|iPhone|iPod/.test(navigator.platform) ||
		(navigator.platform === 'MacIntel' && navigator.maxTouchPoints > 1);

Revert #6855, and fix #6817 in more local way.

Fix #6988, fix #6973, fix #6896, and may be some more similar issues.

This is not ultimate solution, as there are unaddressed issues #6777 (possibly fixable by #5881/#6815), #6865, #6980, #7011.
Test page: https://gist.githack.com/johnd0e/c7b44648c5b365cd9b2a9662a23180e0/raw/test-fix-pointer.html
This is early WIP, created to continue discussion.
Feedback is appreciated.

@ reviewers
Before I proceed to thorough testing please give me a hint that I'm on right way with this:

[ ] 345618e is not actually important here, should I drop it?
[ ] 035314e is controversial, and I'm not completely sure about it yet.
[ ] In af7d241 I am relying on Browser.iOS, but in c33c31c for same purpose I use Browser.safari.
In fact I believe that both cases should use same property, but still haven't decided which.
So do we really need special Browser.iOS (from 77d557c), or better stick to less specific Browser.safari?

@johnd0e hey, thanks so much for working on this! Sorry for not getting back to you earlier.

[ ]  345618e is not actually important here, should I drop it?

Yes, it's not a hot path so we don't have to cache the user agent.

[ ]  035314e is controversial, and I'm not completely sure about it yet.

I would prefer for tap hacks to be added only when they are necessary — there seem to be no use case for forcing them on non-supported platforms, that should be a logic we handle on our side. It's only there to disable it just in case, although I don't really recall why this was introduced as an option and if anyone actually uses it.

[ ]  In af7d241 I am relying on Browser.iOS, but in c33c31c for same purpose I use Browser.safari.
In fact I believe that both cases should use same property, but still haven't decided which.
So do we really need special Browser.iOS (from 77d557c), or better stick to less specific Browser.safari? (I am tending to the latter)

If the browser behavior is the same on desktop and iOS Safari, I would use the more broad check and not introduce a new one.

[ ]  Last commit (0a42baf) should be discussed in #7012.
Perhaps later I will separate it in own PR, after #7011 get clearer.

Did it get clearer? Anyway, if it seems like a reasonable fix, I would trust you on this one — you obviously spent a lot more thought and research on pointer behavior than I am.

It's only there to disable it just in case

Well, good point. But then bad name and documentation.
Anyway I'm removing that change here (leaving it on #6980).

If the browser behavior is the same on desktop and iOS Safari, I would use the more broad check and not introduce a new one.

AFAIK, there is no such device yet (desktop Safari + touchscreen).
I believe that we should start with Browser.safari, and change that later (if it will be needed).

Did it get clearer?

Well, nobody commented neither #7011 nor #7012 yet.

Test page: https://gist.githack.com/johnd0e/c7b44648c5b365cd9b2a9662a23180e0/raw/test-fix-pointer.html


Label not showing in iPhone X/XR/XS

What kind of Issue is this?
Bug Report
Actual behavior
Label not showing in FullTab component in iPhone X + XR + XS
Expected behavior
See the label under the icon
Additional resources
XR simulator:

8 Plus simulator:

Environment

software
version

react-native-material-bottom-navigation
1.0.2

react-native or expo
0.58.3

node
10.13.0

npm or yarn
6.4.1

Please provide a reproductible expo snack so I can check this.

https://snack.expo.io/Hko4mMD44
example without icons

Removing the height solved my problem! Thanks so much


[Incompatibility] Change in actions/runner-images breaks devcontainers if image has user with UID 1001 or group with GID 999

This is not a bug, but a recently introduced incompatibility between the provided devcontainer images and using them on github actions. I'm filing it hoping it will help others identify the problem they're experiencing. Feel free to close this issue.
I'm using devcontainer images to provide turnkey project boilerplates for coding exercises in rradczewski/kata-bootstraps. Recently, builds started to fail with permission errors (see https://github.com/rradczewski/kata-bootstraps/actions/runs/6025462340).
The issue seems to arise from ghcr.io/devcontainers/features/node:1 creating a system group that will be assigned GID 999, which, after a recent update to the GHA image ubuntu-latest, will coincidentally be the GID the GHA user is running with (uid=1001(runner) gid=999(docker) groups=999(docker),4(adm),101(systemd-journal) as per https://github.com/rradczewski/kata-bootstraps-reproducer/actions/runs/6025545201/job/16346481450#step:2:5).
This means the updateUID script will no longer update the remoteUser to match the host user and thus will lead to the permission errors.
Affected images
At least all images that include ghcr.io/devcontainers/features/node:1 in their devcontainer.json will most likely be affected. The javascript-node image further creates another npm group which faces the same issue.

anaconda
dotnet
go
java-8
java
javascript-node
jekyll
miniconda
php
python
ruby
universal

Reproducer
A minimal reproducer using busybox is available in https://github.com/rradczewski/kata-bootstraps-reproducer/tree/1037fdcbe0c7db88d765646a6842acd222b4af70 - see this run for a good example: https://github.com/rradczewski/kata-bootstraps-reproducer/actions/runs/6025545201/job/16346488288
Other issues

actions/runner-images#8160
actions/runner-images#8157 (specifically the investigation from this comment) for reference.

Workaround
As per  microsoft/vscode-remote-release#7284 (specifically this comment) a workaround is to delete the groups using GID 999 in the Dockerfile that is used to create the container, or to specifically avoid the GID 999 when creating groups.

Hi 👋
Thanks for the details information, I am sure people running into similar issues would benefit from it! ✨

This means the updateUID script will no longer update the remoteUser to match the host user and thus will lead to the permission errors.

Dev container Features and Images repo uses the mentioned ^ images within GitHub Actions (Examples - smoke test - workflow, and sample action-run). I wonder why don't we see such errors 🤔

This means the updateUID script will no longer update the remoteUser to match the host user and thus will lead to the permission errors.

"remoteUser": "root",

@rradczewski Does things work if you comment this ^ line? https://github.com/rradczewski/kata-bootstraps/blob/main/dotnet/.devcontainer.json#L4

Ah, we are seeing such issues in this repo as well. See https://github.com/devcontainers/images/actions/runs/6014530431/job/16314428455
From https://github.com/actions/runner-images/issues/8160#issuecomment-1697455235

issue seems to be in conflicting groups on host (uid=1001(runner) gid=998(docker) groups=998(docker)) and container (uid=1000(node) gid=1000(node) groups=1000(node),998(nvm),999(npm)). With https://github.com/microsoft/vscode-remote-release/issues/7284#issuecomment-1271214932 suggestion in devcontainers, I was able to finish builds after additions to Dockerfile:
on ubuntu20 runner - RUN delgroup nvm
on ubuntu22 runner - RUN delgroup npm

I believe we need to update the uids and gids used by the dev container images which are conflicting with action runners
// cc @Chuxel @bamurtaugh

Dev container Features and Images repo uses the mentioned ^ images within GitHub Actions (Examples - smoke test - workflow, and sample action-run). I wonder why don't we see such errors 🤔

The log for that run is rather confusing to me. I would expect the updateUID script to run, thus to find a docker build with --build-arg NEW_UID=$XYZ, but I'm not seeing that. I suspect your test for the ruby image passes because it's never actually creating any files in the mounted workspace. From a quick glance, I don't see any bundle install etc. happening.

"remoteUser": "root",

@rradczewski Does things work if you comment this ^ line<EMAIL_ADDRESS>
I temporarily run all devcontainers with root, circumventing the issue. This is not a longterm solution because people running this locally will have all their node_modules/ etc. files created as root:root, which I think is not acceptable.

Ah, we are seeing such issues in this repo as well. See devcontainers/images/actions/runs/6014530431/job/16314428455

All images with a group with GID=999 existing should be affected, as this prevents the updateUID script from mapping the requested remoteUser (usually UID=1000) to the host user (in GHA right now that's UID=1001).  updateUID will not do anything if the GID already exists (https://github.com/devcontainers/cli/blob/7866e193a49a31ab542c6d3bbe34cc99bcf58dc9/scripts/updateUID.Dockerfile#L21-L23), so even if the remoteUser is in the correct group, they will only get readonly access to the workspace.

In the reproducer repository (https://github.com/rradczewski/kata-bootstraps-reproducer/), I use a container with the problematic users and gids existing. One with the remoteUser set to node, (implicitly, see the Dockerfile and https://github.com/rradczewski/kata-bootstraps-reproducer/blob/main/user_busybox_node_user/.devcontainer.json) and one where it is set to root (https://github.com/rradczewski/kata-bootstraps-reproducer/blob/main/root_busybox_node_user/.devcontainer.json).

I believe we need to update the uids and gids used by the dev container images which are conflicting with action runners (Unless the action-runners team reverts these updates, I'll have an async chat with them)

A tricky situation, I agree. A policy for devcontainers/images to avoid creating groups and users might be more appropriate, or to allocate only UIDs and GIDs that are less likely to cause conflicts  (e.g. UIDs > 1100, and system GIDs < 900)? The ultimate solution would be for ID-mapping or user namespaces to be more widely adopted and easier to use (without having to reconfigure dockerd or run a different container runtime), but that doesn't seem to be coming anytime soon.

Quick update: Investigated this issue with the dev containers team, few findings -

The dev container CLI should have automatic UID/GID syncing, unless the UID or GIDs were already in use
From https://github.com/actions/runner-images/issues/8157, Docker's group was 999, and they then update the user's default group to that rather than adding the docker group to the user
This caused the issue, hence, we necessarily don't have to update anything on the images side
However, we could update our Features to use system groups with lower IDs to try to avoid this in the future.  We do this pretty frequently to deal with priv issues
https://github.com/actions/runner-images/pull/8201 which fixes docker group issues is already merged. Waiting for the action-runners team to release new images. Looks like that would fix the entire issue.

The dev container CLI should have automatic UID/GID syncing, unless the UID or GIDs were already in use

Yepp, that's what updateRemoteUserUID should've been doing.

From
https://github.com/actions/runner-images/issues/8157, Docker's group was 999, and they then update the user's default group to that rather than adding the docker group to the user

I think I understood this differently, as in, the docker group used to be 123, which didn't exist in any of the devcontainer/images, so creating it as part of the auto sync wasn't an issue. (See this comment). Now when that changed to be 999, anything that would just create a system group like the features/node feature would create a group with that GID and cause the automatic UID/GID syncing to stop working because that GID already exists in the devcontainer/image.

However, we could update our Features to use system groups with lower IDs to try to avoid this in the future. We do this pretty frequently to deal with priv issues

I agree this is the way to go for the time being and appreciate the effort, otherwise it's gonna keep popping up. This would probably also be necessary for images that create extra groups like javascript-node.
Thanks a lot for the quick response!

Newer ubuntu (action runner) images were released last week with https://github.com/actions/runner-images/pull/8201 changes. This has fixed the ID problems we have been seeing.
Also, on the CLI side, we have https://github.com/devcontainers/cli/pull/635 opened which fixes https://github.com/microsoft/vscode-remote-release/issues/7284


Uncaught Error: Invariant Violation: ReactDOM.render(): Invalid component element.

Source code

Something Layout.cjsx broken

src/layouts/Layout.cjsx
React = require "react"
Router = require "react-router"
RouteHandler = Router.RouteHandler
AppBar = require("material-ui").AppBar
Layout = React.createClass
render: ->

module.exports = Layout
what's wrong？

@Dreampie  return one component?

Can not do this?

Wrap the components in one ?

Can not solve any problems

I solve  this problem,in
ReactDOM.render Routes, document.getElementById 'app'

not
ReactDOM.render {Routes}, document.getElementById 'app'


How quickly can we tell that a supernova is at a different redshift to the host?

We need this to rapidly initiate followup of potential lensed SN candidates

@tcollett
Could you please elaborate on the question and the the procedure you think needs to be followed. It would be useful (at least for me) since I have not thought about these:

By host do you really mean the host or the lens galaxy which might appear to be the host due to low angular separation? So, is this a 1 SN 1 galaxy or 1 SN (lens + true host) 2 galaxy system with the lens galaxy redshift very different from the source / SN redshift?  It would be great if you have a measured/'expected' separation distribution of such objects.
Are you saying that detecting differences in redshift is the quickest way to identify lensed SN candidates? How accurate does this difference need to be ? Are we talking about ~1.0 vs ~0.5 and how many of such estimates can be outlier level failures?
What kind of follow-up are you imagining and how critical is it to have this? Is the follow up 'spectra' to determine types/ redshifts or or is it photometric (beyond LSST) to determine the time-delayed light curves for a few cases?

This is a hard problem @tcollett. With photometry alone, it is not trivial
to disentangle whether the supernova is fainter because it is at higher
redshift, intrinsically fainter, or at a different point in its evolution.
We should think carefully about this. I'm happy to talk through some of the
issues with you to hear your ideas on how this might work in practice.
On Fri, Jul 22, 2016 at 2:38 PM rbiswas4<EMAIL_ADDRESS>wrote:

@tcollett https://github.com/tcollett
Could you please elaborate on the question and the the procedure you think
needs to be followed. It would be useful (at least for me) since I have not
thought about these:

By host do you really mean the host or the lens galaxy which might
appear to be the host due to low angular separation? So, is this a 1 SN 1
galaxy or 1 SN (lens + true host) 2 galaxy system with the lens galaxy
redshift very different from the source / SN redshift? It would be great if
you have a measured/'expected' separation distribution of such objects.
Are you saying that detecting differences in redshift is the
quickest way to identify lensed SN candidates? How accurate does this
difference need to be ? Are we talking about ~1.0 vs ~0.5 and how many of
such estimates can be outlier level failures?
What kind of follow-up are you imagining and how critical is it to
have this? Is the follow up 'spectra' to determine types/ redshifts or or
is it photometric (beyond LSST) to determine the time-delayed light curves
for a few cases?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DarkEnergyScienceCollaboration/Twinkles/issues/285#issuecomment-234663409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFFcHKLHiSU4LExA0GIHmFeiWyvEhyIcks5qYThhgaJpZM4JSu_B
.

@rbiswas4
By host I meant the nearest object that you think is likely to be SN host (although it'll actually be the lens) [since lensing einstein radii are ~1 arcsecond it should be fairly unambiguous]
If you can realise the lens and supernova aren't at the same redshift it's a good indication of strong lensing
1 vs 0.5 is about the accuracy needed
the followup is likely both spectra and high resolution imaging
@cmccully
Yes I know it'll be hard, but @drphilmarshall suggested we start thinking on how to identify lensed supernovae quickly enough to get useful follow-up.  The other option is to find the lensed SN hosts first, and follow up and SNe that happen near known lenses.
My new student will be simulating lensed supernovae, so hopefully that'll shed some light on what we should look for.


Invalid Arguments warning is shown.

VSCode Version: Code - Insiders 1.13.0-insider (cdaa5f28efd6d6fa012a34a92a6cf3fe57928b38, 2017-05-19T05:06:01.981Z)
OS Version: Darwin x64 15.6.0
Extensions:

Extension
Author
Version

prettier-eslint-vscode
RobinMalfait
0.7.1

vscode-icons
robertohuertasm
7.7.0

react-redux-es6-snippets
timothymclane
2.0.2

Steps to Reproduce:

Open JS file
Create an array, i.e const array = [1,2,3]
And when you type for example array. and then intellisense shows the options after dot and if you press enter by selecting any option the below warning is shown saying Invalid Arguments

PS: All extensions are in disabled mode.

I think it has been resolved in
- VSCode Version: Code - Insiders 1.13.0-insider (ec76a9fc5146b822cdb14b982ac3e5b470dd646a, 2017-05-19T08:07:58.056Z)


Issue 390

Implement permalink feature as described here: #390

[X]  implemented permalink.html
[x] added permalink.html to project-html build
[x] added config setting settings for needs.json location
[x] added feature/function for layouts to add a permalink-icon to each need
[x] resolved error with PackageLoader("needs"), where "needs" is unknown to Jinja.
[x] added your name to the AUTHORS file
[x] added also a line to docs/changelog.rst
[x] added some docs
[x] final test on local webserver

Thanks for the PR :+1: .
There is an error with PackageLoader("needs"), where "needs" is unknown to Jinja.
Also, is this PR still a draft, or could it be merged, when CI is green?
Oh and 2-3 additional hints:

If you like you can add your name to the AUTHORS file
Please add also a line to docs/changelog.rst.
Maybe also some docs are needed?

But the last two steps I can also do after this PR got merged.
Thanks again for your contribution.

Also, is this PR still a draft, or could it be merged, when CI is green?

Thanks for your input.
It's still a draft. Once I'm done I change this to a normal PR and then it can be merged once CI is green.

@danwos Unless you want me to change something this PR can be merged once CI is green.


How can I connect an application with a newer version of react?

When the module is dynamically connected via @module-federation/enhanced/runtime,, at the moment, when I try to use 2 different instances of the react library (an older version on the host application), I get an error:

But the module federation instance shows that 2 react instances have been loaded:

The problem is solved when using singleton, but this is not the behavior I expect.

The problem is solved when using singleton, but this is not the behavior I expect.

What's your expectations? Can you create a basic repo for this?

Hi @gioboa
Yes, something like this https://github.com/ohmygodismax/mf-vite-example

@ohmygodismax I didn't have the time to look at it. Did you find a solution for that?

@gioboa I was unable to use 2 versions of react with an older one in the host application. So far, I've settled on the option where the connection is via a singletone with a warning that the host application has an older version.

I see, is your scenario working with webpack / rspack?


[incubator-kie-drools-6010] Date Between Dates with globals Not Trigg…

…ering for Executable Model
Issue:

https://github.com/apache/incubator-kie-drools/issues/6010

GHA kogito-apps : not related to this PR
2024-07-08T03:44:08.0996602Z [ERROR] Caused by: java.util.concurrent.ExecutionException: com.google.cloud.tools.jib.http.ResponseException: 504 Gateway Time-out
2024-07-08T03:44:08.0997660Z [ERROR] GET https://registry.access.redhat.com/v2/ubi8/openjdk-17-runtime/manifests/1.18

GHA kogito-quarkus-examples : not related to this PR
2024-07-08T02:35:50.1018392Z [ERROR] Caused by: java.util.concurrent.ExecutionException: com.google.cloud.tools.jib.http.ResponseException: 504 Gateway Time-out
2024-07-08T02:35:50.1020052Z [ERROR] GET https://registry.access.redhat.com/v2/ubi8/openjdk-17-runtime/manifests/1.18

@mariofusco @lucamolteni @pibizza Please review, thanks!


Updated eventtype to a search

Updated the eventtype match to a search so this works in Splunk 6.4+

Good catch, that was completely accidental.


[Aura-Safe][Multisig Tx] Tạm ẩn “Total Allocation Amount” ở popups Create, Confirm, Reject, and Execute multisig Tx

Requirements
Tạm ẩn “Total Allocation Amount” ở popups Create, Confirm, Reject, and Execute multisig Tx
Screens

Links
https://www.notion.so/aura-network/d4607c1b0a5441fab9143e21bdc9cda1?v=c8f6f7a68e57475db1cb27df5811abe9&p=d21a0f240c374e56975c49f26d4d2592&pm=s

Verified PASS on serenity (04-Aug-2022)

Check on Create Send Funds popup

Execute popup

Confirm popup


npm install -g amok fails (on OS X? on Node 4.1?)

When trying to do npm install -g amok:
dan@galaxy ~> npm -v
3.3.3
dan@galaxy ~> node -v
v4.1.0
dan@galaxy ~> npm install -g amok
/usr/local/bin/amok -> /usr/local/lib/node_modules/amok/bin/amok

><EMAIL_ADDRESS>install /usr/local/lib/node_modules/amok/node_modules/bufferutil
> node-gyp rebuild

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
In file included from ../src/bufferutil.cc:16:
../node_modules/nan/nan.h:261:25: error: redefinition of '_NanEnsureLocal'
NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Local<T> val) {
                        ^
../node_modules/nan/nan.h:256:25: note: previous definition is here
NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Handle<T> val) {
                        ^
../node_modules/nan/nan.h:661:13: error: no member named 'smalloc' in namespace 'node'
    , node::smalloc::FreeCallback callback
      ~~~~~~^
../node_modules/nan/nan.h:672:12: error: no matching function for call to 'New'
    return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
           ^~~~~~~~~~~~~~~~~
/Users/dan/.node-gyp/4.1.0/src/node_buffer.h:31:40: note: candidate function not viable:
      no known conversion from 'uint32_t' (aka 'unsigned int') to 'enum encoding' for 3rd
      argument
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
/Users/dan/.node-gyp/4.1.0/src/node_buffer.h:43:40: note: candidate function not viable:
      2nd argument ('const char *') would lose const qualifier
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
/Users/dan/.node-gyp/4.1.0/src/node_buffer.h:28:40: note: candidate function not viable:
      requires 2 arguments, but 3 were provided
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, size_t length);
                                       ^
/Users/dan/.node-gyp/4.1.0/src/node_buffer.h:36:40: note: candidate function not viable:
      requires 5 arguments, but 3 were provided
NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                       ^
In file included from ../src/bufferutil.cc:16:
../node_modules/nan/nan.h:676:12: error: no viable conversion from
      'v8::MaybeLocal<v8::Object>' to 'v8::Local<v8::Object>'
    return node::Buffer::New(v8::Isolate::GetCurrent(), size);
           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:210:7: note: candidate constructor (the
      implicit copy constructor) not viable: no known conversion from
      'v8::MaybeLocal<v8::Object>' to 'const v8::Local<v8::Object> &' for 1st argument
class Local {
      ^
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:210:7: note: candidate constructor (the
      implicit move constructor) not viable: no known conversion from
      'v8::MaybeLocal<v8::Object>' to 'v8::Local<v8::Object> &&' for 1st argument
class Local {
      ^
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:214:13: note: candidate template ignored:
      could not match 'Local' against 'MaybeLocal'
  V8_INLINE Local(Local<S> that)
            ^
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:326:13: note: candidate template ignored:
      could not match 'S *' against 'v8::MaybeLocal<v8::Object>'
  V8_INLINE Local(S* that)
            ^
In file included from ../src/bufferutil.cc:16:
../node_modules/nan/nan.h:683:26: error: no member named 'Use' in namespace 'node::Buffer'
    return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
           ~~~~~~~~~~~~~~^
In file included from ../src/bufferutil.cc:7:
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:221:5: error: assigning to
      'v8::Primitive *volatile' from incompatible type 'v8::Value *'
    TYPE_CHECK(T, S);
    ^~~~~~~~~~~~~~~~
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:180:37: note: expanded from macro
      'TYPE_CHECK'
    *(static_cast<T* volatile*>(0)) = static_cast<S*>(0);      \
                                    ^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:414:12: note: in instantiation of function template
      specialization 'v8::Local<v8::Primitive>::Local<v8::Value>' requested here
    return NanEscapeScope(NanNew(v8::Undefined(v8::Isolate::GetCurrent())));
           ^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
# define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                             ^
In file included from ../src/bufferutil.cc:7:
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:221:5: error: assigning to
      'v8::Boolean *volatile' from incompatible type 'v8::Value *'
    TYPE_CHECK(T, S);
    ^~~~~~~~~~~~~~~~
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:180:37: note: expanded from macro
      'TYPE_CHECK'
    *(static_cast<T* volatile*>(0)) = static_cast<S*>(0);      \
                                    ^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:424:12: note: in instantiation of function template
      specialization 'v8::Local<v8::Boolean>::Local<v8::Value>' requested here
    return NanEscapeScope(NanNew(v8::True(v8::Isolate::GetCurrent())));
           ^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
# define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                             ^
In file included from ../src/bufferutil.cc:7:
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:221:5: error: assigning to
      'v8::Function *volatile' from incompatible type 'v8::Value *'
    TYPE_CHECK(T, S);
    ^~~~~~~~~~~~~~~~
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:180:37: note: expanded from macro
      'TYPE_CHECK'
    *(static_cast<T* volatile*>(0)) = static_cast<S*>(0);      \
                                    ^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:1514:12: note: in instantiation of function template
      specialization 'v8::Local<v8::Function>::Local<v8::Value>' requested here
    return NanEscapeScope(NanNew(handle)->Get(kCallbackIndex)
           ^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
# define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                             ^
In file included from ../src/bufferutil.cc:7:
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:221:5: error: assigning to
      'v8::Object *volatile' from incompatible type 'v8::Value *'
    TYPE_CHECK(T, S);
    ^~~~~~~~~~~~~~~~
/Users/dan/.node-gyp/4.1.0/deps/v8/include/v8.h:180:37: note: expanded from macro
      'TYPE_CHECK'
    *(static_cast<T* volatile*>(0)) = static_cast<S*>(0);      \
                                    ^ ~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:1632:12: note: in instantiation of function template
      specialization 'v8::Local<v8::Object>::Local<v8::Value>' requested here
    return NanEscapeScope(handle->Get(NanNew(key)).As<v8::Object>());
           ^
../node_modules/nan/nan.h:398:30: note: expanded from macro 'NanEscapeScope'
# define NanEscapeScope(val) scope.Escape(_NanEnsureLocal(val))
                             ^
9 errors generated.
make: *** [Release/obj.target/bufferutil/src/bufferutil.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/amok/node_modules/bufferutil
gyp ERR! node -v v4.1.0
gyp ERR! node-gyp -v v3.0.1
gyp ERR! not ok
npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "amok"
npm ERR! node v4.1.0
npm ERR! npm  v3.3.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the bufferutil package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls bufferutil
npm ERR! There is likely additional logging output above.

This works fine, however (maybe it's the version of bufferutil?):
dan@galaxy ~ [1]> npm install -g bufferutil

><EMAIL_ADDRESS>install /usr/local/lib/node_modules/bufferutil
> node-gyp rebuild

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
/usr/local/lib
└─┬<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26973712-npm-install-g-amok-fails-on-os-x-on-node-4-1?utm_campaign=plugin&utm_content=tracker%2F12689110&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F12689110&utm_medium=issues&utm_source=github).

Basically everything that depends on native modules broke with node v4.x.
However, despite the error messages it should still work, as these are optional dependencies of the ws library. It continues the install right?

Had a quick look at bufferutil's repo, looks like they've recently upgraded NaN https://github.com/websockets/bufferutil/commit/440faef60ee4ddaf163f8248308a4dccaeb76160

Actually here's the upstream issue https://github.com/websockets/bufferutil/issues/17
And the commit which it landed in ws https://github.com/websockets/ws/commit/ee660710e151779a258f29f33040234c3133a63a
So we should upgrade to<EMAIL_ADDRESS>For now, any users that run into this these errors are safe to ignore. Optional dependencies.
You can skip them all together with npm install --no-optional, but even when they fail it just looks messy but it will still install cleanly.

It continues the install right? (I've yet to try on Node 4 OS X as I'm having a 'windows' week on low-end gear)

I'm not sure... after running it, the amok command is not available.

You can skip them all together with npm install --no-optional, but even when they fail it just looks messy but it will still install cleanly.

 Most likely this is because the latest release (1.1.4) was published from a windows machine with line endings being \n\r.
For now you can roll back to 1.1.3, I'll get a fix out shortly.
npm install --no-optional --global<EMAIL_ADDRESS>

@caspervonb no worries :sweat_smile:
1.1.3 works fine :tada:
dan@galaxy ~> npm install --no-optional --global<EMAIL_ADDRESS>/usr/local/bin/amok -> /usr/local/lib/node_modules/amok/bin/amok
/usr/local/lib
└──<EMAIL_ADDRESS>
dan@galaxy ~> amok

  Usage: amok [OPTION ...] <URL | FILE>

1.1.4 was unpublished #160

Master is now tracking node v4/v5, closing this.


dynamic query restrictions

This PR contains some ideas that I was experimenting with locally for dynamic query restrictions #829 and hadn't been planning to propose until after a lot more discussion occurred.  However, because code changes are already being proposed and I wanted to illustrate how this should tie into the static metamodel, I decided to share this prematurely so everyone can see what I was originally aiming for with the pattern.
@Repository
public interface Products extends CrudRepository<Product, Long> {
    List<Product> search(String namePattern,
                         Restriction<Product> restriction,
                         Order<Product> order);
}

Usage with single restriction,
    List<Product> found = products.search(pattern,
                                          _Product.price.lessThan(50.0f),
                                          Order.by(_Product.price.desc(),
                                                   _Product.name.asc()));

Usage with multiple restrictions,
    List<Product> found = products.search(pattern,
                                          Restrict.all(_Product.price.greaterThan(25.0f),
                                                       _Product.price.lessThan(50.0f),
                                                       _Product.name.startsWith(pattern).ignoreCase(),
                                                       _Product.image.notNull()),
                                          Order.by(_Product.price.desc(),
                                                   _Product.name.asc()));

This was just the basics, and doesn't yet include not/negation, or Pattern/Range, which might make parts of it unnecessary.  It also just occurred to me that if we had a TextRestriction subclass, which I did not include in this, we could omit the *IgnoreCase methods and have .ignoreCase() instead.

After a lot of difficulty reviewing another PR that combines several different new parts of Jakarta Data, I decided to just finish off updating this PR with how I expect Restrictions to work.
I was originally thinking that Restrictions would only come from the static metamodel, but others have expressed a desire that users be able to create them like they can for Sort.  I'm okay with that, but not by giving users access to record/implementation class constructors where they can populate them with any combinations of things they like.  With this PR, all implementation classes are made non-public and kept out of the API.  There are 2 places where users can obtain restrictions:

static metamodel attributes (basic restrictions only)
the Restrict class (both composite and basic restrictions)

This also aims to de-emphasize interfaces that the end user shouldn't care about (and only Data Providers need, such as Operator and the Composite restriction) out of the main view by placing them in inner classes.
There is no JavaDoc in this on purpose. The idea is to iterate over the design first, and later spend time on JavaDoc and other things.
Other spec function like Pattern, Range, Is, ... are intentionally kept out so we can focus only on getting Restriction correct.
Restriction could justifiably be placed in the jakarta.data package alongside some other special classes that are used as repository parameters (Sort, Order, Limit) although we might want to consider if it is worth it to have a separate jakarta.data.restrict package to separate it out like we do with jakarta.data.page for PageRequest, which is the other special parameter type. I think the latter is a good place for it, so that's where I put it in this PR.
greater/lessThan methods require a Comparable parameter (lots of things can be sortable, but I think they are all Comparable).  TextAttribute methods, and their equivalents on Restrict, require a String parameter.  I added a commented out method showing what it might be appropriate to do with Pattern parameter as well.  But ignore that if you don't want to think about Pattern yet.
I would like to see more error checking for values supplied to Restriction factory methods in general, and identify if we can use any more precise types that would help keep invalid objects out, but we can save that for when we are further along.

Restriction could justifiably be placed in the jakarta.data package

This is where I would have put it.

Restriction could justifiably be placed in the jakarta.data package

This is where I would have put it.

That's fine. I have moved it to jakarta.data in the review fixes commit.

Added a commit to cover most of Gavin's review comments.

Thanks!

Switched methods such as startsWith(prefixPattern) to startsWith(prefix) and automatically add escaping to spare the user from that level of detail/complexity.

Review comments have been addressed.

Review comments have been addressed.

I saw, I am moving the documentation and the unit test that make sense against this PR.
I hope finish it today, thus, you will receive a PR soon.

@njr-11 done the first step: https://github.com/njr-11/data/pull/1

Thanks for contributing the unit tests. That helps to confirm the correctness of the changes.
I was thinking maybe we should wait on adding JavaDoc until after this PR is merged, so that we don't need to rewrite it if anyone asks for further changes to the initial PR.

Thanks for contributing the unit tests. That helps to confirm the correctness of the changes. I was thinking maybe we should wait on adding JavaDoc until after this PR is merged, so that we don't need to rewrite it if anyone asks for further changes to the initial PR.

It does make sense.
I will focus on the Unit test to find some issues on it.

@njr-11 one more PR against yours.

@njr-11 one more PR against yours.

@otaviojava I don't see another PR against this anywhere.

@njr-11 one more PR against yours.

@otaviojava I don't see another PR against this anywhere.

This one here: njr-11#2

I see it now and have accepted your PR/commits for more unit tests.  Thanks for adding the test coverage.

@njr-11 one more PR against yours.

@otaviojava I don't see another PR against this anywhere.

This one here: njr-11#2

I see it now and have accepted your PR/commits for more unit tests. Thanks for adding the test coverage.

@njr-11
This is the last one:
https://github.com/njr-11/data/pull/3
I put the validation on field making the field mandatory

As a first step, IMHO, it is good to go.
@njr-11 @gavinking, what do you think?


open_tablet may cause deadlock

open_tablet will acquire the lock of registry. When the tablet is not in registry, it will call open_tablet_raw which may call create_tablet which will acquire the lock of registry again.
So deadlock may happen

/type bug
/severity moderate


Better CN translation

Hi - thanks for the updates! Just quick question on this: "names": "名称样式（国服无效）. Is there a bug for CN client?

Hi - thanks for the updates! Just quick question on this: "names": "名称样式（国服无效）. Is there a bug for CN client?

Nope.Just because the character name format of CN client is different from that of Int client.It does not distinguish between first and last names.（e.g 猫小胖,Blade）


[FSPE-5230] Add search bar component

https://ctl.atlassian.net/browse/FSPE-5230

I just tested including Chi assets from the remote instance of this PR with integrity attribute from the installation page and chi.css and ux-chi-ce.esm.js have been blocked by the browser. @jllr Please rebase from master, run chi test on your local. It will generate sri.json with updated SHA values (for chi.css and ux-chi-ce.esm.js because your changes affect these 2 files) and commit the updated sri.son.


Some enhancements

Cleanup if cleanup.on == Always and error happens in setup step.
Fail setup step if there is command fail in the steps.command.
Retry per case instead of all cases in verify step.
Delete unused function Which.

FYI @mrproliu Please notice these for the document part.


[WIP] (feat) Add cargo audit on presubmit and add allow list licenses

fixes #3
to do:
[] add cargo audit && cargo deny to dockerfile
[] successfully build so cargo.lock updates & allow list can be tested
[] add cargo deny cmd to makefile

Hi @hypernovasunnix. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@hypernovasunnix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel
8a2edd0944ff4426a19ca3df5dfaed9dbfab5035
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Why no CORS headers on Negotiate.WithStatusCode(non-success code)?

Hi
Nancy Version: 1.4.4
.NET Framework: 4.7.1
Just curious why CORS headers aren't included when I use something like Negotiate.WithStatusCode(HttpStatusCode.NotFound?
If using content negotiation, are you responsible for outputting everything that may be needed?
Negotiate.WithModel(model) includes the CORS headers without any additional code.
I know this isn't the format requested for issues. Just looking to be pointed any documentation I may have missed or misunderstood.
Thanks

Found the following though:
return Negotiate.WithStatusCode(HttpStatusCode.NotFound
returns no CORS headers when no model.
return Negotiate
    .WithModel("Your request is bad. :(")
    .WithStatusCode(HttpStatusCode.BadRequest)

returns CORS headers with model.


Paloma verify the attestation TX data

Related issues

https://github.com/palomachain/paloma/issues/379

Background
When attesting to events coming from Pigeon for EVM type of events, we receive serialized TX bytes in case of success. That same TX object contains the payload that was sent as a bytecode. We want to verify the actual data against the message we sent. To do that, it becomes easier if we solve https://github.com/palomachain/paloma/issues/379 first as Paloma would be the bearer of the actual bytecode.
Done when

[ ] Paloma can verify the TX data against the message

Moved to https://github.com/VolumeFi/paloma/issues/43


Link to Dancy Pi in readme?

Hello, could you put a link to Dancy Pi in your readme?  He's giving you full credit, and has a Python 3 port working.  Thanks for this!
https://github.com/naztronaut/dancyPi-audio-reactive-led

I need to email Scott and figure out what the status of this project is. At the current moment I don't have the knowledge or ability to bring this project where it should be so I'm just trying to help with issues and whatnot.
If we decide to put this project into a not maintained status I'll probably add a section near the top with links to forks or alternative projects that fulfill a similar role.

I need to email Scott and figure out what the status of this project is. At the current moment I don't have the knowledge or ability to bring this project where it should be so I'm just trying to help with issues and whatnot.
If we decide to put this project into a not maintained status I'll probably add a section near the top with links to forks or alternative projects that fulfill a similar role.

any updates on this?

any updates on this?

No, at the moment I don't see a real reason to add a single alternative project to the readme.

No, at the moment I don't see a real reason to add a single alternative project to the readme.

ok no worries.
about no reason... have you actually looked at the other repo?  and website?

ok no worries.
about no reason... have you actually looked at the other repo?  and website?

Yes, other repos have more features or are better maintained., I understand that.
My point earlier is that as of right now I am the sole maintainer as Scott hasn't been able to get around to it. I fix the readme and answer questions as best I can about this repo but until I know for sure that this repo is going to be unmaintained, I don't want to declare it dead.

Yes, other repos have more features or are better maintained., I understand that.
My point earlier is that as of right now I am the sole maintainer as Scott hasn't been able to get around to it. I fix the readme and answer questions as best I can about this repo but until I know for sure that this repo is going to be unmaintained, I don't want to declare it dead.

ok sure, totally understand.  No pressure.

ok sure, totally understand.  No pressure.


Feature/add walks

Thanks @stefankorder and @Quaquaro for your feedback! Really appreciate it! I already implemented it. If you don't mind please take another look at it.


System requirement inquiry

What's the minimum system requirements required to execute the code?
Some insight on the GPU and RAM of the system used for the paper would be helpful.

Thanks for the info! I have gotten inference to work but have some issues with the finetuning process, I'll try my best to solve them or inevitably open an issue.


Add domain "whitelist" parameter

Instead of having a blacklist domain.nostore it would be great to have a whitelist (domain.dostore?) which, if set, rejects all mails not having a recipient on that domain(s).
Use-Case: I'm using Inbucket as a single-purpose-mailbox SMTP server for those "enter your email address to get your download link sent to you - and well, we will spam you with newsletters afterwards"-things… Sadly spammers seem to think this SMTP will redirect their messages to whomever they want…

Ah, I guess Inbucket looks like an open relay to them.
I wonder if it's better to have it actually reject the mail so it doesn't appear as an open relay, or just silently drop it.  The former might be a bit more work to implement, but may reduce the amount of traffic you get.

I ended up taking a slightly different strategy, you can set a default accept/reject policy and then specify exceptions.  Same for store/nostore.

I like the solution you've built! Will test it as soon as it's in the next release! Thank you very much for implementing it! 🙂


Better error message when delegating selection set for scalar fields

Mutation:
mutation {
  updatePassword(password: String!): String!
}}

resolver:
ctx.db.mutation.updateLogin(
  {
    where: { id: loginId },
    data: { name: newName },
  },
  info
)

Results in this error:
GraphQLError: Field 'updateLogin' of type 'Login' must have a sub selection. (line 2, column 3):
  updateLogin(data: $_data, where: $_where)
  ^
    at Object.locatedError (/Users/sorenbs/code/gc/cloud/node_modules/graphql/error/locatedError.js:23:10)
    at Object.checkResultAndHandleErrors (/Users/sorenbs/code/gc/cloud/node_modules/graphql-tools/src/stitching/errors.ts:83:11)
    at Object.<anonymous> (/Users/sorenbs/code/gc/cloud/node_modules/graphql-tools/src/stitching/delegateToSchema.ts:91:14)
    at step (/Users/sorenbs/code/gc/cloud/node_modules/graphql-tools/dist/stitching/delegateToSchema.js:40:23)
    at Object.next (/Users/sorenbs/code/gc/cloud/node_modules/graphql-tools/dist/stitching/delegateToSchema.js:21:53)
    at fulfilled (/Users/sorenbs/code/gc/cloud/node_modules/graphql-tools/dist/stitching/delegateToSchema.js:12:58)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:228:7)

as there is no selection set in info. This makes sense, but can be confusing.
Could we provide a better error message?

This is fixed in the newest release.


Update Japanese translation for PR #121

Apply #121 to Japanese translation.
Remove an unnecessary right bracket from README.md.

as always, thanks a lot


Refactor DeviceOrientationCameraController

Refactor DeviceOrientationCameraController

it's now using more APIs to get DeviceOrientation (e.g. IE11 is now supported)
Use camera.setView instead of calculation view by itself

I saw Cesium contains a DeviceOrientationCameraController and because or online demo is more complete with supporting this feature, I integrated our code into DeviceOrientationCameraController.
Browser Support

IE11/Edge are supported
Firefox seems not to support this API anymore (note sure if LTS version still contains support)
Chrome works - but it's not possible to look at sky, because sky and earth have a gamma of 0 :grimacing:

Thanks for the pull request @SunBlack!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks for the PR @SunBlack!  Can you also update DeviceOrientationCameraControllerSpec?
Does firefox work in master?  I did a quick search and I couldn't find anything saying firefox doesn't support deviceorientation

I didn't tried master. But I tried demo of MDN (the green point). This demo worked as I developed the device orientation for our demo - but now it doesn't work anymore with FF.
Currently I just get a warning like this user here
I don't find something in bugtracker of FF to this except this

Played a bit around with it now:

Demo of MDN does not run on any FireFox of Firefox I tested (I tested FF40, 52, 55, 57..62). So I have no idea how to support Firefox device.sensors.orientation.enabledin about:config is already true
Chrome requires further investigation. Specification say gamma has a value range of [-90, 90), so Chrome is correct. So I maybe need to get data from accelerationIncludingGravity too.

Thanks for the update @SunBlack!  We won't be able to merge this until there are new tests.  Ping us when this is ready for review

I tried to write new tests, but it's not possible, because I respect screen orientation and this is a readonly property. So I could write test for a desktop PC, but on any other device tests could fail, if screen is rotated. Other possibility: Write test for all possible screen orientations - but this would be a lot of copy & paste code from tested code, so this would be ugly tests, too.
What do you prefer? Really ugly test (not sure if it is worth) or should I remove them?

@SunBlack did you look at the tests that are already there?  You would just need to write something comparable.  It looks like @bagnell wrote a helper class to simulate how events are fired.

@hpinkos Yep, I already adjusted this test a bit. But then I test only a few things of the code and not 100%.
E.g.:
this._scene.camera.setView({
	orientation: {
		heading : CesiumMath.toRadians(this._orientationAngle + 180) - this._heading,
		pitch : (this._flipPitchRoll ? this._roll : this._pitch) * this._invertPitchFactor - CesiumMath.toRadians(90),
		roll : (this._flipPitchRoll ? this._pitch : this._roll) * this._invertRollFactor
	}
});

If I cannot adjust this._orientationAngle I have two cases:

Assuming orientationAngle is always zero (=> assuming 'landscape-primary' is current device orientation), so only 1 of 4 cases of a correct setView call is tested

that._flipPitchRoll = false;
that._invertPitchFactor = 1;
that._invertRollFactor = 1;

Make a big switch-case in each test to handle current orientation of test device

Maybe I could try to workaround this by locking Screen - but this works not on desktop devices and not sure if it is wanted to change screen orientation during running test.
Other possibility: I try to rewrite my code so I can send dummy events to rotate screen.
Or any better idea?

@SunBlack The existing tests are somewhat minimal so as long as the new tests have the same coverage that will be fine.  I think you can assume the test device won't be firing events as the tests are running, so just worry about firing events from within the test.  As long as they pass on PC that will be good for now.

Added some tests (not finished).
Do you have an idea why two tests are failing? The call of setView in DeviceOrientationCameraController is correct, but at except the values of view has changed.

@SunBlack I'm not sure why those tests are failing.  Are you sure the expected values are what they should be?

Yep,
following test should pass, but doesn't (just insert it in my test class)
it('blubb', function() {
	var position = Cartesian3.clone(camera.position);
	camera.setView({
		orientation: {
			heading: CesiumMath.toRadians(180.0),
			pitch: CesiumMath.toRadians(-180),
			roll: 0.0
		}
	});

	expect(camera.position).toEqual(position);
	expect(camera.heading).toEqual(CesiumMath.toRadians(180.0));
	expect(camera.pitch).toEqual(CesiumMath.toRadians(-180.0));
	expect(camera.roll).toEqual(0.0);
})

Or as sandcastle demo
var viewer = new Cesium.Viewer('cesiumContainer');

viewer.camera.setView({
    orientation: {
        heading: Cesium.Math.toRadians(180),
        pitch: Cesium.Math.toRadians(-180),
        roll: 0.0
    }
});

console.log("heading " + viewer.camera.heading);
console.log("pitch " + viewer.camera.pitch);
console.log("roll " + viewer.camera.roll);

@SunBlack Hmm, I'm sorry, I'm not familiar enough with this code or how the camera works to be able to help with this one.
@bagnell can you review?

Thanks again for your contribution @SunBlack!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks again for your contribution @SunBlack!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Closing this due to inactivity.  Thanks for the PR @SunBlack!  We'll be taking a closer look at  WebXR later this year and will certainly use the changes in this pull request as a reference.


[Bugs] SMF There is a memory increase in AMF due to the IDGenerator's leakage to Allocate

Describe the bug
There is a memory increase in SMF due to the IDGenerator's leakage to Allocate
To Reproduce
Activate/Deactivate uplink tunnel and/or downlink tunnel cause memory leak.
Expected behavior
No memory leak.
Environment (please complete the following information):

free5GC Version: 3.0.4
OS: Ubuntu 18.04
Kernel version: 5.0.0-23-generic
go version: 1.14.4 linux/amd64

Pull Request
Pull Request for the fix. - PR is updated.

Thanks for the PR!


Light color issues

[x] Dimmed buttons wrong color

[x] Drop-down color is wrong

[x] Mouse-over controls makes box dissapear

[x] Header needs to be blue (both light and dark)

[x] Shouldn't have background color for left menu top level nav items (both light and dark)

[x] Active start buttons should be blue color (both light and dark)

[x] In tabbed views, input background same as tab background

[x] On Routers page, the box around a rule is missing

https://github.com/rancher/dashboard/pull/311/

Date - 2/20
Verified fixed


Audio not included in download

Using KaliLinux if it matters.
Video downloads fine, but doesn't include audio.

Issue is in Linux not including audio codecs. Audio works fine on windows.


Fix @CancelRequest and @SendProgress code generation

Fixes #322

@trevorwang can we get this merged?

same error with onReceiveProgress


Imaging masks

This PR is the first step in producing simulated 'imaging' data. It generates a set of masks that can be applied to a set of 'spectra' to produce spectral imaging data. Essentially the masks are each a 2D 'image' with values between 0 and 1, a sum of all the masks is an image where every pixel is ~ 1. In the future this will be used to generate 'spectral images' with each 'mask' being multiplied by a different 'spectra' to generate a set of (2+N)D 'spectral images' where N is the dimension of the spectra. Each of these 'spectral images' can then be summed together to give a 'spectral imaging dataset' where multiple spectra are dispersed over the 'scanned' area. Using the same set of masks with different sets of 'spectra' can result in a 'multi-modal' dataset from the same sample.
Calling data = SpectralImageGenerator() will instantiate a data 'object' that contains the masks as an attribute. As well as the raw_masks (a set of randomnly generated 2D 'blobs') used as the basis of the masks. By default it generates the same spectral masks each time (useful for testing) but using the kwarg seed=None it will generate a randomn set of masks.
Below is a screenshot of the  output of the method data.visualize_masks() which shows the raw_masks, the generated masks and the 'sum' of the masks to give an indication of the output.

@Jiemin-Li please take a look and comment/ request changes/ merge as appropriate. @tfg4280 Feel free to also provide feedback, comments/suggestions are welcome.

As discussed, the summed_mask in line-251 is not used afterwards, so it's unnecessary to keep line-251. Other than this, it all looks to me!

Thanks @Jiemin, good catch. The line has been removed as requested.


Disabled realtime drives conversion from jetpack and removed drives conversion in raid from Ironic

Hi Chris,
In this PR, i have removed drives conversion(in raid before creating raid config) from ironic in (raid.patch file) as we already discussed that we should not remove drives conversion from Jetpack and osp release should itself put that drives conversion.
Also i have disable again drives conversion in realtime mode as some servers does not let drives convert in either mode in realtime.
Thanks,
-Rachit

Sure Chris,
Thanks for the review


how to solve errors while running ctest

Test project /home/lakshmi/tes_traj/trajopt/build
Start  1: arm_to_joint_target.py
1/10 Test  #1: arm_to_joint_target.py .............   Passed    2.87 sec
Start  2: arm_to_cart_target.py
2/10 Test  #2: arm_to_cart_target.py ..............***Failed   11.83 sec
Start  3: fullbody_plan.py
3/10 Test  #3: fullbody_plan.py ...................   Passed    3.71 sec
Start  4: position_base.py
4/10 Test  #4: position_base.py ...................   Passed    1.94 sec
Start  5: this_side_up.py
5/10 Test  #5: this_side_up.py ....................***Failed   11.36 sec
Start  6: arm_to_cart_target_position_only
6/10 Test  #6: arm_to_cart_target_position_only ...***Failed   11.55 sec
Start  7: sco-unit
7/10 Test  #7: sco-unit ...........................   Passed    0.04 sec
Start  8: collision-checker-unit
8/10 Test  #8: collision-checker-unit .............   Passed    0.06 sec
Start  9: planning-unit
9/10 Test  #9: planning-unit ......................   Passed    1.70 sec
Start 10: cast-cost-unit
10/10 Test #10: cast-cost-unit .....................   Passed    0.06 sec
70% tests passed, 3 tests failed out of 10
Total Test time (real) =  45.11 sec
The following tests FAILED:
2 - arm_to_cart_target.py (Failed)
5 - this_side_up.py (Failed)
6 - arm_to_cart_target_position_only (Failed)
Errors while running CTest

Run the tests with the --verbose flag.

@EdsterG Do you know how to solve this error?
Test project /home/geriatronics/Projects/trajopt/build
      Start  1: arm_to_joint_target.py
 1/10 Test  #1: arm_to_joint_target.py .............***Exception: Numerical  0.28 sec
      Start  2: arm_to_cart_target.py
 2/10 Test  #2: arm_to_cart_target.py ..............***Exception: Numerical  0.28 sec
      Start  3: fullbody_plan.py
 3/10 Test  #3: fullbody_plan.py ...................***Exception: Numerical  0.28 sec
      Start  4: position_base.py
 4/10 Test  #4: position_base.py ...................***Failed    0.03 sec
      Start  5: this_side_up.py
 5/10 Test  #5: this_side_up.py ....................***Exception: Numerical  0.28 sec
      Start  6: arm_to_cart_target_position_only
 6/10 Test  #6: arm_to_cart_target_position_only ...***Exception: Numerical  0.28 sec
      Start  7: sco-unit
 7/10 Test  #7: sco-unit ...........................   Passed    0.03 sec
      Start  8: collision-checker-unit
 8/10 Test  #8: collision-checker-unit .............   Passed    0.03 sec
      Start  9: planning-unit
 9/10 Test  #9: planning-unit ......................   Passed    0.95 sec
      Start 10: cast-cost-unit
10/10 Test #10: cast-cost-unit .....................   Passed    0.02 sec

40% tests passed, 6 tests failed out of 10

Total Test time (real) =   2.45 sec

The following tests FAILED:
	  1 - arm_to_joint_target.py (NUMERICAL)
	  2 - arm_to_cart_target.py (NUMERICAL)
	  3 - fullbody_plan.py (NUMERICAL)
	  4 - position_base.py (Failed)
	  5 - this_side_up.py (NUMERICAL)
	  6 - arm_to_cart_target_position_only (NUMERICAL)
Errors while running CTest
Output from these tests are in: /home/geriatronics/Projects/trajopt/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.

when I run 'python arm_to_joint_target.py' in the folder /python_examples, ithe error just like:
You can set logging level with TRAJOPT_LOG_THRESH. Valid values: FATAL ERROR WARN INFO DEBUG TRACE. Defaulting to INFO
Traceback (most recent call last):
  File "arm_to_joint_target.py", line 7, in <module>
    import trajoptpy
  File "/home/geriatronics/Projects/trajopt/trajoptpy/__init__.py", line 1, in <module>
    from ctrajoptpy import *
ImportError: dynamic module does not define init function (initctrajoptpy)
Floating point exception (core dumped)