[misc] improve model support check in another process

previous approach of checking if the last line of the output contains a magic string is error-prone, if the process produces some logging, warning.
changing it to use the same technique as https://github.com/vllm-project/vllm/blob/d5fbb8706d2c7fd00b64cff2efbe7c771fe82c3c/vllm/distributed/device_communicators/custom_all_reduce_utils.py#L254 , to use a dedicated file to communicate the results.

I'm thinking of actually executing the supports_* functions in the same process to avoid spawning a new process for each one. Now that the function doesn't have to return a boolean, perhaps we can return a dictionary of results (one field per function)?

yes that's possible. I launch one function to batch test the things I care in https://github.com/vllm-project/vllm/blob/d5fbb8706d2c7fd00b64cff2efbe7c771fe82c3c/vllm/distributed/device_communicators/custom_all_reduce_utils.py#L254

@DarkLight1337 I mark it as ready and will merge this pr first. You can add follow-up prs to batch test the results.


[BUG] ZepClient not working

Describe the bug
I'm using latest zep-python and the following code:
zep_client = ZepClient("http://<IP_ADDRESS>:8000")

but getting an error:
api-1                 | zep_python.exceptions.APIError: Failed to connect to Zep server. Please check that:
api-1                 |          - the server is running
api-1                 |          - the API URL is correct
api-1                 |          - No other process is using the same port
api-1                 |          : None

At the same time I can access Zep in my browser by http://<IP_ADDRESS>:8000

Have you ever started the Zep server?  Please check.

Closing as a new Server and set of SDKs is now available.


6.4 Crash

When ESP overlay is enabled, the monsters sight area works at first, but after attacking a few monsters it stops working and eventually the client crashes.
There is no crash log after that so I can't be 100% sure if it's conflicting with palace pal, but since it worked fine before the patch and with the ESP overlay turned off the crash stops we can be sure there is something wrong with necrolens.
Btw, after the sight area disappears, I tried to turn off and on the plugin to see if the issue was termporary but the moment I click the button to turn off the plugin the client crashes.

Having the same issue.

Guess its the same reason as #5 - need to check it closer. Just tested if it shows up haha.
I take a look in it, but it might need some time since im a bit busy over the weekend.

Pushed a "workaround" to prevent the crashes and instability. The root cause seems like to come from dalamud itself. Asked there for assistence. It should work like normal again but it MAY not show up single objects like traps or chests. If i find how to fix the root cause i will implement it :3

I tried for a couple of hours and the sight area seems to work well and no crashes, thanks 😄


If my product is to be commercialized?

Hi,
Frist, wiki says Authserver can only be used for testing. If the product to be commercialized must be used other ways to obtain access token. If  use other methods, sample app code needs to be changed?What about the changes?
Second,If my product is to be commercialized, is the sample app available?

Hi @snailwft,
License.txt governs the use of the Amazon Software provided in this repository.
Thanks,
Benny

Hi @snailwft
I am doing a user study on the AVS-device-SDK and would love to talk to you about your experiences as a developer. To participate, please fill out this Contact Form and I will get in touch with you.
Thanks


Added 10km tolerance to geographic area validation for verbatim georeference

This enables users to specify a geographic area other than the one that a verbatim georeference it is contained in provided it is not farther than 10km.

@mjy do you think this is good to go?

@LocoDelAssembly couple very minor comments.  Form etc. is fine for me.

Looks good to merge, thanks much.

Codecov Report

Merging #3077 (dab3847) into development (6bb37ac) will decrease coverage by 22.26%.
The diff coverage is 81.81%.

:exclamation: Current head dab3847 differs from pull request most recent head a7b40b4. Consider uploading reports for the commit a7b40b4 to get more accurate results

@@               Coverage Diff                @@
##           development    #3077       +/-   ##
================================================
- Coverage        86.87%   64.61%   -22.27%
================================================
  Files             1897     1390      -507
  Lines            67818    41588    -26230
================================================
- Hits             58920    26871    -32049
- Misses            8898    14717     +5819

Impacted Files
Coverage Δ

app/models/collecting_event/georeference.rb
44.00% <0.00%> (-2.67%)
:arrow_down:

app/models/georeference/verbatim_data.rb
83.72% <83.33%> (-16.28%)
:arrow_down:

app/models/geographic_item.rb
64.53% <87.50%> (-16.76%)
:arrow_down:

spec/models/collecting_event/geo_spec.rb
100.00% <100.00%> (ø)

spec/support/concerns/controller/delete.rb
9.09% <0.00%> (-90.91%)
:arrow_down:

spec/support/concerns/feature/authorization.rb
9.25% <0.00%> (-90.75%)
:arrow_down:

spec/support/concerns/request/api.rb
11.11% <0.00%> (-88.89%)
:arrow_down:

spec/support/concerns/feature/index_list_show.rb
12.50% <0.00%> (-87.50%)
:arrow_down:

app/models/identifier/global/issn.rb
14.28% <0.00%> (-85.72%)
:arrow_down:

app/models/identifier/global/isbn.rb
8.33% <0.00%> (-85.42%)
:arrow_down:

... and 1069 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


bash: mongodump: command not found...

[root@bim ~]# mongodump --port 27017
bash: mongodump: command not found...
[root@bim ~]# bash wekan-backup.sh
The database backup is in progress.
wekan-backup.sh:行16: /snap/wekan/525/bin/mongodump: No such file or directory
Makes the tar.gz file.
525-2019-06-11_08.59.18/
Backup done.
Backup is archived to .tar.gz file at /var/backups/wekan/525-2019-06-11_08.59.18.tar.gz

sudo apt-get install mongodb-tools
Or some similar command for your distro.
Or, search how to install mongodb.


SF 0.10.3: sf.available_formats() does not include FLAC and OGG

I've recently upgraded soundfile to the latest version on pypi (0.10.3.post1, Win64). Somehow, sf.available_formats() does not include FLAC and OGG anymore. Is this intentional?
This is what my soundfile returns:
{'AIFF': 'AIFF (Apple/SGI)', 'AU': 'AU (Sun/NeXT)', 'AVR': 'AVR (Audio Visual Research)', 'CAF': 'CAF (Apple Core Audio File)', 'HTK': 'HTK (HMM Tool Kit)', 'SVX': 'IFF (Amiga IFF/SVX8/SV16)', 'MAT4': 'MAT4 (GNU Octave 2.0 / Matlab 4.2)', 'MAT5': 'MAT5 (GNU Octave 2.1 / Matlab 5.0)', 'MPC2K': 'MPC (Akai MPC 2k)', 'PAF': 'PAF (Ensoniq PARIS)', 'PVF': 'PVF (Portable Voice Format)', 'RAW': 'RAW (header-less)', 'RF64': 'RF64 (RIFF 64)', 'SD2': 'SD2 (Sound Designer II)', 'SDS': 'SDS (Midi Sample Dump Standard)', 'IRCAM': 'SF (Berkeley/IRCAM/CARL)', 'VOC': 'VOC (Creative Labs)', 'W64': 'W64 (SoundFoundry WAVE 64)', 'WAV': 'WAV (Microsoft)', 'NIST': 'WAV (NIST Sphere)', 'WAVEX': 'WAVEX (Microsoft)', 'WVE': 'WVE (Psion Series 3)', 'XI': 'XI (FastTracker 2)'}

Did you install the source distribution or the wheel?

Did you install the source distribution or the wheel?

Hi, I installed using pip (python 3.8). I suppose that the source distribution is used.

I suspect your soundfile is using some pre-installed version of libsndfile. What are your soundfile._snd and soundfile.__libsndfile_version__?
I just installed a new version of SoundFile on my Windows box, and mine did come with FLAC and OGG support.

You are correct that my soundfile has used the wrong libsndfile.
>>> sf._snd
<Lib object for 'C:\Users\xxxx\miniconda3\envs\xxxx\Library\bin\sndfile.dll'>
>>> sf.__libsndfile_version__
'1.0.29'

It should have used C:\Users\xxxx\miniconda3\envs\xxxx\Lib\site-packages\_soundfile_data\libsndfile64bit.dll which is also available.  This may have happened because, in my conda's environment.yml, I installed librosa using conda's conda-forge and soundfile using pip. I have modified my environment.yml to install both librosa and soundfile using pip. My soundfile now can read and write FLAC and OGG files. Many thanks for the help.
Anyway, is it possible to improve libsndfile's detection to avoid this problem?

Anyway, is it possible to improve libsndfile's detection to avoid this problem?

SoundFile will always try to load a user-installed libsndfile before falling back on its own libsndfile. And that's really how it should be, otherwise it would be impossible to load a custom libsndfile at all.


Create interfaces for repositories

I think it is good practice to use interfaces for repositories.
Repository methods already return DataReaderInterface objects (this gives us independence from DBAL), it remains only to describe their API in the interfaces.

Do you mean a common interface or repository-specific interfaces?

Common interface with ooerations more used, created, modify, delete, find, etc.

Do you mean a common interface or repository-specific interfaces?

It is good to have a common interface in the context of ORM and other common cases.
However in the context of this repository i mean only repository-specific interfaces.

Who would be users/clients of these interfaces?
Would these interfaces separate system boundaries?
Would there be multiple implementations of these interfaces?


CMake Tools doesn't work with multi-root folders with non-CMake folders

Open a workspace with folders configured for CMake and other folders that don't use CMake.

Bug: "Configuring project" gets stuck and the CMake extension incorrectly tries to configure the non-CMake workspace folders.
I'm using the pending 0.27.0-insiders of C/C++ and 1.3.1 of CMake Tools.
It works if both folders use CMake.

The Configuring project but doesn't repro if the 1st workspace folder uses CMake, but the "Select a Kit" and "configure" popup shows up still.

This is a duplicate of #1042.


reduce internal kernel-def

Cleanup-request
Description
The internal kernel-definition objects has its own map with linked buffers, which is only used for the argument-counter for updating a size-value on the device. Buffers should be never be resized, so this value and so the entire additional linked buffer list is unnecessary.

the links in the kernel-def-object is still necessary, but there will be some other sort or rework

the links in the kernel-def-object is still necessary, but there will be some other sort or rework


Simplify build properties

Remove redundant forceCodyBuild variable, use forceAgentBuild
Remove undocumented forceBuild variable

Test plan
./gradlew buildPlugin -PforceAgentBuild=true
./gradlew buildPlugin -PforceAgentBuild=true

and verify that the Cody step,  pnpm run -s build:root && pnpm run -s build:webviews && pnpm run -s build:agent, runs both times.

#2370  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @dominiccooney and the rest of your teammates on  Graphite

Merge activity

Oct 2, 9:27 AM EDT: @dominiccooney merged this pull request with Graphite.


chore:: LANDGRIFFON-50 create s3 bucket

Not really sure why .terraform.lock.hcl was removed. It's my understanding it's a best practice to keep it under VCS but I may be wrong

-I was not sure about that, the side-effects that could produce, but actually makes sense having it on local. Thanks for pointing out

Your module defines a bunch of variables, but then you never use them. I suspect you need to do a bit more reading on the subject, and understand them better.

Changes here
And reading about TF modules as well 👍

@tiagojsag changes applied 6c248b0e9fc31d79b13c46d0a9905ccdedadff45


cuda build failure

Host Environment

OS: Windows
Compiler:

To Reproduce
Steps to reproduce the behavior:
./vcpkg install cuda
Failure logs
vcpkg install cuda
Computing installation plan...
The following packages will be built and installed:
cuda[core]:x64-windows -> 10.1#8
Detecting compiler hash for triplet x64-windows...
Restored 1 packages from C:\Users\luthe\AppData\Local\vcpkg\archives in 162.2 ms. Use --debug to see more details.
Starting package 1/1: cuda:x64-windows
Installing package cuda[core]:x64-windows...
Elapsed time for package cuda:x64-windows: 1.112 s
Total elapsed time: 10.86 s
Additional context
Appears to install Cuda but does not. No error message given but it spends no time installing and no cuda headers or libraries are present.

Port CUDA in vcpkg will only check cuda headers and libs, then install vcpkg_find_cuda.cmake.

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


Fix identification of device path in fs.go:GetDevicePath()

Currently, the code is relying on a "label" file for each pci device which isn't there in Centos and RedHat distros. Need to be able to match the bus number with the dir entries which should work for all cases.

#213 /cc @justinclayton

Closed via #534


Different UUID from same BLE Device on iOS and Watchkit

Describe the bug
I have an iOS app and an Watch Extension. Both have RxBluetoothKit.
If i scan devices on iOS i get uuid 0A8CB164-1682-A7B7-9A97-F73D4C909731 for my device.
But if i scan on Apple Watch i get uuid B0ACF8CA-502F-F8DA-9F57-F2AC21ABE45F for the same device.
Why?
I scan devices on iOS and send uuid to apple Watch. Then the watch will connect to device and write value. But can't connect because not find with this uuid
How i can solve this problem?
Environment:

Device: [e.g. iPhone5a, Apple Watch 4]
OS: [e.g. iOS12.1.4, watchOs 5.1.3]
Library version [5.1.4]
Swift version [4.2]

Thats how apple works.
Your device generate an UUID that means that one phone generate UUID = 1 and another phone will generate UUID = 2 for the same BLE Device.
It's per apple device and has nothing to do with the RxBluetoothKit.

Answer above is correct. Closing.


segfault: String would overflow textgrid. Truncating.

I built and installed revision ce028d2 via the AUR package. When I run it the window appears for a second then it crashes with the following error:
ERR<29523>:eovim /home/wmoore/aur/eovim-git/src/eovim-git/src/termview.c:860 termview_put() String would overflow textgrid. Truncating.
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/libeina.so.1	 0x7f2d1ce1988e 0x7f2d1cdf3000
/usr/lib/libeina.so.1	 0x7f2d1ce1a601 0x7f2d1cdf3000
/usr/lib/libeina.so.1	 0x7f2d1ce1ba23 0x7f2d1cdf3000
[1]    29523 segmentation fault (core dumped)  eovim

The backtrace looks truncated but running eina_btlog on the frames shown gives:
    /usr/lib/libeina.so.1| ??/??: 0 @ eina_log_print_cb_journald()
    /usr/lib/libeina.so.1| ??/??: 0 @ eina_log_print_cb_stdout()
    /usr/lib/libeina.so.1| ??/??: 0 @ eina_log_print()

The same crash also happens when running with -N. When run with -g 80x24 it does not crash.

Hi, I think there are two errors here:

one from eovim, which has an issue when resizing at startup,
one from the EFL (the underlying framework of eovim) which crash when printing the backtrace.

I've already experienced the EFL bug, but haven't pinpoint the version it is present in. What version of EFL are you using? An easy way to circumvent this issue while waiting for a fix in the EFL would be to disable the backtrace feature by setting EINA_LOG_BACKTRACE to something like -1.
The resizing bug in Eovim is a real problem, I'll work on that.

If you are using the GIT version of EFL, the segfaults should now be fixed.

Totally missed your original reply a week ago. Thanks for looking into a fix. I'll try it out when I'm back at work tomorrow.

Tried it out and it no longer crashes 🎉 Thanks.

Nice :)


Running program in Emulator from VSCode problem when using an 'autoexec' file.

I've been trying our VSCode to create some simple programs.  When I hit CMD+ SHIFT + B and RETURN to run the program in the emulator, it loads the emulator and if I an using an 'autoexec' file I get a syntax error:
Ok
RUN "autoexec
Ok
"hello.aqx"
Syntax error
If I disable the 'autoexec' file then I get this:
Ok
run"hello.aqx"
Hello World!
Ok
Looks like the 'run' is being cut off when the 'autoexec' is executed.

Can you try again in the newest version of the OS/pB?
Also, please list the contents of your autoexec here so we can see them.
(Sorry for the delay. We're back-logged, but you knew that...)

The problem here is that plusBASIC clears the input buffer. So you need to delay your command input until plusBASIC is done processing. If you have an autoexec this will take longer. You can adjust your Makefile to add addition \x1D (delay 500ms) before your RUN command.


Need to implement AT.currentAdvocate

Storing the data for the currently referred person locally.

Reckon this is still needed @zcrowe ?

nope


bike should better avoid primary roads

E.g. this route should not happen but it uses the primary road, even when forcing with a via point.
The reason here are the tags maxspeed=30 and cycleway:right=share_busway for the primary road which overrule the avoidance.

funfact: In the meantime a real cycleway has been built on that example route:
https://www.mapillary.com/app/?lat=52.4846613&lng=13.353633400000035&z=18.83520815313215&pKey=835943008414001&dateFrom=2024-04-01&x=0.3843274054032111&y=0.5544758255591679&zoom=0&focus=photo
It is now tagged with cycleway:right = lane:
https://www.openstreetmap.org/way/508614988#map=18/52.485210/13.354627
It would be really amazing to be able to add those bicycle infrastructure informations (f.e. for cycleway:right = lane or cycleway:right=share_busway ) as Encoded Values/"Road attribute".
It would boost the possibilities for custom bicycle routing and would also allow better debugging for unexpected behaviour.
Once it is stored as Road attribute, it would be possible to vizualize the Route segments like this, right?

Or is there an existing workaround for this?

t would be really amazing to be able to add those bicycle infrastructure informations (f.e. for cycleway:right = lane or cycleway:right=share_busway ) as Encoded Values/"Road attribute".
It would boost the possibilities for custom bicycle routing and would also allow better debugging for unexpected behaviour.

I don't understand it. Could you provide a custom rules examples and explain in more detail?
I believe that merging of #3039 will solve this issue.

I imagine a "Road attribute" like "cycling_infrastucture" that would store values like "cycleway_lane" in it, like in this mock up:

I have been trying to explain the "issue" with non-separated cycling infrastucture here:
https://discuss.graphhopper.com/t/take-cycleway-s-along-roads-into-account-for-custom-routing-profiles/9184
and here:
https://discuss.graphhopper.com/t/unexpected-routing-by-bike-ignoring-cycle-paths/9199
I am super happy to elaborate on this, if you need more further details. In here I just realized, that the vizualisation (graph on the bottom right) would help to understand what the routing actually does.

@vizsim Thanks for the visualization. I think now I understood the basic idea, but I'm not sure about the details. If I got it right you want to derive this new encoded value from the cycleway tag and the value would be be mainly for shared ways. What value would you assign for separated ways, e.g. a highway=cycleway? Would this be "MISSING"?


warning: Ignoring InnerClasses attribute for an anonymous inner class that doesn't come with an associated EnclosingMethod attribute.

I have followed the directions as stated on the AdsNative website, but I am getting these errors when trying to compile:
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ab) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ac) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.aa) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.am) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.an) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ae) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.af) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ag) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ah) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.at) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ai) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.aj) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ak) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.al) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ap) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ar) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.as) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.au) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ba) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.bb) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.aw) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ay) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.az) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.b) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.bd) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.be) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.bn) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.bo) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.bg) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.bk) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.bl) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.bp) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.bq) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.br) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.bs) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.f) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.g) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.k) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.c) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.ca) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.d) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.e) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.h) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.i) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.j) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.l) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.n) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.o) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.p) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.q) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.t) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.u) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.v) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.w) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.x) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.y) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.ads.z) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.network.b) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.network.d) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.network.e) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.network.f) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.util.a) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.util.h) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.util.i) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.util.p) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.util.q) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.util.r) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.util.s) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.util.t) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.util.v) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.
Error:warning: Ignoring InnerClasses attribute for an anonymous inner class
Error:(com.adsnative.util.w) that doesn't come with an
Error:associated EnclosingMethod attribute. This class was probably produced by a
Error:compiler that did not target the modern .class file format. The recommended
Error:solution is to recompile the class from source, using an up-to-date compiler
Error:and without specifying any "-target" type options. The consequence of ignoring
Error:this warning is that reflective operations on this class will incorrectly
Error:indicate that it is *not* an inner class.

Here is a snippet of my Gradle file:
repositories {
    jcenter()
    maven { url 'https://maven.fabric.io/public' }
    flatDir {
        dirs 'libs'
    }
}

dependencies {
    compile 'com.android.support:support-v4:24.0.0'
    compile 'com.android.support:gridlayout-v7:24.0.0'
    compile 'com.android.support:design:24.0.0'
    compile 'com.android.support:preference-v7:24.0.0'
    compile 'com.android.support:recyclerview-v7:24.0.0'
    compile 'com.google.android.gms:play-services:10.0.1'
    compile 'com.parse.bolts:bolts-android:1.+'
    compile 'com.parse:parse-android:1.11.+'
    compile 'com.edmodo:rangebar:1.0.0'
    compile 'com.edmodo:cropper:1.0.1'
    compile 'com.nineoldandroids:library:2.4.0'
    compile 'com.squareup.okhttp:okhttp-urlconnection:+'
    compile 'com.tonicartos:stickygridheaders:1.0.1'
    compile 'com.intellij:annotations:+@jar'
    compile 'com.mixpanel.android:mixpanel-android:4.5.3'
    compile 'com.splitwise:tokenautocomplete:2.0.7@aar'
    compile('com.crashlytics.sdk.android:crashlytics:2.5.7@aar') { transitive = true; }
    compile 'com.github.clans:fab:1.6.4'

    compile fileTree(dir: 'libs', include: '*.jar')
    compile(name:'adsnative-sdk-2.5.1', ext:'aar')
}

Also, are there specific Google Play Services libraries I can include instead of including all the libraries (as shown in https://developers.google.com/android/guides/setup)?

The errors can be fixed by adding following to the proguard-rules.pro
-keepattributes EnclosingMethod


IETF Connection Close Frame - Possible narrowing of error code coming from reason phrase

Looks like error code coming from reason phrase of CLOSE_FRAME can be very big number (64 bits) but the target enum QuicErrorCode can be of non-fixed underlying type unsigned int (32 bits). This can lead to narrowing. I have checked this behavior by updating the QuicFramerTest.ConnectionCloseFrameWithUnknownErrorCode so it sends following reason phrase "4294967296:bla" which leads to quic_error_code with value 0 (QUIC_NO_ERROR) because of narrowing.
The problematic code:
void MaybeExtractQuicErrorCode(QuicConnectionCloseFrame* frame) {
  std::vector<absl::string_view> ed = absl::StrSplit(frame->error_details, ':');
  uint64_t extracted_error_code;

...
...
...

  frame->quic_error_code = static_cast<QuicErrorCode>(extracted_error_code);
}

Thank you for pointing out this issue. It has been fixed at https://github.com/google/quiche/commit/b7f167071e34a5f9834ff9bafdf1e62215f2138e.


Fix no-params demangling of template function instance

Resolves #158

I totally bungled this, I'm sorry. I'll submit a new PR to fix it.

I don't think the ArgScopeStack is really the right thing to use to determine "if we're at the top level". We should probably use the DemangleContext.


update(doc) Add Wireshark / Logray as adopters

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area tests

/area proposals

/area CI

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Welcome @geraldcombs! It looks like this is your first PR to falcosecurity/falco 🎉

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: geraldcombs
Once this PR has been reviewed and has the lgtm label, please assign jasondellaluce for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, geraldcombs
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: ec97322886dce48d5414d1b182e08be394876c00

/milestone 0.37.0


JDBCConnectionException at api-dev

Tried to create a new user via:
curl -X POST "http://api-dev.freme-project.eu/current/user?username=templates&password=temp1234"

and got:
{
  "exception": "org.springframework.dao.DataAccessResourceFailureException",
  "path": "/user",
  "message": "could not prepare statement; nested exception is org.hibernate.exception.JDBCConnectionException: could not prepare statement",
  "error": "Internal Server Error",
  "status": 500,
  "timestamp":<PHONE_NUMBER>586
}

Is the MySQL database at Jenkins configured correctly?

It seems that the broker looses the MySQL connection after a while. A quick workaround is to restart freme-dev.
According to this document I added this bit to the broker configuration in order to auto reconnect the database
spring.datasource.testOnBorrow=true
spring.datasource.validationQuery=SELECT 1

The connection is stable for three days now so I assume this is fixed.


Bitimages

Hi! Thanks for sharing this amazing plugin !
Do you think that it's possible to add bitimage printing and cash drawer support ?
Thanks !

Yes, it possible, we can add support both printing image from data and from
url (if it needed). But this functional will be added on IOS plugin
firstly, and then a bit later on Android.
Thank you for your feedback, I''m glad to work for people who need this
functionality.
Vladyslav.
2016-10-12 1:41 GMT+03:00 Igor Magès<EMAIL_ADDRESS>
Hi! Thanks for sharing this amazing plugin !
Do you think that it's possible to add bitimage printing and cash drawer
support ?
Thanks !
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fasteroko/StarIOPrint-cordova/issues/3, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AMuHlkUeEvPL58cumjYeNUMzd6W32oE7ks5qzBCggaJpZM4KULu6
.


Wrong reported amount of gas

Issue: Hyperspace rpc returns wrong gas amount for network: existing deployments with the below gas amount is significantly underpriced.
Reproduction:
cast gas-price --rpc-url https://api.hyperspace.node.glif.io/rpc/v1
199668

Error: (code: 1, message: verify msg failed: message will not be included in a block: 'GasLimit' field cannot be less than the cost of storing a message on chain 315871 < 1025863, data: None)

Closing as not related to Glif - please, create an issue in Lotus repo.


default property doesn't work with roles orientdb-community-2.1-SNAPSHOT

Setup
CREATE CLASS User extends OUser
CREATE PROPERTY User.created datetime
ALTER PROPERTY User.created default sysdate() readonly
ALTER PROPERTY User.roles default [#4:2] readonly

POST Request
http://localhost:2480/document/test

content
{
@class: "User"
name: "Brett"
password: "root"
status: "ACTIVE"
}

Error
com.orientechnologies.orient.core.exception.OValidationException: The field 'OUser.roles' has been declared as LINKSET but an incompatible type is used. Value: [#4:2].field( readonly)
the 'created' property works as expected

fixed with the refactor of validation closing


actions/api.js ... bug ?

I have a rest endpoint locked down with security, and it nicely fails with a 401 code i.e.
server.route({
            method: 'GET',
            path: '/vehicles2',
            config: {
                auth: {
                  strategy: 'session'
                },
                plugins: {
                    'hapi-auth-cookie': {
                        redirectTo: false
                    }
                }
            }

I was hoping that I could nicely handle what do do next in my action, callback
class Actions {
    static getResults(data) {

        console.log('in getResults');
        ApiActions.get(
            '/api/vehicles2',
            data,
            Store,
            Constants.GET_RESULTS,
            Constants.GET_RESULTS_RESPONSE,
            (err, response) => {

                //decide what to do here, if error or status code == 401
            }
        );
    }

but somehow the callback after the store.dispatch() never gets a chance to execute
static makeRequest(request, store, typeReq, typeRes, callback) {

        store.dispatch({
            type: typeReq,
            request
        });

        JsonFetch(request, (err, response) => {

            store.dispatch({
                type: typeRes,
                err,
                response
            });

            if (callback) {
                callback(err, response);
            }
        });
    }

is this a bug is there something I am missing ? I really want to handle rest calls nicely if token is not available for instance

Your callback should be getting fired. If the response code isn't in the 200s you'll need to check the err value of the callback.
https://github.com/jedireza/aqua/blob/4e7cb75253a04e870b73e61a73842f896ecf983e/client/helpers/json-fetch.js#L38-L62
The best thing you can do is setup some breakpoints in the debugger and watch how the code flows to see what prevents your callback from firing or if something else is wrong.

seems when an err is passed to dispatch that it never comes back to execute the subsequent code, so I had to put in this ugly hack:
    static makeRequest(request, store, typeReq, typeRes, callback) {

        store.dispatch({
            type: typeReq,
            request
        });

        JsonFetch(request, (err, response) => {

            if(callback && err && response.statusCode == 401){
                callback(err, response);
                return
            }

            store.dispatch({
                type: typeRes,
                err,
                response
            });

            if (callback) {
                callback(err, response);
            }
        });
    }

If an error exists here:
https://github.com/jedireza/aqua/blob/4e7cb75253a04e870b73e61a73842f896ecf983e/client/actions/api.js#L39-L47
nothing is preventing al callback from being fired. Put a breakpoint on line 39 and 45 and confirm that a callback actually exists.

A 401 would be the same as the 400s that we handle. Like on the login form:

I've shown that stock Aqua does gracefully handle handle 4XX replies from the API.
At this point the best thing to do is create a fork of Aqua with simple changes that reproduce the bug. That way others could clone it and debug themselves.
On the other hand, It sounds like you have started customizing things beyond basic edits, in which case, making a simple reproducible example will probably expose the underlying problem.
This could very well be a bug in Aqua, but we need to pinpoint where it is. Happy hunting. Thanks for being active with the project. 🙏

ok I simplified things a lot and no longer have the issue


Utilize QnABot idtoken and optionally pass to Kendra based authentication

The purpose of this change is to allow QnABot to be configured to pass an OpenID JWT to Kendra Index(es).  It is controlled by the new configuration setting "ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH" which defaults to "false".  If "ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH" is set to "true" and "_userInfo.isVerfiedIdentity" is "true", then QnABot will pass the idtoken with the each Kendra Index query configured for fallback (i.e. ALT_SEARCH_KENDRA_INDEXES).
The primary changes have been made to the es-proxy-layer within the kendra.js file.
Supporting changes have been made to add a new Setting ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH with documentation.
The Settings that are in play:

ENFORCE_VERIFIED_IDENTITY                = false (false allows for unauthenticated user as well as authenticated.)
IDENTITY_PROVIDER_JWKS_URLS          = (set to appropriate cognito user pool and used to verify the user token is valid. If user is logged in and valid token, then UserInfo.isVerifiedIdentity=true)
ALT_SEARCH_KENDRA_INDEXES            = (set to one Kendra Index)
ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH = false / true (false is default. true allows QnABot to send idtoken to Kendra)

Some notes about the 8 Use Cases:

CASE 1 through 4: User is NOT authenticted within Lex-Web-UI.
CASE 5 through 8: User is authenticated within Lex-Web-UI.
CASES 1,2 and 5,6 have Kendra Auth Enabled.  Cases 3,4 and 7,8 have Kendra Auth Disabled.

The following 8 Use Cases have been explored:
CASE 1: Kendra Index has Auth Enabled. isVerifiedIdentity === "false". ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH === false.

User is NOT authenticated. Has no token to send to Kendra.
QnABot is NOT configured to send a token and user has NO token to send.  NO token is sent.
Kendra Index has auth enabled, but does not require a token to be sent.
User will only get public content (not protected by ACLs).

CASE 2: Kendra Index has Auth Enabled. isVerifiedIdentity === "false". ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH === true.

User is NOT authenticated. Has no token to send to Kendra.
QnABot is configured to send a token but user has NO token to send.  NO token is sent.
Kendra Index has auth enabled, but does not require a token to be sent.
User will only get public content (not protected by ACLs).

CASE 3: Kendra Index has Auth Disabled. isVerifiedIdentity === "false". ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH === false.

User is NOT authenticated. Has no token to send to Kendra.
QnABot is NOT configured to send a token and user has NO token to send.  NO token is sent.
Kendra Index has auth disabled.  Any Kendra Source ACLs are ignored.
User will get ALL content from the index since source ACLs are ignored.

CASE 4: Kendra Index has Auth Disabled. isVerifiedIdentity === "false". ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH === true.

User is NOT authenticated. Has no token to send to Kendra.
QnABot is configured to send a token but user has NO token to send.  NO token is sent.
Kendra Index has auth disabled.  Any Kendra Source ACLs are ignored.
User will get ALL content from the index since source ACLs are ignored.

CASE 5: Kendra Index has Auth Enabled. isVerifiedIdentity === true. ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH === false.

User is authenticated. User has a token to send to Kendra.
QnABot is NOT configured to send a token even though user has a token to send.  NO token is sent.
Kendra Index has auth enabled, but does not require a token to be sent.
User will only get public content (not protected by ACLs).

* CASE 6: [EXPECTED PATH] Kendra Index has Auth Enabled. isVerifiedIdentity === "true". ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH === true.

User is authenticated. User has a token to send to Kendra.
QnABot is configured to send a token and user has a token to send.  An idtoken is sent to Kendra Index query.
Kendra Index has auth enabled, but does not require a token to be sent.
User will only get public and private content based on their entitlements as protected by ACLs.

CASE 7: Kendra Index has Auth Disabled. isVerifiedIdentity === true. ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH === false.

User is authenticated. User has a token to send to Kendra.
QnABot is NOT configured to send a token even though user has a token to send.  NO token is sent.
Kendra Index has auth disabled.  Any Kendra Source ACLs are ignored.
User will get ALL content from the index since source ACLs are ignored.

CASE 8: Kendra Index has Auth Disabled. isVerifiedIdentity === "true". ALT_SEARCH_KENDRA_INDEXES_TOKEN_AUTH === true.

User is authenticated. User has a token to send to Kendra.
QnABot is configured to send a token and user has a token to send.  An idtoken is sent to Kendra Index query.
Kendra Index has auth disabled.  Any Kendra Source ACLs are ignored.
User will get no response as Kendra exception is thrown.

@JasonHammett Thank you so much for this PR (sorry it took me so long to spot it - @chrislott tx for the nudge!).  This is great functionality to add to QnABot, and will open up lots of additional use cases! Nice job clearly enumerating all the scenarios and updating the READMEs as well.
Hopefully we can get this into a release soon.. will discuss with the team.
Thank you.. awesome contribution!

Hi @JasonHammett, this will be available in QnABot v6.0.0 release. Thanks for your contribution, closing this PR.


fix(tier4_perception_launch): enable low_intensity_filter as default

Description

To enable the low_intensity_cluster_filter to solve issue: https://github.com/autowarefoundation/autoware.universe/issues/6785
Default perception/object_recognitioin pipeline after change:
(Orange node: added node)

Related links

TIER IV INTERNAL LINK

Tests performed

Confirmed the improvement as in PR https://github.com/autowarefoundation/autoware.universe/pull/6850
Confirmed the number of unknowns objects during rainings condition is decreased by Perception_online_evaluator

Confirmed that there is no degredation by Internal-evalutator tool:(camera_lidar_fusion_mode)

Before
After

Notes for reviewers

Interface changes

ROS Topic Changes

ROS Parameter Changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

Do you want me to run this with my environment?

@YoshiRi Thanks for your reivew. Since I have already checked this change on Evaluator so I think It should be fine.


refactor: Adjust pipeline orchestration in PipelineExecutor

Motivation
The current state of pipeline_executor.py doesn't follow clear sequential or logical order. Also, the setup doesn't allow to automatically profile and log pipeline stage execution. Restructuring the orchestration of a pipeline in a PipelineExecutor here.
Changes

Split all logical pipeline stages into separate PipelineExecutor member functions and merge unused PipelineStages (like RUN_TRAINING and TRAINING_DONE). This allows to have a 1:1 mapping between logical pipeline stages and member functions.
Sort the pipeline stage functions sequentially according to their position in the pipeline
Add @pipeline_stage(...) decorator which wraps every pipeline stage function. When calling the decorated function we record meta information for logging (post-experiment analysis) and tracking (for online feedback) purposes. This includes start & end timestamps as well as the current "dataset/sample time". This is especially useful in experiments to be able to sort/plot different measurements by the time of the processed samples.
Move all state (that is not enclosed in controller objects like grpc) into a central ExecutionState dataclass.
Adjusted tests accordingly, removing code duplication in tests by parameterizing tests with pytest.mark.parameterize(...)
Some renaming and other minor adjustments

TODO

Fix broken integration tests
merge most recent changes on main

GitHub could not determine anymore that merge conflicts were already resolved. The multi-stage merge conflict resolution and auto rebase likely bifurcated the git history. Getting rid of the commit history via a squash merge in #437


Using an AngularMeteorObject as argument for $meteor.call.

I get an object from the database with $meteor.object(Coll, id, false) and set it to a $scope variable. I then try to save the object when a save button is clicked. I use a method call for saving, because I need to touch some users while saving. $meteor.call('updateObj', $scope.obj.id, $scope.obj).
At this point the code fails miserably because the AngularMeteorObject has some circular references and makes EJSON fail. Uncaught RangeError: Maximum call stack size exceeded
Is there a way to use the AngularMeteorObject as an argument to a method call, other than hand-picking the properties from the object to a new plain object?
I can provide sample code later if needed.

@JNissi yes a sample code will be great!

@Urigo This probably happens because of internal properties that exist on the object (used to get the collection and such).
We need to add a function like .raw or something like that to get the raw object and it's properties for situations like this.

@netanelgilad yes, but I still want to see a reproduction first, it might be a different thing

@netanelgilad is on the right track. I was also thinking of some kind of raw object getter. Like Restangular has Restangular.stripRestangular().
I created a small sample project: https://github.com/JNissi/meteor-ng-cat It's pretty much the minimal example I could think of. I didn't even use the method call in the example, because I noticed the problem is a bit broader in scope and breaks all (E)JSON.stringify() calls with an AngularMeteorObject as the parameter.

@JNissi thanks for the reproduction!
Do you want to pull request that solution?  should be pretty simple and we can help you

Is this sufficient? I feel a bit bad adding a method called 'raw' to the object, as the probability of collision with actual data seems quite possible.

how about stripAngularMeteor?

getRawObject?
On Sun, Mar 22, 2015, 18:59 Uri Goldshtein<EMAIL_ADDRESS>wrote:

how about stripAngularMeteor?
—
Reply to this email directly or view it on GitHub
https://github.com/Urigo/angular-meteor/issues/247#issuecomment-84654015
.

yes much better!


Use Postgres containment operator where available

where_object and where_object_changes are currently broken in master when using PostgreSQL JSON and JSONB for object serialization. This pull request fixes the problem in an ugly but performant fashion.
Note that Arel is unlikely to support the Postgres containment operator anytime soon, so I don't think we can rely upon it here. And since JSON and JSONB are Postgres-only for the foreseeable future, it might be OK to use database-specific syntax.
Also, I think there may be a SQL-injection security hole here. Thoughts?

Thanks for the PR, looks like a smart solution for the time being.
Your last statement you mean the code you are proposing for the Postgres JSON && JSONB columns here has a possible SQL-injection security hole?  Not sure there's much we can do about that. Did you have any thoughts?

I think we're protected because we know we're dealing with a Ruby hash by the time we build the SQL query. Any string keys will be escaped.
Likewise, I think to_json will escape potentially malicious SQL strings, but a quick search fails to turn up anything.
I haven't verified either of these assertions with tests or official documentation, hence the caveat.

Any chance we could add some tests for this functionality? I'm happy to assist but I have no experience dealing with real queries against these types of columns.  In the test suite, we can wrap any associated tests in an if ENV['DB'] == 'postgres' blocks to allow the tests to only run against Postgres (which will happen automatically on Travis CI).

I partially ask this because I've never seen the @> operator you are utilizing here. I don't even see it in the Postgres docs..

They're in the 9.4 version of those docs. Hm. The containment operator is JSONB only, so I'll have to to update the conditional.
I'll add some tests as well.

Closed in favor of #518.

Any plans on merging this PR?


JsonPath execute error on bundle references

invalid reference at "spec#parameters#iamInstanceProfile": failed
        to process JsonPath reference notifier--notifier--iamrole--binding:bindsecret#Data.InstanceProfile#"exampleIamInstanceProfile":
        JsonPath execute error: InstanceProfile#"exampleIamInstanceProfile" is not
        found

Initially I thought "Data" was incorrect because it didn't match the case sensitive "data" field in the JSON, but I fixed that and the problem is still there.

That's super-weird. It looks like it's not parsing the 'examples' properly. Err, oops.

 This would be the behaviour if you had an old version of Smith.

I can't duplicate this problem. Seems to resolve fine for me against the current master (deployed to cluster).


Deployment state [DRAFT]

Added ability to toggle randomization of voltage readings (around low bat threshold) for emulation mode via entering ">>>dv"
Added deployment state
Added deployment_manager task

If contact established transition to normal mode
Otherwise activate burnwire for 15 seconds at default duty cycle

Added initial state to config.py (application level)
Added previous state to state machine
Improved safety state to transition back to previous state
Renamed f_deploy to f_contact
Added f_contact to emulation
Added burn function to emulation
Added ability to toggle emulated contact flag via ">>>dc"
Set f_contact to True on recieved message

@jbwillis Looks like we will probably have to add a delay (about 30 minutes to an hour), this is a feature that I've been meaning to
add to the state machine/tasko anyways so I'll make a separate issue for this.

This brings up some interesting operations questions. Like, do we detumble
before deployment?
On Wed, Oct 12, 2022 at 8:43 PM thetazero @.***> wrote:

@jbwillis https://github.com/jbwillis Looks like we will probably have
to add a delay (about 30 minutes to an hour), this is a feature that I've
been meaning to
add to the state machine/tasko anyways so I'll make a separate issue for
this.
—
Reply to this email directly, view it on GitHub
https://github.com/PyCubed-Mini/flight_software/pull/221#issuecomment-1276887914,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHAS4ZX2SV36L57O6KLZZM3WC5LKVANCNFSM6AAAAAARDVGNQI
.
You are receiving this because you were mentioned.Message ID:
@.***>

That's a very good point. I think detumbling if we are over some angular velocity threshold makes sense.


BUG: Mail and Contact Number

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Footer
Shopsy's mail and contact number are not working .

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hello , PA
@arghadipmanna101
Can you please assign me this issue!

Hello  PA ,
I am contribute your project in GSSoc
And you assign mei 3,4 project work and I am fork your project and run in
my vs code then some error . I'm not running your project properly  it
breaks a parts in your code .
On Fri, 7 Jun 2024, 5:23 pm Arghadip Manna, @.***>
wrote:

Assigned #941
https://github.com/arghadipmanna101/Flipkart_Clone/issues/941 to
@SakiraAli1115 https://github.com/SakiraAli1115.
—
Reply to this email directly, view it on GitHub
https://github.com/arghadipmanna101/Flipkart_Clone/issues/941#event-13079584669,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIKL6NWY3FS2YHN75DKIYXDZGGNKPAVCNFSM6AAAAABIUFQCLKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGA3TSNJYGQ3DMOI
.
You are receiving this because you were assigned.Message ID:
@.***
com>


Add automatic Jira field lookup feature

This closes #3037 by adding a new feature (enabled by default) that will attempt to look up the customfield names from Jira based on "friendly" names (e.g. Sprint, Epic, Story Points).
Still a work in progress:

[x] Validate and test out different custom fields
[ ] Add tests
[ ] Update documentation

Hi @edtan , Thanks for the PR and your interest! I have assigned the label work in progress to this PR. Please remove the label once you are done

@edtan Jira feature collector has been migrated to its own repository. Please close this PR and create the new PR against the new repository. Link to the new repository - hygieia-feature-jira-collector


Graph SDK is not pushing the participants added/removed updates

I am working on a case, where user "user1" calls the bot, select the ivr menu, then bot invite the another user (agent) "user2" into the existing call.  In this casem user2 joins the existing call, but from graph SDK I am not receiving the updates on participants added/removed from the call.
User1 calls Bot, then Bot invites User2 into the existing call.
`this.Call.Participants.OnUpdated += this.OnParticipantsUpdated;
private void OnParticipantsUpdated(IParticipantCollection sender, CollectionEventArgs args)
{
}`
Any thoughts on this please?

I have a similar problem. It seems like the bot is not receiving events of joined participants. Scenario looks the same:

A user calls the bot
Bot answers call
Bot invites a second participant
Second participant is able to answer the call

Expected is that the bot receives a OnParticipantsUpdated event, but it doesn't. It also doesn't receive anything when the newly invited participant hangs up.
Any thoughts?

I have a similiar problem when inviting participants after the Bot answers an incoming call.
The scenario is the same as Jopie64 above.
When the participants answer the ParticipantCollection OnUpdated is not called. Not only that but the participant collection is empty after the Bot answers the call. Shouldn't it contain the incoming caller and the Bot?

Any help on this please? This is really a needed one.

It appears like this may be working again on the /beta endpoint in some scenarios.
Here's one scenario where it appears not to be working. If a caller that has a compliance recording policy assigned calls a remote media bot, it appears like the participantsUpdated event does not happen for the remote media bot (although it does appear to happen on the compliance recording bot).
@ananmishr @zhengni-msft

I have downloaded latest SDK which push the participant count and added/removed details. This is for service hosted applications.

With the following use case:

Bot joins scheduled Teams Meeting
User joins (the same) scheduled Teams Meeting

The Call.Participants.OnUpdated event does not get raised on user joining, tried with bot the v1.0 and beta endpoints.
I am able to see all of the participants if I call the following graph endpoint:
https://graph.microsoft.com/beta/communications/calls/{callId}/participants
But that means polling the endpoint for changes :(
Will the graph sdk support this scenario?

The original issue with p2p call escalating to multiparty call should be fixed with latest update.
@daltskin the issue you are seeing should be for a different scenario. Can you provide scenario-id and a time range so that we can look it up from our side?

Scenario id: 8e179f5e-9dc0-4568-baf3-136c48e54c9b
From today around 13:20 GMT

i'm seeing participant update request sent to bot, for example message id: 75c52599-2481-4d54-a983-9ffcbe2c809c
however, it returned 404 from bot. Can you check log on your side to see if everything was setup properly?

I've also the problem with the Participants.Updated event in an 1:1 call.  It is not raised.
The statefulCall.OnUpdated is raised normally.
Graph.Communication.Client  - Calls  v. <IP_ADDRESS>0, the same behaviour in v.1.0 and beta.
The problem started when we developed a a multitenant version with 2 Clients running in parallel.  with separate Call handling.
Everything works fine, events
Call.OnUpdated,
audioSocket.DominantSpeakerChanged,
AudioMediaReceived
No problem,  except the Participants.Updated
@ssulzer

Anyone find some solution regarding this issue?


Warning when compiling with GCC 14

Compilation with GCC 14.1.0 with -std=c++23 is throwing the following warning:

/xxx/zpp_bits.h: In static member function 'static constexpr decltype(auto) zpp::bits::bind_opaque<Function, Id, MaxSize>::call(auto:226&&, auto:227&&, auto:228&&)':
/xxx/zpp_bits.h:3750:19: error: name-independent declarations only available with '-std=c++2c' or '-std=gnu++2c' [-Werror=c++26-extensions]
3750 |                 } _{in, in.remaining_data()};
|                   ^
/xxx/zpp_bits.h:3774:19: error: name-independent declarations only available with '-std=c++2c' or '-std=gnu++2c' [-Werror=c++26-extensions]
3774 |                 } _{in, in.remaining_data()};
|                   ^

If I disable this warning, compilation works fine.
Probably the support for C++26s "Placeholder variables with no name" seems is the cause of this.

Correct, I’ll fix it

Thank you

Should be fixed with #170

Yes, working now. Thank you!


reformat all-contributors table

🚀 Pull Request
Description

The all-contributors table doesn't render very well on a reduced footprint mobile platform, so attempting to compromise by reducing the number of entries per row and the image size.

Click to expand mobile screenshot

@all-contributors please add @trexfeathers for promotion


RecastJSPlugin Choppy Movement since 4.2.0 RC6

The RecastJSPlugin now has choppy movement that used to smooth as a baby's but. But Since the 4.2.0-RC6 update now the movement is CHOPPY
Here is an example playground... Click around as see how choppy the box move around:
https://playground.babylonjs.com/#X5XCVT#261

Looks like it might come from https://github.com/MackeyK24/Babylon.js/commit/5ed4724f80c7b03573148986a7fb12abc124e91e


Allow users to get Contact's push name

Before adding this issue, make sure you do the following to make sure this is not a duplicate:

Search through the repo's previous issues
Read through the readme at least once
Search the docs for the feature you're looking for

Just describe the feature
Given a contact JID or number, I want to be able to know it's push name.

This is possible through USyncQuery, though we haven't been able to get it accurately working yet.

any news ?

algo?

Some news about it, guys?

any news?

any news about?


Crash when spawning PackedScenes conatining GPUParticles3D with Z-Bilboard Enabled in Compatibility

Tested versions
Reproducible in Compatibility mode using both C# and GDScript In:

v4.2.2.stable.mono.official [15073afe3]
v4.3.stable.mono.official [77dcf97d8]
v4.4.dev2.mono.official [97ef3c837]

Not Reproducible in:

Forward+ in any versions listed above

System information
Godot v4.3.stable.mono - Windows 10.0.19045 - GLES3 (Compatibility) - NVIDIA GeForce RTX 2070 (NVIDIA; <IP_ADDRESS>42) - Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 Threads)
Issue description
Possibly related to this but seems like that resolution only solved the issue for Forward+ and not Compatibility mode.
https://github.com/godotengine/godot/issues/78498
When in compatibility mode, spawning a PackedScene containing a GPUParticle3D with Z-Bilboard set causes it to crash with no errors even if --verbose is used.
Disabling Z-Bilboard does indeed prevent this from happening, and this seems to only happen in compatibility mode, but an error on crash would be valuable instead of silently stopping.
This does not apply to the root scene being loaded, it seems to be specific to loading it from a PackedScene.
I'm spawning the scenes with this
class_name GridSpawner
extends Node

@export var sceneToSpawn : PackedScene
@export var gridSize : Vector2i = Vector2(16, 16)
@export var gridCellSize : Vector3 = Vector3(10, 0, 10)

func _ready():
	for y in gridSize.y:
		for x in gridSize.x:
			print("spawning room %s %s" % [x, y])
			var spawnedRoom = sceneToSpawn.instantiate() as Node3D
			add_child(spawnedRoom)
			spawnedRoom.global_position = Vector3(x, 0, y) * gridCellSize

Here is a video of trying different tests with Z-Billboard enabled and disabled, as well as a static test with no packed scene loading:
https://github.com/user-attachments/assets/ec8fe4d9-110b-40b9-8c55-5ced73e426fa
Steps to reproduce
Create a new project in Compatibility mode
Set up a script that spawns packed scenes
Set up a scene to spawn that contains various things including a GPUParticle3D with Z-Bilboard enabled under the Drawing option
Try to spawn that scene some number of times
Over some number of spawns, the game crashes with no error
Minimal reproduction project (MRP)
Minimal Reproduction
GridSpawnerTest.tscn is the main scene that has the issue, but for completeness, StaticObjectTest.tscn is there and that seems to load fine with 256 particles, it seems to specifically be some kind of issue with spawning from PackedScenes.
I made this with 4.2.2 but this was the same code and objects I used for testing 4.3 and 4.4 dev 2
SpawnBug_4.2.2.zip

Can confirm, but not a silent crash, getting errors about failing to compile the shader

I experienced this bug too, while spawning a GPUparticle3d-containg packedscene.
I launched godot from the CLI and got some kind of error message during the crash:
ERROR: Caller thread can't call this function in this node (/root). Use call_deferred() or call_thread_group() instead.
   at: propagate_notification (scene/main/node.cpp:2422)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.3.stable.official (77dcf97d82cbfe4e4615475fa52ca03da645dbd8)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7f2d3805c520] (??:0)
[2] /lib/x86_64-linux-gnu/libGLdispatch.so.0(+0x47fe9) [0x7f2d311e6fe9] (??:0)
-- END OF BACKTRACE --
================================================================