How to reduce compile time for GPU code?

Currently it takes 6-7 minutes to compile before the model will start running on the GPU. This is expected but is there a way to compile once and run multiple times, or even to reduce the compile time? Maybe this is the price we pay for zero-cost high-level abstractions.

Normally Julia will cache compilation, to reduce compilation costs. Sadly for the GPU we currently have to turn off all the caches and each GPU function basically compiles the entire world.

Ah that makes sense. Shouldn't matter for the real-world use case (7 minute compile time << 100+ hour wall clock time simulation). I just need to pick up a hobby I can do in 6-7 minute bursts.

Do you really compile that many kernels? Or, are those 6-7 minutes really spent in CUDAnative compilation? I wonder, because individual kernel compilation tends to be relatively short (100-200 ms). Maybe we could put some timers in the CUDAnative source code a la https://github.com/JuliaGPU/CuArrays.jl/pull/279. Let's track that here: https://github.com/JuliaGPU/CUDAnative.jl/issues/354
Either way, caching code is tricky because only Julia knows when code has to be invalidated.
Created an issue: https://github.com/JuliaGPU/CUDAnative.jl/issues/353

Thank you for your feedback @maleadt! What is CUDAnative compilation? If you mean the precompilation phase when CUDAnative is first loaded, then it's not that as I start timing after all packages are loaded.
I thought 6-7 minutes was normal/expected as @vchuravy et al. reported similar GPU compilation times for their shallow water model: https://github.com/JuliaLabs/ShallowWaterBench
I haven't done any rigorous benchmarking yet but out of those 6 minutes, ~1.5 minutes are spent on compiling code that creates CuFFT plans (the first plan takes 1.5 minutes then the others take <1 second). From watching the log I'm guessing the other 4.5 minutes are evenly split between setting up the model (creating CuArrays, initializing them, etc.) and the first time step (where the kernels are getting compiled presumably).
I don't think we have that many kernels (just 5 bigger ones) but one of them
https://github.com/ali-ramadhan/Oceananigans.jl/blob/2b64d584c79ece0429f2421335ddb6bc0c6c6663/src/time_steppers.jl#L213
has several layers of inlining (it's inlining the majority of the functions in operators/ops_regular_cartesian_grid_elementwise.jl) after which it probably balloons up to be a pretty big kernel. They also have tons of arguments crammed in as the structs I was passing weren't isbitstype (working on this #59).
I should come back and update this issue once we do some proper benchmarking (note to self: nvprof seems like it's being deprecated in favor of Nsight).
Caching kernels between sessions sounds tough but will definitely look into timing compilations in CUDAnative, might provide some insight on how to speed things up.

Some idea (not sure if they would help):

Use https://github.com/JuliaLang/PackageCompiler.jl
Check to see if Julia can compile using multiple cores. Right now it only uses 1, when there are sometimes up to 28 cores available.

Also: https://github.com/vchuravy/GPUifyLoops.jl/issues/46 is now relevant to this issue.

Nono, the problematic modules you identified trigger some quadratic behavior that should just be linear. I'll fix it ASAP.

Ah interesting, would explain why it's been 46 minutes and it's still compiling haha.
@lcw may have been hitting the same issue.

Awesome!  I am guessing that I am hitting the same thing.

Thanks to @maleadt for https://github.com/JuliaGPU/CUDAnative.jl/pull/369 and @vchuravy for https://github.com/vchuravy/GPUifyLoops.jl/pull/49, GPU compile time is now down to 9 seconds!
We'll be able to enjoy these compile times once #147 is finished and merged in.
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.1.0 (2019-01-21)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

julia> using CUDAnative
julia> using Oceananigans
julia> model = Model(N=(128, 128, 128), L=(100, 100, 100), arch=GPU(), float_type=Float32);
julia> time_step!(model, 1, 1)
julia> CUDAnative.timings()
 ────────────────────────────────────────────────────────────────────────────────────
                                             Time                   Allocations
                                     ──────────────────────   ───────────────────────
          Tot / % measured:                164s / 10.7%           6.24GiB / 29.4%
 Section                     ncalls     time   %tot     avg     alloc   %tot      avg
 ────────────────────────────────────────────────────────────────────────────────────
 LLVM middle-end                 14    9.08s  52.0%   649ms    637MiB  33.9%  45.5MiB
   IR generation                 14    7.00s  40.1%   500ms    567MiB  30.2%  40.5MiB
     linking                     14    2.49s  14.2%   178ms      224B  0.00%    16.0B
     emission                    14    2.28s  13.0%   163ms    406MiB  21.6%  29.0MiB
     rewrite                     14    2.13s  12.2%   152ms    157MiB  8.34%  11.2MiB
       hide unreachable       2.02k    540ms  3.09%   267μs   20.9MiB  1.11%  10.6KiB
         find                 2.02k    295ms  1.69%   146μs    902KiB  0.05%     456B
         predecessors         2.02k    162ms  0.93%  80.1μs   13.2MiB  0.70%  6.68KiB
         replace              2.02k   68.7ms  0.39%  34.0μs    368KiB  0.02%     186B
       lower throw               14    528ms  3.03%  37.7ms   47.8MiB  2.55%  3.42MiB
       hide trap                 14   65.8ms  0.38%  4.70ms   4.23MiB  0.23%   309KiB
     clean-up                    14   98.9ms  0.57%  7.06ms   4.85MiB  0.26%   355KiB
   optimization                  14    1.99s  11.4%   142ms   69.8MiB  3.71%  4.98MiB
   device library                14   83.7ms  0.48%  5.98ms   11.5KiB  0.00%     839B
   runtime library               14   6.44ms  0.04%   460μs   7.11KiB  0.00%     520B
   verification                  14   2.97ms  0.02%   212μs     0.00B  0.00%    0.00B
 Julia front-end                 14    6.70s  38.3%   478ms   1.11GiB  60.6%  81.3MiB
 CUDA object generation          14    919ms  5.26%  65.6ms   31.9MiB  1.70%  2.28MiB
   linking                       14    780ms  4.47%  55.7ms   14.0MiB  0.75%  1.00MiB
   compilation                   14    139ms  0.79%  9.91ms   17.9MiB  0.95%  1.28MiB
 LLVM back-end                   14    769ms  4.40%  54.9ms   71.1MiB  3.78%  5.08MiB
   machine-code generation       14    124ms  0.71%  8.89ms    192KiB  0.01%  13.7KiB
   preparation                   14   38.2ms  0.22%  2.73ms   2.94MiB  0.16%   215KiB
 ────────────────────────────────────────────────────────────────────────────────────


Logs aren't flushed after test runs in all browsers

It seems like there aren't log statements produced for whichever browser runs last when running my tests.  I'm running on Windows 8.1, using grunt-protractor-runner and grunt-protractor-webdriver.  My protractor config looks like this:
exports.config = {
    framework: 'jasmine2',
    specs: ['test/e2e/{,**}/*.js'],
    seleniumAddress: 'http://localhost:4444/wd/hub',
    baseUrl: 'http://localhost:9001',
    multiCapabilities: [
        { browserName: 'firefox' },
        { browserName: 'chrome' }
    ]
};

I added some simple log statements to taskLogger.js:
TaskLogger.prototype.flush = function() {
  log.print('### browserName: ' + this.task.capabilities.browserName + EOL);
  if (this.buffer) {
	log.print('### Buffer nonempty' + EOL);
    // Flush buffer if nonempty
    log.print(EOL + '------------------------------------' + EOL);
    log.print(this.buffer);
    log.print(EOL);
    this.buffer = '';
  }
  else {
	  log.print('### Buffer empty' + EOL);
  }
  log.print('### Exiting TaskLogger#flush' + EOL);
};

My output looks like this:
Running "protractor_webdriver:default" (protractor_webdriver) task
Starting Selenium server
Started Selenium server: http://<IP_ADDRESS>:4444

Running "protractor:local" (protractor) task
[launcher] Running 2 instances of WebDriver
Session created: count=1, browserName=chrome
Session created: count=1, browserName=firefox
.Session deleted: 1 session(s) left
### browserName: chrome
### Buffer nonempty

------------------------------------
[chrome #2] PID: 8964
[chrome #2] Specs: <pathToSpecs>
[chrome #2]
[chrome #2] Using the selenium server at http://localhost:4444/wd/hub
[chrome #2] Started
[chrome #2] *.
[chrome #2]
[chrome #2]
[chrome #2] 2 specs, 0 failures, 1 pending spec
[chrome #2] Finished in 9.033 seconds

### Exiting TaskLogger#flush
[launcher] 1 instance(s) of WebDriver still running
.Session deleted: Keeping the Selenium server alive
### browserName: firefox
Shutting down Selenium server: http://<IP_ADDRESS>:4444

Done, without errors.

There are no more log statements after "### browserName: firefox", which makes me assume the script fails at the if-statement.
I'm seeing the same behavior when changing "multiCapabilities" to "capabilities" in my config and running with either Firefox or Chrome.

Previously I was running the following:
node v0.10.28
npm v2.7.5

After updating to the following versions, my issue is resolved:
node v0.12.2
npm v2.8.3

I haven't seen this issue before (or any reports of this issue) for any versions of node. However, it could be a windows-specific issue.
In any case, I'm glad the issue is resolved for you =)


⚠ DesiTorrents has degraded performance

In 8aac0f8, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 500
Response time: 1727 ms

Resolved: DesiTorrents performance has improved in fce8c90.


Rename method for clarity

Using a setter style method call for something which only mutates its
arguments is very misleading.
It looks like this change was made blindly to adress some Rubocop
warnings (the method used to be called #set_token).
Hopefully this is a bit clearer.

Coverage remained the same at 95.541% when pulling b95b6aaf3a8b00d5618ee32b69df3dc5d98273de on covidence:rename-misleadingly-named-method into c9bbb9c58ded9b330ee105778f66f86806335d63 on intridea:master.

Coverage remained the same at 95.541% when pulling b95b6aaf3a8b00d5618ee32b69df3dc5d98273de on covidence:rename-misleadingly-named-method into c9bbb9c58ded9b330ee105778f66f86806335d63 on intridea:master.

Coverage remained the same at 95.541% when pulling b95b6aaf3a8b00d5618ee32b69df3dc5d98273de on covidence:rename-misleadingly-named-method into c9bbb9c58ded9b330ee105778f66f86806335d63 on intridea:master.

Coverage remained the same at 95.541% when pulling b95b6aaf3a8b00d5618ee32b69df3dc5d98273de on covidence:rename-misleadingly-named-method into c9bbb9c58ded9b330ee105778f66f86806335d63 on intridea:master.

Coverage remained the same at 95.541% when pulling b95b6aaf3a8b00d5618ee32b69df3dc5d98273de on covidence:rename-misleadingly-named-method into c9bbb9c58ded9b330ee105778f66f86806335d63 on intridea:master.


Verification error: Invalid key for curve: "Public key is not a point"

Hello
I have an issue during verification verifyAuthenticationResponse -  in the function  convertPublicKeyToPEM
The issue: Invalid key for curve: "Public key is not a point"
it's throw by this function jwkToPem:
const ecPEM = jwkToPem({
      kty: 'EC',
      // Specify curve as "P-256" from "p256"
      crv: COSECRV[crv as number].replace('p', 'P-'),
      x: (x as Buffer).toString('base64'),
      y: (y as Buffer).toString('base64'),
 });

The service is running locally
It's happen on macOs Catalina 10.15.7 when I try to verify Touch Id
Could you please help me?

In my case x and y is not a buffers, it's objects with looks like
{
0: 184
1: 30
2: 104
3: 232
4: 100
....
}

Hello @KuznetsovNikita, can you please include how you're calling verifyAuthenticationResponse()? I'm particularly interested in the value you're passing in for credential when you call it.

Hello @KuznetsovNikita, can you please include how you're calling verifyAuthenticationResponse()? I'm particularly interested in the value you're passing in for credential when you call it.

I'm use it in this way:
      const authentication = await startAuthentication(options);

      // and later

       const authenticator: AuthenticatorDevice = {
          credentialPublicKey: registrationInfo.credentialPublicKey,
          credentialID: registrationInfo.credentialID,
          counter: registrationInfo.counter,
          transports: credential.transports,
        };

       const authenticationResponse = await verifyAuthenticationResponse({
          credential: authentication,
          expectedChallenge: options.challenge,
          expectedOrigin: expectedOrigin,
          expectedRPID: expectedRPID,
          authenticator,
        });

I didn't serialize/deserialize startAuthentication response.
I guess the issue is that I try to run this function in a browser context. I try to run in the chrome extension background service worker, and the context for this environment is close to the browser instead node.
Do you know if it possible to verify authentication in the browser?
Thank you in advance!

I found a lot of discussions in discussions page.
Looks like it's not possible.
Thank you for you time.

Thank you for looking around, I'm glad to see you were able to find previous discussions around this. Your story is yet another point convincing me to try for a "universal" refactor to make SimpleWebAuthn work in more environments than just Node. I'll attempt that as part of addressing #268


Exit octree_server on Ctrl-C, not on Enter

See above. The old way of exiting as soon as anything arrived on stdin was dangerous, and often triggered by accident.

ptal @catevita

@wally-the-cartographer merge

@pifon2a Wally seems unresponsive, also in other PRs like https://github.com/googlecartographer/point_cloud_viewer/pull/262. Would you be able to take a look?


Select stops working randomly in Chrome in macOS

latest macOS Catalina, latest Vuesax 3, latest NodeJS 12, latest Chrome (80), NPM
As this video shows, the Select component stops working out of nothing, I'm just unable to use it on Chrome. Just open the Select documentation page and play around clicking selectors and then clicking out side. Some times it works for a while and stops working, and some times it stops working at the first or second use.
https://youtu.be/LahMHi9WAuU

Same issue here. I have to reload the page, or click 3/4 times to make it work.

+1

Project is completely abandoned

+1

Same issue! +1

I found the error in the "event.target.closest" in vsSelect.vue , and I change this method for event.target.getElementsByClassName().
I wait for the merge!
    clickBlur(event) {
      //let closestx = event.target.closest(".vs-select--options");
      let closestx = event.target.getElementsByClassName(
        "vs-select--options"
      )[0];
      if (!closestx) {
        this.closeOptions();
        if (this.autocomplete) {
          this.filterItems("");
        }
        this.changeValue();
      }
    },

@ivangreve awesome!! I hope somebody merges it

+1

@ivangreve your patch have to be improved for cases if there are no options in select
event.target.getElementsByClassName(
"vs-select--options"
) -- this can be empty

Yes, you´re right. Now I'm using this piece of code
  let closestx;
  if (event.target == document.body) {
    closestx = event.target.getElementsByClassName("vs-select--options")[0];
  } else {
    closestx = event.target.closest(".vs-select--options");
  }

@ivangreve more safe is
let closestx;
if (event.target == document.body) {
closestx = event.target.getElementsByClassName("vs-select--options").item(0);
} else {
closestx = event.target.closest(".vs-select--options");
}
also there is issue with this component where there are no options (vs-select-item) in it. when you click it it will looks strange have no idea how to fix it

+1

I mailed the author a month ago with no answer so far, I hope he's ok

I switched to vue-select as this one has so many issues

I fixed this problem please use https://www.npmjs.com/package/fvuesax

I fixed this problem please use https://www.npmjs.com/package/fvuesax

Select working normally, but the table doesn't working at all.
Check these fiddle
Vuesax Original Source
Yours

I fixed this problem please use https://www.npmjs.com/package/fvuesax

i can confirm that the vs-select of that repo is working. Only changed vs-select-component and kept vs-select-item and vs-select-group from vuesax 3.11.15.
You see any problems with that? @fbasar

This issue can be reproduced by clicking and holding on the vs-select for more than 100ms. On Chrome, the mouse button release fires the click event which in turn closes the options. On Firefox it works properly. That's the reason it stops working randomly.
Changing mouse events from "click" to "mousedown" in vsSelect.vue worked out for me.
focus() {
  this.active = true;
  this.setLabelClass(this.$refs.inputSelectLabel, true);
  let inputx = this.$refs.inputselect;
  setTimeout(() => {
    // document.addEventListener("click", this.clickBlur);
    document.addEventListener("mousedown", this.clickBlur);
  }, 100);
  ...
}

+1


bug: how to exclude the current directory (as empty buffer) on session restore

Did you check docs and existing issues?

[X] I have read all the persistence.nvim docs
[X] I have searched the existing issues of persistence.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.9.0
Operating system/version
Linux Mint 21.1 Vera
Describe the bug
Suppose I have a single buffer

However, on restore, it also creates an empty buffer for the directory, which is not what I expect (the buffer to the left of App.tsx)

I've tried to exclude "curdir" from options but it doesn't work either. Actually, even if I set options to nil, it still functions as default.
Steps To Reproduce

Open and edit a file
Save the file and quit
Open and restore session

Expected Behavior
It should not create an empty buffer for current directory on restoring
Repro
No response

Must be something in your config. Never heard anyone having such an issue before

@xuanhung1509 did you ever track this down? I'll try to take a look otherwise

As far as I can tell, this has sth to do with the distro. The above issue exists in NvChad, but if I install onto LunarVim, it seems to work fine.

It's present in Astronvim as well, so that's useful info. Thanks!

@folke This is happening for to me on a fresh install of LazyVim when I start nvim on a directory (e.g. nvim .).
To reproduce:

Open nvim with nvim .
It will open neo-tree, then select and open a file.
Close nvim (<leader>qq)
Open nvim again, and restore session (pressing s in the dashboard). It will open the previous file together with an netrw buffer.

Now, if I disable netrw in LazyVim config ("netrwPlugin" in opts.performance.rtp.disabled_plugins, and I repeat the process above, instead of a netrw buffer I get an empty buffer with a title as the name of the current directory in which I opened neovim initially. This buffer has the name of the current buffer (based on vim.api.nvim_buf_get_name(0)) and no filetype whatsover (lua print(vim.bo.filetype prints nothing).

I am encountering this issue in LazyVim as well. I did switch from NeoTree to mini.files but other than that my config is pretty stock LazyVim. Driving myself crazy trying to figure out how to stop it!

Could it be that some hidden buffer is created, but the "hidden" state is not saved by persistence, so it appears after reloading the session?


Start limited to 255

Hello,
I need to build a text which is a combination of several cells, which are composed by some text with different colors:
text1 = bla bla(this one is bleu) bla
text2 = bla bla bla
bla(in blue) bla
text3 = bla bla bla
etc....
To not lose the text color, the only way I found is to work at character level.
Thus when the result cell index is higher than 255, characters are ignored.
Sirma

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 029240d0-c1eb-a219-583c-be7d28314584
Version Independent ID: 8371f791-3ce3-da3d-b142-0f7e6be85d06
Content: Range.Characters Property (Excel)
Content Source: api/Excel.Range.Characters.md
Product: excel
GitHub Login: @o365devx
Microsoft Alias: o365devx

@sirmasiang
Thanks for your feedback. We use Github issues for documentation bugs, not for developer support. Please try the VBA developer community on Stack Overflow (https://stackoverflow.com/questions/tagged/vba) where you can get help from actual developers. If you find a bug in our documentation, please let us know! Thanks!


Update Content “homepage”

Automatically generated by Netlify CMS

👷 Deploy Preview for pensive-borg-bce8d6 processing.
🔨 Explore the source changes: 39fbf54f992b5718ef34d1a8633c44e2e9a33f4e
🔍 Inspect the deploy log: https://app.netlify.com/sites/pensive-borg-bce8d6/deploys/6148e26a7a75400008c6d0f6


add multislice graph building

add support to build graph across multiple slides stored in adata

close #332 and #318


Chart Area not filled correctly.

Im having an issue when using ChartPointsAreaLayer, for some reason the fill is not going to the end of the chart, it always stops 1 point before the end. Any ideas?
Update:
Seems to be linked to addPaddingSegmentIfEdge: true

@Neilfau I am absolutely fall into the same problem, can you tell me where to set this addPaddingSegmentIfEdge: true when you generate the arealayer, thank you


Merge release 1.6.0 into develop

What does this PR do?
This PR does the merge of 1.6.0 release into develop.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #139 (f7c7c66) into develop (d3119a0) will decrease coverage by 0.18%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop     #139      +/-   ##
=============================================
- Coverage      86.25%   86.07%   -0.18%
+ Complexity       174      173       -1
=============================================
  Files             21       21
  Lines            560      560
  Branches          72       72
=============================================
- Hits             483      482       -1
  Misses            49       49
- Partials          28       29       +1

Impacted Files
Coverage Δ

...m/datadog/gradle/plugin/internal/OkHttpUploader.kt
82.52% <ø> (ø)

...com/datadog/gradle/plugin/DdAndroidGradlePlugin.kt
74.14% <0.00%> (-0.86%)
:arrow_down:


feat(modelgen):custom pk support for all platforms

[DO NOT MERGE] until ALL library teams are ready
Description of changes

Modelgen changes applied to all platforms, including:

Fixed the bug that 'id' field is auto-generated even if the different primary key is defined
Introduced three types of primary key and being processed as model metadata

ManagedId
OptionallyManagedId
CustomId (including composite key when the sort key fields are defined)

New types introduced for custom pk support

CodeGenCustomPrimaryKeyType
CodeGenCustomPrimaryKeyInfo

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] Breaking changes to existing customers are released behind a feature flag or major version update
[ ] Changes are tested using sample applications for all relevant platforms (iOS/android/flutter/Javascript) that use the feature added/modified

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #427 (9d89d17) into master (929947a) will increase coverage by 0.03%.
The diff coverage is 90.90%.

@@            Coverage Diff             @@
##           master     #427      +/-   ##
==========================================
+ Coverage   85.20%   85.23%   +0.03%
==========================================
  Files         142      142
  Lines        6698     6740      +42
  Branches     1728     1743      +15
==========================================
+ Hits         5707     5745      +38
- Misses        900      904       +4
  Partials       91       91

Impacted Files
Coverage Δ

...nc-modelgen-plugin/src/visitors/appsync-visitor.ts
94.91% <90.90%> (-0.57%)
:arrow_down:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


⚠ BCR Bot has degraded performance

In 399a7c0, BCR Bot (https://bcr.alternativasinteligentes.com/BCRApi/web/chatbot) experienced degraded performance:

HTTP code: 200
Response time: 998 ms

Resolved: BCR Bot performance has improved in 44fc114.


Stable/0.3.x: Fix @api_view wrapper detection on DRF 3.4.7+

Since the merge of https://github.com/encode/django-rest-framework/commit/5df54a711f3770de28c0aaed9350e589df082117, functions wrapped with @api_view decorator could no longer be detected which resulted in failing tests.

@marcgibbons As soon as this PR is merged, my other PRs (#650, #651, #652, #653, #655) will also pass testing.


Some minor updates

Hi @patrickelectric — many thanks for this PR. I was waiting a but because with #162 and #142 probably some of these files would be deleted or changed. Once PR #183 is merged, can you review your changes to avoid conflicts and then I think we're good to merge?

@cuducos, corrections done to be compatible with #183. Merged without problem with #142.
We are good to go.

@cuducos done.

Hi @patrickelectric — testing your PR again I got an error when running your src/clean_cnpj_info_dataset.py:
$ python src/clean_cnpj_info_dataset.py
Traceback (most recent call last):
  File "/usr/local/var/pyenv/versions/anaconda3-4.1.1/envs/serenata_de_amor/lib/python3.5/site-packages/pandas/indexes/base.py", line 2134, in get_loc
    return self._engine.get_loc(key)
  File "pandas/index.pyx", line 132, in pandas.index.IndexEngine.get_loc (pandas/index.c:4433)
  File "pandas/index.pyx", line 154, in pandas.index.IndexEngine.get_loc (pandas/index.c:4279)
  File "pandas/src/hashtable_class_helper.pxi", line 732, in pandas.hashtable.PyObjectHashTable.get_item (pandas/hashtable.c:13742)
  File "pandas/src/hashtable_class_helper.pxi", line 740, in pandas.hashtable.PyObjectHashTable.get_item (pandas/hashtable.c:13696)
KeyError: 'message'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "src/clean_cnpj_info_dataset.py", line 73, in <module>
    data[key] = data[key].astype('category')
  File "/usr/local/var/pyenv/versions/anaconda3-4.1.1/envs/serenata_de_amor/lib/python3.5/site-packages/pandas/core/frame.py", line 2059, in __getitem__
    return self._getitem_column(key)
  File "/usr/local/var/pyenv/versions/anaconda3-4.1.1/envs/serenata_de_amor/lib/python3.5/site-packages/pandas/core/frame.py", line 2066, in _getitem_column
    return self._get_item_cache(key)
  File "/usr/local/var/pyenv/versions/anaconda3-4.1.1/envs/serenata_de_amor/lib/python3.5/site-packages/pandas/core/generic.py", line 1386, in _get_item_cache
    values = self._data.get(item)
  File "/usr/local/var/pyenv/versions/anaconda3-4.1.1/envs/serenata_de_amor/lib/python3.5/site-packages/pandas/core/internals.py", line 3543, in get
    loc = self.items.get_loc(item)
  File "/usr/local/var/pyenv/versions/anaconda3-4.1.1/envs/serenata_de_amor/lib/python3.5/site-packages/pandas/indexes/base.py", line 2136, in get_loc
    return self._engine.get_loc(self._maybe_cast_indexer(key))
  File "pandas/index.pyx", line 132, in pandas.index.IndexEngine.get_loc (pandas/index.c:4433)
  File "pandas/index.pyx", line 154, in pandas.index.IndexEngine.get_loc (pandas/index.c:4279)
  File "pandas/src/hashtable_class_helper.pxi", line 732, in pandas.hashtable.PyObjectHashTable.get_item (pandas/hashtable.c:13742)
  File "pandas/src/hashtable_class_helper.pxi", line 740, in pandas.hashtable.PyObjectHashTable.get_item (pandas/hashtable.c:13696)
KeyError: 'message'

TBH it doesn't look like it's your fault. Maybe the bug was already there, maybe the data being fetched has changed… IDK.
However I can't merge something if it's raising an error. Would you mind adding something like and test (a) if it works and (b) is data still consistent?
for key in categories:
    try:
        data[key] = data[key].astype('category')
    except KeyError:
        pass

Hi @patrickelectric since #218 clean_cnpj_info_dataset.py was removed, would you mind fixing the conflicts so we can merge this?
I'm looking forward for that try ... except on the setup file ;)

Closed by inactivity


Update floodlightdefault.properties

Floodlightdefault.properties file is modified for SSL related properties. these values shall be used for setting SSL connection between switch and controller.

Floodlight support for SSL was developed as an internal project at Aricent-Gurgaon (IN) centre. For more details please visit - www.aricent.com.


Provide a binary release built on musl-c for taplo-cli

Right now to use taplo-cli I have to get cargo first and then build taplo-cli. Runime performance-wise it's a good idea but when it comes to an ease of setup it's not that good. Lately I started working more with Docker containers and GH Actions with a variety of Linux distributions on it and using taplo there to lint my tol files is quite problematic.
What I'd like to see is a pre-built release of taplo-cli I can download from this page. I think x86_64-unknown-linux-musl target will suite this purpose best.
I see there is a GitHub Action to automate such process - https://github.com/marketplace/actions/automatic-releases
Would you be interested in such a feature?

Definitely! The only reason Taplo doesn't have prebuilt binaries is that I didn't take the time to set them up.
That being said, I don't have a lot of time right now either, so PRs are welcome!

I started work on this here.
For every new tag prefixed v GH Action will compile taplo-dummy with x86_64-unknown-linux-musl target and will attach compiled application as a zip to releases page
To not mix this with your existing workflow I would see this as a new workflow file in .github/workflows
Is this good enough for taplo?

Thanks!
Looks good so far, just a few things:

Right now things are independently versioned, the CLI tags start with release-cli-*
It would also be good to have a glibc version as well I think that's still more common than musl
I would use .tar.gz instead of .zip as it should the executable permission
probably run strip on the binary? It seems to shrink its size to about half of the original
Probably include a windows (and macos) build as well while we're at it


Opening 2 files at the same time

Hello, I've been using your package to open a target file and a diagnosis file, adding a time delay of more than 20 seconds, but I can't manage to open them both, only one of them, maybe you could give a hand ? I'll leave you my code below so you can give it a look.
//////////////////////////////////////////////////////////////////////////
import os
import sys
import subprocess
import time
import threading
import keyboard
import win32com.client
from win32com.client import *
from win32com.client.connect import *
from py_canoe import CANoe
from time import sleep as wait
def just_open():
diagnose = CANoe()
diagnose.open(canoe_cfg=r'my_path_for_diagnose_file')
diagnose.start_measurement()
time.sleep(20)
target = CANoe()
target.open(canoe_cfg=r'my_path_for_target_file')
target.start_measurement()
if name=="main":
just_open()
//////////////////////////////////////////////////////////////////////////
When I run it, the diagnose file opens, it turns on for 20 seconds, then I get Exception Thrown for the return.
def Open(self, config=defaultNamedNotOptArg, autoSave=defaultNamedNotOptArg, promptUser=defaultNamedNotOptArg):
'method Open'
return self.oleobj.InvokeTypes(7, LCID, 1, (24, 0), ((8, 1), (11, 17), (11, 17)),config, autoSave, promptUser)
Here is the exception: (-2147352567, 'Exception occurred.', (0, None, None, None, 0, -2147467259), None)
I got the same exception when I try to open and start the target file first.
If I don't start the measurement before opening the second one, the first one closes and the second opens and runs without a problem.
Maybe you can give me a hand and try to give me a clue on how to keep both open and run them. Good luck!

for now, py_canoe package supports running only one CANoe application instance at a time.
if you want to run more than one instance then follow below steps:

open --> C:\ProgramData\Vector\CANoe\<version>\CAN.ini
search for SingleCOMClient and set value to 1. example: SingleCOMClient=1
comment this line https://github.com/chaitu-ycr/py_canoe/blob/main/src/py_canoe.py#L163

Hopefully this should let you open more than one canoe application instances.

It worked, thank you very much, I wasted a whole week trying to figure it out, love you.

And I got one more thing, it happens when I try to stop the measurement, I get this exception and and my program freeze for some time , it happens when I try to do it manually too

Hi @Alexrai123
This happens when you are trying to operate the CANoe application manually.
also make sure there is no duplicate CANoe instance running in background (check in task manager).
for me running multiple canoe configurations (start, stop and quit) working fine.

And if I find multiple duplicates in task manager, what should I do ? Close them ?

Looking at the logs when I'm opening both files, yes, it's opening the same files twice each. But got any idea on how to open just one ? Or what to do with the second one if I find them in task manager or somewhere else ?

before running any python script close all the CANoe application instances from task manager.
then you can start opening canoe instances from your script.
always stop simulation and quit before exiting your script. this will close all the CANoe instances you opened.
if you are not closing CANoe instances before exiting, then every time a new instance is created.
i tried below example and its working fine.
from py_canoe import CANoe
if __name__ == '__main__':
    canoe_inst = CANoe()
    canoe_inst.open(canoe_cfg=r'D:\_kms_local\py_canoe\tests\demo_cfg\demo.cfg')
    canoe_inst.get_canoe_version_info()
    canoe_inst.start_measurement()
    canoe_inst_2 = CANoe()
    canoe_inst_2.open(canoe_cfg=r'D:\_kms_local\vector_canoe_tool_notes\capl_basics\demo_cfg.cfg')
    canoe_inst_2.get_canoe_version_info()
    canoe_inst_2.start_measurement()
    canoe_inst.stop_measurement()
    canoe_inst_2.stop_measurement()
    canoe_inst.quit()
    canoe_inst_2.quit()

Each log about opening a file and starting the measurement appears 2 times each, but I cannot find more than 1 instance in task manager while the script is running or any instance when the script is not running.


400 Parameter verification failed. (api2/json/nodes/prox/qemu/9000/clone)

I am trying to clone a new machine and Terraform fails when executing this command.
https://<IP_ADDRESS>:8006/api2/json/nodes/prox/qemu/9000/clone?full=1&name=worker&newid=102&storage=local-lvm&target=<IP_ADDRESS>
If I remove target=ip from the url, clone is successful.  Here goes the output from the curl
Error : {
"data": null,
"errors": {
"target": "invalid format - value does not look like a valid node name\n"
}
}
Success: {
"data": "UPID:prox:00076C9F:0106C652:646A9B55:qmclone:9000:terraform-prov@pve!token_id:"
}
version:
erraform v1.4.6
on darwin_amd64

provider registry.terraform.io/telmate/proxmox v2.9.14

Target node. Only allowed if the original VM is on shared storage.


Added experimental sub-module and array (JACC.ones and JACC.zeros) fo…

…r OneAPI back-end

Test this please

Test this please


Always on is just always on capable, not fully always on

Documentation now makes is clear that the switch merely sets the profile to be always-on capable, not that the always-on switch will be turned on. The user needs to click the 'always connect' button to make the profile actually connect automatically.

@PeterSmithRedmond : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@stevewhims : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add custom auth header to session

(https://github.com/ukwa/npld-player/issues/13) Adds custom header to every session request.

@ikreymer what would be the best way to manually test this change?


Inheritance from non-protocol type 'DarwinBoolean'

Hello,
I'm using pod version 1.1.1 and swift 3.0 and Xcode 8.
Can you help me for this issue :- "Inheritance from non-protocol type 'DarwinBoolean'"
Thanks in advance.

I've released DrawerController 2.0.0 with Swift 2.3 support and DrawerController 3.0.0 with Swift 3.0 support.


Modified uDNS AuTest extension

addRecords to uDNS extension
Documentation for uDNS, Condition.PluginExists and other minor fixes
Got rid of an unnecessary print statement

[approve ci].

Did you run autopep on the python files? I think there is a requirement now for doing that.

Seems like microserver.test.ext was merged in without running autopep. But now all the files have been autopep'd.

[approve ci]

[approve ci]

[approve ci]


V2.0 Candidate - Modular Implementation

This PR consolidates a few changes made in order to make the library
A) JDK 11 Compatible, and
B) Modular
The following changes are in this extremely large PR

Remove sealed and non-sealed declarations in classes to make JDK 11 Compatible
Convert records back to final classes for JDK 11 Compatibility
Don't use custom/vendor-specific validation annotations for fields

@NotNull moved to jakarta.validations packages
@nullable removed entirely as Java default is Nullable. No annotation should be specified, and it doesn't override any inherited @NotNull validation

Tyrus web socket support changed for modular jakarta.websockets, removed non-modular glassfish dependency
@beta annotation removed, take a look at
Reflections updated to Duke-choice winner ClassGraph

Reflections has no support for the JRT filesystem, which is the base for any JDK 9 and up distribution
Reflections is no longer maintained, javassist and the type are undergoing major refactoring for support

Modular with JMod/JLink support for JDK 9^ distributions

I believe I've kept your architecture and style, and haven't changed the operation of any method (maybe the reflections piece a little)
Please give some consideration, Will post the maven co-ordinates for the release in a bit

I'm looking at the commits right now, thanks for the awesome work.
I was wondering though that it might not be important to support Java 11 as of now, as Java 17 is right around the corner and should be the next LTS.  This way, records can remain in, as well as sealed classes.
Also, I've seen that you've introduced a better library for reflective operations, this is not needed anymore though as I've been working on an implementation using only the ToolProvider class.
The JetBrain's library for @Nullable and @NotNull was used to provide better type safety in Kotlin, I think that using a different @NotNull annotation shouldn't introduce any issues, though I'm not sure if something like this:
private @Getter String hello; // Without @Nulllable

Would be interpreted by Kotlin as platform type, which disables type safety, or as a nullable type as it should

I am honestly not sure about kotlin, but I imagine as jetbrains originals, those are probably included inside the actual VM for it,
I tried to stick as close to JSR's as possible, and used jakarta as the default root,
I think what can happen is by using the validation processor, the types and validations would be included in the generated classes much as they would be in Kotlin

I am all for setting the base line to JDK 17 -
I can revert the seals and records replacements

RE Reflection -
I actually made a comment on my closed PR #13 on that exact thing xD
I haven't seen ToolProvider before is it part of the JDK? I was wondering about going the SPI route lol
Thanks for taking a good look and not just writing off such a large PR

I am honestly not sure about kotlin, but I imagine as jetbrains originals, those are probably included inside the actual VM for it,
I tried to stick as close to JSR's as possible, and used jakarta as the default root,
I think what can happen is by using the validation processor, the types and validations would be included in the generated classes much as they would be in Kotlin

I have checked and it seems to be working as intended.

I am all for setting the base line to JDK 17, and my use case is JDK 16, it was a change based on an observation
I can revert the seals and records replacements

As far as I remember, I also specified the intention to support Java 11 in the README, but on the other hand, it's not very convenient as of now to do something like this.

RE Reflection -
I actually made a comment on my closed PR #13 on that exact thing xD
I haven't seen ToolProvider before is it part of the JDK? I was wondering about going the SPI route lol
Thanks for taking a good look and not just writing off such a large PR

Yeah it's part of the javax.tools package, it provides an interface to the JVM's file manager so that you can query all the classes loaded by the System's ClassLoader. I've noticed though that it's not as fast as reflection(thought I'd never see the day xF), so I'm not really sure if I should include it.
Also, I've noticed that my Curve25519 implementation using the classes introduced in Java 11 doesn't work for some reason, so I reverted back to using Signal's library. I'm almost sure though that it's not modular, so I'm wondering if that would be a problem

I wouldn't worry about that too much, I'm racking up a good collection (https://github.com/GedMarc/GuicedEE-Services) and will move across anything you select -
SPI's I think could be a good choice, as they allow modules to define beautifully, and at some point, oracle is going to lock down any illegal-access commands and the encapsulation for class path scanning is going to become a real difficult, (This is my opinion?)
They also get precompiled during boot which is a nice thingy, because it gets put inside the java vm class data sharing for 9 and up (https://docs.oracle.com/javase/8/docs/technotes/guides/vm/class-data-sharing.html)
I'll revert the records and seals ;)

I wouldn't worry about that too much, I'm racking up a good collection (https://github.com/GedMarc/GuicedEE-Services) and will move across anything you select -
SPI's I think could be a good choice, as they allow modules to define beautifully, and at some point, oracle is going to lock down any illegal-access commands and the encapsulation for class path scanning is going to become a real difficult, (This is my opinion?)
They also get precompiled during boot which is a nice thingy, because it gets put inside the java vm class data sharing for 9 and up (https://docs.oracle.com/javase/8/docs/technotes/guides/vm/class-data-sharing.html)
I'll revert the records and seals ;)

No idea why, I had no idea that was a thing. It looks perfect. I'll take a deeper look and try to create a working prototype.
I should have said this before, but I noticed you don't use the var keyword inside method bodies. Considering that the whole project respects this convention, it would be nice if you could also refactor all the types that are not necessary to specify to use var. Otherwise, I'll just do it when I'll merge this PR

I wouldn't worry about that too much, I'm racking up a good collection (https://github.com/GedMarc/GuicedEE-Services) and will move across anything you select -
SPI's I think could be a good choice, as they allow modules to define beautifully, and at some point, oracle is going to lock down any illegal-access commands and the encapsulation for class path scanning is going to become a real difficult, (This is my opinion?)
They also get precompiled during boot which is a nice thingy, because it gets put inside the java vm class data sharing for 9 and up (https://docs.oracle.com/javase/8/docs/technotes/guides/vm/class-data-sharing.html)
I'll revert the records and seals ;)

I've implemented this, but I noticed that the user should define their implementation in the manifest, which kinds of defeats the purpose of auto registering listeners.

I've pushed the version I've been working on, everything I changed is included in the changelog. Sorry for the huge commit xF

Ready for review

Ready for review

Hello, I'm reviewing the code and noticed that you added the maven shade plugin. Is it needed?

Okay I can confirm that the build is not indeed working. Delombok fails silently which causes the javadocs generation to fail, but that doesn't stop the build as you specified failOnError to be false.

Oh Yes - forgot - there is a JDK Javadoc bug for sealed classes, the permit keyword is not catered for and fails the javadoc build - It's not delombok though that I saw, just two class files who's javadoc fail to render?
hmm still waiting for jdk confirmation / bug number though

mm i see it now
06:36:07
  [ERROR] Nexus Staging Rules Failure Report
06:36:07
  [ERROR] ==================================
06:36:07
  [ERROR]
06:36:07
  [ERROR] Repository "comguicedee-1484" failures
06:36:07
  [ERROR]   Rule "javadoc-staging" failures
06:36:07
  [ERROR]     * Missing: no javadoc jar found in folder '/com/guicedee/services/whatsappweb4j/<IP_ADDRESS>-jre16'
06:36:07
  [ERROR]

Oh Yes - forgot - there is a JDK Javadoc bug for sealed classes, the permit keyword is not catered for and fails the javadoc build - It's not delombok though that I saw, just two class files who's javadoc fail to render?
hmm still waiting for jdk confirmation / bug number though

[INFO] --- lombok-maven-plugin:<IP_ADDRESS>:delombok (default) @ whatsappweb4j ---
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:13: error: module not found: jakarta.validation
    requires jakarta.validation;
                    ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:14: error: module not found: jakarta.xml.bind
    requires jakarta.xml.bind;
                        ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:15: error: module not found: jakarta.websocket.api
    requires jakarta.websocket.api;
                              ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:17: error: module not found: com.google.common
    requires com.google.common;
                       ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:19: error: module not found: com.fasterxml.jackson.databind
    requires com.fasterxml.jackson.databind;
                                  ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:21: error: module not found: ez.vcard
    requires static ez.vcard;
                      ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:22: error: module not found: hkdf
    requires static hkdf;
                    ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:23: error: module not found: curve25519.java
    requires static curve25519.java;
                              ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:25: error: module not found: lombok
    requires static lombok;
                    ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\api\WhatsappAPI.java:18: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\api\WhatsappAPI.java:19: error: package lombok is not visible
import lombok.Getter;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\api\WhatsappAPI.java:20: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\socket\WhatsappWebSocket.java:18: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\socket\WhatsappWebSocket.java:19: error: package jakarta.websocket is not visible
import jakarta.websocket.*;
              ^
  (package jakarta.websocket is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\socket\WhatsappWebSocket.java:20: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\socket\WhatsappWebSocket.java:21: error: package lombok is not visible
import lombok.RequiredArgsConstructor;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\socket\WhatsappWebSocket.java:22: error: package lombok is not visible
import lombok.SneakyThrows;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\socket\WhatsappWebSocket.java:23: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\utils\CypherUtils.java:3: error: package at.favre.lib.crypto is not visible
import at.favre.lib.crypto.HKDF;
                   ^
  (package at.favre.lib.crypto is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\utils\CypherUtils.java:10: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\utils\CypherUtils.java:11: error: package lombok is not visible
import lombok.SneakyThrows;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\utils\CypherUtils.java:12: error: package lombok.experimental is not visible
import lombok.experimental.UtilityClass;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\utils\CypherUtils.java:13: error: package org.whispersystems.curve25519 is not visible
import org.whispersystems.curve25519.Curve25519;
                         ^
  (package org.whispersystems.curve25519 is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\utils\CypherUtils.java:14: error: package org.whispersystems.curve25519 is not visible
import org.whispersystems.curve25519.Curve25519KeyPair;
                         ^
  (package org.whispersystems.curve25519 is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\binary\BinaryArray.java:4: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\binary\BinaryArray.java:5: error: package jakarta.xml.bind is not visible
import jakarta.xml.bind.DatatypeConverter;
                  ^
  (package jakarta.xml.bind is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\api\WhatsappConfiguration.java:4: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\api\WhatsappConfiguration.java:5: error: package lombok is not visible
import lombok.Builder;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\api\WhatsappConfiguration.java:6: error: package lombok.Builder does not exist
import lombok.Builder.Default;
                     ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\api\WhatsappConfiguration.java:7: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\api\WhatsappConfiguration.java:8: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappDataManager.java:13: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappDataManager.java:14: error: package lombok is not visible
import lombok.AccessLevel;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappDataManager.java:15: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappDataManager.java:16: error: package lombok is not visible
import lombok.Getter;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappDataManager.java:17: error: package lombok is not visible
import lombok.RequiredArgsConstructor;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappDataManager.java:18: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappKeysManager.java:3: error: package com.fasterxml.jackson.annotation is not visible
import com.fasterxml.jackson.annotation.JsonProperty;
                            ^
  (package com.fasterxml.jackson.annotation is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappKeysManager.java:4: error: package com.fasterxml.jackson.databind is not visible
import com.fasterxml.jackson.databind.ObjectMapper;
                            ^
  (package com.fasterxml.jackson.databind is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappKeysManager.java:5: error: package com.fasterxml.jackson.databind is not visible
import com.fasterxml.jackson.databind.ObjectReader;
                            ^
  (package com.fasterxml.jackson.databind is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappKeysManager.java:6: error: package com.fasterxml.jackson.databind is not visible
import com.fasterxml.jackson.databind.ObjectWriter;
                            ^
  (package com.fasterxml.jackson.databind is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappKeysManager.java:9: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappKeysManager.java:10: error: package lombok is not visible
import lombok.AllArgsConstructor;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappKeysManager.java:11: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappKeysManager.java:12: error: package lombok is not visible
import lombok.NoArgsConstructor;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappKeysManager.java:13: error: package lombok is not visible
import lombok.SneakyThrows;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\manager\WhatsappKeysManager.java:14: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\listener\WhatsappListener.java:12: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContact.java:5: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContact.java:6: error: package lombok is not visible
import lombok.AllArgsConstructor;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContact.java:7: error: package lombok is not visible
import lombok.Builder;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContact.java:8: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContact.java:9: error: package lombok is not visible
import lombok.ToString;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContact.java:10: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\response\model\BinaryResponseModel.java:4: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\response\model\BinaryResponseModel.java:5: error: package lombok is not visible
import lombok.ToString;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappUserMessage.java:4: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappUserMessage.java:5: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappUserMessage.java:6: error: package lombok is not visible
import lombok.EqualsAndHashCode;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappUserMessage.java:7: error: package lombok is not visible
import lombok.ToString;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappUserMessage.java:8: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappMessage.java:7: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappMessage.java:8: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappMessage.java:9: error: package lombok is not visible
import lombok.ToString;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappMessage.java:10: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContactMessage.java:3: error: package ezvcard is not visible
import ezvcard.Ezvcard;
       ^
  (package ezvcard is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContactMessage.java:4: error: package ezvcard is not visible
import ezvcard.VCard;
       ^
  (package ezvcard is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContactMessage.java:5: error: package ezvcard.io.chain is not visible
import ezvcard.io.chain.ChainingTextStringParser;
                 ^
  (package ezvcard.io.chain is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContactMessage.java:8: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContactMessage.java:9: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContactMessage.java:10: error: package lombok is not visible
import lombok.EqualsAndHashCode;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContactMessage.java:11: error: package lombok is not visible
import lombok.ToString;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappContactMessage.java:12: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappGroupInviteMessage.java:5: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappGroupInviteMessage.java:6: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappGroupInviteMessage.java:7: error: package lombok is not visible
import lombok.EqualsAndHashCode;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappGroupInviteMessage.java:8: error: package lombok is not visible
import lombok.ToString;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappGroupInviteMessage.java:9: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappLocationMessage.java:5: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappLocationMessage.java:6: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappLocationMessage.java:7: error: package lombok is not visible
import lombok.EqualsAndHashCode;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappLocationMessage.java:8: error: package lombok is not visible
import lombok.ToString;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappLocationMessage.java:9: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappMediaMessage.java:7: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappMediaMessage.java:8: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappMediaMessage.java:9: error: package lombok is not visible
import lombok.EqualsAndHashCode;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappMediaMessage.java:10: error: package lombok is not visible
import lombok.SneakyThrows;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappMediaMessage.java:11: error: package lombok is not visible
import lombok.ToString;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappMediaMessage.java:12: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappTextMessage.java:6: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappTextMessage.java:7: error: package lombok is not visible
import lombok.Data;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappTextMessage.java:8: error: package lombok is not visible
import lombok.EqualsAndHashCode;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappTextMessage.java:9: error: package lombok is not visible
import lombok.ToString;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappTextMessage.java:10: error: package lombok.experimental is not visible
import lombok.experimental.Accessors;
             ^
  (package lombok.experimental is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappGenericMessage.java:4: error: package jakarta.validation.constraints is not visible
import jakarta.validation.constraints.NotNull;
                         ^
  (package jakarta.validation.constraints is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappGenericMessage.java:5: error: package lombok is not visible
import lombok.EqualsAndHashCode;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappGenericMessage.java:6: error: package lombok is not visible
import lombok.SneakyThrows;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappGenericMessage.java:7: error: package lombok is not visible
import lombok.ToString;
       ^
  (package lombok is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\response\impl\MessageResponse.java:3: error: package com.fasterxml.jackson.annotation is not visible
import com.fasterxml.jackson.annotation.JsonProperty;
                            ^
  (package com.fasterxml.jackson.annotation is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\it\auties\whatsapp4j\model\WhatsappProtobuf.java:49505: error: package com.google.protobuf is not visible
      com.google.protobuf.GeneratedMessageLite<
                ^
  (package com.google.protobuf is declared in the unnamed module, but module it.auties.whatsapp4j does not read it)
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:31: warning: [module] module not found: com.fasterxml.jackson.databind
    opens it.auties.whatsapp4j.model to com.fasterxml.jackson.databind;
                                                             ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:32: warning: [module] module not found: com.fasterxml.jackson.databind
    opens it.auties.whatsapp4j.response.impl to com.fasterxml.jackson.databind;
                                                                     ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:33: warning: [module] module not found: com.fasterxml.jackson.databind
    opens it.auties.whatsapp4j.response.model to com.fasterxml.jackson.databind;
                                                                      ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:34: warning: [module] module not found: com.fasterxml.jackson.databind
    opens it.auties.whatsapp4j.request.impl to com.fasterxml.jackson.databind;
                                                                    ^
C:\Users\alaut\NativeWhatsapp4j\src\main\java\module-info.java:35: warning: [module] module not found: com.fasterxml.jackson.databind
    opens it.auties.whatsapp4j.request.model to com.fasterxml.jackson.databind;
                                                                     ^
[INFO] Delombok complete.
[INFO]

As I told you, I've tried to do this before. Here's the issue I opened for this exact problem;
https://github.com/awhitford/lombok.maven/issues/46

Hmm that's weird, I was sure i had put in the plugins tag with the ordering,
also the zxing and protobuf as part of google commons removed.. super strange
hmm doing that though... are we sure lombok works with seals?
/C:/Java/projects/DevKit/Guiced-EE/Services/WhatsappWeb4J/target/delomboked-sources/it/auties/whatsapp4j/response/model/BinaryResponseModel.java:[13,17] sealed, non-sealed or final modifiers expecte

Hmm that's weird, I was sure i had put in the plugins tag with the ordering,
also the zxing and protobuf as part of google commons removed.. super strange
hmm doing that though... are we sure lombok works with seals?
/C:/Java/projects/DevKit/Guiced-EE/Services/WhatsappWeb4J/target/delomboked-sources/it/auties/whatsapp4j/response/model/BinaryResponseModel.java:[13,17] sealed, non-sealed or final modifiers expecte

My bad, I removed it because I thought the order specified normally was already correct. Let me try again

Probably delombok doesn't support sealed types, records were supported fully only once they are added as a stable feature.

whatsappweb4j-1.3-SNAPSHOT.zip
Building at here (guest access allowed) https://jwebmp.com/teamcity/buildConfiguration/GuicedEe_PerformReleaseJdk16/149429?buildTab=log&expandAll=true&logFilter=debug&focusLine=5
This is the current branch as it is now

ok I think that's working - trying to do a live test now


rez-test --interactive flag

I've been using a custom script to get "a Rez environment of a rez-test" for a while but it has flaws. Looking through Rez's list of issues and PRs, it looks like this has been on the menu for a while (https://github.com/nerdvegas/rez/issues/665).
I'd like to implement this work. Full disclosure, I've already written a mostly-working version of this, including unittests (in this forked branch). But before putting in a PR, I wanted to discuss it a bit more. Reading Fede's PR on the topic (https://github.com/nerdvegas/rez/pull/759) was very insightful. However I discovered a some sharp edges related to tests "requires", "on_variants" and the UX of providing an explicit --variant (or not). I think I got a list of expected behavior that is consistent and makes sense though. I'll outline it below.
Given some_package:
name = "some_package"

# ... more package definition here ...

variants = [["python-2", "backports.functools-lru-cache-1"], ["python-3"]]

tests = {
    "foo": {
        "command": "echo foo",
        "requires": ["python-2", "six"],
    },
    "fizz": {
        "command": "echo another",
        "requires": ["python-2", "extra_package-2"],
    },
    "bar": {
        "command": "echo foo",
        "requires": ["python-3"],
    },
    "buzz": {
        "command": "echo buzz",
        "requires": ["python-3", "thing-1"],
    },
    "lastly": {
        "command": "echo lastly",
        "requires": ["python-3"],
        "run_on": "explicit",
    }
}

Here's how I'm thinking that the CLI would behave:
# Gets the combination of "foo & fizz"
rez-test some_package foo fizz --interactive

# Resolves the "bar & buzz" package. "lastly" is ignored because it is "explicit"
rez-test some_package --variant 1 --interactive

# Resolves with "lastly", explicitly
rez-test some_package lastly --interactive

# Fails to resolve because --variant 0 does not match the requires of "lastly"
rez-test some_package lastly --variant 0 --interactive

# Fails to resolve because "foo / fizz" conflict with "bar", which are all default tests
rez-test some_package --interactive

# Fail to resolve because python versions conflict
rez-test some_package foo bar --interactive

# Resolves if all default tests are compatible
rez-test another_package --interactive

To summarize the behavior, I tried to make --interactive work like the actual rez-env behavior.

If --variant is included, the resolve must use that variant or fail
If a test is included explicitly, its requirements / content must be included in the resolve or fail

And the flipside also being true

If no --variant is given (and the package has a variant), a suitable resolve using any variant is returned

I'm considering also adding behavior such as "if no test names are given, not all of the default tests are guaranteed to be part of the resolve". Because it could be that not all tests are resolvable and maybe variant "0" resolves 2/4 tests but variant 1 resolves 3/4 tests. In either case, you're missing at least one test but at least you get a resolve back. The logic does not do this currently, but that may be a consideration. Maybe people will think that's a good idea.
Special consideration is given for "on_variants". For example if 2+ tests have
a common variant that resolves and the user doesn't specify an explicit
--variant, a matching resolve is returned. However if they do specify
--variant and it is invalid, the resolve conflicts and fails.
What do you think of this behavior? I can make a PR with the changes as-is but I figured it'd be better to discuss the exact behavior in a discussion thread prior to opening a PR, in case others have suggestions.

Generally I think this is fine, but there's a caveat:
You can't explicitly select variants. Even if you specifically know the variant index you want, rez just doesn't work that way (yet). You can only influence the variant it selects by changing the request. rez-test already has an --extra-packages arg, which you can use to do this. So, drop all the variant-specific stuff from this. Explicit variant selection is a much bigger topic than rez-test itself, we definitely don't want to be bringing that into the mix here.

Just so I know how to move forward with this - When you say drop the variant-specific stuff, do you mean "drop the --variant flag and all things related to on_variants completely" or do you mean something like "keep it but don't force things to fail if that specific variant cannot be found"?
FWIW I recall getting the --variant idea from Fede's previous PR so I'm not married to it. However what if you need to determine why a specific variant is failing to run tests (e.g. python 2 vs python 3 variant). Wouldn't we need this? I agree that variant selection is only really possible by changing the request. However if the end resolve is the same, isn't it alright even if the mechanism that chooses the variant is indirect?
My current implementation (variant -> appends the variant's request list -> resolve) works in my test cases but you may be thinking of edge cases I'm unaware of. For now, I'll remove that work and we can revisit it for a "version 2".


[Request] SMPlayer

Package Request Information
Name: SMPlayer
Description: a video player forked from MPV
Homepage: https://www.smplayer.info/en/info
Download link(s): https://www.fosshub.com/SMPlayer.html/smplayer-22.2.0-x64.exe
PS: I know there is a similar package https://github.com/ScoopInstaller/Extras/pull/429. But, the old request is portable version

The app can be extracted and work properly. Unfortunately SMPlayer's repo has protected their link from direct download.
Probably someone can give us a good idea about how to solve this.
Under Chrome, The link https://www.fosshub.com/SMPlayer.html?dwl=smplayer-22.2.0-x64.exe resolves to something like: https://download.fosshub.com/Protected/expiretime=1655445161;badurl=aHR0cHM6Ly93d3cuZm9zc2h1Yi5jb20vU01QbGF5ZXIuaHRtbA==/679febd20b4060ecec245dca1507cd8a31ab884d211f09b289865079430e5eae/5b8e6ac059eee027c3d78a0d/621cc4b90d4819d031b5b0e0/smplayer-portable-<IP_ADDRESS>-x64.7z, but this cannot work in direct downloads.

Have you seen Scoop Wiki: Autoupdate: Special cases for FossHub and SourceForge and scoop/lib/core.ps1: handle_special_urls? It should work if you use the recommended conventions. Happy to open a PR if not.

Have you seen Scoop Wiki: Autoupdate: Special cases for FossHub and SourceForge and scoop/lib/core.ps1: handle_special_urls? It should work if you use the recommended conventions. Happy to open a PR if not.

It works fine. Thank you for the info.


Query: Any way for navbuddy to ignore some lsp clients ?

as the question says is there any way for navbuddy to ignore some lsp clients line tailwindcss-ls or null-ls as i got this error:

was able to solve this by doing this:

M.on_attach = function(client, bufnr)
    if client.name ~= "tailwindcss" or client.name ~= "null-ls" then
        require("nvim-navbuddy").attach(client, bufnr)
    end
end

what i am curious is that is there other better way ?

asking this couz sometimes this works sometimes it doesn't.

Instead of filtering by client name, you could filter by the server's capabilities directly:
if client.server_capabilities.documentSymbolProvider then
    require("nvim-navbuddy").attach(client, bufnr)
end

You can also try using the built-in auto-attach functionality by setting auto_attach = true in the config.

Ohh can do that, Thank you!


Connect through Proxy

Describe your feature request
It would be great to be able to connect to a SurrealDB instance through a proxy directly from the Surrealist app, therefore you could directly connect with your database even if it's in a VPN somewhere only accessible through a local proxy.
Are you willing to contribute this feature?
Yes
Related pull request (if applicable)
n/a

Sounds interesting, could you give a more detailed explanation of how you would imagine this working?


Remove HTML5 Application entitlement requirement

It is no longer required to have HTML5 Application entitlement to deploy applications to HTML5 application repository because it is now a utility service: https://help.sap.com/doc/43b304f99a8145809c78f292bfc0bc58/Cloud/en-US/98bf747111574187a7c76f8ced51cfeb.html?sel1=HTML5 Applications&date=all&from=2020-08-01

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


Fix issues with variables in GuardDuty module

What this PR does / why we need it:
Users will not be able to push through with the creation of a pod that will trigger the GuardDuty Impact:Kubernetes/SuccessfulAnonymousAccess finding because of errors with the variables in the commands. See this section.
Which issue(s) this PR fixes:
Fixes variable naming and variable usage
Quality checks

[x] My content adheres to the style guidelines
[ ] I ran make test or make e2e-test and it was successful

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for picking this up @Hansuuuuuuuuuu !


Read JAVA_OPTIONS fix

If you add JVM arguments of type -Dkey1=value1 -D key2=value2... in JAVA_OPTIONS property of file security.properties, only the "-Dkey1" part gets captured and added as JVM arguments when starting the server. Adding the "-" to the "-f2" argument fix the problem because you get the rest of the value. This could also be applyed to password value because equals sign could be part of a password.

@mriccell, you need to please look at this too.


Implement Delegate Call far_call opcode

Description
This PR implements the Delegate Call opcode variant for the three types of far_call available on era vm.
With this implementation, test suite call_chain runs successfully and test suite function has f6.sol test failing (most probably because of try-catch)
Main changes

Modify far_call function under far_call.rs
Modify Context::new, adding new parameter

Closes #57

On delegate call there are changes to context register u256 and caller, check on vm2 what changes are made

NVM my bad, It was fine


Ark is amazing

@ollied123 I guess that you solve your problem ;)

Yes thank you Jaun
On 31 Dec 2017 10:38, Juan<EMAIL_ADDRESS>wrote:
@ollied123https://github.com/ollied123 I guess that you solve your problem ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/ArkEcosystem/ark-desktop/issues/494#issuecomment-354596860, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AhXBvi9RqykEUNkanv8YK2dlPpPaL8sFks5tF2QXgaJpZM4RP0Jj.


Can not be used JFXComboBox with javafxports on Android

Android logcat output:
log.txt
Android 6 and bellow dont support streams - forEach method etc.
See: row 188 in com.jfoenix.controls.JFXListCell where is: getChildren().forEach((child)->{

Here is patch:
`protected void makeChildrenTransparent(){
/getChildren().forEach((child)->{
if(child instanceof Label || child instanceof Shape){
child.setMouseTransparent(true);
}
});/
	for (Node child : getChildren()) {
		if(child instanceof Label || child instanceof Shape){
			child.setMouseTransparent(true);
		}
	}
}`

the issue has been fixed, thanks for pointing out the issue  :+1:
Regards,


Pull Request to fix "containerap up" resource group not found bug

This checklist is used to make sure that common guidelines for a pull request are followed.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

Hi @simonjj
This issue will be fixed in PR: https://github.com/Azure/azure-cli-extensions/pull/7601
You can close this PR.


Copy the existing code from google-cloud-cpp

I probably should have created this earlier.

[x] Copy holder.py and its test
[x] Copy bucket.py and its test
[x] Copy object.py and its test
[x] Copy database.py and create a test for it
[x] Copy emulator.py and create a test for it, maybe rename to testbench.py
[ ] Copy grpc_server.py and create a test for it

We decided not to move the storage/v1 gRPC implementation. I can now close this issue.


Adding a test in problem-14-Longest-collatz-sequence.english.md

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Originally, this challenge was designed to check the case of all starting number under one million produces the longest chain, as you can see on the official Project Euler website.
but in the challenge here, the highest test is on starting number under one hundred thousand.
so I added another test to check the case of all starting number under one million.

Hello, thanks for opening the PR, I'm having a little trouble understanding the intent of the PR. Please help me out here. I realize that we want to check under 10^6 rather than 10^5. Shouldn't we be checking for 9.99999E5?

Looks like this test was deliberately removed at one point. Likely to stop code from timing out.

@ojeytonwilliams I believe the commit referenced by @moT01 is yours.  Do you have anything to add here?

Thanks @moT01.
joins @RandellDawson's question,
@ojeytonwilliams why did you drop the test on 1000000, even though it is the original challenge?

@yitzhak-bloy it had most probably been done to stop the tests from timing out

Sorry for the late reply, and yes, that's exactly why it was removed.  The problem is that long running code can trigger the loop-protection, exit early and give unpredictable results.
If memory serves, I didn't find a fast enough algorithm, which would have allowed the original test to be used.  I'll take another look. If anyone else knows of a smarter algorithm, that would be great!

I researched a bit and improved the algorithm a reasonable amount.  It should be good enough for the 1,000,000 case.
@yitzhak-bloy thanks for finding my mistake!  Clearly I wasn't being careful enough when I cut out slow tests.

Thanks for fixing this @yitzhak-bloy, and congratulations on your first contribution to freeCodeCamp 🎉


Automated Package Upgrade

:tada: This PR is included in version 25.3.225 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Push docs to root instead of /preview

Description
Push docs to root instead of /preview
Type of change

[ ] :sunflower: Feature
[ ] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Test
[x] :computer: CI/Deployment
[ ] :hamster: Trivial/Minor

Issue(s)

fixes https://github.com/alcionai/corso/issues/1327

Test Plan

[x] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

@meain Can you please ensure that the test bucket for docs has a robots.txt that disallows all web crawlers. Duplicates can lead to SEO problems otherwise.

@meain - let's remove blocked label once robots.txt is added


Not really an issue but would be nice

So i came across this today
className={cn(
  'flex h-10 w-full border border-input bg-background px-3 py-2 text-sm ring-offset-background file:border-0 file:bg-transparent file:text-sm file:font-medium placeholder:text-muted-foreground focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2 disabled:cursor-not-allowed disabled:opacity-50',
  className,
)}

It would be nice if this was prettified too. not a major issue though.

This is already possible, but you have to add "cn" to the list of callees in the rule options:
"readable-tailwind/multiline": ["warn", { "callees": ["clsx", "cva", "ctl", "twMerge", "cn"] }],
"readable-tailwind/no-unnecessary-whitespace": ["warn", { "callees": ["clsx", "cva", "ctl", "twMerge", "cn"] }],
"readable-tailwind/sort-classes": ["warn", { "callees": ["clsx", "cva", "ctl", "twMerge", "cn"] }]

I'm thinking about adding it to the defaults in the next release though.

I've had the same experience! I'm glad to see that the solution is straightforward. Adding "cn" to the list of callees in the rule options does the trick. I would also recommend considering adding it to the defaults in the next release, as it could be a helpful improvement for many users.

The next bigger release will include a new concept called matchers, that will enable more fine grained control which strings will get linted. This allows much better defaults and no false positives.
The matchers feature is almost complete, but it needs more testing prior to the release. If anybody wants to try it out I'd be happy to get some feedback.
It can be installed using
npm i eslint-plugin-readable-tailwind@beta

The next bigger release will include a new concept called matchers, that will enable more fine grained control which strings will get linted. This allows much better defaults and no false positives.
The matchers feature is almost complete, but it needs more testing prior to the release. If anybody wants to try it out I'd be happy to get some feedback.
It can be installed using

Thanks for the update on the 'matchers' concept! I'm excited to try it out on my personal project right away. With two weeks of vacation ahead, this seems like the perfect time to test it out. I'll provide you with feedback on how it works. Thanks for your hard work, and I'm looking forward to using the new feature!

The next bigger release will include a new concept called matchers, that will enable more fine grained control which strings will get linted. This allows much better defaults and no false positives.
The matchers feature is almost complete, but it needs more testing prior to the release. If anybody wants to try it out I'd be happy to get some feedback.
It can be installed using

Thanks for the update on the 'matchers' concept! I'm excited to try it out on my personal project right away. With two weeks of vacation ahead, this seems like the perfect time to test it out. I'll provide you with feedback on how it works. Thanks for your hard work, and I'm looking forward to using the new feature!

I tested the beta for 2 weeks and it worked great! No issues, and no false positives!! Thanks for the awesome feature and your hard work!


Couldn't draw polygons/polylines using leaflet, leaflet.draw

I could easily draw rectangle, circle and markers as well, but I am not able to draw polygon or polyline. Here is my code,
`
import L from "leaflet";
import "leaflet/dist/leaflet.css";
import 'leaflet-draw/dist/leaflet.draw.css';
import 'leaflet-draw/dist/leaflet.draw-src.css';
import 'leaflet-draw'
useEffect(() => {
    var mapDisplay = L.map("map", {drawLayers:true, drawControl:true, drawControlTooltips:true}).setView(
      [-26.4391, 133.2813],
      5
    );
    let drawLayers = new L.FeatureGroup()
    mapDisplay .addLayer(drawLayers)

    var drawnItems = L.featureGroup().addTo(newMap);

    mapDisplay .on(L.Draw.Event.CREATED, function (event) {
         var layer = event.layer;

         drawnItems.addLayer(layer);
     });
    setMap(mapDisplay );
  }, []);
 return (
    <>
      <div
        style={{ padding: 0, margin: 0, width: "100%", height: "100vh" }}
        // ref={(el) => (mapContainer.current = el)}
        id="map"
      ></div>
    </>
  );

`
here is the versions I am using in my code
"leaflet": "^1.8.0",
"leaflet-draw": "^1.0.4",

This is a duplicate of #1026, which also includes a workaround.


Button Log out admin

Context :
As a user I want to disconnect from the application.
Add a button depending on the figma model (current one or the UI/UX one)

this was done during yaki sprint 22