COMMONSRDF-9: Bootstrap Commons site build

I've created an inital site for Commons RDF (shamelessly copied from Commons Lang). There are still a number of TODOs, but we can use this as a starting ground.

mvn site works.
But mvn clean install fails:
{code}
[INFO] --- license-maven-plugin:2.8:check (default) @ commons-rdf-parent ---
[INFO] Checking licenses...
 Why do we have both license-maven-plugin and rat plugin?

Looks good - will have to modify the site-deploy target, as it tries to push to:
https://svn.apache.org/repos/infra/websites/production/commons/content/proper/commons-rdf-parent
while I guess it should be to:
https://svn.apache.org/repos/asf/incubator/commonsrdf/site/trunk/
?
(https://issues.apache.org/jira/browse/INFRA-9260 is still pending)

Hello @stain,

.. even though (most of) those have the correct header. Why do we have both license-maven-plugin and rat plugin?

Sorry about the build failure, I only sued mvn clean site, which did not fail. My fault!
About the license-maven-plugin: I'm not sure. At commons we only use RAT. I think that's sufficient.

while I guess it should be to: https://svn.apache.org/repos/asf/incubator/commonsrdf/site/trunk/

Yes, that's the place. Note that I've discovered a glitch in the commons skin https://issues.apache.org/jira/browse/COMMONSSITE-82 Maybe we have to modify the site.css after the site deploy. I'm currently working on the skin but that will take some time.

Is there something in this pull request that remains relevant for COMMONSRDF-9 given that we now have the site live? (Perhaps the download stubs?) If not, are you OK to close this?

@stain We need to figure out how to get the project reports working (see my comment on the Dev ML). But I think we can do this in a separate PR.


Update Marked version: mitigate XSS vulnerability

Pretty sure this commit: https://github.com/chjj/marked/commit/cb72584c5d9d32ebfdbb99e35fb9b81af2b79686
Handles the XSS vulnerability mentioned here: https://nvd.nist.gov/vuln/detail/CVE-2017-17461
Issue here: https://github.com/jsdoc3/jsdoc/issues/1489

Q
A

Bug fix?
yes/no

New feature?
yes/no

Breaking change?
yes/no

Deprecations?
yes/no

Tests added?
yes/no

Fixed issues
comma-separated list of issues fixed by the pull request, if any

License
Apache-2.0

+1

+1 can it be merged?


Fix JS SPROC examples

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

#sign-off


Add an option to center children around the new parent when reparenting

Adds the functionality of proposal #8449, in the case that others feel this would be a good enhancement.
This enhances the "Reparent to New Node" tool in the Scene view by adding the ability to create a new based around the selected node(s) rather than always adding the new parent node at the origin.
Production edit: Closes https://github.com/godotengine/godot-proposals/issues/8449

Pushed a rebase to squash the commits.


Polygon2D UV editor doesn't follow filter parameters

Godot version
4.0.3, 4.1.dev 4 [5c2295ff5]
System information
Godot v4.1.dev (5c2295ff5) - Garuda Linux ZEN SMP PREEMPT_DYNAMIC Wed, 24 May 2023 17:43:43 +0000 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3050 Ti Laptop GPU () - 11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz (12 Threads)
Issue description
In Godot 3, Polygon2D UV editor followed the texture's filer parameters, making it easy to edit polygons for pixelart sprites.

However, the same doesn't happen in Godot 4, where the expected result is the texture_filter parameter of Polygon2D node being respected. Instead, a linear filter is used. Project defaults are ignored, too.

Possible fix
It seems to be fixable by adding uv_edit_draw->set_texture_filter(node->get_texture_filter_in_tree()); to Polygon2DEditor::_menu_option function in editor/plugins/polygon_2d_editor_plugin.cpp. That way, the window's texture filter is set accordingly every time a polygon is being edited. However, I'm not experienced enough in C++ to consider this fix safe and clean.
I used get_texture_filter_in_tree() instead of get_texture_filter to account for TEXTURE_FILTER_PARENT_NODE.
Steps to reproduce

Add a Polygon2D node and assign a pixelart texture to it. This lock can be used as a reference.

Set the node's Texture filter to "Nearest".
Open the UV editor of that node and behold the blurred version of the sprite.

Minimal reproduction project
N/A

I dug around but calling set_texture_filter seems okay. Opened a PR to spark up the discussion if nothing else


Exhibition Guides QA II

What does this change?

Adds a duration icon for audio/video in GuideStopCards
Rationalises font size in guide stop header and footer
Removes icons in guide stop header

How to test
Verify that the above things are true (although not sure this is required)
How can we measure success?
n/a
Have we considered potential risks?
n/a

If e2es are not necessary, can we make sure we mark them as such so the PR tests are all green? 🙏 (one last check for the reviewer as it could also flag a Cardigan change)


Added clang 7.0.0-3 to the list of tested compilers

@VioletasTheThird Thanks for your contribution =D


Not working in Safari

tested with localhost development

Can confirm, not working in firefox either :)

Can confirm, not working in firefox either :)

Localhost works in firefox but not in safari.
Seems like requests toward the backend does not work in prod on pengebingen atm.

This is finished?

Seems to work fine now


add new version unison(2.48.3)

add new version of unison(2.48.3)

So, this is the version from master added as a separate version to 14.12? Hmm, I'm unsure ATM.

I have not checked with master but it seems the same as master

I don't really see a reason to push such changes to 14.12 now, as it's no longer maintained except for severe security fixes after 15.09 got out, and that one does contain unison-2.48.3.

I hope you don't mind much.


LeConnectionOrientedChannel enters invalid state in race condition

LeConnectionOrientedChannel has a race condition:

Call disconnect and enter state DISCONNECTING
Receive on_disconnection_request and enter state DISCONNECTED
Receive on_disconnection_response and see that state is not DISCONNECTING, log invalid state and return

Not sure what the best solution is here, but it seems valid (though unlikely) that one might receive a disconnection request before disconnect is done processing.

Thanks for reporting this. It definitely looks like a race condition that should be avoided. I'll push a PR shortly.


Text Generation WebUI issue

openbmb/MiniCPM-2B-sft-bf16 on Text Generation WebUI  issue on ubuntu22.04:
set up the webUI following similar steps as window described  here:   https://github.com/intel-analytics/ipex-llm/blob/main/docs/mddocs/Quickstart/webui_quickstart.md
when loading the model, error would show as below:

hi @wluo1007 , we are working on reproducing your issue. We will inform you once we make progress.

Hi @wluo1007 , you may set export BIGDL_IMPORT_IPEX=0 before launching the webui.

thanks for the quick response, after export BIGDL_IMPORT_IPEX=0, it worked.

Hi @sgwhat I have a question, webUI default bind adress is <IP_ADDRESS> how to change it?

@niceTeen84 , python server.py --load-in-4bit --listen --listen-host xxx.xxx.xxx.xxx --listen-port xxx


Sreesruth university

@Sreesruth psvpec.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


[polyfills-loader]

This is a weird one. I'm using a standard setup via createCompatibilityConfig(). In IE11, if I try to grab a <template> element's content property, it's undefined -- as if the web component polyfill isn't fully polyfilling. I'm aware that I can't do anything with templates until after DOMContentLaoded -- that's not the issue.
The problem appears to be related to how webcomponents-bundle.js is getting included, which is done by creating a script element in JS and appending it to the <head>. If instead I include it using a <script> element right in the markup, all is fine -- as long as I include it after core-js. If I include it before core-js, "Out of stack space" errors occur.
Obviously I don't actually want to do this, since then I can't use the nice open-wc feature detection code to exclude the bundle on modern browsers.
My page has something like this in it:
<template>Oh hello</template>
<script>
window.addEventListener('DOMContentLoaded', function() {
    // just be extra super sure that all the polyfills have loaded
    setTimeout(function() {
        var node = document.querySelector('template');
        console.log(node.content); // -> undefined
    }, 5000);
});
</script>

Any thoughts/ideas?

The problem appears to be related to how webcomponents-bundle.js is getting included, which is done by creating a script element in JS and appending it to the

If this is true, this is a bug. webcomponents-bundle.js bundle is a block script and needs to be in a script tag in the source to function correctly.

Using the test app, here's essentially what gets produced (sorry it minifies things):
<script>
        window.importShim = t =>
            import (t.startsWith(".") ? new URL(t, document.baseURI) : t);
    </script>
    <script src="polyfills/core-js.577a5602a7262d6256830802d4aaab43.js" nomodule=""></script>
    <script src="polyfills/systemjs.6dfbfd8f2c3e558918ed74d133a6757a.js" nomodule=""></script>
    <script src="polyfills/regenerator-runtime.92d44da139046113cb3739b173605787.js" nomodule=""></script>
    <script>
        ! function() {
            function e(e, o) {
                return new Promise((function(t, n) {
                    document.head.appendChild(Object.assign(document.createElement("script"), {
                        src: e,
                        onload: t,
                        onerror: n
                    }, o ? {
                        type: "module"
                    } : void 0))
                }))
            }
            var o = [];

            function t() {
                "noModule" in HTMLScriptElement.prototype ? window.importShim("./d2l-test-app-2283c0e2.js") : System.import("./legacy/d2l-test-app-0c265be5.js")
            }
            "fetch" in window || o.push(e("polyfills/fetch.191258a74d74243758f52065f3d0962a.js", !1)), "noModule" in HTMLScriptElement.prototype && !("importShim" in window) && o.push(e("polyfills/dynamic-import.b745cfc9384367cc18b42bbef2bbdcd9.js", !1)), "attachShadow" in Element.prototype && "getRootNode" in Element.prototype && (!window.ShadyDOM || !window.ShadyDOM.force) || o.push(e("polyfills/webcomponents.d406f4685fdfb412c61f23b3ae18f2dc.js", !1)), !("noModule" in HTMLScriptElement.prototype) && "getRootNode" in Element.prototype && o.push(e("polyfills/custom-elements-es5-adapter.84b300ee818dce8b351c7cc7c100bcf7.js", !1)), o.length ? Promise.all(o).then(t) : t()
        }();
    </script>

Note how the webcomponent bundle is included with all the rest of the polyfills and loaded async.

Both our webpack and rollup configs support only modules. Inline module scripts are delayed until after polyfills are loaded.
We could look into supporting inline scripts, but it can get pretty complicated.

Try putting the async property of the script element to false before appending it. The scripts should now be run on time (and thus before DOMContentLoaded)

@LarsDenBakker switching my inline script to a module (in my index.html) still doesn't work. And I would have expected the 5 second timeout before execution would ensure all the polyfills are loaded anyway. If I run the same script inside a LitElement, it does weirdly have access to the content property. So I don't think it's a polyfill timing issue, but maybe a scoping (root document vs. in a component) issue? Like somehow templates are polyfilled correctly inside LitElement but not in the root document.
@justinfagnani is right though that the polyfill docs only seem to mention using the bundle with a <script> element. The loader on the other hand can be used asynchronously, so I might play around with using it and the defer attribute and then loading the rest of the polyfills and the app.
@tmsns I don't think there's any way to load a script synchronously without using a <script> element or doing something hacky like using a synchronous XHR.

Ah, now I understand the problem. You have a template element in the index.html directly, and when the template polyfill is loaded is crawls the DOM and upgrades the elements. This doesn't work with the polyfills loader, it loads polyfills before running your application.
The only way to handle your use case is indeed to not load the web components polyfills with the polyfills loader, and include the webcomponents-loader.js in your page directly. The web component polyfills include their own polyfills for promise and symbol, which clash with the core-js polyfills like you experiences. So you will also need to load core-js polyfills yourself.

Yeah that's kind-of it. I think it's that the template polyfill only runs on the main document when the DOMContentLoaded event fires. But by loading the polyfill asynchronously, DOMContentLoaded has already fired by the time it loads.
I've confirmed this with some console.logs in the polyfill's event handler -- it's adding the listener after DOMContentLoaded has already fired. Potentially it could be fixed to check for this case and execute right away in this scenario.
Regardless, now that I see what's going on, this seems more like I have a strange edge case (templates in the main document) and I can work around it in a few different ways.
Thanks for the help all!

FYI I ended up raising a defect in the Template polyfill in case they want to handle the polyfill being loaded after DOMContentLoaded.


Country request: Nauru

Can you add please?

Hi @herriotto. MapWithAI road data has already been released for Nauru. You can check it out here!


Yarn start without upload

Problem
Is there a way to have yarn start work without it uploading all the files first? At the moment if Developer A worked on the site on Monday, developer B comes along to work on it Tuesday. If developer A doesn't push all of the changes in to git and Developer B just runs yarn start it will erase everything on the dev store.
Replication steps

yarn start
Asks if i want to upload, say no, shuts off.

More Information
Currently with theme kit the normal process when moving to a project it's normal to run theme download -e env then theme watch -e env. Something that would emulate this at the very least would be nice.

I don't think this is practical because of the liquid templates needing a server to compile. And shouldn't you be pushing to git, is this scenario realistic?

@dan-gamble I think there's a couple pieces to this:

Sounds like you're suggesting a warning prompt that yarn start will overwrite everything? A check for overwriting your live theme is in place with a Y/N question.  Though it sounds like you'd want to asking this for all cases of yarn start.
You mention you use the download command from ThemeKit. This has been talked about before and comes with some challenges.  This is a relevant thread: https://github.com/Shopify/slate/issues/403
You also mentioned the watch command. Would you see a benefit in having a stand alone watch command?

We do push to git but you can't push things to git like settings_data.json, etc.

Why is that @dan-gamble? If you're concerned about that file specifically, you can add it to the ignore files in the .env file.

Hi @NathanPJF,
My fundamental issue at the moment is having yarn start perform the equivalent of a theme upload before it goes in to the equivalent theme watch.
I'll detail my current workflow when switching to a project:
cd ~/path/to/project
git pull
theme download -e env
git add .
git commit -m 'Theme download'
theme watch -e env
# Start development

This ensures that the files i have locally are up to date with the files on the server. (As a side note i think it makes sense to probably gitignore pushing settings_data.json as a rule)
Currently with Slate i'd do:
cd ~/path/to/project
git pull
yarn start
# Start development

Now if for some reason the last dev to work on the site hadn't pushed to git (unfortunately this does happen) or a client has edited a template themselves, as they were told to add a snippet to x.liquid, then when i run yarn start i would've now overwritten all of these changes as it would have uploaded my current local files.
I was just curious to see if we could get a yarn start that doesn't upload all of my local files overwriting things that are currently on the store. Making it act a bit like theme watch in the it will only bundle / upload on a local file change.

I believe that Shopify / slate team has a broken workflow for anyone working on teams. This has been called out several times, with the team failing to address the issue in every thread. It makes no sense to push local changes up to the Shopify store with every local change.
https://github.com/Shopify/slate/issues/385
https://github.com/Shopify/slate/issues/373
I'd be happy to contribute to creating a better solution, but as it stands this tool is a giant pain-in-the-ass for teams larger than 1.

Yea, this issue does look the same as #385 and #373 to be fair.
Could be worth closing this one in favour of opening #373 back up as i think that has more details than this.

@dan-gamble Have you had a chance to look at https://github.com/Shopify/slate/issues/383? I feel like this, in addition to https://github.com/Shopify/slate/issues/403, might eliminate the pains you're having right now with accidentally.

but as it stands this tool is a giant pain-in-the-ass for teams larger than 1

@auntluke I can totally understand that a detailed workflow has now been documented, but we've been successfully developing themes internally with team sizes ranging from 2-5 developers with these tools. Yes, we know there are areas that can be improved, but themes like Debut, Venture, Boundless, and Narrative are proof we have something that works.
Saying this, I understand that the Shopify Themes team only develops for the Theme store, and doesn't need to deal with edits performed after theme installation in the code editor. Thats why we love hearing from you guys about your pains and gripes 😄
Do you feel like https://github.com/Shopify/slate/issues/403 and https://github.com/Shopify/slate/issues/383 would would solve this issue?

Also @dan-gamble there is an undocumented --skipFirstDeploy flag you can pass use with yarn start, if that helps in the meantime?

I'll test the flag out when i get home tonight, also #383 looks like a solution that possible work to me.
Also, please don't mistake this issue as a "Please fix your shit" kind of post, i really like what you guys have done with Slate, it's a massive step in the right direction in terms of having a modern day workflow and i appreciate all the work you guys have put in to it!

Cool - so I'll close this in preference to #403 and #383. If there is another proposed solution, please make a new issue to discuss it.


remove bot files

Fixes #653
C# .Net core

[x] Sample 11
[x] Sample 12
[x] Sample 13
[x] Sample 14
[x] Sample 20
[x] Sample 21
[x] Sample 51
[x] Sample 52

C# Web API

[x] Sample 11
[x] Sample 12
[x] Sample 13

Node

[x] Sample 11
[x] Sample 12
[x] Sample 13
[x] Sample 14
[x] Sample 20
[x] Sample 21
[x] Sample 51

Typescript has different instructions that tell the users to manually update the bot file

@JasonSowers Can you resolve the merge conflicts? Should be quick.


[bugfix] Fix regression when filtering with multiple criteria

This was introduced with #1594 and it is a regression. I've added also a unit test to catch this in the future.

Codecov Report

Merging #1603 (0def98e) into master (5224348) will not change coverage.
The diff coverage is 25.00%.

@@           Coverage Diff           @@
##           master    #1603   +/-   ##
=======================================
  Coverage   87.48%   87.48%
=======================================
  Files          45       45
  Lines        7127     7127
=======================================
  Hits         6235     6235
  Misses        892      892

Impacted Files
Coverage Δ

reframe/frontend/cli.py
79.51% <25.00%> (ø)

Continue to review full report at Codecov.

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


Android app can't compile with this plugin

Hi,
i can't compile my android app anymore since i've added this plugin.
i've used this command to add the plugin:
cordova plugin add com.admob.google
in the console i see this error:
    [javac] ***my-app-path***\platforms\android\src\com\appfeel\cordova\admob\AdMobAds.java:56: error: package com.appfeel.cordova.connectivity does
 not exist
    [javac] import com.appfeel.cordova.connectivity.Connectivity;
    [javac]                                        ^
    [javac] ***my-app-path***\platforms\android\src\com\appfeel\cordova\admob\AdMobAds.java:57: error: package com.appfeel.cordova.connectivity.Conn
ectivity does not exist
    [javac] import com.appfeel.cordova.connectivity.Connectivity.IConnectivityChange;
    [javac]                                                     ^
    [javac] ***my-app-path***\platforms\android\src\com\appfeel\cordova\admob\AdMobAds.java:65: error: cannot find symbol
    [javac] public class AdMobAds extends CordovaPlugin implements IConnectivityChange {
    [javac]                                                        ^
    [javac]   symbol: class IConnectivityChange
    [javac] ***my-app-path***\platforms\android\src\com\appfeel\cordova\admob\AdMobAds.java:98: error: cannot find symbol
    [javac]   private Connectivity connectivity;
    [javac]           ^
    [javac]   symbol:   class Connectivity
    [javac]   location: class AdMobAds
    [javac] ***my-app-path***\platforms\android\src\com\appfeel\cordova\admob\AdMobAds.java:145: error: cannot find symbol
    [javac]     connectivity = Connectivity.GetInstance(cordova.getActivity(), this);
    [javac]                    ^
    [javac]   symbol:   variable Connectivity
    [javac]   location: class AdMobAds
    [javac] ***my-app-path***\platforms\android\src\com\appfeel\cordova\admob\AdMobAds.java:810: error: method does not override or implement a meth
od from a supertype

Hi @aledelgo sorry for the delay. From your logs it seems that there is a dependency missing (something went wrong when you installed the plugin, but don't know exactly what could it be).
Try removing the plugin and adding it again:
$ cordova plugin rm com.adob.google

You should verify that you get it from source, not from cache. To ensure this, delete everything inside /Users/<username>/.plugman/cache/*
Then add the plugin again.  I have tried re adding the plugin with no success.
I get the following error on 'cordova run android':
...
:generateDebugSources
:compileDebugJava/home/flori/dev/fallenritemonk/numbers/platforms/android/src/com/appfeel/cordova/admob/AdMobAds.java:330: error: cannot find symbol
      webView.addView(adViewLayout, params);
             ^
  symbol:   method addView(RelativeLayout,LayoutParams)
  location: variable webView of type CordovaWebView
/home/flori/dev/fallenritemonk/numbers/platforms/android/src/com/appfeel/cordova/admob/AdMobAds.java:423: error: cannot find symbol
            ViewGroup parentView = (ViewGroup) webView.getParent();
                                                      ^
  symbol:   method getParent()
  location: variable webView of type CordovaWebView
 FAILED
Note: /home/flori/dev/fallenritemonk/numbers/platforms/android/src/org/apache/cordova/globalization/Globalization.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
2 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileDebugJava'.

BUILD FAILED
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Total time: 6.112 secs

/home/flori/dev/fallenritemonk/numbers/platforms/android/cordova/node_modules/q/q.js:126
                    throw e;
                          ^
Error code 1 for command: /home/flori/dev/fallenritemonk/numbers/platforms/android/gradlew with args: cdvBuildDebug,-b,/home/flori/dev/fallenritemonk/numbers/platforms/android/build.gradle,-PcdvBuildArch=arm,-Dorg.gradle.daemon=true
ERROR running one or more of the platforms: Error: /home/flori/dev/fallenritemonk/numbers/platforms/android/cordova/run: Command failed with exit code 1
You may not have the required environment or OS to run this project

the same:
:compileDebugJava
/home/tadas/Development/development-loberta/game-app-crosswalk/platforms/android/src/com/appfeel/cordova/admob/AdMobAds.java:330: error: cannot find symbol
webView.addView(adViewLayout, params);
^
symbol:   method addView(RelativeLayout,LayoutParams)
location: variable webView of type CordovaWebView
/home/tadas/Development/development-loberta/game-app-crosswalk/platforms/android/src/com/appfeel/cordova/admob/AdMobAds.java:423: error: cannot find symbol
ViewGroup parentView = (ViewGroup) webView.getParent();
^
symbol:   method getParent()
location: variable webView of type CordovaWebView
2 errors
:compileDebugJava FAILED
FAILURE: Build failed with an exception.

Hello,
I have the same probleme when I tri to compile my Android App.
Did you find a solution ?

Seem problem, only happen after upgarde to cordova 5.0
Installed plugins:
$ cordova plugin list
android.support.v4 1.0.0 "Android Support v4"
com.admob.google 2.0.14 "AdMob Google Ads + Tappx"
com.connectivity.monitor 1.1.0 "Connectivity Monitoring"
com.google.play.services 22.0.0 "Google Play Services for Android"
nl.x-services.plugins.socialsharing 4.3.18 "SocialSharing"
org.apache.cordova.inappbrowser 0.6.0 "InAppBrowser"

error message:
:compileDebugJava
/home/user/Programming/AnyApp/platforms/android/src/com/appfeel/cordova/admob/AdMobAds.java:330: error: cannot find symbol
      webView.addView(adViewLayout, params);
             ^
  symbol:   method addView(RelativeLayout,LayoutParams)
  location: variable webView of type CordovaWebView
/home/user/Programming/AnyApp/platforms/android/src/com/appfeel/cordova/admob/AdMobAds.java:423: error: cannot find symbol
            ViewGroup parentView = (ViewGroup) webView.getParent();
                                                      ^
  symbol:   method getParent()
  location: variable webView of type CordovaWebView
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
2 errors
:compileDebugJava FAILED

FAILURE: Build failed with an exception.

Here is a work around, edit the that file by replacing lines 330 and 423 by the following:
((ViewGroup) webView.getView()).addView(adViewLayout, params);

ViewGroup parentView = ((ViewGroup) webView.getView().getParent());

the app compile, but it show the Ad in the middle instead of the bottom

Hi @appfeel could you give as any hint to fix this issue?

To add on your comment @boussouira  you can try as following to get the ad showing up at the bottom of the active screen again:
lines 330 and 423:
((ViewGroup) webView.getView().getRootView()).addView(adViewLayout, params);
ViewGroup parentView = ((ViewGroup) webView.getView().getRootView());

Hi all, I'm still testing on it. It seems that the solution proposed by @boussouira will do the job, but I would like to make some tests before pushing it. The mail thing is that the ad will be attached to the parent view of the webview and I'm evaluating which are the implications.

@glimpa Thank you for the fix

At this point there is no clear solution for cordova >= 4.0.0.
I've marked cordova >= 4.0.0 unsupported at the moment, I'm still working on this.
The main problem with the solution proposed by @boussouira  and @glimpa is that it works but the ad will overlay the web view. So take it just as a temp workaround.
Thanks for your patience, work in progress...

I did all the above steps. Now i have version 4.0.4. But still I am getting error. Advise what I am missing here. Using Cordova 4.1.2  and ionic 1.3.2
[javac] /Users/moeen/Documents/ionicApps/test/platforms/android/src/com/appfeel/cordova/admob/AdMobAds.java:443: cannot find symbol
[javac] symbol  : method getView()
[javac] location: class org.apache.cordova.CordovaWebView
[javac]                 parentView.addView(webView.getView());
[javac]                                           ^
[javac] Note: /Users/moeen/Documents/ionicApps/test/platforms/android/src/com/appfeel/cordova/admob/AdMobAds.java uses unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 5 errors
[javac] 11 warnings

BUILD FAILED
/Applications/Android Studio.app/sdk/tools/ant/build.xml:713: The following error occurred while   executing this line:
/Applications/Android Studio.app/sdk/tools/ant/build.xml:727: Compile failed; see the compiler error output for details.

Total time: 15 seconds

/Users/moeen/Documents/ionicApps/test/platforms/android/cordova/node_modules/q/q.js:126
                throw e;
                      ^

In ionic update the android platform:
ionic platform update<EMAIL_ADDRESS>

anyone solve this?

This issue is already closed, which is the problem? Please specify your cordova-cli, cordova-android and cordova-admob plugin versions if it's related.

I'm still facing this issue in ionic's latest version with capacitor.

@mayankkataria  Was this issue resolved for the issue in latest ionic and capacitor?


NextJS App Router RSC sample

Addresses #6012
This PR adds a sample that integrates @azure/msal-node with React Server Components in the NextJS App Router.
Submitting a Draft PR as I've gotten most core parts to work, but need to finalize the sample.
Saw you did some stuff with client components already @tnorling, but this sample aims to integrate @azure/msal-node, so the full capabilities of the NextJS server with RSC can be utilized. I'll gladly accept feedback and help to make this sample meet the standards of this repository 😊
Sample goals

[x] React Server Component support
[x] Forced Auth
[x] Optional Auth
[x] Gradual Consent
[x] Works with Route Handlers
[x] Works with Server Actions
[x] Logout
[x] JSDoc on AuthProvider
[ ] Multiple accounts
I don't have any stake in this feature, but will gladly help if required.
[ ] Error handling
I've mostly done the happy path, but this depends on auth scenario, so didn't pursue it for this sample.
[ ] Work with Pages Router as well?

Remarks
I tried to make a generic React Server Component integration with the AuthProvider, but that might have made this sample more complicated than needed.
I also needed to find a suitable cookie/session management library. Most I could find was either too specific for the old pages router, or so small and specific I would need to manually combine and cook something. I ended up using createCookieSessionStorage from Remix, which might sound a little weird, but since it works directly against core Web APIs it works out.

@h3rmanj this seems exciting, thanks for your time! I'll get to review it as soon as I can.

Is the idea here that every time the application needs to get data from an API it needs to go back to the server, make a token request, make the API request and then render the client content? It might be good to demonstrate the hybrid flow so that once the client has rendered it can continue to do authenticated things on the client rather than going back to the server. That can be a future enhancement, however.

This sounds like the backend for frontend proxy architecture, am I right? We recently wrote a sample implementing this pattern. I actually would love this sample to appear along the other BFF sample in that repo, but I'll leave it your and @tnorling's preference.
Regarding the hybrid flow, it might be optional but I wouldn't say its a necessary improvement on top of this. The BFF pattern has the advantage of keeping the frontend side clear of auth logic and browser storage free of auth artifacts against XSS (though this will be less of an issue in future with token binding), but hybrid flow would be more performant for sure (since the roundtrip for every API call means additional latency).

Thank you so much for putting together this PR @h3rmanj. I left a couple comments, but feel free to disregard them, just a couple of tips 😃.
@tnorling I replied to a couple of your comments where you had some questions about some of the Next.js/React specific stuff that's relatively new. Hope they're helpful.

There's a lot going on here... I agree some of these things could be abstracted away by an official library but prioritization is the name of the game... In the meantime it would be great if you could move all configurations to a central file and update the README to list out each file with a short description of what it's responsible for as well as a short high-level overview of how this works (some of the pieces are there but I think it assumes the reader is already familiar with both MSAL and Next.js RSC)

Updated the README a bit more, it's more of a first draft of things, so feedback on the structure is greatly appreciated. I think some familiarity with MSAL, RSC and Next.js would be required in general if you want to use this sample, but I could elaborate on specific things if necessary.

Is the idea here that every time the application needs to get data from an API it needs to go back to the server, make a token request, make the API request and then render the client content? It might be good to demonstrate the hybrid flow so that once the client has rendered it can continue to do authenticated things on the client rather than going back to the server. That can be a future enhancement, however.

Yes, as pointed out, this would be the BFF pattern, which is essentially what all these new React-frameworks (Remix, Next.js etc) are, BFFs with the added ability to render React.
I'm not sure how I would go about implementing a hybrid flow that can do things both on the server and client though. Would I serialize the cache on the server, then initialize an instance on the client with that cache? Or do the server just send the user to azure, and the client handle the redirect? Either way I think that would be best kept in it's own sample.
Regarding the performance part, it's essentially a tradeoff depending on the users of your application. Is it better that the acquire token + fetch api (maybe even multiple apis) waterfall happens on the client, or on the server? This greatly depends on the users condition, and the BFF would make the performance consistent between users. Since there already are client samples with msal-react, this sample would cater to the other end.

We recently wrote a sample implementing this pattern. I actually would love this sample to appear along the other BFF sample in that repo, but I'll leave it your and @tnorling's preference.

If that is a better (or additional) location for this sample is up to you, I've personally missed something like this along the official library repo, so I just started here.

I feel like I also have to mention that while App Router is stable in Next.js, React Server Components aren't really documented by React themselves yet, and Server Actions are still experimental. I've included an alternative to server actions in the sample, but I still feel like they should be included, as they play an important part to RSCs story.
Also, if anyone have any suggestion of a library that handles cookie sessions/signing, I'd greatly appreciate it. The only ones I could find was too tied up to the old pages router, or very specific for express middleware etc. While the one I use now works straight with the cookie header, which is kind of what I'm after, I think "importing remix in next" might raise some eyebrows.

@h3rmanj Finally had a chance to spin this up and try it out. It mostly works but I'm seeing an issue with the logout server action. It doesn't seem to rerender the page until I manually refresh and API calls are failing in the console (expected but the calls shouldn't be made at all after a logout)

@h3rmanj Finally had a chance to spin this up and try it out. It mostly works but I'm seeing an issue with the logout server action. It doesn't seem to rerender the page until I manually refresh and API calls are failing in the console (expected but the calls shouldn't be made at all after a logout)

I've upgraded next from 13.4.4 to 13.4.9, which seems to have fixed the issue with the page not revalidating properly after server action logout. Not sure which API calls you mean, but I don't see any now at least. Did the errors pop up in the browser console or the server console?

This looks good to me from the confidential client perspective. I am not sure Redis back-end storage is mandatory here, as that's a high bar of entry, we should maybe describe how to use this without a persistent back-end storage. .

Updated to next.js 14, server actions are no longer experimental, so I removed the route handler alternatives. Also changed the calendar page to show consent button using nextjs error component.

I'm closing this for now, as there seems to be a lack of interest.
I will revisit this, as this is close to the technical direction react is heading, and how we'll use it at our company. Hopefully either next-auth or iron-session will be out of alpha/beta stage by then, and the sample be more attractive to you.

@h3rmanj iron-session released v8 to the main stable branch this past Friday https://github.com/vvo/iron-session/releases/tag/v8.0.0

Oh, I hadn't seen that! I don't have bandwidth to look at it this year, but I welcome anyone who wants to continue working on this iteration of the sample. I'll probably do another pass at this in the start of the next year.

Thank you for the great effort, @h3rmanj!
Hope this PR can regain traction, since this sample is pretty essential to cover the direction where React ecosystem is heading.


[MB-9388] TIO can edit a shipment's billable weight and remarks

Description
TIO can edit a shipment's billable weight and remarks
Reviewer Notes

You cannot currently edit max billable weight and TIO remarks
There is currently no API support for editing the orders.authorized weight and move.tio_remarks. This behavior will be added in future cards
In a future task I want to standardize all the names being passed around (ex. billable weight, justification, etc.) but for now I kept the renamings to a bare minimum until full functionality is complete

Setup
make db_dev_e2e_populate
make server_run
make office_client_run
Log in as a TIO
Visit a move
Ensure the status of the mto_shipments for that move are APPROVED
Click on Review Weights
Click on Edit
Fill in max billable weight and remarks
Click on Save Changes
Expected result: Changes should persist, you should also get an error if max billable weight exceeds weight allowance
Click on Review Shipment Weights
Click on Edit
Fill in billable weight and remarks
Click on Save Changes
Expected result: Values should be saved
Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Messages

:book:
:link: MB-9388

  Generated by :no_entry_sign: dangerJS against a6069ae56762ff7520ad4e4cff4f3efbf1876fd9

The code looks fine, but I'm seeing some strange behavior.
I am open to putting stuff in a separate story if you think it's out of scope.

I can update the weights to be negative.
There's a few console errors for the ShipmentCard and the WeightSummary.
I think the WeightSummary needs to be updated to use the calculatedBillableWeight. All the numbers and alerts are off.

Actually I just realized my last point (and possibly the second one as well) is handled in @pearl-truss's PR.
So mostly just the negative weight is my main concern.

That's for the billable weight on the shipment right?
Sounds like we should have a story to address that for the backend. For the frontend validation, there's a story that I just created.

@YanZ777 Confirming that the validation will be done in a separate story to make negative weights impossible

Yep, that's cool with me!


addition gamesense plugin file

The plugin makes it possible to send game related data (Hp,Prayer, last trained skill xp) to the steelseries gamesense client. This enables users to display in game stats on the keyboard (such as a bar correlating to your HP)
A short example of the result in the event of prayer is shown in the attached file.
https://user-images.githubusercontent.com/60964789/172820111-955e135a-edcc-427a-8b9d-73b3455e7464.mp4

Instead of adding a dependency on org.json, you can use GSON to submit JSON in requests.

ah is that why the checks failed? I'll replace it once i find the time to do so.

ah finally, took me way to long to figure out that verification metadata

Do you really need to String->fromJson->toJson->String? https://github.com/LowieN-1848537/SteelseriesGamesense/blob/d45025d8995472f11dadc1d9baaa273a2a222b59/src/main/java/com/example/GamesensePlugin.java#L75

Ideally you would define these message types as POJOs and then serialize with Gson to prevent any formatting/interpolation errors https://github.com/LowieN-1848537/SteelseriesGamesense/blob/efd084c68b2e8ad30b59fcb9c80fb8901df741dd/src/main/java/com/example/GamesensePlugin.java#L68
You can use OSType https://github.com/LowieN-1848537/SteelseriesGamesense/blob/efd084c68b2e8ad30b59fcb9c80fb8901df741dd/src/main/java/com/example/GamesensePlugin.java#L159
Same here for a POJO message type but on the parsing end https://github.com/LowieN-1848537/SteelseriesGamesense/blob/efd084c68b2e8ad30b59fcb9c80fb8901df741dd/src/main/java/com/example/GamesensePlugin.java#L182
You should inject and use the client's existing OkHttpClient with a custom user agent https://github.com/LowieN-1848537/SteelseriesGamesense/blob/efd084c68b2e8ad30b59fcb9c80fb8901df741dd/src/main/java/com/example/GamesensePlugin.java#L248
Your config group should not contain a space (since you are not using a config you can remove it instead) https://github.com/LowieN-1848537/SteelseriesGamesense/blob/efd084c68b2e8ad30b59fcb9c80fb8901df741dd/src/main/java/com/example/GamesenseConfig.java#L7


Add more cypress front end tests

completed with commit https://github.com/yashtibrewal/leechcode/commit/dbbbfddeb0b6300876a8d958b02aa4170860e4ab


Add JVM cataloger

Implements a JVM cataloger, capable of detecting OpenJDK and Oracle JDK installations based off of release files:
IMPLEMENTOR="Oracle Corporation"
JAVA_RUNTIME_VERSION="22.0.2+9-70"
JAVA_VERSION="22.0.2"
JAVA_VERSION_DATE="2024-07-16"
LIBC="gnu"
MODULES="java.base java.compiler java.datatransfer ..."
OS_ARCH="aarch64"
OS_NAME="Linux"
SOURCE=".:git:5b97d5323482 open:git:8153097cea20"

AFAICT there is no JEP or spec for this release file (please shout out here if you find one!).
No java/jre/jdk binary signatures have been removed, since it's possible that folks may still be installing a JDK and purging the release file, but in cases when both are found the binary signature package is dropped (in favor of the JVM binary package).
Closes #2422
Closes #3188
Closes #1426

Heads up: this is blocked from being merged until an appropriate grype matcher is implemented (working on that now)


Refactor README into docs

There's a branch which is quite old & didn't get too far with the task of creating sphinx docs;
https://github.com/groveco/django-sql-explorer/tree/docs
(I've merged master to sync it)
It would be ideal to refactor the README into proper docs, leaving a simple 'getting start' type overview for a README. There's far too much detail in there at the moment.

If you're still looking for help with this. I could help.

@bojanderson that would be ideal. 👍

@marksweb should I add a folder called docs and then put all the documents in there? And then put links from the readme to the various documents in the folder? I'll pry break it up by major headings.
Once I got that feedback I'll make a fork and try to get it done in a couple days during my free time.

Resolved by #410 and #416


docs(infrastructure/esy#1099) fix docs to describe reality

Mention issue esy/esy#1099 for Linux users.
Update root binary folder created by esy '@release' create.
Explain where the binary of Oni2 is actually generated, current documentation is false since not _release folder is created in the root folder of the Oni2 repo.
I ran into an issue when running esy '@release' create, it was saying it failed since esy '@release' install had not been run prior to running it, so I added this line in the documentation.

Hope theses changes will help people to build Oni2 more easily.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: bryphe:white_check_mark: CrossR:x: AkechiShiroYou have signed the CLA already but the status is still pending? Let us recheck it.

I've just solved the conflict (done a rebase based on upstream/master I think what's left is to merge this PR).

Is there any reason why the CI has failed ? Maybe the current branch doesn't build successfully I'm not too sure, how do I go about relaunching the Azure DevOps to try and verify if the tests passes fully ??

Thanks @AkechiShiro for the updates - great improvements! And thanks for the review @glennsl

Is there any reason why the CI has failed ? Maybe the current branch doesn't build successfully I'm not too sure, how do I go about relaunching the Azure DevOps to try and verify if the tests passes fully ??

We unfortunately have some flaky tests that need to be fixed - failure doesn't look related to the changes. I do see some extra changes in the diff though - it'd be helpful to rebase so that the change is just scoped to the documentation changes. LMK if you want help with this. Otherwise, doc changes look good to me :+1:


How to cancel Text Layer's editing status

When filling text to Text Layer, if the Text Layer's status is editing, the fill value will fail.
So, how to cancel Text Layer's editing status?

That's not an skpm issue


Update storage-premium-storage-preview-portal.md

Add a bullet point for updating fstab

Hi @siriusk-MSFT, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


OpenStack image v2 api does not handle pagination

Summary
When listing images with list_images() on OpenStack, not all images are listed.
Detailed Information
The OpenStack image service (Glance) v2 api does have a pagination mechanism. So when iterating over all images, the user needs to look for a next link. See https://docs.openstack.org/api-ref/image/v2/#list-images
But this next link is not handled in the current OpenStack driver. This happens with apache-libcloud 3.0.0 from pypi.
The relavant code is here: https://libcloud.readthedocs.io/en/stable/_modules/libcloud/compute/drivers/openstack.html#OpenStack_2_NodeDriver.list_images

I remember that from this PR https://github.com/apache/libcloud/pull/1263.

listing images seems to work slightly different than the other ones unfortunately so I'm gonna leave that out of the scope of this PR for now.

@vdloo fix is here: https://github.com/apache/libcloud/pull/1467


Update pkg-descr

add pertinent information.

Fine.  The fact that it was obvious to you is beside the point.  My case in point https://forum.opnsense.org/index.php?topic=37011.0
Your call.

I'm trying to separate concerns. Adding more boilerplate everywhere only leads to more maintenance and further hit and misses.


Update the media port in the SDP parser

Description
There is something wrong in the current SDP parser that is affecting Simulcast and some feedback mechanisms. I've compared the SDPs generated by the previous solution and the current one and this is the only thing that is different, and that could be causing those issues. Not sure 100% if there is any other cause.
[] It needs and includes Unit Tests
Changes in Client or Server public APIs
Not needed.
[] It includes documentation for these changes in /doc.

this might fix #1079

confirm it fixes #1079


Final tweaks, bug fixes, and performance checks for this stage of Uproot-writing

Follows up on #426 with similar work for TTrees.

Performance testing, just Uproot and C++ ROOT this time. Uses the same (singly) jagged dataset as https://arxiv.org/abs/2102.13516 .
scaling-trees-uproot.py
import time

import numpy as np
import awkward as ak
import uproot

content = np.fromfile("/home/jpivarski/storage/data/chep-2021-jagged-jagged-jagged/sample-content.float32", dtype=np.float32)
offsets = np.fromfile("/home/jpivarski/storage/data/chep-2021-jagged-jagged-jagged/sample-offsets1.int64", dtype=np.int64)

array = ak.Array(ak.layout.ListOffsetArray64(ak.layout.Index64(offsets), ak.layout.NumpyArray(content)))

print(repr(array))
# <Array [[-0.423, 2.34, -0.757, ... 1.41, 0.72]] type='134217728 * var * float32'>

ENTRIES_PER_BASKET = 50000

starttime = time.time()

with uproot.recreate("/tmp/output.root", compression=None) as fout:
    fout.mktree("tree", {"branch": array.type})
    for start in range(0, len(array), ENTRIES_PER_BASKET):
        fout["tree"].extend({"branch": array[start : start + ENTRIES_PER_BASKET]})

print(f"entries per basket {ENTRIES_PER_BASKET}, time {time.time() - starttime}")

entries per basket 1000, time 61.869351863861084
entries per basket 1000000, time 15.633187770843506
entries per basket 2000, time 34.52807021141052
entries per basket 500000, time 14.124958038330078
entries per basket 5000, time 16.41567373275757
entries per basket 200000, time 13.47899842262268
entries per basket 10000, time 15.130658864974976
entries per basket 100000, time 13.349303483963013
entries per basket 20000, time 13.790864944458008
entries per basket 50000, time 13.850778579711914

scaling-trees-ROOT.cpp
#include <iostream>
#include <chrono>

#include "TFile.h"
#include "TTree.h"
#include "TBranch.h"

const int64_t ENTRIES_PER_BASKET = 50000;

int main(int argc, char** argv) {
  FILE* content_file = fopen("/home/jpivarski/storage/data/chep-2021-jagged-jagged-jagged/sample-content.float32", "r");
  FILE* offsets_file = fopen("/home/jpivarski/storage/data/chep-2021-jagged-jagged-jagged/sample-offsets1.int64", "r");

  float* content = new float[1073741824];
  int64_t* offsets = new int64_t[134217729];

  for (int64_t step = 0;  step <<PHONE_NUMBER>;  step += 1024*1024) {
    fread(&content[step], sizeof(float), 1024*1024, content_file);
  }
  fread(offsets, sizeof(int64_t), 134217729, offsets_file);

  auto starttime = std::chrono::high_resolution_clock::now();

  auto f = new TFile("/tmp/output.root", "RECREATE");
  f->SetCompressionLevel(0);
  auto t = new TTree("tree", "");
  t->SetAutoFlush(0);
  t->SetAutoSave(0);

  uint32_t counter;
  float array[16];  // this is big enough

  t->Branch("nbranch", &counter, "nbranch/I", 100*1024*1024);      // temp TBasket must be bigger
  t->Branch("branch", array, "branch[nbranch]/F", 100*1024*1024);  // than written TBasket size

  for (int64_t i = 0;  i < 134217729 - 1;  i++) {
    int64_t start = offsets[i];
    int64_t stop = offsets[i + 1];
    counter = stop - start;

    for (int64_t j = start;  j < stop;  j++) {
      array[j - start] = content[j];
    }

    t->Fill();
    if (i % ENTRIES_PER_BASKET == ENTRIES_PER_BASKET - 1) {
      t->FlushBaskets();
    }
  }

  t->Write();
  f->Close();

  auto stoptime = std::chrono::high_resolution_clock::now();

  std::cout << "entries per basket " << ENTRIES_PER_BASKET << ", "
            << "time " << std::chrono::duration_cast<std::chrono::microseconds>(
                 stoptime - starttime
               ).count() / 1e6
            << std::endl;

  return 0;
}

entries per basket 1000, time 26.1168
entries per basket 1000000, time 15.4534
entries per basket 2000, time 16.5195
entries per basket 500000, time 15.6402
entries per basket 5000, time 14.8063
entries per basket 200000, time 15.2132
entries per basket 10000, time 15.4887
entries per basket 100000, time 15.0006
entries per basket 20000, time 14.5771
entries per basket 50000, time 14.309

Now the most significant effect is the number of entries per TBasket/extend/flush/cluster. For these data, 1 entry is very nearly 40 bytes, so 1000 entries is 40 kB and 1000000 entries is 40 MB.

So for writing performance on par with C++ ROOT, you need to be writing at least 100 kB per branch in each call to extend. (The lines converge at 5000 entries per flush, which is 200 kB, but that's for 2 branches, and the data vs overhead scales with the number of branches, so that's why the rule is "100 kB per branch in each call to extend.)

Basically, it improves speed by not writing small baskets. So is there a way to set the min size per tree, such as
uproot.newtree(..., flushsize=100000)

And then do:
file.extend(..., flush=False)

And this way, keep stuff in memory and only write to file when the basket is full. So is this (https://indico.cern.ch/event/840667/contributions/3527109/attachments/1908764/3153297/uproot-irisfellow-final.pdf) out of date for uproot4 now?

Uproot 3 is out of date now. Reik's IRIS-HEP presentation on Uproot TTree-writing was the Uproot 3 implementation. The Uproot 4 implementation (#321) now completely replaces it,

with a different public API (not much different, mostly allowing assignment and uproot.WritableDirectory.mktree instead of introducing an uproot.newtree function),
with considerably reorganized internal mechanics for maintainability,
without flushing logic, which is what you're referring to above. All that Uproot 3's flushsize did (or attempted to do; it sometimes didn't work) was gather array data until the limit is reached, then concatenate and write. That's easy enough to do in a script, but mixing that logic with the file-writing logic made quite a mess. So we also dropped append.

The downside of dropping the flushsize logic is that each uproot.WritableTree.extend is inexorably bound to one TBasket—no exceptions. Writing files with lots of little TBaskets is problematic. Hence, the new interface, if used unwisely, would lead users to create files with lots of little TBaskets. I just hope I've posted enough warnings to guard against that.
This PR doesn't seem to introduce any performance improvements, not like #426 for histograms. It's just where I tested it at scale and fixed a few bugs that were revealed by doing so.


Add definitions for React DnD

Adding React DnD type definitions for React DnD v1.1.4, which is the latest
version.
Paired with @vsiao on parts of this

react-dnd/react-dnd.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/react-dnd
http://bower.io/search/?q=react-dnd
others?

[ ] has a test file? (react-dnd/react-dnd-tests.ts or others)
[ ] pass the Travic-CI test?

@epelz thank you for your contributions.
please rename react-dnd/react-dnd-test.ts to react-dnd/react-dnd-tests.ts

@vvakame Woops, should be all set now.

@epelz thanks mate!


ERC20 Token non-custodial

VerusDeskWallet v0.6.5-3
Token eth /  link have the same pub address, correct!
Token link/eth cannot be sent, see Attache.

ETH stuck in chain is not written well (etherscan.io )
Transaction ID (TXID): 0xdc4c88570c17343bf28d80ddffe1749c9111fb7676f1c93c77bc6e696d81bdec ((veruswallet))
ETH Transaction to Bitstamp, stopped, gas problem?
IDtx: 0xd606dcfa6060b99cebda5408582ba7b456aaf129275b0d64ec94ce445296570f

Please release my tokens for transmission, thank you very much.
<EMAIL_ADDRESS>

Just transferred my Ethereum from address 1 on  a VM to address 2 on my physical machine.
It cannot send the entire amount, the last digit (max 9 sats) needs to be removed in order for the transaction to succeed, leaving 8e-9 ETH in my wallet.

Tested again you may see further errors in the input.
Test TX with link to Binance: aborted with known message, the fee can not preset.

Test Tx ETH 0.009 Amount.

Again aborted because of gas problem, but I have enough ETH in my deposit.
Meldung: Error Occured durind contract execution

2 Transactionen von Bitstamp wurden korrekt gesendet, In verusDeskWallet kein Eingang notiert?

Withdrawal
Jun. 03, 2020
09:48 PM UTC
Main Account
0.02000000 ETH
0.00100000 ETH
Transaction ID (TXID): 0x182a7c220f6e61631acd88ebe473de8c0f3131848b5e6728dfc4711f81120c36 ((veruswallet))
Withdrawal
Jun. 01, 2020
12:52 PM UTC
Main Account
0.00682720 ETH
0.00100000 ETH
Transaction ID (TXID): 0xdc4c88570c17343bf28d80ddffe1749c9111fb7676f1c93c77bc6e696d81bdec ((veruswallet))

Link IN/OUT all send attempts failed? No indications of incorrect input to be seen!

I have now received all the information that I know of that there are problems with VerusDeskWallet deposits/withdrawals for which I am not responsible.
I am waiting for further inputs from Dev`s.

Have Verus Desk Wallet on a 2nd PCdesk newly set up with new SEED/address.
Test: 0.5 Link from 1st PcDesk sent to new address, unfortunately the same error message and abort appears!
Please contact Miketouth and discuss the situation, thanks.

Just transferred my Ethereum from address 1 on a VM to address 2 on my physical machine.
It cannot send the entire amount, the last digit (max 9 sats) needs to be removed in order for the transaction to succeed, leaving 8e-9 ETH in my wallet.

Yes, I know, that's why my ETH deposit is filled accordingly.
I have also tested with two vrsc-profiles on 2 machines, again no transaction is completed and the test is aborted immediately.
Please connect to Miketout to solve the problem.

Continued imprisonment for ERC20 ETH/ ChainLink Token.
Is there any progress to report on the matter?

Update Verus 0.7.0 installed.
ETH can now deposit/pay out correctly in the Explorer.
Token ChainLink payout still blocks with known warning.
!
Is there any progress to report on the matter?

Verus Desktop v0.7.0-3
Chainlink still blocked, our efforts are not bearing fruit?

Is there any progress to report on the matter?

Today:   Test transmission ETH

a few minutes later Out message...

Explorer reports cecancelet, fee charged (loss)
https://etherscan.io/tx/0x38219fe242d6de20c0f037c4ed0613c8a65b5aedd3b7776e21a3c286319396e6
Token Chainlink still blocked .
Is there any progress to report on the matter?

Even on 2nd PC with new profile Veruswallet v0.7.0-3 and current SEED, will erc20 Token Link/ETH remain blocked? A solution to this problem is urgently desired!

Is there any progress to report on the matter?

Verus v0.7.0-4, Still Token link/eth payout blocked?

Is there any progress to report on the matter?

"ERC20 token transmission failed"
Verus v0.7.0-4 In my case, so I hope I'm not the only one, I can deposit but not withdraw.
The link below lists the reasons why tokens are not paid out.
https://info.etherscan.com/reason-for-failed-transaction/
Hello to VerusDeskWallet users, ERC20 Token Link/ETH deposits and withdrawals are not executed correctly, messages about too little GAS do not reflect the fact that there are enough ETH credits. Has anyone had the same experience?  The support in case of discrepancies could not help so far. I report a technical program error?
Is there any progress to report on the matter?

So far this problem has only been reported and reproduced for LINK (no other ERC20s) in a specific scenario, and it is being looked into. In the meantime, if you experience this problem with LINK, copy your ERC20 WIF key from the receive screen and use it to access your LINK wallet from another source.

In my "ChainLink" case, was moved to another account with Wkey, so my problem is solved.
Since there is no security regarding Link-ERC20 tokens yet, I will not use VerusWallet, thank you for your help.

There is security, as all stored lite mode wallets (electrum & erc20) are securely password encrypted, but the LINK usability issue is under development. Thank you for the feedback and responsiveness so far. I'll keep this issue open until it is resolved, until then, if anyone experiences the same issue, feel free to add to this thread.

This, should now be resolved in the latest version (0.7.3 and newer) due to a refactor of the ETH/ERC20 backend


cannot get the remove item work

i cannot get the controller works for my remove item.
here's my controller code for removing item:
public function getRemoveitem($id){
$product = Product::whereId($id)->first();
Cart::remove($product->rowid);
return Redirect::to('store/cart');
}
and this is my link to delete the product in the view:
a href="/store/removeitem/{{$product->rowId}}">{!!Html::image('img/remove.gif', 'Remove product')!!}
the error said "Missing argument 1 for App\Http\Controllers\StoreController::getRemoveitem()"
if i dd($product->rowid) it gave me some value. but i cant seem to put the rowid of product in my controller so that i can remove it from my shopping cart.
Can someone gave a hint to this matter?

My bad. It should be $product->rowid instead of $product->rowId. Now its working fine.
Great plugin.

Glad you got it to work!


Mennekes - Missing "Targetare.ro" link; - Graph without active data for the jobs on

ENVIRONMENT: production
URL: https://scrapers.peviitor.ro
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:

Open the URL in the browser
Search for "  Mennekes " Company
Click on the "Targetare.ro" link
Open "Targetare.ro" link.
Check the graph functionality

EXPECTED RESULTS:
The "Targetare.ro" link is functional and the page is opened.
The graph have active data and show the number of valid jobs
ACTUAL RESULTS:
Missing "Targetare.ro" link
Graph without active data, doesn't show the number of valid jobs
ATTACHMENTS:

Fixed

Re-tested, The "Targetare.ro" link is functional and the page is opened.
The graph have active data and show the number of valid jobs


Is Exodus4D still around?

Notice that there hasn't been any activity on the project since April and @exodus4d github activity has disappeared over the last few months. Hopefully everyone is safe and healthy and this is just an extended summer vacation?

He is, join the slack and you will find him on there.


Cors

Support for CORS in Vert.x Apex:
http://www.w3.org/TR/cors/

@purplefox I can get this to work, still getting blocked
Here is my router setup
        Router router = Router.router(vertx);
		router.route().handler(CookieHandler.create());
		router.route().handler(SessionHandler.create(LocalSessionStore.create(vertx, SESSION, 10000)));
		router.route().handler(basicAuthHandler);
		router.route().handler(BodyHandler.create());
		router.route().handler(CorsHandler.create("*"));
		router.get("/api/auth").handler(new AuthServiceHandler());
  ...

No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8081' is therefore not allowed access. The response had HTTP status code 401
Am I missing something?

Hi Philip,
Can you show me a reproducer and a bit of explanation about what you're
trying to do?
On 08/05/15 21:49, Philip K. Adetiloye wrote:

@purplefox https://github.com/purplefox I can get this to work,
still getting blocked
Here is my router setup
|         Router router = Router.router(vertx);
router.route().handler(CookieHandler.create());
router.route().handler(SessionHandler.create(LocalSessionStore.create(vertx, SESSION, 10000)));
router.route().handler(basicAuthHandler);
router.route().handler(BodyHandler.create());
router.route().handler(CorsHandler.create("*"));
router.get("/api/auth").handler(new AuthServiceHandler());
...
|
No|'Access-Control-Allow-Origin'| header is present on the requested
resource. Origin 'http://localhost:8081' is therefore not allowed
access. The response had HTTP status code 401
Am I missing something?
—
Reply to this email directly or view it on GitHub
https://github.com/vert-x3/vertx-apex/pull/20#issuecomment-100358819.

If there is an issue with the CORS support in master, can you please file an issue against that, with a reproducer?

Oh my bad, please ignore this.
Will push a reproducer for this. Thanks


Add changelog for v1.7.2

What this PR does / why we need it:
Add changelog for v1.7.2. I'm planning to cut this release today
Which issue(s) this PR fixes:
xref #2994
What type of PR is this?
/kind documentation
Does this PR introduce a user-facing change? Then add your Release Note here:
NONE

Documentation:
NONE

/assign @kron4eg

/cherrypick release/v1.7


Improve Visual C++ 14.X support

Summary of changes

Improve VC++14 support for VS 2017 and 2019.
Separate VC from VS version (Miss match starting VS15).
Improve docstrings args and returns information + fixe typos.
Fix coding style and minor coding issues.
Remove Microsoft "Windows SDK 7.0" dead link.

Tested on Windows 10 with Python 3.7.4 and "Visual Studio Build Tools 2019" with following setup cases:

VC++14.2 (VS 2019)
VC++14.1 (VS 2017)
VC++14.0 (VS 2015)

This setuptools file cover a wide variety of VS configurations that I cannot test easily. So any code review and other tests are really welcome.
There is no automated tests for this. This setuptools part did not really had tests before this PR, and it may be very hard to do real relevant automated tests for it.
Pull Request Checklist

[ ] Changes have tests
[x] News fragment added in changelog.d. See documentation for details

Concerning the evolution of this file (msvc.py):
The majority of the code was written to support some  VC9 & VC10 old compilers that does not really had a  vcvarsall.bat or had a messed up one. It was also done to add support for some early VC14 standalone compilers:

Since Python 3.4 is deprecated, the VC10 part is deprecated.
Once Python 2.7 is deprecated in setuptools, the VC9 part can also be deprecated.
Recent versions on Python does not need the VC14 fix. Only Python 3.5 will require help to detect VC 2017 or 2019 vcvarsall.bat.

So, in the end of this year, this file can be easily simplified to remove almost all its content and only keep a Python 3.5/VC compat part that will be kept until Python 3.5 deprecation.

Thanks for putting this together.

Hi! There is a change in this PR that breaks Python 2: https://github.com/pypa/setuptools/pull/1811/files#diff-ebddaa1b649ef567c2534a012ba25913R627
with open(state_path, 'rt', encoding='utf-8') as state_file:

That encoding argument is only available for py3
Is it intentional?
Thanks


Titan Server gremlin.sh graph initialisation

I have configured my Titan db to run with Berkeley Lucene. When I run the server, be it with gremlin-server.sh or titan.sh -v start, I get all the proper messages
1230 [main] INFO  org.apache.tinkerpop.gremlin.server.GremlinServer  - Graph [graph] was successfully configured via [conf/titan-berkeleyje-lucene.properties].
2601 [main] INFO  org.apache.tinkerpop.gremlin.groovy.engine.GremlinExecutor  - Initialized gremlin-groovy ScriptEngine with scripts/empty-sample.groovy
2609 [main] INFO  org.apache.tinkerpop.gremlin.server.util.ServerGremlinExecutor  - A GraphTraversalSource is now bound to [g] with graphtraversalsource[standardtitangraph[berkeleyje:../db/berkeley], standard]
When I connect to the server instance with
gremlin> :remote connect tinkerpop.server ../conf/remote.yaml
I get
==>Connected - localhost/<IP_ADDRESS>:8182
gremlin> g.V()
No such property: g for class: groovysh_evaluate

You are evaluating g.V() locally not remotely and therefore "g" is not available. Issue your command with the :> to submit the traversal remotely:
gremlin> :> g.V()

In the future please use the mailing list for usage questions and not the issue tracker: https://groups.google.com/forum/#!forum/aureliusgraphs


[Bug]: Calendar popup broken with Experimental Live Preview

Describe the bug
I'm not sure if it's even possible to show the calendar popup with new live preview editor but I noticed that the calendar popup doesn't trigger when live preview is enabled. It does work as expected after disabling live preview.
Expected Behavior
The calendar popup should display
Steps to reproduce
Enable live preview from the Editor options (catalyst required)

Type the calendar popup trigger, ex: (@
Operating system
macOS

I saw the excalidraw plugin has at least a partial patch for fixing it in the live preview mode<EMAIL_ADDRESS>I'm not sure if this is helpful at all, I haven't looked at either codebase or what the live preview editor are doing to understand why it would be broken.

I'm facing the same problem with the calendar pop-up. Now, instead of a calendar, there is just a small window with three options: "today", "yesterday" and "tomorrow"... and in my case the plugin stop working after 0.13 release - at a specific time the reminder windows is not trigged

I've observed same behavior with Obsidian v0.13.14.
I will start to fix it soon.

there is just a small window with three options: "today", "yesterday" and "tomorrow"...

Do you happen to have the Natural Language Dates plugin installed? I've been using it as a workaround, and that's the same popup that it uses. I made a template that's just "⏰ @" and trigger it with a hotkey.

Workaround for this issue has been implemented.
https://github.com/uphy/obsidian-reminder/releases/tag/1.1.4
Now calendar popup is available not as inline popup but as a modal.

The new version of the plugin still didn't seem to be working for me but I just updated from v0.13.18 (insider) to v.0.13.19 and it's working now! Thanks @uphy for the fix


React UI: More conversions to Function Components

Signed-off-by: Julius Volz<EMAIL_ADDRESS>No tests needed changing, which I see as a success :)

@boyskila

Got :+1: via chat


[eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.[BUG]

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

DeepFlow Component
Agent
What you expected to happen
2023-06-25 11:10:42 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
thread_num: 1,
perf_pages_count: 128,
ring_size: 65536,
max_socket_entries: 524288,
max_trace_entries: 524288,
socket_map_max_reclaim: 520000,
go_tracing_timeout: 0,
io_event_collect_mode: 1,
io_event_minimal_duration: 1ms,
},
} to EbpfConfig {
collector_enabled: true,
l7_metrics_enabled: true,
vtap_id: 3,
epc_id: 1,
l7_log_packet_size: 1024,
l7_log_session_timeout: 120s,
l7_protocol_inference_max_fail_count: 50,
l7_protocol_inference_ttl: 60,
l7_log_tap_types: [
(
0,
true,
),
],
ctrl_mac: 00:00:00:00:00:00,
l7_protocol_enabled_bitmap: [
Http1,
Http2,
DNS,
SofaRPC,
MySQL,
Kafka,
Redis,
PostgreSQL,
Dubbo,
MQTT,
],
l7_protocol_ports: {
"DNS": "53",
},
ebpf: EbpfYamlConfig {
disabled: false,
log_file: "",
kprobe_whitelist: EbpfKprobeWhitelist {
port_list: "",
},
uprobe_proc_regexp: UprobeProcRegExp {
golang_symbol: "",
golang: ".",
openssl: ".",
},
thread_num: 1,
perf_pages_count: 128,
ring_size: 65536,
max_socket_entries: 524288,
max_trace_entries: 524288,
socket_map_max_reclaim: 520000,
go_tracing_timeout: 0,
io_event_collect_mode: 1,
io_event_minimal_duration: 1ms,
},
}
[2023-06-25 11:10:42.151625 +08:00] INFO [src/collector/quadruple_generator.rs:659] quadruple generator update collector_enabled to true
[2023-06-25 11:10:42.151811 +08:00] INFO [src/collector/quadruple_generator.rs:659] quadruple generator update collector_enabled to true
[2023-06-25 11:10:42.290964 +08:00] INFO [src/sender/uniform_sender.rs:335] 1-telegraf-to-sender sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:10:42.291193 +08:00] INFO [src/sender/uniform_sender.rs:346] 1-telegraf-to-sender sender update dst port from 30033 to 20033
[2023-06-25 11:10:42.315300 +08:00] INFO [src/sender/uniform_sender.rs:335] 1-compressed-otel-to-sender sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:10:42.315554 +08:00] INFO [src/sender/uniform_sender.rs:346] 1-compressed-otel-to-sender sender update dst port from 30033 to 20033
[2023-06-25 11:10:42.325733 +08:00] INFO [src/sender/uniform_sender.rs:335] 1-profile-to-sender sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:10:42.326122 +08:00] INFO [src/sender/uniform_sender.rs:335] 1-otel-to-sender sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:10:42.326282 +08:00] INFO [src/sender/uniform_sender.rs:346] 1-profile-to-sender sender update dst port from 30033 to 20033
[2023-06-25 11:10:42.326349 +08:00] INFO [src/sender/uniform_sender.rs:346] 1-otel-to-sender sender update dst port from 30033 to 20033
[2023-06-25 11:10:42.349862 +08:00] INFO [src/sender/uniform_sender.rs:335] 1-proc-event-to-sender sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:10:42.350383 +08:00] INFO [src/sender/uniform_sender.rs:346] 1-proc-event-to-sender sender update dst port from 30033 to 20033
[2023-06-25 11:10:42.362520 +08:00] INFO [src/sender/uniform_sender.rs:335] 1-prometheus-to-sender sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:10:42.362905 +08:00] INFO [src/sender/uniform_sender.rs:346] 1-prometheus-to-sender sender update dst port from 30033 to 20033
2023-06-25 11:10:44 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
[2023-06-25 11:10:44.321140 +08:00] INFO [src/sender/uniform_sender.rs:335] 2-packet-sequence-block-to-sender sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:10:44.321694 +08:00] INFO [src/sender/uniform_sender.rs:346] 2-packet-sequence-block-to-sender sender update dst port from 30033 to 20033
2023-06-25 11:10:46 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:10:48 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:10:50 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:10:52 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:10:54 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:10:56 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:10:58 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:00 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:02 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:04 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:06 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:08 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:10 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:12 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
[2023-06-25 11:11:14.139469 +08:00] ERROR [src/sender/uniform_sender.rs:391] 3-flowlog-to-collector-sender sender tcp connection to <IP_ADDRESS>:30033 failed
[2023-06-25 11:11:14.140164 +08:00] INFO [src/sender/uniform_sender.rs:335] 3-flowlog-to-collector-sender sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:11:14.140720 +08:00] INFO [src/sender/uniform_sender.rs:346] 3-flowlog-to-collector-sender sender update dst port from 30033 to 20033
2023-06-25 11:11:14 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:16 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:18 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
[2023-06-25 11:11:19.168826 +08:00] WARN [src/rpc/synchronizer.rs:950] ntp response empty
2023-06-25 11:11:20 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
[2023-06-25 11:11:21.642985 +08:00] INFO [src/rpc/synchronizer.rs:1298] ProxyController update to Some("<IP_ADDRESS>"):20035
2023-06-25 11:11:22 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:24 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:26 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:28 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:30 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:32 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:34 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:36 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:38 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:40 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
[2023-06-25 11:11:41.518922 +08:00] INFO [src/rpc/session.rs:501] rpc Proxy changed to proxy <IP_ADDRESS> 20035 from proxy <IP_ADDRESS> 30035
[2023-06-25 11:11:41.522222 +08:00] INFO [src/platform/platform_synchronizer/linux.rs:785] local version<PHONE_NUMBER>, remote version 0
2023-06-25 11:11:42 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
[2023-06-25 11:11:42.811405 +08:00] ERROR [src/sender/uniform_sender.rs:391] 3-doc-to-collector-sender sender tcp connection to <IP_ADDRESS>:30033 failed
[2023-06-25 11:11:42.811470 +08:00] ERROR [src/sender/uniform_sender.rs:391] stats sender tcp connection to <IP_ADDRESS>:30033 failed
[2023-06-25 11:11:42.811405 +08:00] ERROR [src/sender/uniform_sender.rs:391] 2-protolog-to-collector-sender sender tcp connection to <IP_ADDRESS>:30033 failed
[2023-06-25 11:11:42.811928 +08:00] INFO [src/sender/uniform_sender.rs:335] 2-protolog-to-collector-sender sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:11:42.811965 +08:00] INFO [src/sender/uniform_sender.rs:335] 3-doc-to-collector-sender sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:11:42.812132 +08:00] INFO [src/sender/uniform_sender.rs:346] 2-protolog-to-collector-sender sender update dst port from 30033 to 20033
[2023-06-25 11:11:42.812099 +08:00] INFO [src/sender/uniform_sender.rs:346] 3-doc-to-collector-sender sender update dst port from 30033 to 20033
[2023-06-25 11:11:42.812174 +08:00] INFO [src/sender/uniform_sender.rs:335] stats sender update dst ip from <IP_ADDRESS> to <IP_ADDRESS>
[2023-06-25 11:11:42.812332 +08:00] INFO [src/sender/uniform_sender.rs:346] stats sender update dst port from 30033 to 20033
2023-06-25 11:11:44 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:46 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:48 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:50 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:52 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:54 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:56 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:11:58 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:00 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:02 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:04 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:06 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:08 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:10 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:12 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:14 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:16 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:18 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:20 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
[2023-06-25 11:12:20.181156 +08:00] WARN [src/rpc/synchronizer.rs:950] ntp response empty
[2023-06-25 11:12:22.168072 +08:00] ERROR [src/ebpf_dispatcher/ebpf_dispatcher.rs:467] The tracer_start() error. Kernel offset adapt failed. Provide the operating system name and the 'kernel-devel' package for developers to adapt.
[2023-06-25 11:12:22.168559 +08:00] INFO [src/ebpf_dispatcher/ebpf_dispatcher.rs:579] ebpf collector started
2023-06-25 11:12:22 [eBPF] WARNING: func socket_tracer_start() [user/socket.c:1704] Adapting the linux kernel(4.18.0-3<IP_ADDRESS>.po1.x86_64) is in progress, please try the start operation again later.
2023-06-25 11:12:22 [eBPF] INFO Received limit_size (1024), the final value is set to '1024'
[2023-06-25 11:12:22.180429 +08:00] INFO [src/dispatcher/local_mode_dispatcher.rs:270] Stopped dispatcher (0)
[2023-06-25 11:12:22.182870 +08:00] INFO [src/dispatcher/base_dispatcher.rs:655] Decap tunnel type change to VXLAN IPIP
[2023-06-25 11:12:22.182977 +08:00] INFO [src/dispatcher/local_mode_dispatcher.rs:63] Start dispatcher (0)
[2023-06-25 11:12:22.186456 +08:00] INFO [src/dispatcher/base_dispatcher.rs:788] Dispatcher(0) Adding VMs: [00:00:00:00:00:00, fa:16:3e:d4:d3:38, f6:8f:f9:23:66:3d, 26:15:07:cf:59:38, 96:5c:5d:be:d3:2e, fa:1e:ec:d9:88:9b, 56:7b:6d:1d:0f:8e, f2:6b:c7:58:e1:13, d6:bd:1f:cc:09:67, 2a:36:b7:e9:38:fc, 7e:68:b5:9b:7b:28, 82:b4:61:2c:50:bd, be:e6:f4:77:fe:51, aa:46:75:6c:a7:24, 7a:03:ec:53:45:c8, 3a:c5:e5:df:5c:5b, 42:be:c2:19:c5:e7]
[2023-06-25 11:13:21.193344 +08:00] WARN [src/rpc/synchronizer.rs:950] ntp response empty
[2023-06-25 11:14:22.221218 +08:00] WARN [src/rpc/synchronizer.rs:950] ntp response empty
How to reproduce
[root@localhost show-kernel-struct-offset-master]# make
make -C /lib/modules/4.18.0-3<IP_ADDRESS>.po1.x86_64/build M=/root/show-kernel-struct-offset-master modules
make[1]: 进入目录“/usr/src/kernels/4.18.0-3<IP_ADDRESS>.po1.x86_64”
CC [M]  /root/show-kernel-struct-offset-master/skso.o
Building modules, stage 2.

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The new image of agent run eBPF successfully. If have any other issue, we will feedback.


tor instaling

how to install tor

sudo apt-get install tor

it says tor has no installation candidate
$sudo apt-get install tor
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package tor is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'tor' has no installation candidate
???

echo "deb http://http.kali.org/kali kali-rolling main contrib non-free" > /etc/apt/sources.list && apt-get update && apt-get install tor -y && apt autoremove -y

It's working. Thanks..

Run: ‘pkill apt-get’ Then try again
…
On Mon, Jan 29, 2018 at 2:10 AM kabbu59 @.> wrote: @.:~# echo "deb http://http.kali.org/kali kali-rolling main contrib non-free" > /etc/apt/sources.list && apt-get update && apt-get install tor -y && apt autoremove -y Reading package lists... Done E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable) E: Unable to lock directory /var/lib/apt/lists/ please help it's very urgent .... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/ATFT104_by7Bn-_7hY0G_MAsnDHXFpyFks5tPW75gaJpZM4RLa2V .


Add option for #release-none

When shipping moot changes, such as README changes, the version bump is not necessary and causes clutter in automated patching that requires manual approvals. This commit allows for #release-none, so the version will not bump on those kinds of changes

looking great


Feature: Settings panel should include Add/View/Delete api keys for the service provider

The Edit Account panel allows the user to add api keys for the given account:

The api keys created here are associated with the account (via api_keys.account_sid in the database).
It is also true that api keys can be associated with a service provider, rather than an account.  In that case, the row in the api_keys table has a NULL value for account_sid and has a non-NULL value for service_provider_sid.
However, in the UI there is currently no way to create service provider level api keys.
The Settings panel is where the user is able to view and edit properties that are specific to the currently selected service provider, so it makes sense to add a replica of the add/view/delete api keys control shown above.
Of course, this control will be used to manage service provider level keys.  The APIs to do this already exist, please refer to these test cases to see the example POST/GET/DELETE signatures.
Please implement the form pictured above in the Settings panel, where it should show the api keys for the currently selected service provider, and be able to add new api keys for that service provider.
(Note: for testing make sure to pull the latest jambonz-api-server code)

added in v0.7.5-rc15


Suggestion:  Add an aditional check that an "_event_emitter" returns the expected type

Please fill out the sections below to help us address your issue.
What issue did you see ?
In upgrading botocore, the 'before-send' event hook I had in place broke.
This was because the system expected an AWSResponse, but I was actually providing it an HTTPResponse.
It then failed with an "AttributeError" in botocore.endpoint.convert_to_response_dict.
Steps to reproduce
import boto3
from botocore.client import BaseClient
from urllib3 import HTTPResponse

client: BaseClient = boto3.client(
            's3',
            region_name=AWS_REGION,
            aws_access_key_id=AWS_ACCESS_KEY_ID,
            aws_secret_access_key=AWS_SECRET_ACCESS_KEY
        )
aws_request = None

def request_faker(self, params=None, **kwargs):
    aws_request = kwargs['request']
    response = HTTPResponse()  # Should be AWSResponse(...)
    response.status_code = 200
    return response

event_system = self.client.meta.events
event_system.register('before-send.s3.UploadPart', request_faker)
self.client.upload_part(
            Bucket=AWS_S3_BUCKET_NAME,
            Key=key,
            UploadId=upload_id,
            PartNumber=part_number,
            ContentLength=content_length,
            ContentMD5='',
        )

Suggested Improvement
Adjust either botocore.hooks.first_non_none_response or botocore.endpoint.Endpoint._do_get_response to check the response type.  It currently checks if it is not None, but an additional raise on an unexpected type would save significant headaches in the future.
This would allow quick and easy debugging.  Instead of parsing through logs trying to figure out what went wrong, and then further trying to understand what type the function expected.
An alternative approach would be to type hint functions such as convert_to_response_dict, so at the least we can know what the function expected to see in the first place.

Also, it might be worth it to document AWSRequest a bit better.  Certainly, it's somewhat annoying to stub it since raw is not documented at all, and it took some trial and error to determine that raw.stream() must be implemented.

Also, it might be worth it to document AWSRequest a bit better.  Certainly, it's somewhat annoying to stub it since raw is not documented at all, and it took some trial and error to determine that raw.stream() must be implemented.

@EmperorArthur - Thank you for your post. AWSResponse is a data class representing an HTTP response. I am marking it as feature request for adding an additional condition to check the response type.
This is the documentation about AWSRequest if it helps:
https://botocore.amazonaws.com/v1/documentation/api/latest/reference/awsrequest.html

@EmperorArthur - Thank you for your post. AWSResponse is a data class representing an HTTP response. I am marking it as feature request for adding an additional condition to check the response type.
This is the documentation about AWSRequest if it helps:
https://botocore.amazonaws.com/v1/documentation/api/latest/reference/awsrequest.html