test: compilation error "the trait bound hashes::sha256::Hash: ThirtyTwoByteHash is not satisfied"

I still see these errors with cargo test --all-features after a cargo clean
error[E0277]: the trait bound `hashes::sha256::Hash: ThirtyTwoByteHash` is not satisfied
   --> src/policy/satisfy.rs:293:23
    |
293 |             let msg = secp256k1_zkp::Message::from(sighash);
    |                       ^^^^^^^^^^^^^^^^^^^^^^ the trait `ThirtyTwoByteHash` is not implemented for `hashes::sha256::Hash`
    |
    = help: the following other types implement trait `ThirtyTwoByteHash`:
              bitcoin::secp256k1::bitcoin_hashes::sha256t::Hash<T>
              bitcoin::secp256k1::bitcoin_hashes::sha256::Hash
              bitcoin::secp256k1::bitcoin_hashes::sha256d::Hash
              Sighash
              bitcoin::LegacySighash
              bitcoin::SegwitV0Sighash
              bitcoin::TapSighash
    = note: required for `Message` to implement `From<hashes::sha256::Hash>`

error[E0277]: the trait bound `hashes::sha256::Hash: ThirtyTwoByteHash` is not satisfied
   --> src/policy/satisfy.rs:376:23
    |
376 |         let message = secp256k1_zkp::Message::from(sighash);
    |                       ^^^^^^^^^^^^^^^^^^^^^^ the trait `ThirtyTwoByteHash` is not implemented for `hashes::sha256::Hash`
    |
    = help: the following other types implement trait `ThirtyTwoByteHash`:
              bitcoin::secp256k1::bitcoin_hashes::sha256t::Hash<T>
              bitcoin::secp256k1::bitcoin_hashes::sha256::Hash
              bitcoin::secp256k1::bitcoin_hashes::sha256d::Hash
              Sighash
              bitcoin::LegacySighash
              bitcoin::SegwitV0Sighash
              bitcoin::TapSighash
    = note: required for `Message` to implement `From<hashes::sha256::Hash>`

error[E0277]: the trait bound `hashes::sha256::Hash: ThirtyTwoByteHash` is not satisfied
   --> src/policy/serialize.rs:307:23
    |
307 |         let message = secp256k1_zkp::Message::from(sighash);
    |                       ^^^^^^^^^^^^^^^^^^^^^^ the trait `ThirtyTwoByteHash` is not implemented for `hashes::sha256::Hash`
    |
    = help: the following other types implement trait `ThirtyTwoByteHash`:
              bitcoin::secp256k1::bitcoin_hashes::sha256t::Hash<T>
              bitcoin::secp256k1::bitcoin_hashes::sha256::Hash
              bitcoin::secp256k1::bitcoin_hashes::sha256d::Hash
              Sighash
              bitcoin::LegacySighash
              bitcoin::SegwitV0Sighash
              bitcoin::TapSighash
    = note: required for `Message` to implement `From<hashes::sha256::Hash>`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `simplicity` (lib test) due to 3 previous errors

rust version: 1.74.1
cargo clippy --all-targets actually does the same locally, not sure why it's not caught by CI

Sigh. Another case of outdated Cargo.lock file.

Frustrating, but yes: The set of dependencies that cargo resolves can make or break the crate :/

cc https://github.com/rust-bitcoin/rust-secp256k1/issues/673


Check if condition is empty before constructing MultiValuer

Closes #13393

@johnnyjian thanks for the PR.  Thanks!

@johnnyjian thanks for the PR.  Thanks!

@e-dard While looking at the 1.8 branch, I found that @seebs had fix it in another way: https://github.com/influxdata/influxdb/commit/5525240d

@johnnyjian in that case I'll close this out. Thank you very much for your contribution!


[BUG] Skipped doctests still being run?

Describe the bug
This main test fails due to a doctest which is supposed to be skipped.
https://github.com/aeon-toolkit/aeon/actions/runs/5478731072/jobs/9979784969
Steps/Code to reproduce the bug
N/A
Expected results
Doctests with the skip comment are skipped.
Actual results
A doctest line with a skip comment is run and fails.
Versions
N/A

weird! Maybe is not quite formatted correctly, I'll take a look

think its meant to be
#DOCTEST: +Skip
not
#DOCTEST +Skip


[BEAM-6062] Spark runner do not show Beam metrics in Spark Web Interface

MetricsContainerStepMap#toString overwritten to show Beam metrics in Spark Web Interface.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

Run Python PreCommit

Run Spark ValidatesRunner

Python build seems to be broken at the moment, that should not impact merging this PR since it does not touch python or the build files at all.

Run Spark ValidatesRunner


Changing markers cause flickering

Maybe this is more like a howto than a bug. If I change the data basis for the markers (the 'stations' Array), all markers shortly disappear before they appear again. This happens even when there is no actual change for the active markers.
At the corresponding list view (with the exact same data basis), Vue does the mutation/merging smoothly (even animated). But on the map, the markers get deleted and re-created (so it seems.) Here ist some code from the Component:
<GoogleMap
  id="map"
  ref="mapRef"
  :api-key="apikey"
  style="width: 100%; height: 60vh; max-height: 120vw"
  :center="center"
  :zoom="zoom"
>
  <Marker
    v-for="station in stations"
    :key="station.id"
    :options="{
      title: station.name,
      position: { lat: station.geoPos.lat, lng: station.geoPos.lng },
      icon: markerIcon(station)
    }"
  />
</GoogleMap>

computed: {
  apikey () {
    return this.$store.state.googlemapsapikey;
  },
  zoom () {
    return this.$store.state.map.zoom;
  },
  center () {
    return this.$store.state.map.center;
  },
  stations () {
    return this.$store.state.stations;
  }
}

And here is some code from the global Vuex store:
state () {
  return {
    googlemapsapikey: 'xxxxxxxxxxx',
    map: {
      radius: 10000,
      zoom: 14,
      center: {
        lat: 49.7971716,
        lng: 9.9269455
      }
    },
    stations: []
  };
},
mutations: {
  fetchStations (state) {
    Axios.get('/station/geo', {
      params: {
        lat: state.map.center.lat,
        lng: state.map.center.lng,
        radius: state.map.radius || 10000
      }
    }).then(response => {
      if (response.status === 200) {

        // change the reactive station data
        state.stations = response.data;
      }
    });
  }

Is there a way to enable smart/lazy marker changing behaviour?

Hey @gerritvanaaken,
You're right we're currently watching the config/options object for each of these components and destroying then recreating them when the watcher fires. It seems that Vue performs a simple comparison for objects and will fire the watcher even if non of the child properties has changed. Please refer to these:

https://github.com/vuejs/vue/issues/5776#issuecomment-304570693
https://forum.vuejs.org/t/watch-doesnt-fire-if-value-is-same/38002/2

The only way around this is to perform deep comparison on the config objects to pinpoint the properties that have changed and react to them. It would require special treatment for each property though (and consideration of duration/easing for animations). We're sort of doing this kind of special treatment for the zoom and center props of the base GoogleMap component. Doing it for all properties of other components is another beast though.

Than you for providing us this awesome library.
We are a user of this open source and we are in desperate need your help about adding this specific function to the library since it is essential for our system.
We would be appreciated if you could help us about it. Thank you again.

@dudeo4106 this is a feature request and like all feature requests we're open to a PR if you need this please consider this path

I need the same thing fixed too. I'm willing to help if you tell me how to get started. It seems to me that if there's a way to compare the options for the existing Marker in the watch section, it would be easy to not update the marker.

@gmalignon Yes that's something I had considered (the deep object comparison) but didn't implement, fearing perf issues. Might give it a try and see how it goes.

I ended up managing the markers myself with the map reference. I simply keep track of the one that's clicked and change the icon dynamically, also resetting the one previously selected. I also use setVisible true or false depending on if I want to show the marker or not. There's no flickering at all (since the markers are not removed and added again) and it's very quick.


react-query/devtools's module entry points to a CJS file

Describe the bug
Essentially reposting https://github.com/tannerlinsley/react-query/issues/3505 here.
Though Vite reverted that change, I believe it is a bug in react-query.
The module field of react-query/devtools points to a CJS file that reexports from a subfolder containing nothing but a package.json, and it expects the reexport resolves to the module field of that subfolder.
It violates the convention that module field should contain ESM syntax.

To provide different exports for different environments in the ES module system, maybe the exports field can help here: https://nodejs.org/api/packages.html#community-conditions-definitions
Your minimal, reproducible example
https://github.com/akharkhonov/vite-react-query
Steps to reproduce

Install dependencies yarn --frozen-lockfile
Run dev mode yarn dev
Open devttools and see errors

Expected behavior
No errors.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome
Version: Version 100.0.4896.88 (Official Build) (arm64)

react-query version
3.34.19
TypeScript version
4.6.3
Additional context
No response

I would be very grateful if you could help with fixing this. My knowledge about modules and bundling is quite limited to be honest

:tada: This issue has been resolved in version 4.0.0-beta.6 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature Request: Adding recent outputs from the terminal into the prompt

For when you are debugging something in the terminal or you are executing a standard set of commands for which the errors or the outputs would be helpful in generating a good autocomplete.
It is my understanding that the main problem is that terminals do not have access to the values on the display as well stdout and stderr after the command is run.
Here is some good discussion regarding using  PROMPT_COMMAND

https://unix.stackexchange.com/questions/460651/is-prompt-command-a-colon-separated-list
https://stackoverflow.com/questions/3058325/what-is-the-difference-between-ps1-and-prompt-command
https://stackoverflow.com/questions/24283097/reusing-output-from-last-command-in-bash
https://stackoverflow.com/questions/63670957/how-to-log-every-single-command-executed-from-shell-script

This code in a .bashrc file will just set AC_RET to the exit code of the previous command.  Not quite what's needed
function ac_prompt_command {
    AC_RET=$?
}
export PROMPT_COMMAND=ac_prompt_command

I could see a system when people use script command to log outputs.  It could essentially capture the terminal behavior and provide it to the autocomplete operating within the script session.
I'm going to wait until I get more feedback on this.

This type of work will be moved to https://github.com/closedloop-technologies/justbuild
Merging this issue with #6  and only focusing on

get currently selected line contents or clipboard?


CMake Warning ...JPEG not found

Error
cmake ..
-- The C compiler identification is GNU 8.3.0
-- The CXX compiler identification is GNU 8.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- No build type selected, default to Release
-- No target type selected, default to shared library
CMake Warning at CMakeLists.txt:58 (message):
  JPEG not found.  libuvc will not support JPEG decoding.

-- Configuring done
-- Generating done
-- Build files have been written to: /home/pi/GetThermal/libuvc/build

Problem
if(JPEG_FOUND)
  message(STATUS "Building libuvc with JPEG support.")
  include_directories(${JPEG_INCLUDE_DIR})
  SET(LIBUVC_HAS_JPEG TRUE)
  SET(SOURCES ${SOURCES} src/frame-mjpeg.c)
else()
  message(WARNING "JPEG not found. libuvc will not support JPEG decoding.")
endif()

Proof of libjpeg* install
pi@raspberrypi:~/GetThermal/libuvc/build $ sudo apt policy libjpeg*
libjpeg-dev:
  Installed: 1:1.5.2-2
  Candidate: 1:1.5.2-2
  Version table:
 *** 1:1.5.2-2 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        100 /var/lib/dpkg/status
libjpeg62-turbo-dev:
  Installed: 1:1.5.2-2+b1
  Candidate: 1:1.5.2-2+b1
  Version table:
 *** 1:1.5.2-2+b1 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        100 /var/lib/dpkg/status
libjpeg8:
  Installed: 8d1-2
  Candidate: 8d1-2
  Version table:
 *** 8d1-2 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        100 /var/lib/dpkg/status
libjpeg62-turbo:
  Installed: 1:1.5.2-2+b1
  Candidate: 1:1.5.2-2+b1
  Version table:
 *** 1:1.5.2-2+b1 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        100 /var/lib/dpkg/status

Same issue bro. Did u find any solution to this???

This doesn't matter, the message is informational only. The PureThermal camera does not produce jpeg images.

Appreciate ur immediate reply. Well initially i thought the same and tried using running the project using QTCreator, but then I faced some issues such as shown in the pic. So, trying to build libuvc... and obviously it failed in build.

After going through several digging and installing QT & other dependencies, left out 3 issues. Unfortunately, I don't have the expertise to solve this issue.

To solve the build issue libuvc, I tried this GitHub issue page [https://github.com/libuvc/libuvc/issues/109]. Seems that this guy fixed the issue using libuvc official. I see that qt warning is somewhat related to not using getthermal repository libuvc.


Adding simple label to slices of pie chart

can I add some text to the chart pie??
I don't see any text api in the document

Regarding @aml987's jsfiddle, here's a working example: http://jsfiddle.net/zetzt9gu/255/


Time logicalTypes

Adds handling for time and timestamp logical types …The avro 1.8 specification defines multiple date related logical types and specifies how they should be mapped :

time-millis
time-micros
timestamp-millis
timestamp-micros

This PR adds the following mappings :

(int, time-millis) => java.time.LocalTime
(long, time-micros) => java.time.LocalTime
(long, timestamp-millis) => java.time.Instant
(long, timestamp-micros => java.time.Instant

Possible further inprovements to this feature :

Make the mapped types configurable.
Add mappings for date and duration types.
Propose a more general mecanism to extends type and logicalType mapping to handle custom user types (iso8601 dates come to mind for example)

--
I tried to fix the tests,  I managed to do so for the unit tests but I am unsure how to fix the scripted sbt tests. They fail in the same way with and without my modification ...

Update: There is also a need to upgrade to Avro 1.8.2 to support timestamp_ms, so I will make a new PR.

Replaced by #30

Sorry not to have rebase earlier I have been busy with other things and
didn't get to this
Thanks for taking the time to address it


Add system role 'everyone'

[ ] prepopulate sys_roles table with everyone role (we can simly use 1 for it's ID)
[ ] auto append role to each user (when authenticated)

@titpetric comments?

So, everyone should be a sticky role, all users should be members of it, and by default that role has access to compose and messaging? LGTM

Also added admin/Administators role with all permissions set to allow.


Remove all references to old shouldBatch option in 0.5 preview

It's mentioned in a lot of comments and some commented-out tests

done


I'm seeing a lot of comments with brakets in HTML after running yarn dev.

Versions

nuxt: v3.0.0
node: v18.13.0

Summary
I'm seeing a lot of comments in HTML after running yarn dev.
Steps to reproduce

Clean install VS Code
Clean install Nuxt with no other dependencies
Remove app.vue
Create pages folder and add an index.vue
yarn dev

What is Expected?
No comments should appear in the HTML on Chrome browser
What is actually happening?
Output HTML contains comments with brakets such as [ or ].
This is happening for each layout, page, or component that I use, so the resulting HTML is getting more and more flooded with these comments as I try to add another page/component.
The comments appear not only after yarn dev, but also in production build as well.

This is Vue 3 behaviour and required for supporting components without a single root element.


[GOBBLIN-1527] Add finder latestFlowGroupExecutions to FlowExecutions endpoint.

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1527
"Extend REST flowexecutions endpoint with finder latestFlowGroupExecutions"

Description

[x] Here are some details about my PR, including screenshots (if applicable):

This adds the new endpoint while augmenting both (primary) forms of JobStatusRetriever (Mysql and FS) to support querying flow executions across a flow group.
It leverages the recent refactoring of https://github.com/apache/gobblin/pull/3378
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Included enhancements of existing unit tests cover added code paths.
Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3382 (4be6178) into master (d9d2222) will decrease coverage by 3.38%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #3382      +/-   ##
============================================
- Coverage     46.41%   43.02%   -3.39%
+ Complexity    10157     1960    -8197
============================================
  Files          2056      396    -1660
  Lines         80099    16961   -63138
  Branches       8949     2090    -6859
============================================
- Hits          37179     7298   -29881
+ Misses        39471     8853   -30618
+ Partials       3449      810    -2639

Impacted Files
Coverage Δ

...he/gobblin/metastore/MysqlJobStatusStateStore.java
0.00% <0.00%> (ø)

.../org/apache/gobblin/metastore/MysqlStateStore.java
8.09% <0.00%> (-0.17%)
:arrow_down:

...obblin/util/function/CheckedExceptionFunction.java
0.00% <0.00%> (ø)

...a/org/apache/gobblin/cluster/GobblinHelixTask.java
60.21% <0.00%> (-2.16%)
:arrow_down:

...a/org/apache/gobblin/runtime/RateBasedLimiter.java

...ion/hive/converter/AbstractAvroToOrcConverter.java

...action/mapreduce/CompactionOrcJobConfigurator.java

...ent/copy/replication/ReplicationConfiguration.java

...sedconstructs/CompactionLauncherWriterBuilder.java

.../extractor/extract/kafka/UniversalKafkaSource.java

... and 1648 more

Continue to review full report at Codecov.

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


ImportError: cannot import name 'AnalogSGD' from 'aihwkit.optim'

Description
I tried to run the py files under  tests/ and examples/ but it will return an error: ImportError: cannot import name 'AnalogSGD' from 'aihwkit.optim'

How to reproduce
python tests/test_utils.py

Expected behavior

Other information
Follow the installation guide and python version is 3.7.3

Pytorch version:
Package version:0.2
OS:MAC Catalina
Python version: 3.7.3
Conda version (or N/A):

Hi @spwjr ,
and thanks for reporting! It seems there might be a mismatch between the version of aihwkit that you are using (which I'm assuming you installed from pip) and the "version" of the examples that you are using (in this case, I'm assuming you are using the master branch from this repo).
If that is the case, the master branch contains code that has not been released as a stable version in pip yet - in a way, it is ahead by some commits. In particular, at #54 we introduced a more comfortable from aihwkit.optim import AnalogSGD way to import the optimizer instead of the previous from aihwkit.optim.analog_sgd import AnalogSGD.
In order to solve the mismatch, can you try either:

using the examples from the v0.2.0 tag instead of the master branch: that tag contains the codebase (including tests and examples) at the time the 0.2.0 release was made. If you cloned the repository, git checkout v0.2.0 would change to the right tag.
use the code from the master branch instead of the pip-installed 0.2.0 release - this involves some more steps (most notably compilation, and dealing with the pythonpath - they are hopefully outlined at the docs) for setting up the development environment, but would allow you to use the new features introduced after 0.2.0.

Thanks Diego
I tried both
1:switch to v0.2.0 tag and it works !
2:with a new terminal and virtual env I have tried the method described in the Development setup page
and running the example from master branch, it will show error regarding symbol can not be found,  for example
from aihwkit.simulator.rpu_base import devices
ImportError: dlopen(/ibm_test/aihwkit_env/lib/python3.7/site-packages/aihwkit/simulator/rpu_base.cpython-37m-darwin.so, 2): Symbol not found: __ZN3c104impl23ExcludeDispatchKeyGuardC1ENS_11DispatchKeyE
Referenced from: /project/ibm_test/aihwkit_env/lib/python3.7/site-packages/aihwkit/simulator/rpu_base.cpython-37m-darwin.so
Expected in: flat namespace
in /project/ibm_test2/aihwkit_env/lib/python3.7/site-packages/aihwkit/simulator/rpu_base.cpython-37m-darwin.so
The following are the steps I have tried based on the help page, please correct me if I missed some steps.
1:python3 -m venv aihwkit_env
2:cd aihwkit_env/
3:source bin/activate
4:git clone https://github.com/IBM/aihwkit.git
5:brew install openblas
6:pip install cmake scikit-build torch pybind11
7:pip install -v aihwkit
8:python setup.py build_ext --inplace

Thanks for the detailed feedback @spwjr ! Can you attach the output of your last step (python setup.py build_ext --inplace)? Specifically, for trying to see which compiler are you using, which we can verified by the output of the command in a line similar to:
-- The CXX compiler identification is ...

In osx, we currently recommend using the compiler that is part of the latest Xcode (Apple clang), and  it might be that you are using gcc and running into an issue similar to https://github.com/RcppCore/RcppArmadillo/issues/224#issuecomment-386943484 (thanks to @maljoras for the pointer!). If the command is picking up gcc automatically, can you try instructing it to use clang via:
python setup.py build_ext --inplace -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++

And see if the Symbol not found reappears?

Hi Diego
Thanks for the feedback,

The C compiler identification is AppleClang <IP_ADDRESS>00032
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00032

after I use python setup.py build_ext --inplace -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++
it stop and report an error
/project/ibm_test/aihwkit_env/lib/python3.7/site-packages/torch/include/torch/csrc/python_headers.h:17:2: error:
"Python 2 has reached end-of-life and is no longer supported by PyTorch."
#error "Python 2 has reached end-of-life and is no longer supported by PyTorch."
n file included from /project/ibm_test/aihwkit_env/aihwkit/src/aihwkit/simulator/rpu_base_src/rpu_base.cpp:13:
An error occurred while building with CMake.
Command:
cmake --build . --target install --config Release --
Source directory:
/project/ibm_test/aihwkit_env/aihwkit
Working directory:
/project/ibm_test/aihwkit_env/aihwkit/_skbuild/macosx-10.15-x86_64-3.7/cmake-build

Interesting - it seems that for some reason the build system is picking up the wrong Python version during your latest run.
Can you:

verify that you are running the command inside your activated aihwkit_env virtualenv (it seems to be the case, but just for double-checking)
run make clean and remove the _skbuild directory (it is a temporary folder used by the build system for caching: by removing it, we ensure you attempt compiling in a "clean" state)
try compiling again and attach the log of the output? In the same way it prints some information about the compiler identification, it also outputs information about the Python version it identified, ie:

...
-- Found PythonInterp: ...
-- Found PythonLibs: ...
-- Found Python: ...
-- Found Torch: ...

In the same spirit as the flags for overriding the compiler detection, there are some flags that you can pass to setup.py that allow pointing the build system to a specific Python version:
-DPYTHON_EXECUTABLE=/something -DPYTHON_INCLUDE_DIR=/somethingelse -DPYTHON_LIBRARY=/other

The values for those variables would be the related to your virtualenv - however, let's see if we can find out why it is not picking the right ones automatically, which is much more convenient and fail-proof.

Thanks Diego, the execution path is under aihwkit_env
I did your suggestion : make clean and re-run python setup.py build_ext --inplace -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++
the log shows the version below
-- Found OpenBLAS libraries: /usr/local/opt/openblas/lib/libopenblas.dylib
-- Found OpenBLAS include: /usr/local/opt/openblas/include
-- Found PythonLibs: /Users/xxx/.pyenv/versions/3.7.3/lib/libpython3.7m.a (found version "3.7.3")
-- Found PythonInterp: /Users/xxx/project/ibm_test3/aihwkit_env/bin/python (found version "3.7.3")
-- Found PythonLibs: /Users/xxx/.pyenv/versions/3.7.3/lib/libpython3.7m.a
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- Performing Test HAS_FLTO_THIN
-- Performing Test HAS_FLTO_THIN - Success
-- Found pybind11: /Users/xxx/project/ibm_test3/aihwkit_env/lib/python3.7/site-packages/pybind11/include (found version "2.6.1" )
-- Found Python: /Users/xxx/project/ibm_test3/aihwkit_env/bin/python3 (found version "3.7.3") found components: Interpreter
-- Found Torch: /Users/xxx/project/ibm_test3/aihwkit_env/lib/python3.7/site-packages/torch/include;/Users/xxx/project/ibm_test3/aihwkit_env/lib/python3.7/site-packages/torch/include/torch/csrc/api/include
-- Configuring done
-- Generating done
The result of error message from executing example is the same, thanks

Thanks for the detailed output - it seems on this round indeed it picked up the right compiler, and the right Python. Assuming that the compilation ended successfully:

The result of error message from executing example is the same, thanks

Do you mean that the error you get is this one from https://github.com/IBM/aihwkit/issues/65#issuecomment-723367269?
from aihwkit.simulator.rpu_base import devices
ImportError: dlopen(/ibm_test/aihwkit_env/lib/python3.7/site-packages/aihwkit/simulator/rpu_base.cpython-37m-darwin.so, 2): Symbol not found: __ZN3c104impl23ExcludeDispatchKeyGuardC1ENS_11DispatchKeyE
Referenced from: /project/ibm_test/aihwkit_env/lib/python3.7/site-packages/aihwkit/simulator/rpu_base.cpython-37m-darwin.so
Expected in: flat namespace
in /project/ibm_test2/aihwkit_env/lib/python3.7/site-packages/aihwkit/simulator/rpu_base.cpython-37m-darwin.so

If the paths shown are similar (specifically, if they include lib/python3.X/site-packages) this likely points to aihwkit being installed in the virtualenv, and when executing, is trying to use the downloaded library instead of the library that you just compiled - and actually, if that is the case, it seems you are being hit by #52.
So, in order to make sure that you use the compiled library from master for running the examples, can you:

remove the installed stock version of aihwkit:$ pip uninstall aihwkit

rebuild the shared library (likely not really needed, but just for making sure):$ make clean
$ python setup.py build_ext --inplace -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++

run the examples with the right PYTHONPATHPYTHONPATH=src/ python examples/1_simple_layer.py

And let me know if that does the trick? We'll look into tuning a bit more the developer install docs highlighting a bit more some particular points (the details about PYTHONPATH, for example) and adding others.

Hello Diego,
Thanks for the detailed answer!
I got the same error like this one.
and after I tried prcodeure in the your new post
$ make clean
$ python setup.py build_ext --inplace -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++
run the examples with the right PYTHONPATH
$ PYTHONPATH=src/ python examples/1_simple_layer.py
It is working now!

Hi Diego
My part is also working now
I don't uninstall aihwkit
but just execute the following steps
$ make clean
$ python setup.py build_ext --inplace -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++
PYTHONPATH=src/ python examples/1_simple_layer.py
Thanks for your help!

For MacOS user, if you still get a similar error you can create a new path and follow the following procedure:
python3 -m venv aihwkit_env
cd aihwkit_env/
source bin/activate
cd aihwkit
git clone https://github.com/IBM/aihwkit.git
brew install openblas
pip install cmake scikit-build torch pybind11
pip install -v aihwkit
pip install torch torchvision torchaudio
(optional) pip install matplotlib
make clean
python setup.py build_ext --inplace -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++
PYTHONPATH=src/ python examples/1_simple_layer.py
Hope this one help :)

Hello,
I'm following the exact same steps like the ones listed above but I run into this error instead which is weird because I've checked that this package has indeed been installed via pip:

says it couldn't find pybind cmake config path and also I think after fixing this error the build phase will result in another error saying that it can not find torch path but the torch has been installed just like pybind11

Steps I've followed:
python3 -m venv aihwkit_env
cd aihwkit_env/
source bin/activate
cd aihwkit
git clone https://github.com/IBM/aihwkit.git
brew install openblas
pip install cmake scikit-build torch pybind11
pip install -v aihwkit
pip install torch torchvision torchaudio
(optional) pip install matplotlib
make clean
python setup.py build_ext --inplace -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++
PYTHONPATH=src/ python examples/1_simple_layer.py
Note: I'm using python 3.8.6 would this be a problem?

@diego-plan9 Do you know what's going on? Thanks!

@spwjr and @HungYangChang - glad that you have been able to compile, and thanks as well for sharing your tips and flows! It does help everyone that might be facing similar problems. As hinted earlier, I'll try to revise/extend the docs to reflect the conversation.
@jhu960213 from the screenshot, I think we can chalk it (at least partially) to a _skbuild caching issue - the screenshot seems to be missing some lines that are only printed when starting from a clean state. The _skbuild folder helps in a number of cases (for example, if modifying the c++ files, allowing to only recompile the changed bits), but the caching unfortunately is not smart enough for bigger changes such as changing dependencies, etc. It's also a bit out of our control, so in case of doubt removing the _skbuild folder (or running make clean since #69) is recommended before compiling.

Also is there a way to make aihwkit work with Jupiter notebooks?

Would you mind opening a new issue with the issues you might be encountering related to Jupyter? In theory it should be a matter of making jupyter aware of the right PYTHONPATH (in the case of compiling manually).

Hello! @diego-plan9
@jhu960213  is one of my partners, now it seems he already solved the problem.  I will let them post his flow later.
As for opening a new issue for Jupyter setting. We will try it later and report our problems.
Thanks!

@diego-plan9 Thanks for the advice I will do that from now on! And I will also make an issue about the Jupyter notebook!
As for the flow of my current setup if anyone else had been experiencing caching related issues I suggest doing the following:

delete the _skbuild folder or do $ make clean before building with setup.py
Follow the flow posted by @HungYangChang:

python3 -m venv aihwkit_env
cd aihwkit_env/
source bin/activate
cd aihwkit
git clone https://github.com/IBM/aihwkit.git
brew install openblas
Note: now instead of installing all the dependencies with pip activate conda and install all of them using conda forge
or from any of their repositories and make sure the versions match with the ones listed in the advanced installation guide.
make clean (just to be sure...optional at this point if you've already removed the _skbuild folder)
python setup.py build_ext --inplace -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++
PYTHONPATH=src/ python examples/1_simple_layer.py
Then after all this, it should work hopefully..... :)
-J.H

Closing as part of the 0.3 release cleanup - thanks for all the feedback and information, and don't hesitate on opening a new issue or commenting back if needed, as there has been quite some changes included in the release.


Add base layers, overlay layers and layer switcher

Base layers:

OSM India
Indian Railways
NASA True Marble satellite
Bhuvan satellite

Overlay layers:

Highways
Postal map
Place Connectivity

Layers control made using this example: http://leafletjs.com/examples/layers-control.html

@planemad looking at this now -

You think the connectivity layer is useful for 'most' people looking at openstreetmap.in?
What's the license for NASA Marble layer? Do we need all those base layers? Trying to see if this actually makes sense.

Highways and post codes :+1:

@geohacker the layering are more of a proof of concept and not for any immediate practical use. Hopefully we'll have requests coming in for new layer ideas with this.
NASA products are cc-0


SArray return type

for R1->R1 functions current code is inefficient since it allocates and array to hold the return value. Add option to make_function to return SArray instead.

completed


support install crd by helm3

Description
Now support to install crd by helm 2 as well as helm 3
hook: "crd-install will be unknown and skipped when helm3 is used
Fixes
crd cannot be installed neither by helm 2 nor helm 3

Any idea when this will be available?


Android: Autoscroll

Like it says on
https://github.com/samuelclay/NewsBlur/issues/1171

@samuelclay Is this a feature that we still want to add support for?

Nah, nobody is asking for it but me.

I still use it on iOS but until somebody on Android wants Autoscroll let's punt on it.


doc: python-tambo is in the stable EPEL repo

The EPEL updates-testing period is over and I've pushed python-tambo to the stable repo. Drop the references to epel-testing.

Does this mean that this block in our functional tests is not needed? https://github.com/ceph/ceph-medic/blob/master/tests/functional/playbooks/setup.yml#L31-L35

Great catch, yes


Update Chatbot for Travel

Hi can you check for me my simple travel chatbot and then accept my merge to master request. Thank you


Enabling typescript.preferGoToSourceDefinition breaks Intellisense

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

VS Code Version:
Version: 1.86.2
Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda
Date: 2024-02-13T19:42:12.210Z
Electron: 27.2.3
ElectronBuildId: 26908389
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.3.0
OS Version: Mac OS 14.3.1 (23D60)

Steps to Reproduce:

Download the above version of VSCode
Enable "typescript.preferGoToSourceDefinition": true in settings
Try and cmd + click functions etc in TypeScript files, the Loading text will show in the intellisense hover over, suggestions aren't loaded, colours for any functions, classes, import etc aren't applied to new code added

We need a way to reproduce this

I could send you my typescript verbose log from VSCode if it's helpful and you have a secure way which I could do this? @RyanCavanaugh The outlined way in the issue is the only way which I can reproduce the issue

Usually for issues like these, a log is not enough.
Is your project big (> 250,000 LOC or so) ? If so, this is likely just ts server running out of memory, and the option shouldn't be enabled

No it's a pretty fresh repository it's a monorepo but only has a Next application which is very small and a small component library so nowhere near that many lines of code. I've used that setting with much larger repos and it worked fine. Maybe there's something wrong with my tsconfig?


Querydsl Projection.bean not finding setters when usin fluent pattern

We use fluent setters pattern in our Entities and DTOs so trying to use Projections.bean I found that querydsl cant find setters for QBean.
I think it is convenient to support fluent setters as some good programming approaches and patterns like builder pattern take advantages on it.
If I can find some time I'll also try to submit a pull request if it is welcome...
What you guys think about it?

the key code:

java.beans.Introspector

if (void.class.equals(resultType) && name.startsWith(SET_PREFIX))

java.beans.PropertyDescriptor

if (!writeMethod.getReturnType().equals(void.class)) {                     writeMethod = null; }


Rewrite unaryNot EXPR

Rewrite UnaryNotExpr so that indexes can be used during indexScan. Following rules are supported:

Colasspe nested UnaryNot expression

e.g. !!(expr)  =>  (expr)

Rewrite the combination of logical expr and unary expr

e.g. !(a && b && c)  =>  (!a || !b || !c)

Rewrite the combination of relational expr and unary expr

e.g. !(a > b)  =>  (a <= b)

[x] Add support to TCK frame so that operator info in the execution plan can be compared in the CI test. https://github.com/vesoft-inc/nebula-graph/pull/850

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


[19.03 backport] Revert docker/swarmkit#2804

backport of https://github.com/moby/moby/pull/39281 for 19.03.
Local changes applied cleanly, but the vendor.conf did not; fixed by changing vendor.conf to point to the bump_v19.03 branch (which includes https://github.com/docker/swarmkit/pull/2863), and running vndr again.

- What I did
Reverts the change to swarmkit that made all updates set UpdateStatus to Completed.
See docker/swarmkit#2861
related: https://github.com/docker/swarmkit/pull/2804, https://github.com/moby/moby/pull/38520
fixes https://github.com/docker/swarmkit/issues/2861
fixes https://github.com/moby/moby/issues/39023
- How I did it
Returned the integration test to the way it was before

thank you sebastiaan 🙌

windows failure is almost certainly unrelated

Yes, RS1 failure is unrelated, and being looked at

WIP, waiting for upstream to be merged


feat: include x-deno-ray in error message

Displays the x-deno-ray id when the error is an internal server error.

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


Bug in MXML with Bindable Constants

while creating an example for a new component, I found a bug in MXML with constants. In the following example:
<j:beads>
        <js:ContainerDataBinding/>
    </j:beads>

<j:Wizard id="wizard">
        <j:WizardPage id="firstPage">
            <j:step>
                <j:WizardStep name="second_page"
                            nextStep="second_page"
                            initialPage="true"/>
            </j:step>
        </j:WizardPage>

        <j:WizardPage id="secondPage">
            <j:step>
                <j:WizardStep name="{MyModel.SECOND}"
                            previousStep="{MyModel.FIRST}"
                            nextStep="{MyModel.THIRD}"/>
            </j:step>
        </j:WizardPage>
</j:Wizard>

Each WizardPage has WizardStep that is a simple class that holds the data used by the component to know what's the previous and next page, and more, so here we have only normal getters and setters.
Now the bug: The first step don't use binding while the second binds constants to the member properties of the class.
I'm finding that at run time using constants with binding Royale fails to retrieve the data, but if I set normal values, the component is capable to access the data and works fine.

test in real app, thanks for solving Greg! :)


fix: Extend k8s synthetic test timeout for nightly build.

The current timeout is 60 minutes. Seems it needs 10 more minutes to complete. Thus, update the timeout to the larger level "eternal", which is 3 hours.

This change is


iPad Pro webviews not detected

I am using browser gem's browser.platform.ios_webview? method to detect requests coming from iOS webviews.
It seems to work fine except for the iPad Pro. For iPad Pro this method returns false instead of true.
Any idea why this might be happening?

Rails version: 5.2
Browser gem version: 4.0.0

Can you please post the user agent?

User Agent: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15) AppleWebKit/605.1.15 (KHTML, like Gecko) WeTime iOS"

@fnando I ran into the same error. Is there any solution to this issue?

I believe this is related to https://github.com/fnando/browser/issues/404. There's nothing I can do, unfortunately.

@saikiransripada I got it to work.
Apparently, the platform on iPad Pro is not iOS, it is Mac OS. And according to the code in the gem, they determine that it is a webview by checking that the user agent should not contain "safari".
So, if the following is true then it's an iPad Pro webview:
browser.platform.name.downcase.include?('macos') && !request.user_agent.downcase.include?('safari')
this worked for me.

Thanks @asad-imtiaz you made my day

Testing the solution @asad-imtiaz suggests - in 2024 and iPadOS 17.1.1, the platform name iPad Pro 12.9 reports is "macintosh".


Modify the resetWriterIndex. There is no reason to implements by assigning directly instead of invoking writerIndex.

Modify the resetWriterIndex. There is no reason to implements by assigning directly instead of invoking writerIndex.
Motivation:
If someone invoke writeByte(),  markWriterIndex(), readByte() in order first, and then invoke resetWriterIndex() should be throw a IndexOutOfBoundsException to obey the rule that the buffer declared "0      <=      readerIndex   <=   writerIndex    <=    capacity".
Modification:
Changed the code writerIndex = markedWriterIndex; into writerIndex(markedWriterIndex); to make the check affect
Result:
Throw IndexOutOfBoundsException if any invalid happened in resetWriterIndex.

@kakashiio ping

@kakashiio ping... can you add the tests ?

@normanmaurer Okay,let me try tomorrow. I have a lot of work to do in the past several days.

Thanks a lot 👍

Am 26.02.2018 um 10:43 schrieb kaka<EMAIL_ADDRESS>@normanmaurer Okay,let me try tomorrow. I have a lot of work to do in the past several days.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks.. Merged with https://github.com/netty/netty/pull/7750 and opened https://github.com/netty/netty/pull/7751


Add GH Action to test cross-compilation

Strictly speaking, cross-compiling with rb-sys isn't foolproof; no software is. In Commonmarker, I poached a lot of ideas from Nokogiri on how cross-platform gems should be tested. I created three main tests:

The compilation output is tested; that is, the gem configured rb-sys correctly to generate a valid {so, bundle} file
The gem can be installed on another platform; this tests that the cross compilation itself works by downloading a previously compiled artifact, unpacking it, and attempting to execute the tests
A generic version of the gem can be installed on a platform with sufficient Ruby/Rust tooling; this tests that, for a platform where a gem version was not uploaded to RubyGems, the gem can still be built and installed (think, Compiling native extensions... on like solaris or something)

Of these, only the first is the most relevant to every gem. 2 suggests an error in the build-pipeline (ie., rb-sys), because if a gem can't install on a target system it might mean it was not compiled correctly. (Here's what that test looks like.)
3 opens the door to supporting platforms that are uncommon, or at the very least, untested on GitHub Action runners, and so it too can go.
In that light, I've decided to port over 1 into this project and you can see it working here. This should help downstream users also validate that they've configured their project to use rb-sys correctly.

Oh this is an incredible idea. Will dive into this PR this week ❤

Friendly bump! 👋


[BUG] @cap-js/cds-types v0.6.0 - Post install script not working

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Currently when enabling @sap/cds with typescript (using cds --add typescript, typer) and after reinstalling the dependencies, the post installation script doesn't create the symbolic link to the @types folder.
This results in not being able to use the following statement in ts files: import cds from '@sap/cds'.
This can be fixed by manually creating the symbolic link as follows (on Linux):
ln -s /workspaces/advanced-output-management/node_modules/@cap-js/cds-types node_modules/@types/sap__cds
I'm running the project in a dev container with image: mcr.microsoft.com/devcontainers/typescript-node:1-20-bookworm
Expected Behavior
The post install script to automatically create the necessary symbolic link
References
not applicable
Versions

advanced-output-manage

@cap-js/asyncapi
1.0.1

@cap-js/cds-typer
0.23.0

@cap-js/cds-types
0.6.0

@cap-js/hana
1.1.0

@cap-js/openapi
1.0.4

@cap-js/sqlite
1.7.3

@sap/cds
8.0.3

@sap/cds-compiler
5.0.6

@sap/cds-dk
8.0.2

@sap/cds-dk (global)
8.0.2

@sap/cds-fiori
1.2.7

@sap/cds-foss
5.0.1

@sap/cds-mtxs
2.0.2

@sap/eslint-plugin-cds
3.0.4

Node.js
v20.14.0

home
/workspaces/advanced-output-management/node_modules/@sap/cds

Anything else? Logs?
Devcontainer.json configuration:
// For format details, see https://aka.ms/devcontainer.json. For config options, see the
// README at: https://github.com/devcontainers/templates/tree/main/src/typescript-node
{
	"name": "advanced-output-management-devcontainer",
	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
	"image": "mcr.microsoft.com/devcontainers/typescript-node:1-20-bookworm",
	// Features to add to the dev container. More info: https://containers.dev/features.
	// "features": {},
	// Use 'forwardPorts' to make a list of ports inside the container available locally.
	"forwardPorts": [
		4004,
		5000
	],

	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
	"remoteUser": "root"
}

This issue is causing errors in initializing a sample cap project.
PS D:\temp> cds init cap-app-sample
Creating new CAP project in .\cap-app-sample

Adding feature 'nodejs'...

Successfully created project. Continue with 'cd cap-app-sample'.
Find samples on https://github.com/SAP-samples/cloud-cap-samples
Learn about next steps at https://cap.cloud.sap
PS D:\temp> cd .\cap-app-sample\
PS D:\temp\cap-app-sample> cds add sample
Adding feature 'sample'...

Successfully added features to your project.
PS D:\temp\cap-app-sample> cds -v -i

| cap-app-sample         | <Add your repository here>                                                        |
| ---------------------- | --------------------------------------------------------------------------------- |
| @cap-js/asyncapi       | 1.0.1                                                                             |
| @cap-js/openapi        | 1.0.4                                                                             |
| @sap/cds               | 8.0.3                                                                             |
| @sap/cds-compiler      | 5.0.6                                                                             |
| @sap/cds-dk (global)   | 8.0.2                                                                             |
| @sap/cds-fiori         | 1.2.7                                                                             |
| @sap/cds-foss          | 5.0.1                                                                             |
| @sap/cds-mtxs          | 2.0.2                                                                             |
| @sap/eslint-plugin-cds | 3.0.4                                                                             |
| Node.js                | v18.16.0                                                                          |
| home                   | C:\Users\me\AppData\Roaming\npm\node_modules\@sap\cds-dk\node_modules\@sap\cds |

PS D:\temp\cap-app-sample> npm i
npm ERR! code 1
npm ERR! path D:\temp\cap-app-sample\node_modules\@cap-js\cds-types
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c ./scripts/postinstall.js
npm ERR! '.' is not recognized as an internal or external command,
npm ERR! operable program or batch file.

npm ERR!      C:\Users\me\AppData\Local\npm-cache\_logs\2024-07-17T07_23_13_223Z-debug-0.log

package.json has the following entry
  "devDependencies": {
    "@cap-js/sqlite": "^1",
    "@cap-js/cds-types": "^0.6"
  },

changing this to the following allows to proceed with initializing sample project.
  "devDependencies": {
    "@cap-js/sqlite": "^1",
    "@cap-js/cds-types": "^0.2"
  },

Hi everyone,
thanks for pointing out this problem on Windows. We will see what we can do to unblock Windows users.
Best,
Daniel

Hi @daogrady,
I'm not sure if you are aware, but this issue can also be solved without creating a symbolic link.
I've adapted my tsconfig.json with typeRoots like so:
{
  "compilerOptions": {
    "target": "ESNext",
    "module": "NodeNext",
    "moduleResolution": "NodeNext",
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "strict": true,
    "skipLibCheck": true,
    "sourceMap": true,
    "allowJs": true,
    "paths": {
      "#cds-models/*": [
<EMAIL_ADDRESS>      ]
    },
    "typeRoots": [
      "./node_modules/@types",
      "./node_modules/@cap-js"
    ]
  }
}

This is working perfectly fine without the need of a symbolic link. (similar setup like the UI5 team does for the UI5 types)
With that minor difference, that in this case we can't specify the @cap-js/cds-types package explicitly (probably because of the way the package structure is setup, in this case the types are in a dist folder while in the UI5 types these are in a types folder)
Anyway, this feels like a more solid and standard TypeScript configuration. Might be worth considering for you guys :)
Cheers,
Geert-Jan

Hi Geert-Jan,
thanks for pointing this out! We have considered an additional typeRoots entry (among a few other options), but wanted to not burden the user with any additional config they would have to do add to their project (for JS projects, this could even mean the user would need an entire jsconfig.json for just this entry).
If having the typeRoots entry works for you then that is perfectly fine for you to use! 👍
Still, I hope to be able to come up with a solution that works for everyone out of the box.
Best,
Daniel

Hi @daogrady,
I opened the issue on Linux, not on Windows.
I've just checked, v0.6.1 still causes issues on Linux.
I get the same issue on my local installation and in a container running as a GitHub action:

Cheers,
Geert-Jan

Hi Geert-Jan,
sorry for the inconvenience! Is this the same error you encountered originally? It looks like this error pops up in the context fo building/ bundling?
Best,
Daniel

Hi @daogrady,
Seems like a slightly different situation indeed.
What seems to be the issue I'm encountering:

Existing project running @sap/cds  @ 7.9.3
No explicit installation of @cap-js/types
Running npm install -> works fine (adds dependency to @cap-js/cds-types @ 0.2.0)
Running npm update --package-lock-only -> causes error (adds dependency to @cap-js/cds-types @ 0.6.1)

Based on the configuration the last situation shouldn't happen (as @cap-js/cds-types has peer dependency to @sap/cds @ 8)
I'm able to fix this by explicitly installing @cap-js/cds-types @0.2.0 in the project.
I also retested the initial issue (on cds v8) and this issue does seem to be resolved. So maybe lets close this issue, I'll do some further analysis on the existing project and if needed I'll open a new issue.
Cheers,
Geert-Jan

Hi Geert-Jan,
thanks for the analysis of the problem! That is indeed an issue, as cds-types 0.6 should only be used in combination with cds 8. Pipelines pulling in cds-types 0.6 despite its peerDependency to cds 8 is not the desired behaviour and will lead to problems. I will investigate this.
Best,
Daniel

Hi @daogrady,
Seems like a slightly different situation indeed. What seems to be the issue I'm encountering:

Existing project running @sap/cds  @ 7.9.3
No explicit installation of @cap-js/types
Running npm install -> works fine (adds dependency to @cap-js/cds-types @ 0.2.0)
Running npm update --package-lock-only -> causes error (adds dependency to @cap-js/cds-types @ 0.6.1)

Based on the configuration the last situation shouldn't happen (as @cap-js/cds-types has peer dependency to @sap/cds @ 8)
I'm able to fix this by explicitly installing @cap-js/cds-types @0.2.0 in the project.
I also retested the initial issue (on cds v8) and this issue does seem to be resolved. So maybe lets close this issue, I'll do some further analysis on the existing project and if needed I'll open a new issue.
Cheers, Geert-Jan

@chgeo FYI

related: https://github.com/cap-js/cds-types/issues/136

@geert-janklaps @hakimio
thanks for pointing out this incompatibility with cds7 projects. The problem stems from an open dependency range in cds7 which we will fix asap.

@daogrady that's seems to be the case I was worried about yesterday in out discussion.
Yes, it's probably worth closing the dependency range in the next sap/cds patch 7.9.x

Thanks for the fix. Initializing a sample project with CDS@8 works fine now with this this fix.
PS D:\temp\cap-app-sample> npm ls
<EMAIL_ADDRESS>D:\temp\cap-app-sample
+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>

@daogrady, @chgeo
I think part of the problem with CDS V7 projects is that the postinstall script assumes the folder location for the symlink target. https://github.com/cap-js/cds-types/blob/main/scripts/postinstall.js#L17
Would be be more robust to use const pathToModule = require.resolve('@cap-js/cds-types'); so the symlink always has a valid target

Could point.  Should check if this is more robust.

Hi @devinea,
thanks for the suggestion! While I see the general appeal of the more generic approach, I have a hard time seeing the case in this specific scenario. As the script is executed as part of the installation of @cap-js/cds-types, it should always find that package. Could you please point out the circumstances under which targeting the specific folder location is incorrect?
Best,
Daniel

I just experienced this issue with following devDependencies:
"devDependencies": {
"@cap-js/cds-typer": ">=0.1",
"@cap-js/cds-types": "^0.8.0",
"@cap-js/sqlite": "^1",
"@sap/cds-dk": "^8",
"@types/node": "^20.0.0",
"typescript": "^5"
}
cds -v
@cap-js/asyncapi: 1.0.2
@cap-js/cds-typer: 0.31.0
@cap-js/cds-types: 0.8.0
@cap-js/hana: 1.5.2
@cap-js/openapi: 1.1.1
@cap-js/sqlite: 1.7.8
@sap/cds: 8.6.0
@sap/cds-compiler: 5.6.0
@sap/cds-dk: 8.6.1
@sap/cds-dk (global): 8.6.1
@sap/cds-fiori: 1.1.0
@sap/cds-foss: 4.0.2
@sap/cds-mtxs: 2.4.2
@sap/eslint-plugin-cds: 3.1.2
Node.js: v20.17.0
Creating the symbolic link as in @geert-janklaps initial response fixed it for me. I am running VS Code on Mac/Linux


[release/5.0] Previously Source Built Artifacts have differing size when created manually

Describe the Bug
An issue with RHEL CI meant that we needed to manually build and create the Previously Source-Built artifacts archive for .NET 5.0.212. The resulting artifacts tarball is 2.3 GiB vs. previous months being around 1.4-1.7 GiB.

Steps to Reproduce

Grab all CI previously source built artifacts from the legs specified here, except for RHEL:

https://github.com/dotnet/source-build/blob/e01134818d4189e0f402b664c0e0e7cd507624d1/.vsts.pipelines/builds/matrix.yml#L140-L147

Follow the instructions in prepare-artifacts.yml exactly to create the previously source built archive.

Examine the size of the resulting archive.

[Triage] @crummel is this affecting 3.1 as well?

From my research, it seems that we have never had RHEL artifacts in both the 3.1 and 5.0 Previously Source Built Artifacts archives. My guess is that this is a CI issue with the way that the artifacts are uploaded. I'll continue to investigate.

The missing RHEL packages is acceptable as these fall back to CentOS7 artifacts, similar to how release/6.0 is working now.  With the ending EOLs this doesn't seem worth doing at this point.


The host https://app-analytics-services-att.com is considered malicious by Norton 360 when backgrounding the app, Apple Transparency Tracking set to "Ask app not to Track"

Description
If 10.23.0, 10.23.1 are included in the app and Norton 360 is installed on the device, https://app-analytics-services-att.com and https://app-analytics-services.com are flagged as malicious by Norton. (see screenshot).
When you use the app using 10.23.0:

NSPrivacyTracking set to YES
https://app-analytics-services-att.com and https://app-analytics-services.com included in NSPrivacyTrackingDomains

The Norton warning appears in multiple places:

on app launch
while using the app generating events
when backgrounding the app

When you use the app using 10.23.1:

NSPrivacyTracking set to YES
https://app-analytics-services-att.com and https://app-analytics-services.com included in NSPrivacyTrackingDomains

The Norton warning is reduced, appearing:

when backgrounding the app

It is unclear to us what the actual effect of the privacy manifest(s) should be having on this URL. Even after following guidance, adding these problematic URLs to the list, we still see the issue. The latest SDK update has some improvement, but not a complete fix.
Reproducing the issue

Install Norton 360 on iOS 16.5, iOS 17 (we have multiple reports spanning across all these versions).
Open an app that used Firebase Analytics.
When the Apple Tracking Transparency Prompt appears, select "Allow".
Traffic will be submitted https://app-analytics-services-att.com if you audit the traffic. When it is set to "Don't track" https://app-analytics-services.com is called instead and there is no issue.

Notes:
We build a special versions of our apps with various Firebase components removed to narrow this down, as long as Firebase Analytics is set up traffic is called.
In
Firebase SDK Version
10.23.0-10.23.1
Xcode Version
15.3
Installation Method
Swift Package Manager
Firebase Product(s)
Analytics, Crashlytics, Performance
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

This feels closely related to:
https://github.com/firebase/firebase-ios-sdk/issues/12720

After studying this more, we only see the app-analytics-services-att.com traffic if FirebaseApp.configure() is called in code.

For the Firebase Team-  Do you know when the Firebase Team may have a resolution to this issue?
Also, do you know why other applications are not seeing the issue?
Is there a recommendation of any type of code adjustment we should make on our end?

is there any reason to think there is real security exposure to using Firebase right now?

@ncooke3 Hello.  On the Norton site, Norton now rates this url http://app-analytics-services-att.com/ as safe, but mobile users with Norton AV installed on their mobile device still recieve an "unsafe site" warning when shopping our sites.  Can Firebase reach out to Norton to determine what needs to be done so a memebr/customer won't see a warning message?

This should now be addressed with Norton. Please let us know if it's still occurring.


How to generate 360-Degree Scene Video

Thank you for sharing your work! I noticed that on the project page, there's a video showcasing the 360-Degree Scene Results, which is very impressive. However, I couldn't find the code for generating such a video in the run.py script or anywhere else in the repository.
Could you please clarify if this functionality is included in the codebase? If not, it would be great if you could share the relevant code or provide some guidance on how to generate these videos from the model's output.

Thanks for the question! I haven't included this functionality but I'd be happy to share my approach. The following code is licensed as outlined in LICENSE. I haven't had time to create a proper script, so I encourage you to extend it as you see fit.
In essence, I create a json file that describes a camera trajectory for the render.py script in the gaussian-splatting-lightning repository. That script renders the frames and creates a final video. For its usage, please consider the code in that repository.
Here is the bare-bones code that I used to create the demo on the website:
import json
import numpy as np
import math

from pytorch3d.renderer import look_at_view_transform

def r_and_t_to_c2w(R, t):
    coordinate_system_transform = np.ones((3, 3))
    # replace diagonal
    coordinate_system_transform[0, 0] = -1
    coordinate_system_transform[1, 1] = -1
    c2w = np.eye(4)
    c2w[:3, :3] = R[0].numpy() * coordinate_system_transform
    c2w[:3, 3] = t[0].numpy() * np.array([-1, -1, -1])
    return c2w

def interpolate_between(initial_c2w, target_c2w, num_frames, h=480, w=720):
    camera_paths = []
    fx = w
    fov = 2 * math.atan((w / 2) / w) * 180 / math.pi
    for i in range(num_frames):
        t = i / (num_frames - 1)
        t = -(math.cos(math.pi * t) - 1) / 2

        c2w = initial_c2w * (1 - t) + target_c2w * t

        camera_paths.append({
            "camera_to_world": c2w.tolist(),
            "fov": fov,
            "aspect": w / h,
            "enable_model_transform": True,
            "model_sizes": [],
            "model_poses": []
        })
    return camera_paths

pan_left = ... # manually picked 4x4 pose

pan_left_detail = ... # manually picked 4x4 pose

pan_right = ... # manually picked 4x4 pose

projected_c2w = r_and_t_to_c2w(*look_at_view_transform(azim=0, elev=0, dist=0.01))
zoomed_out_c2w = r_and_t_to_c2w(*look_at_view_transform(azim=0, elev=0, dist=5))
# ...

frames_to_generate = 60
h, w = 480, 720

camera_paths = interpolate_between(projected_c2w, zoomed_out_c2w, 60, h, w)
# ...

traj = {
    "camera_type": "perspective",
    "render_height": h,
    "render_width": w,
    "fps": 30.0,
    "seconds": 6.0,
    "is_cycle": False,
    "smoothness_value": 0.0,
    "orientation_transform": [
        [
            1.0,
            0.0,
            0.0,
            0.0
        ],
        [
            0.0,
            1.0,
            0.0,
            0.0
        ],
        [
            0.0,
            0.0,
            1.0,
            0.0
        ],
        [
            0.0,
            0.0,
            0.0,
            1.0
        ]
    ],
    "enable_transform": False,
    "background_color": [
        1.0,
        1.0,
        1.0
    ],
    "sh_degree": 3,
    "camera_path": camera_paths
}

with open("camera_trajectory.json", "w") as f:
    json.dump(traj, f, indent=4)

Please let me know if that helps!


Import @Icenowy GLVNDizd mesa-pvr

From #1

BTW do you want to import my GLVNDizd mesa-pvr from https://github.com/Icenowy/aosc-os-pvr/tree/master/ddk117/mesa-ddk117 ? This will allow coexistence with a normal mesa.

Added to my Todo list

Done as a separated package: https://github.com/cwt-lpi4a/mesa-pvr-ddk117


chore: remove accidental wiremock jar

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.67%. Comparing base (3833592) to head (891b982).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #251      +/-   ##
==========================================
- Coverage   92.55%   89.67%   -2.89%
==========================================
  Files         273      273
  Lines        4095     4095
  Branches      634      634
==========================================
- Hits         3790     3672     -118
- Misses        304      416     +112
- Partials        1        7       +6

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


Update carousel.component.ts

Small API Ref description improvements

Current coverage is 84.14% (diff: 100%)

Merging #1380 into development will not change coverage

@@           development      #1380   diff @@
=============================================
  Files               73         73
  Lines             1961       1961
  Methods             17         17
  Messages             0          0
  Branches           262        262
=============================================
  Hits              1650       1650
  Misses             214        214
  Partials            97         97

Powered by Codecov. Last update a688e6a...b7e05e8


Allow deb packages to be build using docker

Created Makefile target to utilize docker to build .deb files..

@janpekar Thanks for the docker-build, it is a very nice addition


There is something wrong when use highcharts and highmaps at the same time

Description
angular2-highcharts is perfect operation with highcharts, but when i add highmaps modules as official method, it reports error, and it same to effect only one of highcharts and highmaps
How to reproduce
Generate an Angular CLI application, and add angular2-highcharts
Notes
if i just only use highcharts or  highmaps alonely, it has no problem，but when use both of them,app run error.
systemjs.config.js
...
map: {
  ...
  'angular2-highcharts': 'node_modules/angular2-highcharts',
  'highcharts': 'node_modules/highcharts',
}
...
packages: {
  ...
  highcharts: {
    main: './highcharts.js',
    defaultExtension: 'js'
  },
  'angular2-highcharts': {
    main: './index.js',
    defaultExtension: 'js'
  }
}

app.module.js add highmaps module
import { ChartModule } from 'angular2-highcharts';

@NgModule({
    imports: [
       ···
        ChartModule.forRoot(
            require('highcharts'),
            require('highcharts/highmaps'),    //add hightmaps part
        ),
    ],

app.comporent.html use highcharts and highmaps at the same time
<!-- highcharts part -->
 <chart [options]="opt1"></chart>

<!-- highmaps part -->
<chart type="Map" [options]="opt2"></chart>

error result
 Uncaught (in promise): Error: module is not a function

I suspect the problem is  system.js loades two module ,so I'm wondering if you're using these two type chart at the same time, Is this error?

I have alreadly find a way to fix it
official advice add <script src="http://code.highcharts.com/maps/modules/map.js"></script>,if you want to use both of highcharts and highmap
so just system.js change hightmap path
//system.js
'highcharts': 'npm:highcharts',
'highmaps':'npm:highcharts/modules/map.js',

//module.ts
ChartModule.forRoot(
            require('highcharts'),
            require('highmaps'),
        ),


How to change or remove the color of the folded line?

Feature description
How to change or remove the color of the folded line?
Describe the solution you'd like
I'd like to change the color of the folding text line
Additional context
No response

https://github.com/kevinhwang91/nvim-ufo/blob/6f2ccdf2da390d62f8f9e15fc5ddbcbd312e1e66/doc/example.lua#L129-L170


Agent manager lbdriver not initialized in proper order

Issues:
Fixes #893
Problem:
The lbaasv2 agent is not registering with neutron in the neutron agent-list upon
installation and start of the process. The service status looks as though it is active.
Analysis:
Moved the load_driver call to initialize the agent_manager driver attribute
before it is used to build configuration.
Tests:
Manual

Can one of the admins verify this patch?

test this please

@pjbreaux and @richbrowne , I can close this, right ?

Yes, the original change never made to newton. Closing. @dflanigan


Create base model selector

[x] Update config.YAML
[x]  research or analysis
[x]  Update the entity
[x]  Update the configuration manager in src config.
[x]  Update the components
[x]  Update the pipeline
[x]  Test case added

completed


onSnapToItem not called when drag+release in center of item.

Is this a bug report, a feature request, or a question?
Bug report
Have you followed the required steps before opening a bug report?
(Check the step you've followed - put an x character between the square brackets ([]).)

[x] I have read the guidelines regarding bug report.
[x] I have reviewed the documentation in its entirety, including the dedicated documentations :books:.
[x] I have searched for existing issues and made sure that the problem hasn't already been reported.
[x] I am using the latest plugin version.
[x] I am following the issue template closely in order to produce a useful bug report.

Have you made sure that it wasn't a React Native bug?
Yes.
Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
Both platforms. Happens on all versions I've tested so far.
Is the bug reproducible in a production environment (not a debug one)?
Yes
Environment
Environment:
React: 16.9.0
React native: 0.61.5
react-native-snap-carousel: 3.8.4
Target Platform:
iOS (13.2.2)
Expected Behavior
Dropping the control in the center of a new item should fire onSnapToItem, as it does when it dropped anywhere else.
Actual Behavior
Dropping the control in the exact center of a new item doesn't fire onSnapToItem. But it does fire when moving away from the item. See the gif below.

Reproducible Demo
https://snack.expo.io/S1rs_rpaB
Steps to Reproduce
(Write your steps so that anyone can reproduce the issue in the Snack demo you provided.)

Select first item (if not already selected), the item with a 1.
Drag the next item (2), and move it to the center of the screen, and release it when the black line in the item is perfectly aligned with the black line in the view behind it.
If perfectly aligned, onSnapToItem won't be called and carousel won't move.
If onSnapToItem is called, repeat the process until 3. is reproduced.

Have the same issue

Can you try the shiny new beta version and let me know how it works for you?
Click here to learn everything about the upcoming v4!

I had this issue. Tried the PR mentioned above with patch-package, it didn't work. But I have tried the beta version (4.0.0-beta.6) now. Seems fixed to me. When will the beta version be released to production?

I came up with a workaround on this. onSnapToItem is still broken but you can use combination of onScrollIndexChanged and onTouchEnd like below. onScrollIndexChanged gets triggered while you're still dragging the carousel. So capture its index. And onTouchEnd event does not know about the current index, so you use the index that you saved to state before.
onScrollIndexChanged={index => this.setState({ currentIndex: index })}
onTouchEnd={() => alert("Item snapped to index:" + this.state.currentIndex) }


Consider routers in Vite's development

Description
Hello
Vite is making the difference between frontend, backend, ssr, local server become smaller. Thank you!
One opportunity you guys have now,   I find almost strange that in your documentation, backend integration is still considered as that: an external process, an integration.
Another example is SSR, that is considered as an integration, an addition, an after-thought.
That may have been the reality, there is nothing wrong. What I want to say is that you are in position now, with the advent of Environment API, to dream more.
Suggested solution
vinxi is one plugin for Vite that is doing something great for the ecosystem. Please read its description: https://github.com/nksaraf/vinxi           and this interview: https://dev.to/this-is-learning/what-is-vinxi-and-how-does-it-compare-to-vike-4883
I believe that vinxi is trying to improve one area that is of interest of Vite.
vinxi could be offered as an official plugin or be integrated in Vite.
In my opinion, vinxi does not need to be a plugin.
vinxi offers a common base for people to build their routers, adapters and wrappers, things that work well in different environments.
This approach is elegant, different from the common thought out there, in which every backend reinvents the wheel and creates the same inconsistencies.
With my suggested solution, in the future the need for backends will decrease, as their routers, authentications mechanisms are going to be plugins to Vite, instead of being abstract entities that are connected to Vite through a backend.
Currently there is overlap, there is a lot of duplication when integrating vite with a backend.
Thanks.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Hey @mrredtree! The approach Vinxi took is really interesting and a great place for inspiration, and the need for multiple Vite dev servers and complex orchestration code they need to implement it is one of the many reasons we worked on the new Environment API. We hope that solutions like Vinxi will be easier to maintain and maybe simplified after Vite 6. If you have concrete proposals for features or changes to the Environment API proposal, please let us know at https://github.com/vitejs/vite/discussions/16358. I'll close this issue as there isn't an actionable item here for us.


ug: Minor fixes in aklite CLI documentation

A few fixes that I've missed from PR #734.

PR Template and Checklist
Please complete as much as possible to speed up the reviewing process.
Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness

[ ] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
Why merge this PR? What does it solve?
Checklist

[ ] Run spelling and grammar check, preferably with linter.
[ ] Avoid changing any header associated with a link/reference.
[ ] Step through instructions (or ask someone to do so).
[ ] Review for wordiness
[ ] Match tone and style of page/section.
[ ] Run make linkcheck.
[ ] View HTML in a browser to check rendering.
[ ] Use semantic newlines.
[ ] follow best practices for commits.

[ ] Descriptive title written in the imperative.
[ ] Include brief overview of QA steps taken.
[ ] Mention any related issues numbers.
[ ] End message with sign off/DCO line (-s, --signoff).
[ ] Sign commit with your gpg key (-S, --gpg-sign).
[ ] Squash commits if needed.

[ ] Request PR review by a technical writer and at least one peer.

Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

@kprosise , just noticed the adjustments for some of your suggestions were missing in PR #734. File was not saved to the last state when I've executed the commit amend command 🤦. Sorry about that.  Please merge this PR as well to fix it.

Docs for 9baa24cb9948166d35e9d6b9facb741e1a9bef94 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2768/docs/artifacts/html/index.html

@kprosise , I've just noticed the adjustments for some of your suggestions were missing in PR #734. File was not saved to the last state when I've executed the commit amend command 🤦. Sorry about that. Please merge this PR as well to fix it.

No worries, I should have caught that myself!


Cannot comment-out the selected code from VS tool bar

Config:
Dev14 Ent RC + latest PoshTools (http://aka.ms/Get-PoshToolsNightly)
Cannot Comment-out the selected lines from VS tool bar, please see below screenshot:

Thanks for reporting this!  related to https://github.com/adamdriscoll/poshtools/issues/206


iOS lot of warnings

after i build my app, I get this warnings:
PushPlugin.m

PushPlugin.m:169:9:

'UIRemoteNotificationType' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead.

PushPlugin.m:169:54:

'UIRemoteNotificationTypeNone' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead.

PushPlugin.m:178:34:

'UIRemoteNotificationTypeBadge' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead.

PushPlugin.m:186:34:

'UIRemoteNotificationTypeSound' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead.
And many others "UIRemoteNotificationType" warnings. Also I get this one

PushPlugin.m:535:42:

Undeclared selector 'userHasRemoteNotificationsEnabled'

PushPlugin.m:536:49:

Undeclared selector 'userHasRemoteNotificationsEnabled'

/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/

PushPlugin.m:536:17: Incompatible pointer to integer conversion assigning to 'BOOL' (aka 'signed char') from 'id'

/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/

PushPlugin.m:579:24: Unused variable 'app'
Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(Descriptor.pb.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(ObjectivecDescriptor.pb.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBArray.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBCodedInputStream.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBDescriptor.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBUtilities.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBExtensionField.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBExtensionRegistry.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBField.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBGeneratedMessage.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBRootObject.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBCodedOutputStream.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBUnknownFieldSet.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): Object file (/Users/juampi/Desktop/LIDI/FacInfoApp/Frontend/platforms/ios/Informática UNLP/Plugins/phonegap-plugin-push/GCM/Libraries/libProtocolBuffers.a(PBWireFormat.o)) was built for newer iOS version (8.3) than being linked (8.0)
(null): warning: /var/folders/f4/lg23spf10fv19twg_lmrp8zm0045gx/C/org.llvm.clang.136701/ModuleCache/1JNUDWCYE5LC7/Foundation-A3SOD99KJ0S9.pcm: No such file or directory
(null): warning:
/var/folders/f4/lg23spf10fv19twg_lmrp8zm0045gx/C/org.llvm.clang.136701/ModuleCache/1JNUDWCYE5LC7/UIKit-2LM3EQU7VVY4O.pcm: No such file or directory
(null): warning: /var/folders/f4/lg23spf10fv19twg_lmrp8zm0045gx/C/org.llvm.clang.136701/ModuleCache/1JNUDWCYE5LC7/Darwin-MI6WZSG1PNOM.pcm: No such file or directory
(null): warning: /var/folders/f4/lg23spf10fv19twg_lmrp8zm0045gx/C/org.llvm.clang.136701/ModuleCache/1JNUDWCYE5LC7/SystemConfiguration-2O070L5BFB5B1.pcm: No such file or directory
(null): warning: /var/folders/f4/lg23spf10fv19twg_lmrp8zm0045gx/C/org.llvm.clang.136701/ModuleCache/3ITUVTFWQXGWD/Foundation-A3SOD99KJ0S9.pcm: No such file or directory
(null): warning: /var/folders/f4/lg23spf10fv19twg_lmrp8zm0045gx/C/org.llvm.clang.136701/ModuleCache/3ITUVTFWQXGWD/UIKit-2LM3EQU7VVY4O.pcm: No such file or directory
(null): warning: /var/folders/f4/lg23spf10fv19twg_lmrp8zm0045gx/C/org.llvm.clang.136701/ModuleCache/3ITUVTFWQXGWD/Darwin-MI6WZSG1PNOM.pcm: No such file or directory
How could I solved it? the build was success but the app crashed.
My system  info is:
Your system information:
Cordova CLI: 6.1.1
Ionic Version: 1.3.0
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
ios-deploy version: 1.8.6
ios-sim version: 5.0.8
OS: Mac OS X El Capitan
Node Version: v4.1.0
Xcode version: Xcode 7.3.1 Build version 7D1014

@jffs the warnings are fine, the crash is not. What are the circumstances of the crash.

my fault, it was another thing.


Iterative mode

A wrapper script to run iteratively on smaller subsets of samples, until all samples have been assigned. To produce a smaller initial db to conserve resource use for huge datasets

This is less important as of v2.0.0, and will be left up to users if needed (wish to encourage use of --assign-query with high quality DB instead)


Default View starting Wander should be the filter view

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When I enter wander, as a user I begin to type the name of the Wander Job I want, I hit different keyboard keys when I type a job like "my-super-critical-app" where the letters are taken as keyboard navigation events.
I then remember I have to hit /.
This is similar to the experience with vi or vim where the user needs to remember or learn about insert mode i.
Describe the solution you'd like
A clear and concise description of what you want to happen.
When I enter wander, as a user I begin to type the name of the Wander Job I want.
As a user I begin typing the nomad job I want and expect it to filter so I can hit enter.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
it might be confusing because if its default filter, entering filter mode might be confusing

Let me know if you find that reasonable.

Going to assume yes, @qwo :)

Will be included in next release with --start-filtering/WANDER_START_FILTERING=true/wander_start_filtering: True (defaults False)

Released in v0.12.0


Give enough time for replication to complete in unit tests

Complement to #11001
Status
ready
Description
The original changes provided in #11001 were missing this extra function used to create CouchDB replication task in the unit tests. Pass a 6 seconds sleep to ensure that the task is triggered and that documents get to the expected destination in unit tests.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
Complement to #11001
External dependencies / deployment changes
None

test this please

Exactly. That method is only used by unit tests. Thanks Todor.


Count single digits

Feature ✅
Description
For a given number find out the count of digits appearing exactly once
Example
Input: 99995844
Output: 2(only 5 and 8 appear once)
Contributors are supposed to mention their coding language while asking for assignment

@pratik-choudhari  Can you assign me this? I want to work on it in Python.

Interested, python

Can you assign this to me? I would like to work on it in CPP

I wanna work in JS. Assign the issue please.

@moderators

Can I work on this using C++? Kindly assign. Thank you

@almas-ashruff It already been assigned for c/c++.

Hi really interested in this problem, could assign me this ,i will be coding in python

@alvinuday It is already been assigned in python.

@pratik-choudhari  I made a PR. Check it and merge

can you please assign numero perfecto to me , python
On Mon, Oct 12, 2020 at 12:08 AM Pratik Choudhari<EMAIL_ADDRESS>wrote:

@alvinuday https://github.com/alvinuday It is already been assigned in
python.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pratik-choudhari/AlgoCode/issues/273#issuecomment-706748616,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARKWDHQW3K5L7PVEQQV65OLSKH3UBANCNFSM4SLXW3KA
.

Can you please assign it to me, for JAVA?
Thank you.

Can I do Single digit count issue in python?

please let me know if I can work on these using python

@ke3peR007 Nope, It has already been assigned.

Can you please assign it to me, for C#?
Thank you.

Can you assign this to me (C++)?


Add functionality to determine source points from a model path

Still a work in progress
Requires

More testing around differnet model layouts (e.g. relationship and attribute dictionaries, links, JObjects)
More testing on netstandard1.0 (there is a shim in place, but needs to be tested that it works)
Update readme with details of new functionality

Would also like to investigate further

Way to convert from sourcePointer to model expression (i.e. reverse conversion)

FWIW I think you can target just netstandard2.0. It's the defacto default now.

@codecutout sorry for the comment spam - github was having issues and posted a bunch of duplicates.

@jonnii is there a benefit in targeting netstandard2.0 if we are not using any of the additional API definitions?
my understanding was that the netstandards are backward compatible and only define the API contracts. So a netcoreapp2.x should be able to use a netstandard2.0 library just as easy as a netstandard1.5 library

The only real benefit that I've come across of targeting netstandard2.0 is that it reduces the reference spam for anyone using net461 and the old csproj tooling. Now that .NET Core 2.1 is LTS I (personally) don't see the point in targeting anything less - it's things like shimming TypeInfo which I'd want to do without.


Cache update errors are caught

I had an error in my update resolver logic which was really hard to find because the error was caught by the cache exchange like nothing happened. I'm not sure if this is intentional or not.
urql version & exchanges:

 urql
	 2.0.6

 @urql/exchange-graphcache
	 4.3.6

Steps to reproduce
const cache: GraphCacheConfig = cacheExchange({
	schema,
	updates: {
		Mutation: {
			doSomething: () => {
				throw new Error("this is caught")
			},
		},
	},
})

Expected behavior
Errors are propagated/re-thrown
Actual behavior
Errors are caught inside the cache exchange

Nothing in urql is catching these we are throwing them for the user, here is a simple reproduction highlighting this case. When you press a todo it will throw an error.