Database to fire events

I've been thinking about how the toolbar collectors work lately, and think it might make more sense to have some of the modified to fire events instead of storing data that is accessed by the Collectors. This is cleaner code, and allows for a lot more flexibility. The database engine is the first one that really makes to me. By having events fired off listeners could be provided that:

collect data to be shown in the Debug Toolbar
analyze queries to automatically detect slow queries and tell the user
analyze queries (in MySQL) using EXPLAIN to detect queries that could benefit from rewriting or missing indexes.
etc.

This would require refactoring the Database class to fire an event, and create a new listener for collecting the query information.
Enhancement Checklist:

[ ] Component(s) modified
[ ] Unit testing updated
[ ] User guide updated
[ ] Securely signed commits
[ ] Conforms to style guide

Makes sense, especially the query analysis with explain ... that has been a can of worms in CI3.

Instead of refactoring most of the Database class,  why not use Traits instead? Laravel seems to have no trouble putting a lot of new features via Traits.

Hope this helps http://symfony.com/doc/current/components/event_dispatcher.html

Hooks in CI have been changed quite a bit since v3 so it's good to go. Though I've been considering modifying to use an extra class as the "package" like Laravel does, but only because the class forms a contract so all listeners know exactly what's there. Haven't decided if that's happening or not, yet.
As for refactoring - it's a tiny refactor that's needed. Instead of saving the query you broadcast and event with the query as the payload. That's all that would have to change there. The Toolbar's Database portion would need to be modified, but that's no biggie. Part of me thinks all toolbar collectors should have event listeners to grab their info from, but I'm undecided on that part, also, if just for the performance hit, but that would likely be offset by memory and storage considerations that wouldn't be necessary in production.
The flexibility of having these converted to events, though, instead of saving the debug info, could be huge. People could create all sorts of things that work with them, form a simple "slow log" collector that is db-agnostic, to simply displaying all queries in STDOUT so you could watch, or any number of other things I haven't really thought of yet. Seems very promising.
As for Taylor's love of traits - I personally think he uses too many and could probably allow a number of them to be composed into the class as class instances instead of traits and be better off. But that wouldn't provide the magical use-case he's so fond of. The way I've been taught and seen for myself a bit, is that an over-reliance of traits is bad, if only in part because of the way inheritance and method overriding works when you start combining traits and inherited classes, etc. Traits have their uses, and I believe we have one or two currently, but I don't personally believe they're the magic bullet that Taylor does.

This is what I said at the start of CI 4 that an event system should be built into it even the ci system could use it., I have to agree with you on over doing traits etc;

I'm not sure if that's all of it, but there are actually a few Traits in laravel https://laravel.com/api/5.3/traits.html. and yes, i do love events too!


Add "Features" section to README

Add a Features section to the README that details some of the main features of this project.
For example:

ES6/7
Flowtype
Redux
react-router
webpack
Bootstrap
SCSS
foundation for protected pages
++

Other things to add tot he features list:

[ ] react-intl v2 for i18n and location of translations.


feat: add vs-code dev container json file

Description
As a contributor I want to have convenience when setting up the project for development so that I'm more productive and more likely to actually contribute.
https://code.visualstudio.com/docs/remote/containers
https://code.visualstudio.com/docs/remote/devcontainerjson-reference
TLDR on dev containers:
VSCode can build the project inside the dev container so you can spare people the hassle of installing all of the build dependencies of the project on their machine (such as the JDK 8 which many people may run into trouble with especially if they already have a different version installed). With the dev container json file all one would need is VSCode and a functioning docker installation to be able work on Cactus code. @kikoncuo
Acceptance Criteria

.devcontainer.json file added in the project root
The image references by the added .devcontainer.json file in step 1) suports Docker in Docker or at least binding to the host's docker so that integration tests can be executed inside the container which themselves start other containers for ledger simulation.
Documentation added in the README.md that mentions the fact that we have this convenience feature available for those who do not wish to pollute their host machine with NodeJS/JDK installations for example.

cc: @sfuji822 @takeutak @hartm @jonathan-m-hamilton

I am taking this

Additional Acceptance Criteria:

Find out if it is possible to create more than one devcontainer within the project and then discuss what folders a devcontainer may be useful for

@TonyRowntree Random, potentially helpful fact: If you hit issues with docker containers needing to run inside the dev-container I recommend mounting the sock file of the host machine's docker daemon instead of going the full-on docker-in-docker route.
Might not even need this, but in case you do I figured I'd jot it down.


tcmalloc for large object return null always

The server memory size is 256g. My application uses about 2%. There is a lot of remaining memory, but the application often gets null.The memory I applied for is probably between 8m and 80m.
Can someone help me analyze the cause of the problem?

I'm experiencing similar issues. After updating to gperftools-2.8 (w/ libunwind-1.4.0) our applications started crashing with null pointer dereferences and std::bad_alloc exceptions. Rolling back to gperftools-2.7 (w/ libunwind-1.2.1) resolved the issue.
These regressions run on a server farm with ~500GB of memory.

Here's an example backtrace:
 #0  __cxxabiv1::__cxa_throw (obj=0x1fb711f0, tinfo=0x7fffdf137790 <typeinfo for std::bad_alloc>, dest=0x7fffdee56e50 <std::bad_alloc::~bad_alloc()>) at ../../../../gcc-5.2.0/libstdc++-v3/libsupc++/eh_throw.cc:62
 #1  0x00007fffdfad28b3 in (anonymous namespace)::handle_oom (retry_fn=retry_fn@entry=0x7fffdfad3b30 <(anonymous namespace)::retry_malloc(void*)>, retry_arg=retry_arg@entry=0xc0000, from_operator=from_operator@entry=true, nothrow=nothrow@entry=false) at src/tcmalloc.cc:1264
 #2  0x00007fffdfaf0c96 in tcmalloc::cpp_throw_oom (size=size@entry=786432) at src/tcmalloc.cc:1736
 #3  0x00007fffdfaf23aa in tcmalloc::do_allocate_full<tcmalloc::cpp_throw_oom> (size=786432) at src/tcmalloc.cc:1779
 #4  tcmalloc::allocate_full_cpp_throw_oom (size=786432) at src/tcmalloc.cc:1791
 #5  0x000000000055e788 in __gnu_cxx::new_allocator<unsigned long>::allocate (this=0x247d90b8, __n=98304) at /home/utils/gcc-5.2.0/include/c++/5.2.0/ext/new_allocator.h:104
 #6  0x000000000055b27f in std::allocator_traits<std::allocator<unsigned long> >::allocate (__a=..., __n=98304) at /home/utils/gcc-5.2.0/include/c++/5.2.0/bits/alloc_traits.h:360
 #7  0x0000000000559292 in std::_Vector_base<unsigned long, std::allocator<unsigned long> >::_M_allocate (this=0x247d90b8, __n=98304) at /home/utils/gcc-5.2.0/include/c++/5.2.0/bits/stl_vector.h:170
 #8  0x0000000000592bcd in std::_Vector_base<unsigned long, std::allocator<unsigned long> >::_M_create_storage (this=0x247d90b8, __n=98304) at /home/utils/gcc-5.2.0/include/c++/5.2.0/bits/stl_vector.h:185
 #9  0x0000000000591fcd in std::_Vector_base<unsigned long, std::allocator<unsigned long> >::_Vector_base (this=0x247d90b8, __n=98304, __a=...) at /home/utils/gcc-5.2.0/include/c++/5.2.0/bits/stl_vector.h:136
 #10 0x000000000059172b in std::vector<unsigned long, std::allocator<unsigned long> >::vector (this=0x247d90b8, __x=std::vector of length 98304, capacity 98304 = {...}) at /home/utils/gcc-5.2.0/include/c++/5.2.0/bits/stl_vector.h:320
 #11 0x00007fffe211aa07 in sparse::EWAHBoolArray<unsigned long>::EWAHBoolArray (this=0x247d90b8, other=...) at xxx
 ...

I am tracking the same problem, after upgrading from 2.7 to 2.8, we've begun seeing a large scale (not the first or the largest - about 83 MB)  cause an abort, with errno set to 2.
These crashes are intermittent, but consistently occur on the same code.  It occurred directly after upgrade and stops if I revert back to 2.7

In order to alleviate this problem, I made the following changes in src/common.h：
`static const size_t kMaxThreadCacheSize = 4 << 28;
static const size_t kPageSize   = 1 << 14;
static const size_t kMaxSize    = 512 * 1024;
// For all span-lengths <= kMaxPages we keep an exact-size list in PageHeap.
static const size_t kMaxPages = 1 << 14;`
I know this may not be the best way, but it does alleviate the problem.

#1226 might be a duplicate of this issue. We've bisected the issue down to be3da70298bf3d25c7d64655922ab82dd819ec98 there

Same issue here after upgrading from 2.7 to 2.8.

I concur with robryk.
This issue was occurring multiple times daily for our product.
I found it was specific to the 2.8 decision to unlock the pageheap during system memory release.
I added the following patch as a temporary fix.
The system has been running steady, meeting load requirements and passing all tests for the past month since this fix:
| -  Static::pageheap_lock()->Unlock();
  | +  // gperftools version 2.8 intentionally unlocks during a span release, as this
  | +  // can be a slow operation.  However the SBC was showing instability caused
  | +  // by the removal of the page lock, so (for now) we are adding the lock back in.
  | +
  | +  // Static::pageheap_lock()->Unlock();
  | bool rv = TCMalloc_SystemRelease(reinterpret_cast<void*>(span->start << kPageShift),
  | static_cast<size_t>(span->length << kPageShift));
  | -  Static::pageheap_lock()->Lock();
  | +  // Static::pageheap_lock()->Lock();

For now I am reverting problematic commit. There is indeed at least one bug pointed out in issue #1227. And this is only place I can see some races being possible too.
So my question to people on this ticket are you all running with aggressive decommit? Also can someone offer some kind of reproduction of this bug?

Ok, it was not aggressive decommit. It was race in how we're growing heap. I.e. when PageHeap::New finds no suitable free chunk, it calls GrowHeap and than tries to search for free chunk again. Anticipating it will work, since we just grew heap anyways.
But when we added code to drop lock while releasing memory, there is small chance that GrowHeap's call to Delete (to place newly added chunk of memory to page heap) will trigger IncrementalScavenge which decides to release some smaller, unrelated span, and while this happens, lock is released, then other thread is able to "steal" this just added chunk of memory. So then GrowHeap succeeds, but this success is stolen by another thread. And thread that grew heap sees OOM event.
I'll see how to safely re-enable this original feature adding more careful tests. For now I am satisfied with:
a) revert
b) 2 bugs that we found.
Notably, that second bug is also present in "abseil" tcmalloc. It is just that tcmalloc defaults to different page heap implementation. So I'll be fixing it over there too.

https://gist.github.com/alk/e46cce07da5a5182dbc092815e2db546 is the test program that helped find the second bug


[BEAM-1092] Rollback global shading of Guava

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Revert PRs #2096 and #2249
PR #2096  has caused BigtableITs to fail, as of https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/2906/
The BigtableDataClient has methods that return Guava types, e.g. sampleRowKeys returns an ImmutableList, and we rewrite those calls to reference the repackaged type, but we don't repackage the actual client libraries; as a result when the JVM tries to find the sampleRowKeys(SampleRowKeysRequest) -> ImmutableList<SampleRowKeysResponse> it fails.
We can certainly not shade guava in the google-cloud-platform IOs module; I believe it is also possible to repackage the appropriate Bigtable libraries to ensure the return types of those methods are also repackaged. However, BigtableIO uses classes that are defined in the Bigtable libraries, so we would have to force our version on users.
@davorbonaci @aviemzur

Coverage remained the same at 70.193% when pulling 12873b9500c31b78d84ec6d52c0d9cf1a68edc39 on tgroh:no_repackage_gcp_io into 477e789a4f554a23c9a100364c95bee1e01b23f8 on apache:master.

In the original PR we devised a way to opt out modules which need to ignore the default shading configuration.
Please see original PR comment
And accompanying mail in the dev list.


Root admin action to change the status of a tax form

User story
As a platform admin, I want to update the status of users' tax forms myself, so we don't have to ask a dev each time we have to process one manually, and to enable faster unblocking for users held up by a tax form status issue.
Best solution for this problem
Add a 'tax form' section to root admin dashboard, where you can select a user profile and change between statuses (not requested, requested, received - or whatever they are called)
@Betree WDYT?

Looking back at this one I think we should add this feature directly into the interface, on the "Tax form required" message. A simple button like "Mark as received" would open a modal with an input for the document link.

Ideally this would also include a way to upload the form itself (received manually) to the right place in storage with the other tax forms

Looking back at this one I think we should add this feature directly into the interface, on the "Tax form required" message. A simple button like "Mark as received" would open a modal with an input for the document link.

@Betree : Only issue I have here is the placement of the button. Are we good to add it on the tax form warning message itself?

This would only be shown to host admins.
Once clicked we open a modal with field to add the link.

Once clicked we open a modal with field to add the link.

Is it the responsibility of the host admin to find this link and set it? We already have it in the database, why not send it directly?

@SudharakaP Oh my bad, I thought this was the issue about being able to re-send tax forms request emails (https://github.com/opencollective/opencollective/issues/6126). You proposal sounds good then!


Don't include tempest/app sources in projects

Discovery also includes tests command etc.

It's fixed but not fixed 😅

Oh, it was fixed and I was looking at an outdated version

However, the CI actions seem to complain: https://github.com/tempestphp/tempest-framework/actions/runs/8247465436/job/22555654075
Locally they work fine. Need to dig into it some more

Now it works properly :) It had to do with discovery cache not being cleared before running tests


fixed google plus integration

#118 This will fix issues with var next giving an error, especially since this variable is never used to begin with.

Thanks! This makes sense. I think the original plan was to support redirection to the ?next=... url with Google Login, but I don't think I found a way to do it using their API, so I left it half-implemented. Am happy to merge this in!

Perhaps we should implement an option in our config, such as socialProviders.google.nextUri ? This would be similar to how we handle all of our other redirects, and gives us a way to declare a post-google-login redirect (without relying on their API).

This has is specifically meant for people who want to hit a protected page, eg: /secret, then get redirected to login: /login?next=%2Fsecret, then log in with Google and get back to /secret automatically.

Ah, thanks for clarification.


Changing prefix of parameter's unit leads to wrong value displayed in part view

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find a similar issue

Describe the bug*
After creating a new part with a parameter, the value is correctly display in the part parameter view (/part/<n>/, select Parameters) when hovering the mouse of the parameter value.
Here's an example of a 33 pF capacitor created with a parameter "Capacitance" which has a unit of "farad" correctly showing 3.3e-11 F:

If one changes the prefix of the parameter (i.e. the multiple or submultiple of the unit) in Settings -> Part Parameter -> Part Parameter Templates, the value of the part is still calculated based on the previous prefix.
Here's the same 33pF capacitor after changing the unit of the parameter "Capacity" from "F" to "mF":

This should be either 3.3e-8 mF or 3.3e-11 F since the value hasn't changed (i.e. it's still 33 pF).
The issue is not reproducible on https://demo.inventree.org. Here, the value is correctly shown as 3.3e-8 mF.

Steps to Reproduce

Create parameter "Capacitance" with unit "F"
Create new part
Add parameter "Capacitance" with value 33 pF to part
Change unit of Capacitance from "F" to "mF"

Expected behaviour
Either 3.3e-8 mF or 3.3e-11 F .
Deployment Method

[ ] Docker
[X] Bare metal

Version Information
Version Information:
InvenTree-Version: 0.13.0 dev
Django Version: 3.2.19
Commit Hash: 3ea5a36
Commit Date: 2023-07-04
Commit Branch: master
Database: mysql
Debug-Mode: True
Deployed using Docker: False
Platform: Linux-6.3.8-200.fc38.x86_64-x86_64-with-glibc2.37
Installer: GIT
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}]
Please verify if you can reproduce this bug on the demo site.

[ ] I can reproduce this bug on the demo site.

Relevant log output
No response

When you update the "units" of a parameter template, the parameters are scheduled for update (it may take some time to update them all).
Each part parameter keeps two copies of data. The "raw" input (e.g. "33 pF") and the "native" value (e.g. "33e-12"). The "native" values get re-calculated when you update the parameter template, but this does not happen instantaneously. You should find that the values are updated after ~ 30 seconds?

The "native" values get re-calculated when you update the parameter template, but this does not happen instantaneously. You should find that the values are updated after ~ 30 seconds?

Gave it over a minute between changes but unfortunately the value is never updated. I've check part_partparameter.data_numeric in the mysql database and it stays 0.000000000033.

Is the background worker process running?

Check "server status" in the "system information" window

D'OH! Thanks for you help and sorry for wasting your time.


Remove one of the compatibility envs and move docs

Description
Changes proposed in this pull request:

Remove ENABLE_EXTERNAL_NAME_ALIAS from the compatibility mode envs
Move docs

Related issues

/check-required-labels

/check-required-jobs


Incorporate increment operator with compound assignment

#439 added initial suppprt for #412, but there are several shortcomings to the approach.
In the name of expediency, the simpler case of just ++ was implemented, which is functionally exquivalent to +=1.
The behaviour is also that if a pre-increment, and post-increment is not possible under the currrent implementation.
Variables and maps are handled separately, where the codepaths should be shared to reduce obvious duplication. This can be achieved by generically accepting expresssions instead of having a case for both types. This can probably be done by looking up the identifier and handling types separately only where needed.
Additionally, the support for binops  described in will need to be handled, meaning that the argument list will be variations (one or two in most cases)
The current implementation lacks any codegen tests, so these should also be added.
Once these issues are fixed, we should be able to close this issue, as well as #412 and #53.
I’d be happy to contribute these fixes when I have the time to do so.

This was done


Duplicate Emails sent by Sentinl

Sentinl and Kibana version
6.2.2

Issue description

Duplicate Emails sent by Sentinl

Tried changing throttle_period
Recreated reporter & watcher using wizard

Sample data - Raw Anonymized JSON

{
  "actions": {
    "Report": {
      "throttle_period": "0h1m0s",
      "report": {
        "to"<EMAIL_ADDRESS>        "from"<EMAIL_ADDRESS>        "subject": "Report",
        "body": "Report",
        "save": true,
        "snapshot": {
          "res": "1920x1080",
          "url": "Kibana Dashboard URL ---  Every 1 hour"
          "path": "/tmp/",
          "type": "pdf",
          "params": {
            "delay": 30000,
            "username": "_XX_",
            "password": "_XX_"
          },
          "name": "Report"
        }
      }
    }
  },
  "input": {
    "search": {
      "request": {
        "index": [],
        "body": {}
      }
    }
  },
  "condition": {
    "script": {
      "script": "payload.hits.total > 100"
    }
  },
  "transform": {},
  "trigger": {
    "schedule": {
      "later": "every 1 hour"
    }
  },
  "disable": false,
  "report": true,
  "title": "Report"
}

I am not sure what is it that i am missing ?

@smhulkund I'm not sure I understand. The watcher seems to run every hour. How many emails are received, and when?

Apologies for not being clear, when the watcher is triggered every hour it sends out two emails ( attached screen shot )

@smhulkund
Do you have multiple watchers? Disable all of them except the one you test now.
Could you please try master branch and tell me if you still have those duplicates?
Instruction to test the master is below.
Delete Sentinl:
cd kibana
rm -rf kibana/plugins/sentinl
rm -rf kibana/optimize/bundles/*

Install Sentinl from master branch:
git clone https://github.com/sirensolutions/sentinl
cd sentinl
gulp sync --kibanahomepath=/path/to/kibana/

Restart Kibana.

Thank you @sergibondarenko, i wouldn't want to clone on a production system.
Will tar and untar of master branch work ?

You can do
wget --no-check-certificate https://github.com/sirensolutions/sentinl/archive/master.zip
unzip master.zip
cd sentinl-master
gulp sync --kibanahomepath=/path/to/kibana

You need Internet connection and access to npm in order to allow Sentinl install its dependencies.

Or you can build a release from master branch:

Clone Sentinl repo to a test computer and build a release from master:

gulp package --version="sentinl-master-6.2.2" && mv ../target/gulp/sentinl* ~/Downloads

After build is finished the release is available in ~/Downloads/sentinl-master-6.2.2.zip, move the archive to the production server.
Install it:

kibana/bin/kibana-plugin install file:///home/your user name here/Downloads/sentinl-master-6.2.2.zip

Thank you @sergibondarenko, although i followed the procedure, the duplication problem exists.
It turns out we have 2 instance of sentinl running, this was causing the email duplication. Disabling report on one ( i.e kibana2 ) solved the problem.

Well, does sentinl support this kind of setup ?

Hi @smhulkund the clustering feature is currently only available in the Siren stack
The only approach possible is to install SENTINL only on a single node at this time

Thank you @lmangani


Not able to move to desired location on goBack

I am using react-router for my hybrid app. In that, there is a use case where I get callback from web browser.
Here are the points it does -

Clicks on a button, goes to external website and it is opened in chrome or safari, depending on mobile
External website then provides me a callback
This callback is received by the same page.
If I get an error then I have to move automatically (<Redirect />) to error screen.
If I get a success then I have to move automatically (<Redirect />) to success screen.
Now if I go back from success screen, it should go back to home screen, which is happening normally.
If I go back from error then it should go back to the screen where callback was received. This is not working properly. It is going to home not to callback screen.

Callback Screen render part-
render() {
    if (this.state.success) {
      return <Redirect to={ constants.PATH.PAYMENT_COMPLETED } />
    } else if (this.state.error) {
      return <Redirect to={ constants.PATH.PAYMENT_FAILED } />
    } else if (!this.state.isPaymentData) {
      return (

          { this.populateUI() }
          { this.spinner() }

      )
    }

Success screen
render() {
   if (this.state.goHome) {
       return <Redirect to={ constants.PATH.HOME } />
   }
}

Failure screen
constructor(props) {
    super(props)
    this.goBack = this.goBackToCart.bind(this)
  }
getButton() {
    return (

        <Button name={ constants.RETRY_CHECKOUT } callback={ this.goBack } />

    )
  }

  goBackToCart = () => {
    this.props.history.goBack()
  }

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!

Yea it should be on Stack Overflow or similar forums. But is there anything that supports this query? I am new to javascript so I may be writing question in wrong way, but I didn't found anything in document that supports my problem


create POST route to create new user (sign up)

User should also have a password which I forgot to put into schema

Takes username, email, password and creates new user
Saves to DB, saves session with loggedIn and user_id session variables


Support toggling "dev mode" on/off

See #30 for context.
Support toggling "dev mode" in the argo config. In a dev environment, we want to be able to tweak the ogdc-runner Docker image and build/use it locally. In order to do this, argo must be told not to pull the image from a remote source. This is how the code is currently setup, but once we publish our image (#31 ) and want to use the runner in non-dev environments, we'll need to toggle this option off.

Resolved by #35


Unable to query NSDate properties

When trying to query date properties, I get an 'Invalid value' exception: 'object must be of type date'.
@interface MyModel : RLMObject
@property (nonatomic, copy) NSDate *date;
@end

RLMResults *results = [MyModel objectsWhere:@"date <= '%@'", [NSDate date]];

The query string looks like this
date <= '2015-01-01 11:06:51 +0000'

// I'm using  v0.89.1

incorrect query, you are trying to compare date with string from date. change to:
RLMResults *results = [MyModel objectsWhere:@"date <= %@", [NSDate date]];

incorrect query, you are trying to compare date with string from date. change to:
RLMResults *results = [MyModel objectsWhere:@"date <= %@", [NSDate date]];

@Kirow , you're right. Thanks.
But something seems to be wrong with the string to date conversion:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Unable to parse the format string "date <= 2015-01-01 17:41:01 +0000"'

@Kirow , you're right. Thanks.
But something seems to be wrong with the string to date conversion:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Unable to parse the format string "date <= 2015-01-01 17:41:01 +0000"'


Import: manage morph weights at node level

Fixes #312.
Also see #290.
This will use the pynode.weights property to set a mesh's shapekey weights.
It changes the key for the pymesh.blender_name cache to take into account both the skin and the morph weights. To be precise, two instances of the same mesh in glTF will be instances of the same mesh in Blender if

if they are skinned, they have the same pynode.skin
if their mesh has morph targets, they have the same pynode.weights
if their mesh has morph targets, neither one has its morph weights animated

@julienduroure I think this should satisfy what you said here.

Here's an example:

all cubes are instances of the same mesh in glTF
the left-most cube has its pynode.weights animated
the next two cubes both have no pynode.weights property
the last two cubes both have pynode.weights = [0.5, 0.5].

Cubes with the same letter are instances of the same mesh

Thanks @scurest !


Dead position not detected

8/8/2k5/1p2p2p/1P2P2P/8/5K2/8 b - - 0 34
I have reached dead position with Leela off.
The game was not terminated, but it must.

Why should it terminate ? Which rule says so ? I'm not sure what you mean

@Uriopass, neither player can checkmate. FIDE Laws of Chess


no-duplicates breaks some files.

Please refer to this issue: https://github.com/eslint/eslint/issues/13182
Descriptions are there.
declare module '*/office.gql' {
  import { DocumentNode } from 'graphql';
  const defaultDocument: DocumentNode;
  export const AllOffices: DocumentNode;

  export default defaultDocument;
}

declare module '*/p-graphql.gql' {
  import { DocumentNode } from 'graphql';
  const defaultDocument: DocumentNode;
  export const HelloMessage: DocumentNode;
export const HelloValue1: DocumentNode;
export const HelloValue2: DocumentNode;
export const HelloValue3: DocumentNode;
export const Hi: DocumentNode;
export const HelloAndHi: DocumentNode;

  export default defaultDocument;
}

Seems like we need to update the rule to treat each declare module in a d.ts file as a separate context.

This isn't a duplicate; we need to fix the rule to handle declare module.

@ljharb #1479 is about declare module also.
https://github.com/import-js/eslint-plugin-import/issues/1479#issuecomment-782871787


branch-2.0fix check available fail when s3 aws_token is set and reset as, sk faild on be.

Issue Number: close #xxx
ref https://github.com/apache/doris/pull/34057, fix same issue on branch 2.1
fe return 'S3 can't use, return "please check your properties" when AWS_TOKEN is set
When altering the AK/SK resource, S3 client did not reset

run buildall


Board report scrape: Update action definitions

@shrayshray Ported from my mistaken diagnosis in #740
Hi, @shrayshray. Our scrapers have been struggling with new bill types and actions, which has been interfering with full and windowed bill scrapes. We've resolved bill types, but are blocked by one new action: What does "APPROVED UNDER RECONSIDERATION" mean? https://webapi.legistar.com/v1/metro/matters/7717/histories
Please let me know ASAP and I can apply a patch to restore full bill scrapes.
Also, for your reference, these are the actions we currently know how to interpret:

WITHDRAWN
APPROVED
RECOMMENDED FOR APPROVAL
RECEIVED AND FILED
RECOMMENDED FOR APPROVAL AS AMENDED
APPROVED AS AMENDED
APPROVED THE CONSENT CALENDAR
APPROVED ON CONSENT CALENDAR
DISCUSSED
ADOPTED
ADOPTED AS AMENDED
FORWARDED WITHOUT RECOMMENDATION
CARRIED OVER
RECEIVED
REFERRED
FORWARDED DUE TO ABSENCES AND CONFLICTS
NO ACTION TAKEN
FAILED

If we see a new action, the scrape will fail until we define what that action means. Are there any additional actions we should add, in addition to "APPROVED UNDER RECONSIDERATION"?
Thanks a ton.

From the Board Secretary's office: "Approved Under Reconsideration was the action for Item 54 (file ID 2021-0331) because the vote had to be taken again.
There was a public commenter who said he could not make his comment at the beginning of the board meeting (Chair Garcetti took all agenda comments at the beginning) so public comment was re-opened for that speaker toward the end of the meeting. Once the public commenter made his comment, Chair Garcetti reopened the vote for Item 54 and it was voted on again.
As for now, there are no new actions to be added besides Approved Under Reconsideration."

Cool, @shrayshray, is it correct to interpret "Approved Under Reconsideration" as a passage/approval, then?

@hancush yes, correct.

@shrayshray Added the new action and deployed! (You can see the new action in, well, action, here: https://boardagendas.metro.net/board-report/2021-0331/)

@hancush great, thank you!


Historical request timing out

Requesting curl https://theforexapi.com/api/2021-07-01 times out.
I've tried several other dates with the same result. No change was made to the API so I assume there's an issue with the server?
Curling latest returns a response so it appears specific to this endpoint.

I am having the same issue

it is fixed

fixed


face_encodings return empty list

face_recognition version:1.2.2
Python version:2.7.12
Operating System:Ubuntu  16.04.4 LTS

Description
I have an image dataset and half of them couldn't be encoded using face_encodings() function.
This is one of them:

Firstly, I used load_image_file() and I got a numpy array with shape (182,182,3). There was no problem, but when I use the numpy array I've got with face_encodings(), it return [ ].

That means it didn't find any faces in the image to encode. By default, it tries to locate a face in the image before it encodes it. Since your image is already cropped to the face area, you can pass in known_face_locations=[(0, width, height, 0]] to tell it where the face is.

That seems to work, thank you @ageitgey


opacity option broken in IE9 for GridLayer in Leaflet master

The opacity option for L.TileLayer.WMS seems to be broken in IE9 in the current Leaflet master.  I haven't done any digging into the commit history to hunt down the cause yet, but here's a fiddle (and some screenshots) that show the issue.
http://jsfiddle.net/tugpa0L5/1/
IE9

Firefox 42.0 (working correctly)

I did some digging through the source.  It looks like the problem is the check in the _updateOpacity method of L.GridLayer.  See https://github.com/Leaflet/Leaflet/blob/master/src/layer/tile/GridLayer.js#L162-L164
IE9 is failing the check because L.Browser.any3d is false for it, which causes this._map._fadeAnimated to be false.  There's a comment referencing setting opacity on tiles individually, but I wasn't able to find where this was happening elsewhere in the code.
I'm not familiar enough with the codebase, project history, and CSS opacity browser compatibility issues to suggest a fix. Looks like this block was changed to fix another nasty opacity issue (#3652). Any feedback from those more familiar with the issue would be much appreciated.

Somehow I missed #4068 when submitting this.  This is a duplicate of that issue.

@msiadak Thanks for taking the time to investigate the issue and notice it's a duplicate! :-)
Please subscribe to notifications about #4068 - we can always use an extra pair of eyes (and an extra IE9) to test a fix when it becomes available.


⚠ Bofrost.de has degraded performance

In d854c24, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1161 ms

Resolved: Bofrost.de performance has improved in f8d1afa.


Air purifier does not respond - problem with plugin

I have an issue in my log: This plugin slows down Homebridge. I use it in a child bridge mode, but not work... what is the problem?

I'm having the same issues, the device is not responding in Homekit app and in the homebridge status it says: "This plugin slows down Homebridge. The read handler for the characteristic 'Active' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info."

I'm having the same issues, the device is not responding in Homekit app and in the homebridge status it says: "This plugin slows down Homebridge. The read handler for the characteristic 'Active' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info."

Same problem with the plugin

Same issue. My 2S purifier is no longer responding, same issue for maybe a week now, tried updating plugin and homebridge but didn't fix the issue. Following

Same issue
Following

Same issue: [homebridge-xiaomi-mi-air-purifier] This plugin slows down Homebridge. The read handler for the characteristic 'PM2.5 Density' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
Tried to add it as a childbridge but cant add it in homekit.

same problem:
[3/6/2021, 1:35:54 AM] [homebridge-xiaomi-mi-air-purifier] This plugin generated a warning from the characteristic 'Rotation Speed': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
AND
[3/6/2021, 1:33:38 AM] [homebridge-xiaomi-mi-air-purifier] This plugin generated a warning from the characteristic 'Lock Physical Controls': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[3/6/2021, 1:33:40 AM] [homebridge-xiaomi-mi-air-purifier] This plugin generated a warning from the characteristic 'Target Air Purifier State': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.

@Csehla You were the first to report the issue 15 days ago. According to the commit timeline Dependabot bumped homebridge to 1.3.1 16 days ago. I am hoping to pin down the origin of this bug so we can testing for it.

@Csehla You were the first to report the issue 15 days ago. According to the commit timeline Dependabot bumped homebridge to 1.3.1 16 days ago. I am hoping to pin down the origin of this bug so we can start testing for it.

hi @drz01 I experienced this issue on an earlier version of Homebridge (1.1.x), not just the latest release. So it might not strictly be something in 1.3.1.

Homebridge states in https://github.com/homebridge/homebridge/wiki/Characteristic-Warnings :

This plugin slows down Homebridge...
If you see this message in the logs it means the plugin was very slow to respond from a request to get the current status or update the state of an accessory. Plugins that respond slowly can impact the responsiveness of the entire bridge.
👤 If you're an end user, you should report this issue to the plugin developer.
Moving slow plugins to a Child Bridge can prevent it from impacting other plugins.
🧑💻 If you're the plugin developer:
Make sure the callback() is called.
Make sure you are catching any possible exceptions and still calling the callback() even if an error occurred.
If the action does take some time to complete, adjust your plugin code to return the callback() instantly, and call characteristic.updateValue once the action has completed.

I tried moving it to a child bridge but it wont add it to my iOS Homekit.

I got that far as well. This repo may be dormant; I'll look into the issue some more...

This plugin works 20% of the time. I had to use Mi Home app to turn on the Air Purifier.

Can you please try the new version? The old one wasn't working properly with Homebrige 1.3.

I try it. I have a new problem (but the plugin works now): This plugin threw an error from the characteristic 'Filter Life Level': Unhandled error thrown inside read handler for characteristic: Cannot read property 'value' of undefined. See https://git.io/JtMGR for more info.

Hey @Csehla, please create a new issue for the filter level problem please 🙏🏽. Also, it would be nice to mention your device in the issue.


added header toggle

https://github.com/amandasaurus/waterwaymap.org/issues/35

I've made the header default open, so new visitors won't get confused.
You also did some HTML formatting, so I went down a [rabbit @.***/111900691211745163) of trying to Do That Right™
Thanks for your suggestion. Let me know if you have any more. 🙂
On Fr, 09 Feb 2024 11:58 +01:00, Amanda @.***> wrote:

Merged #36 https://github.com/amandasaurus/waterwaymap.org/pull/36 into main.
—
Reply to this email directly, view it on GitHub
https://github.com/amandasaurus/waterwaymap.org/pull/36#event-11756554064,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAMC4WARGNIJ4TFQBEASTYSX6MRAVCNFSM6AAAAABC5W5KUGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRG42TMNJVGQYDMNA.
You are receiving this because you are subscribed to this
thread.Message ID:
@.***>

--
Amanda


io.grpc.StatusRuntimeException: UNAVAILABLE

Hedera SDK is integrated into our app and it's working fine. but there is a problem testing the app in some networks. I guess there is some network ban or cloudfire exception in between.
The actual error happens when I use in the Iran internet network.
I don't know if this error comes from Hedera network or the ISP has done something with gRPC calls.
Can you please give your opinion regarding this issue?
BTW I've put the error I am getting in the following GIST:
https://gist.github.com/amircoder/7393171eeb88c6365582fba8b6279cad

I believe the mainnet nodes have been moved from port 50211 to 50212. This is fixed on the master branch of the SDK, but has not been released yet, but will be released soon.


Upgrade to Java 21 and airbase 153

Description

Upgrade the airbase version to 153
Upgrade JDK to 21
Change the base docker image from Zulu to Temurin.
Although airlift is migrating from TestNG to JUnit, we won't follow suit in this PR. Because JUnit lacks something akin to DataProvider, which is heavily utilized in wren engine testing, it's challenging to migrate to JUnit at this time.

Do we will create an issue to make all tests with JUnit?

Do they have a new code-style schema? I found some import order and import.* is different.

Do we will create an issue to make all tests with JUnit? JUnit5 has @ParameterizedTest that could be helpful.

The style of ParameterizedTest is very different from DataProvider. I'm not sure that it's a good idea to use it.

Do they have a new code-style schema? I found some import order and import.* is different.

I'm not sure but I didn't import any new schema.

The style of ParameterizedTest is very different from DataProvider. I'm not sure that it's a good idea to use it.

If we want to follow the airbase, maybe using the same test framework is a good choice.

The style of ParameterizedTest is very different from DataProvider. I'm not sure that it's a good idea to use it.

If we want to follow the airbase, maybe using the same test framework is a good choice.

Sure, let's create an issue for it.

Related issue: #520


Updated x64-linux

Hi Mr Kingtous
I used this repo to build rust-desk, it was really helpful but when I tried to build on x64-linux it failed. Turned out that libraries were missing in x64-Linux so I installed those libraries and built the project successfully. If you find it suitable, you can merge these updated files, it might be helpful for others.
Also I have updated readme file with few instructions
Thanks
Regards,
Aamir Ali

LGTM, nice thanks!


Fix Black-Scholes model to handle Put Options correctly

This PR addresses issue https://github.com/Waifod/quant_finance_models/issues/58.
Currently the Black-Scholes model is only defined for Call Options.
This change extends the model to also handle Put Options and add safeguards to abort the operation early and emit a warning message if the asset received it not an Option.

Recreating PR to fix formatting error.


Fixing error metrics as discussed in #27

I implemented these changes, plus two minor additions.
First, for keypoints which are supposed to be not-visible, it seemed reasonable to replace their confience score with 1 minus the confidence score, for the purposes of reporting online during training, since the target confidence for these points is 0. Euclidean errors however should be masked out, since they are not defined for non-visible keypoints. These changes only affect values printed to command line during training, but not logged values to disk. This is fine, because the keypoint errors logged to disk includes NaN values for non-visible keypoints
Second, in debugging these changes, I noticed that the logger callback appeared to be broken. Instead of adding a new entry for each epoch, it appears to have a first entry with all zeros, and a second entry with only the most recent values. This looked like a single line got misplaced outside a conditional statement, and I tested that logger works correctly after making this change.

This push is to fix the issues discussed in open issue #27

I'd just get rid of all the code for detecting nans and just use np.nanpercentile and np.nanmean. That would greatly simplify things and give the same result. If you could update to use that then I'll merge.

We do have to detect nans still, at least to do what I've implemented here,
because the confidence values for non-visible target keypoints should be 0.
But I can make the other changes you mention, and sorry about the commented
code...that's deleted in my version of the code I must have pushed the
wrong version.
The code is a bit complicated because I didn't want to remove the option to
do confidence thresholding that you had already built in. If it's ok to get
rid of that, the code is much simpler.
On Sun, Apr 26, 2020 at 4:45 AM Jake Graving<EMAIL_ADDRESS>wrote:

@jgraving commented on this pull request.
In deepposekit/callbacks.py:

   euclidean_perc, confidence_perc = keypoint_percentile

   euclidean_mean, confidence_mean = np.mean([euclidean, confidence], axis=1)

       y_visible = y_visible[mask]

   if ~y_visible.all():

       euclidean = euclidean[y_visible]

       confidence[~y_visible] = 1-confidence[~y_visible]

   euclidean_perc = np.percentile(euclidean, [0, 5, 25, 50, 75, 95, 100])

   euclidean_mean = euclidean.mean()

   confidence_perc = np.percentile(confidence, [0, 5, 25, 50, 75, 95, 100])

   confidence_mean = confidence.mean()

   # keypoint_percentile = np.percentile(

   #     [euclidean, confidence], [0, 5, 25, 50, 75, 95, 100], axis=1

   # ).T

Just delete this commented code. git keeps track of changes. There's no
need to keep old code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jgraving/DeepPoseKit/pull/50#pullrequestreview-400477025,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJNQGS56CNHGNTZGUL747TROPYAVANCNFSM4MLRFRPA
.


get correct field name in struct tag

this fix will correct code of detecting field name in struct tag. JSON tag in struct is usually in this format:
type RequestInput struct {
   Query string `json:"query,omitempty"`
}

we need to get correct json field name query instead of query,omitempty

Awesome! Thanks @htmd !

you are super fast @joeybloggs 👍

I will cut a proper release in a little bit


Fixed integration bugs in viz generator

Fixed integration bugs in visualization file
Testing:
Tests tbd

Thanks for fixing the bugs! Great work @abhinavdv


[Release-1.27] - Fix Error getting the node object error spew on initial startup

Backport fix for Fix Error getting the node object error spew on initial startup

#9574

Validated using release-1.27 branch with commit 1268cf0a
Followed the same steps as mentioned here: https://github.com/k3s-io/k3s/issues/9574#issuecomment-1988693534
Replication
$ k3s -v
k3s version v1.27.11+k3s1 (06d6bc80)
go version go1.21.7

$ sudo journalctl -u k3s | grep 'forbidden:'
Mar 11 15:38:32 server1 k3s[6034]: time="2024-03-11T15:38:32Z" level=error msg="Error getting the node object: nodes \"server1\" is forbidden: User \"system:k3s-controller\" cannot get resource \"nodes\" in API group \"\" at the cluster scope"
Mar 11 15:38:34 server1 k3s[6034]: time="2024-03-11T15:38:34Z" level=error msg="Error getting the node object: nodes \"server1\" is forbidden: User \"system:k3s-controller\" cannot get resource \"nodes\" in API group \"\" at the cluster scope"
Mar 11 15:38:36 server1 k3s[6034]: time="2024-03-11T15:38:36Z" level=error msg="Error getting the node object: nodes \"server1\" is forbidden: User \"system:k3s-controller\" cannot get resource \"nodes\" in API group \"\" at the cluster scope"

Validation
$ k3s -v
k3s version v1.27.11+k3s-1268cf0a (1268cf0a)
go version go1.21.7

$ sudo journalctl -u k3s | grep 'forbidden:'
Mar 11 15:54:11 server1 k3s[7374]: time="2024-03-11T15:54:11Z" level=debug msg="Network policy controller waiting to get Node server1: nodes \"server1\" is forbidden: User \"system:k3s-controller\" cannot get resource \"nodes\" in API group \"\" at the cluster scope"
Mar 11 15:54:13 server1 k3s[7374]: time="2024-03-11T15:54:13Z" level=debug msg="Network policy controller waiting to get Node server1: nodes \"server1\" is forbidden: User \"system:k3s-controller\" cannot get resource \"nodes\" in API group \"\" at the cluster scope"
Mar 11 15:54:15 server1 k3s[7374]: time="2024-03-11T15:54:15Z" level=debug msg="Network policy controller waiting to get Node server1: nodes \"server1\" is forbidden: User \"system:k3s-controller\" cannot get resource \"nodes\" in API group \"\" at the cluster scope"


Re-enable Jekyll external linkchecks

A report of a broken link on the FAQ page led me to realize that the external linkchecking was currently broken (as per the ",/," URL exclusion in build.sh).
This PR updates build.sh to reenable the linkchecking and fixes the few broken links and missing alt attributes, mostly in the curation workflow page.
Only remaining todo is the broken https://www.ebi.ac.uk/bioimage-archive/our-roadmap/ link from the FAQ (which incidentally was the original report). I have opened a ticket with EBI to confirm this page has now disappeared.
Update (2021-04-10): the link has been redirected to the project development page.

Thanks, merging and I'll update the curation workflow accordingly.


Insertion into ServiceRegistry::classServices taking too much time.

Based on the benchmark test results it was found that the vector insertion is causing a significant performance hit. using push_back instead of insertion at the start of the vector will help reduce the runtime for RegisterService API

fixed in PR #364


fix: use envconfig.Models for model path

This removes noop helper function.

@maaslalani got back the error check for empty model dir. Otherwise it would create models in current directory if user home is not found for some reason.

Can we please get this merged in? The ability to set the models dir is very important.

Fwiw, you can already set the OLLAMA_MODELS directory, this is just a refactor to use the established envconfig pattern.

It worked for me after I deleted everything inside the old ollama folder, with the exceptions of the keys (id_ed25519)

This PR solves the id_ed25519 keys location: https://github.com/ollama/ollama/pull/4656

@jmorganca hi Jeffrey. Any chance to get this merged?

Good news - @pdevine made the same changes in - https://github.com/ollama/ollama/pull/5029
@maaslalani our code is probably too bogus to deserve attention. :D
I am going to solve conflict here and see if there is something left.

After #5029 only a minor cleanup left. Rebased.

@abitrolly yeah, the reason why this didn't get moved into envconfig initially was because there were issues w/ the unit tests failing. My last change fixed that as well too. I think we can go ahead and close this PR?

@pdevine there is still one cleanup left here. Take a look at the diff.


denyAccess('update') does not hide the edit button

Bug report
What I did
I called $this->crud->denyAccess('update'); in setup() method.
What I expected to happen
Edit button disappeared.
What happened
Edit button still visible, alhtough i get 403 when click on it.
What I've already tried to fix it
View for the edit button and the UpdateOperation trait seems ok, i don't know what`s wrong. Maybe i just try to disable the button wrong way?
Backpack, Laravel, PHP, DB version
backpack/crud                          4.0.59
backpack/generators                v2.0.7
backpack/permissionmanager 5.0.7
laravel/framework                    v7.5.2
php                                           7.3.9

Indeed, please move your denyAccess() call inside the setupUpdateOperation() method. That will fix it.
The reason this happens is because of the order things are run in:

first setup()
then all operation defaults - ex setupUpdateDefaults()
then all custom operation setup methods - ex setupUpdateOperation()

But the first thing setupUpdateDefaults() does is allowAccess('update'). So your call from setup() gets overwritten. Moving it to the last method that's run will fix this.
Also, it's best practice in Backpack 4.0 to no longer do things inside the setup() method directly - so that logic is separated per operation. You can still do most things inside setup... but... it's just cleaner to separate them.
Hope it helps.
Cheers!

Thanks! Putting denyAccess('update') into setupListOperation() method helped. It has meaning because i check policy for each entity when doing request, but show some buttons or not is a deal of operations access.


Stuck on grey screen due to websocket error 500

code-server version: 1.1156-vsc1.33.1
OS Version: Ubuntu Server 16.04 on private VPS

Description
Installed code-server a couple days ago and finally went around to getting the reverse proxy working so I can use it on a semi-restricted network (network blocks direct IP:port access). Followed the docs for setting one up using Apache, and it somewhat works. The login page shows up and is usable, but once logged in, it sits on a grey screen repeatedly spitting out websocket connection to 'ws://coder.mydomain.com' failed: Error during websocket handshake: Unexpected response code: 500. Direct access over IP:port works, but the Apache reverse proxy only seems to partially work.
This happens in latest version of desktop chrome.
Steps to Reproduce

Download the binary and run it on server with --allow-http
Configure Apache according to docs
Attempt to access via chrome
Enter password and your at a grey screen, constantly getting a websocket 500.

Let me know if more details are needed, such as what my configs are currently set at.

I have the same issue.

Is there any support for alternatives (like long-polling / socket.io) rather than web sockets? Some environments don't support websockets.

Same issue, even whit HTTPS

This is likely caused by a misconfigured reverse proxy. I'm reviewing the reverse proxy documentation and rewriting parts that aren't clear or incorrect with the current version right now.

i was not using a reverse proxy in my case

@Mrgove10 Does anything appear in the code-server log or browser log that could be helpful?

If anyone still experiences this on v2 lemme know.


make setBuildTargets work in more cases

Description of changes
This modifies the setBuildTargets function in haskell.lib to remove profiling and checks. These create extra compiles that differ from the spirit of specifying targets. Removing them also allows projects with tests to build executables without having to manually call dontCheck.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

setBuildTargets should not disable tests; that's why we have differing functions for the purposes.
I agree that setBuildTargets is suboptimal in some respects, but I'd rather address that at the root by improving the builder's knowledge of the targets. Unfortunately, here we are limited by Cabal's bugs/behavior.

@sternenseemann what your are suggesting can't work. Think it through. There is not a time when we can specify a build target and have tests as well.

It feels like @sternenseemann and @Fresheyeball want two different functions:

@sternenseemann wants a function that's only job is to set the Haskell generic builder buildTarget option.  This is how the setBuildTargets function currently works in master.  This also matches how many of the other functions work in pkgs/development/haskell-modules/lib/compose.nix.

@Fresheyeball wants a function that that is able to say, "build only these targets (and absolutely nothing else)".  This is how the setBuildTargets function appears to work in this PR.

I think both of these are valid use-cases.
@sternenseemann How would you feel about adding a new function, similar to what @Fresheyeball is proposing is proposing in this PR (called something like setOnlyBuildTargets)?

it can't work with setBuildTarget, we have no way of knowing what tests are relevant to run, and given the way cabal does this, the build will fail unless all are compiled. There is only one instance where it would make sense to leave checks on with setBuildTargets, and it is when the target list happens to include all test suites.

Could you explain this is more detail?
For instance, here are a couple questions I have around the target disabling feature:

If you have a cabal file with two test components, and you pass one of them to setBuildTarget, then will the build fail?  It sounds like you're suggesting that the build would fail.
Imagine you have a cabal file with one executable, one library component, and the executable depends on the library.  If you only pass the executable to setBuildTarget, will the build fail?  Is Cabal smart enough to know that the library also needs to be built because it is a dependency?
Why do you also throw on justStaticExecutables in this PR?  This doesn't seem to me to be related to selecting targets.

I have a better function. I think this should be two functions now.


resolve TODO in DiamondFallback.sol

it's not clear why TODO is placed there
https://github.com/solidstate-network/solidstate-solidity/blob/master/contracts/proxy/diamond/fallback/DiamondFallback.sol#L10
there is an import of IDiamondFallback, isn't it enough?
maybe just remove the line, it's confusing, it looks like the contract is not coomplete

Fixed in 7be27707a219634aeb07aafeac9f85e301138e53.


Provide more information on Patch

This is a Feature Request
Page
https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/patch/
This page is auto-generated
What would you like to be added
Provide more information on Patch  or can provide a link on the page that can give more information on the Patch

/language en
/kind feature

We can also revise https://github.com/kubernetes-sigs/reference-docs/

/assign

/assign

Hi @0904-mansi, Please see above comments before assigning this issue yourself .

Since it is an auto generated page , it can only be fixed by upstream code at kubernetes repo.

Hey I didn't really got what you are trying to say here, I would really appreciate if you can explain it. I am sorry if this question is really dumb, Am just starting out.

If we improve https://github.com/kubernetes-sigs/reference-docs/ then we can try to change the generation so that https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/patch/ is more helpful to readers.
Assistance is welcome (you'll need to know Golang).

@KhushPatibandha @0904-mansi are you people working on this issue as it has inactive for a long time.

/close


fix(storage): correct directory handling for mobile file uploads

Problem solved
Short description of the bug fixed or feature added
Changes made

[ ] Public API changes: list the public API changes made if any
[ ] Internal API changes: explain the internal logic changes

How to test

[ ] Automated tests: link to unit test file
[ ] Manual tests: step by step instructions on how to test

Contributor NFT
Paste in your wallet address below and we will airdrop you a special NFT when your pull request is merged.
Address:

PR-Codex overview
This PR focuses on fixing file uploading on mobile by adjusting the directory wrapping logic.
Detailed summary

Updated logic for directory wrapping in file uploading on mobile
Removed unnecessary commented out code
Improved clarity and efficiency in mobile.ts file

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#3633  👈
main

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

Join @joaquim-verges and the rest of your teammates on  Graphite


Service Toolkit - Feedback link / form sits outside of layout

The link "is anything wrong with this page" and associated form on /service-toolkit is outside of the main page layout and hard aligned to the left. It should be aligned with the rest of the content.

this is fixed for now but will need to be updated in #518

Closing this as it's not an issue anymore (feel free to reopen if I'm wrong)


Missing description of the "aggregateElementType" attribute in the "onComplete" element of an "aggregate" mediator.

Description:
There is no description for the "aggregateElementType" attribute in the "onComplete" element of an "aggregate" mediator.
Suggested Labels:
bug, micro-integrator
Suggested Assignees:
Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Write a mediation sequence with an "aggregate" mediator. See the properties of that mediator in the graphical editor.
Related Issues:

Will be done by https://github.com/wso2/docs-mi/issues/935

Hi @chanikag #935 has been closed but I still don't see the description of the "aggregateElementType" attribute.
Am I missing something?
Thanks

Yes, we have reopend this.


Parks Local

Current metadata draft for Utah Parks Local. There was very little available information on this dataset, so definitely let me know if there are important details missing. Thank you!

@ZachBeck are you the data creator/maintainer for parks? Implying we don't have external stewards providing updates?

I consider myself neither of those but I've added a couple parks here and there over the years. The bulk of the work was done by Gordon and Cindy, there might have been a few counties that sent shapefiles of their parks to get them started. Unfortunately there are no external stewards that I'm aware of.

This could be another OSM derived dataset

This could be another OSM derived dataset

Yeah something should happen for a dataset without stewards. Is there a running list for OSM candidates?

@gregbunce @steveoh @ZachBeck I'm looking to merge this layer but didn't want to close the pull request if the discussion about OSM candidates still needs to be had. Is this something we need to figure out before checking this layer off, or can I go ahead and merge it? Perhaps we should have a broader conversation about stewardless layers? I have a few more coming up that don't seem to have assigned stewards

i would say go ahead and move forward with this PR (merge it,).
I will create and share a list of layers that are good candidates for OSM and my suggestions for what that might look like, but we don't need to have that conversation here.
carry on! thanks Miriam!


--sku-name is incorrect

I get an error:
Gen4 hardware is not supported for this region. when I try to run the az postgres create command. When I use --sku-name GP_Gen5_2 it works.

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

ID: 7bb30245-963c-d1ec-76a9-66119c79fb1e
Version Independent ID: d3ee025c-ad6d-d8bd-84a2-9409f1a682f7
Content: Tutorial: Linux Ruby app with Postgres - Azure App Service
Content Source: articles/app-service/containers/tutorial-ruby-postgres-app.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@mgreg90 Thanks for the feedback! We are currently investigating and will update you shortly.

@mgreg90, Kindly checkout this doc for a list of regions by hardware generation. The possible reason for the error, Gen4 is not supported in the region you had provisioned.   As you have already done, you could consider moving (retaining) your databases to Gen 5 hardware. Please refer this doc for more details -

@mgreg90, We will close this out, but if you feel you need more information please just let us know.


[FR]: Optimize UI for modifying command alias

Is your feature request related to a problem? Please describe.
It's not convenient for users to modify command alias. For example I haven't found the method to rename alias without adding the same command.
Also selecting existed commands is not convenient as users can't input and filter.
Describe the solution you'd like
Maybe you can imitate the way what chorded hotkeys plugin does. It is easy to select commands, modify, rename alias, sort and so on.

I hope this will make command alias better.

me too


Comment in src/CodeExplorerBundle/Resources/views/source_code.html.twig contradicts file name

The comment states that fragments should be prefixed with an underscore. Is this just a typo in the file name?

@frankadrian, this file was moved from the AppBundle. I think we should remove that comment.

Yes. The comment should be removed. Thanks.


设备无法联网（外网），测试的时候内网能的地址都能ping通，但是ping外网就不行了

Core
2023.12.1
Supervisor
2023.11.6
Operating System
11.1.rc2
Frontend
20231208.2
我的系统是用SD装的，Maskrom已经短接。
你好我的问题不知道是什么原因导致的haos连接丢失，所有外网无法连接，我用ssh输入 ha network info
显示的是
docker:
address: <IP_ADDRESS>/23
dns: <IP_ADDRESS>
gateway: <IP_ADDRESS>
interface: hassio
host_internet: false
interfaces:

connected: true
enabled: true
interface: eth0
ipv4:
address:

<IP_ADDRESS>/24
gateway: <IP_ADDRESS>
method: auto
nameservers:
<IP_ADDRESS>
<IP_ADDRESS>
ready: true
ipv6:
address:
XXXX:XX:XX:XX::XXX/128
XXX:XX:XX:XXXX:XXXX:XXXX:XXXX:XXXX/64
fe80::XXXX:XXXX:XXXX:XXXX/64
gateway: fe80::XXXX:XXXX:XXXX:XXXX
method: auto
nameservers: []
ready: true
mac: XX:XX:XX:XX:XXXX
primary: true
type: ethernet
vlan: null
wifi: null

connected: false
enabled: false
interface: wlan0
ipv4:
address: []
gateway: null
method: disabled
nameservers: []
ready: false
ipv6:
address: []
gateway: null
method: disabled
nameservers: []
ready: false
mac: XX:XX:XX:XX:XX:XX
primary: false
type: wireless
vlan: null
wifi: null
supervisor_internet: false
前两天还好好着了

<IP_ADDRESS>/24
gateway: <IP_ADDRESS>
method: auto
nameservers:
<IP_ADDRESS>
<IP_ADDRESS>

Is the gateway address valid? ie is your router on <IP_ADDRESS>?
You are using external nameservers, make sure you can connect to these as well.
nslookup <domain.com>
ping <dns_ip>

of course, the gateway address and dns address are valid，I have another haos work ingon PVE with the same address，and it's network is fine. when nslookup www.baidu.com,it returns "server can't find www.baidu.com: servvfall"发自我的荣耀手机-------- 原始邮件 --------发件人： Tim L @.>日期： 2023年12月15日周五 08:04收件人： darkxst/ha-operating-system @.>抄送： astangcong @.>, Author @.>主    题： Re: [darkxst/ha-operating-system] 设备无法联网（外网），测试的时候内网能的地址都能ping通，但是ping外网就不行了 (Issue #17)
<IP_ADDRESS>/24
gateway: <IP_ADDRESS>
method: auto
nameservers:<IP_ADDRESS><IP_ADDRESS>
Is the gateway address valid? ie is your router on <IP_ADDRESS>?
You are using external nameservers, make sure you can connect to these as well.
nslookup <domain.com>
ping <dns_ip>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I dont change anything network related compared to other HAOS. So it should work the same as your other device.

所以我也不知道是什么原因，我也没改动别的地方，前几天还好好地，莫名其妙的就发现需要联网的集成都报错，后来试了试发现是设备根本连不到外网。下次系统更新是什么时候，已经不想重刷系统了

can you ping the dns ip addresses? given that local network is working, perhaps its something with your router?
There will be an update in the next week, but it doesnt change anything releated to ethernet.

can you ping the dns ip addresses? given that local network is working, perhaps its something with your router? There will be an update in the next week, but it doesnt change anything related to ethernet.

dns IPaddress  ‘<IP_ADDRESS>’没有办法ping通（没有返回任何信息），另一个装在pve里的ha就可以ping通。更新的话我看看会不会恢复，不知道是不是下载某些集成或者ADDONS的时候导致的问题，如果更新后还不行那就再重装系统试试

没找到原因，重新刷了系统就没有这个问题了


issue during setup after authentication

after setting up the azure app with the correct permissions, after the first run of oauth2ms I log in and grant permissions in the browser, then I get the following error after I see a blank page with "Authorization complete.".
Traceback (most recent call last):
  File "/home/japhir/bin/oauth2ms", line 226, in <module>
    app_state, token = build_new_app_state(crypt)
  File "/home/japhir/bin/oauth2ms", line 143, in build_new_app_state
    token = result["access_token"]
KeyError: 'access_token'

here's an overview of my permissions config:

what am I doing wrong?

Will need some more information to debug this issue.
Could you please try out this branch: https://github.com/harishkrupo/oauth2ms/tree/debug?
This prints out the returned result incase of authorization failures. This should help debug the issue.

this is the output of that now:
> oauth2ms
Something went wrong during authorization
Server returned: {'error': 'invalid_client', 'error_description': 'AADSTS7000215: Invalid client secret is provided.\r\nTrace ID: 2ef9d4dc-c7ae-4c08-a5c7-11b47b776100\r\nCorrelation ID: 94479270-6c9b-4e73-ab1b-f37405267ab4\r\nTimestamp: 2020-12-07 18:43:49Z', 'error_codes': [7000215], 'timestamp': '2020-12-07 18:43:49Z', 'trace_id': '2ef9d4dc-c7ae-4c08-a5c7-11b47b776100', 'correlation_id': '94479270-6c9b-4e73-ab1b-f37405267ab4', 'error_uri': 'https://login.microsoftonline.com/error?code=7000215'}
Traceback (most recent call last):
  File "/home/japhir/bin/oauth2ms", line 232, in <module>
    app_state, token = build_new_app_state(crypt)
TypeError: cannot unpack non-iterable NoneType object

I'm sharing it as-is, I hope that's not a security issue. I've deleted this app and created a new app with the same settings.

From the log, looks like the client secret is not valid:  Invalid client secret is provided.
Could you try regenerating once again?

I tried again yesterday already :(.
I did just receive a notification: "You do not have any Azure subscriptions in the Universiteit Utrecht directory. Click here to switch to another directory." but I'm not sure what that means... Especially because when I look at my tenant overview, it says: "Azure AD Premium P1"
Anyway, I tried again, also messing around with changing localhost with https://<IP_ADDRESS> in the Azure portal and as redirect_host because that's recommended in the quickstart guide, but it doesn't work:
oauth2ms
Something went wrong during authorization
Server returned: {'error': 'invalid_client', 'error_description': 'AADSTS7000215: Invalid client secret is provided.\r\nTrace ID: 72de6745-07e9-4bc7-a301-3c100dc71500\r\nCorrelation ID: 3ee98029-0331-4b0e-9efe-30d47127f191\r\nTimestamp: 2020-12-08 09:12:32Z', 'error_codes': [7000215], 'timestamp': '2020-12-08 09:12:32Z', 'trace_id': '72de6745-07e9-4bc7-a301-3c100dc71500', 'correlation_id': '3ee98029-0331-4b0e-9efe-30d47127f191', 'error_uri': 'https://login.microsoftonline.com/error?code=7000215'}
Traceback (most recent call last):
  File "/home/japhir/bin/oauth2ms", line 232, in <module>
    app_state, token = build_new_app_state(crypt)
TypeError: cannot unpack non-iterable NoneType object

I don't think the subscriptions should be an issue. If you can use the outlook web login, this should work too. That said, I would suggest re-checking your config file. The error says that the client secret is invalid. Either it is an old secret or you have multiple tenants and some other configuration parameter is wrong.
Another option is to try this app: https://github.com/Azure-Samples/ms-identity-python-webapp. It is a simple webapp that lets you log in and fetch basic info about yourself. If this app also doesn't work, then there is something wrong with the setup. The apps readme contains more information on how to setup.

I just tried it again, now 100% sure I copied everything as in example. This is so frustrating because I spent so much time already :P. I'll have a look at the other app later.
> oauth2ms
Something went wrong during authorization
Server returned: {'error': 'invalid_client', 'error_description': 'AADSTS7000215: Invalid client secret is provided.\r\nTrace ID: ad29675c-70ec-4d71-a5d9-f32a8b85f000\r\nCorrelation ID: 07f72c3b-1b15-4f0f-b962-32d3ae93d8c3\r\nTimestamp: 2021-01-05 08:50:26Z', 'error_codes': [7000215], 'timestamp': '2021-01-05 08:50:26Z', 'trace_id': 'ad29675c-70ec-4d71-a5d9-f32a8b85f000', 'correlation_id': '07f72c3b-1b15-4f0f-b962-32d3ae93d8c3', 'error_uri': 'https://login.microsoftonline.com/error?code=7000215'}
Traceback (most recent call last):
  File "/home/japhir/bin/oauth2ms", line 232, in <module>
    app_state, token = build_new_app_state(crypt)
TypeError: cannot unpack non-iterable NoneType object

I just tried it again, now 100% sure I copied everything as in example. This is so frustrating because I spent so much time already :P. I'll have a look at the other app later.
> oauth2ms
Something went wrong during authorization
Server returned: {'error': 'invalid_client', 'error_description': 'AADSTS7000215: Invalid client secret is provided.\r\nTrace ID: ad29675c-70ec-4d71-a5d9-f32a8b85f000\r\nCorrelation ID: 07f72c3b-1b15-4f0f-b962-32d3ae93d8c3\r\nTimestamp: 2021-01-05 08:50:26Z', 'error_codes': [7000215], 'timestamp': '2021-01-05 08:50:26Z', 'trace_id': 'ad29675c-70ec-4d71-a5d9-f32a8b85f000', 'correlation_id': '07f72c3b-1b15-4f0f-b962-32d3ae93d8c3', 'error_uri': 'https://login.microsoftonline.com/error?code=7000215'}
Traceback (most recent call last):
  File "/home/japhir/bin/oauth2ms", line 232, in <module>
    app_state, token = build_new_app_state(crypt)
TypeError: cannot unpack non-iterable NoneType object

Perhaps it cannot find the config file? I placed it in ~/.config/oauth2ms/config.json but when I echo "$XDG_CONFIG_HOME" it does not return /home/user/japhir/.config`.

Perhaps it cannot find the config file? I placed it in ~/.config/oauth2ms/config.json but when I echo "$XDG_CONFIG_HOME" it does not return /home/user/japhir/.config`.

Waaah I just copied the wrong client secret. I copied the "ID" field from there, not the "value" field. Cheers for helping out!

Waaah I just copied the wrong client secret. I copied the "ID" field from there, not the "value" field. Cheers for helping out!

Ah, yes the XDG_CONFIG_HOME is not set by default. Thanks for letting me know, I will update the documentation to reflect that.

Ah, yes the XDG_CONFIG_HOME is not set by default. Thanks for letting me know, I will update the documentation to reflect that.

Perhaps the sentence in steps.org that says to copy the client secret could include something like "from the value field"?

Perhaps the sentence in steps.org that says to copy the client secret could include something like "from the value field"?

Thanks for the suggestion. Will add it there.

Thanks for the suggestion. Will add it there.

Hi, I'm having trouble configuring an Office365 account. Since it seems that @japhir has the same kind of (wicked) server, could you please share what values did you use for redirect_host, redirect_port, redirect_path?

I think I left them as they were, but in my config file they're currently at:
    "redirect_host": "localhost",
    "redirect_port": "5000",
    "redirect_path": "/getToken/",

Yeah, thanks, @japhir, that's the default...
I'm confused since with the alternative script mutt_oauth2, there's a field redirect_uri which has the default value https://login.microsoftonline.com/common/oauth2/nativeclient. Authentification works more or less fine with that script, and the error I'm getting with oautn2ms seems to point to that uri... Weird. Maybe @harishkrupo knows better...


Add to Bower

Would you consider making this available via Bower? I have prepared the required bower.json and cleaned up the docs a bit. After that all you have to do is accept the PR and register the package with Bower like so:
http://bower.io/docs/creating-packages/#register
At that point all you'd have to do is bump the version and make a release. (Bower relies on git tags to know what to retrieve.)

Thanks a lot! Just one question, what would be the use case? I am not a big user of bower but as I understand it's only for client-side assets, so does it mean that bower would only have pre-generated svgs and the actual generation code?

+1

Thanks! Yes, you're right that Bower would only pull the source files as well as the generation code... but those source files can be integrated into an asset pipeline and used to generate SVG icon sprite sheets, among other things. The same could be accomplished with npm but it's nice to have options :+1:

BTW, one catch with Bower is that it'll retrieve the latest release... which won't have bower.json as of yet so an error will be thrown. You'll have to bump the release to complete this PR :)
In the meantime, for anyone interested in playing around, this will also work: bower install https://github.com/encharm/Font-Awesome-SVG-PNG.

Run: bower info font-awesome-svg-png
To list the available versions.

That works because I (or someone else, but I tried it too) registered the package.  Solution: add and push a 1.1.1 tag.

Yes, I registered minutes ago.

For reference: roll your own SVG sprite sheets with Bower and Gulp. That might explain a bit about the rationale for adding this project to Bower.

@brunowego thanks for registering, I've fallen asleep after merging the branch. :)

Added 1.1.2 tag, since that's the version in package.json.

Checks out OK!
$ bower install font-awesome-svg-png -D
bower font-awesome-svg-png#*    cached git://github.com/encharm/Font-Awesome-SVG-PNG.git#1.1.2
bower font-awesome-svg-png#*  validate 1.1.2 against git://github.com/encharm/Font-Awesome-SVG-PNG.git#*
bower font-awesome-svg-png#~1.1.2          install font-awesome-svg-png#1.1.2

Thanks! :+1:


The version of neutron-lbaas used by nightly regression runs is incorrectly set.

Title: This issue is a bug, neutron-lbaas should be pip installed as "@stable/$branch" to match the version of f5-openstack-agent we are running against.

Issue resolved by merge #436


feat: add status update features for (admin) attractions

Adds buttons in the list dropdown and the attraction editor to update the status of individual attractions.

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1205673236797618

I’ll go ahead and merge this now!


Add docs on passing SSH through to container

Wasn't clear how to pass SSH connections through the container, found a
few blog posts which described roughly the same procedure I've
documented here.
Credit should really go to:

https://blog.sakuragawa.moe/gitea-in-docker-container-and-sharing-ssh-with-host/
http://www.ateijelo.com/blog/2016/07/09/share-port-22-between-docker-gogs-ssh-and-local-system

Signed-off-by: Dane Elwell<EMAIL_ADDRESS>

Codecov Report

Merging #5019 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5019      +/-   ##
==========================================
- Coverage   37.41%   37.41%   -0.01%
==========================================
  Files         306      306
  Lines       45374    45374
==========================================
- Hits        16978    16976       -2
- Misses      25944    25946       +2
  Partials     2452     2452

Impacted Files
Coverage Δ

models/repo_list.go
61.76% <0%> (-1.18%)
:arrow_down:

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 d7ca839...b05ebcf. Read the comment docs.

Fixes https://github.com/go-gitea/gitea/issues/4978

With the plan on removing OpenSSHD from the container, this would no longer work so I'm hesitant to add this to documentation

When we switch to builtin ssh we can always remove this section but while we have not switched it is still good to have it

@lafriks ok. sounds good.

@lafriks I've updated PR with changes from your feedback, please review


Using malformed ticket should not print absolute path to web application in the filesystem

When malformed ticket is used, phpCAS gives out the following error to user:

phpCAS error: phpCAS::client(): ill-formed ticket found in the URL (ticket=`foo') in /var/www/this_is_dummy_webapp/public_html/dummy_app/vendor/xavrsl/cas/src/Xavrsl/Cas/Sso.php on line 172
This is unneccessary and exposes unneeded information to users.

This could uses some hardening like #147

Should be fixed, see #152


Update docs

Remove outdated information, add info about coffeelint, add wireframes

Added info about CoffeeLint

Replaced "JavaScript Style Guide" with "CoffeScript Style Guide"

Added info about social network authentication

Added ER-diagram


Include "cloudPlatform" in the data lake list API

Based on the cloudPlatform (AWS or Azure) we need to hit different services to interact with metadata for data residing with the cloud providers (in addition to ATLAS), e.g. AWS Glue Data Catalog in AWS.

NOTE: This implementation will incur an additional API call per SDX Cluster.

Could you add a JIRA ticket number to the PR?

It's the branch name, but sure: https://jira.cloudera.com/browse/CB-7928


Sync eng/common directory with azure-sdk-tools for PR 2276

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/2276  See eng/common workflow

/azp run js - keyvault-keys - tests


Add a tool to support detection engine developers

Would be nice to have a tool based on Geneve that can help detection engine developers iterate on their works.

@spong please describe your flow and how this tool could improve it.

Of course! 🙂
So as detailed a bit over in https://github.com/elastic/geneve/pull/128#discussion_r1098127262, one of the most frequent and basic workflows for us on the dev side is triggering a specific Detection Rule. We'll need to do this when developing new features, debugging rules, or digging deeper into SDH's. This often needs to be done locally on the dev machine (against a local kibana/es), but support for cloud clusters would be great too as this is often the quickest way to test previous stack versions (and of course is a more accurate representation of a customer deployment). Let's go through what this might look like...
Deployment setup
Devs will usually either be running both ES (yarn es snapshot) and Kibana (yarn start) locally against Kibana source, or running Kibana locally (yarn start) and connected via CCS to an internal deployment (like the o11y test envs. If not running locally, the other use case is usually an Elastic Cloud deployment.
Current Workflow
With the above deployments, our current workflow is to either setup beats locally, configure to the specified deployment, then perform some actions that may create the necessary source events to trigger the desired rule, or to configure an agent/endpoint and then trigger within the agent env (now a bit easier with the Endpoint CLI introduced in https://github.com/elastic/kibana/pull/149903).
Note that index/mapping configuration happens as part of beat, integration, and/or agent setup, so this is handled as part those steps.
Automated Workflow
Ideally, it would be great to interact with geneve or an intermediary tool that would automate the index/mapping configuration setup, and then perform an index operation for a number of documents that would trigger a specific detection rule.
At minimum, this tooling would take a Detection Rule name (Persistence via Update Orchestrator Service Hijack) or id/rule_id (58df1cf0-a643-11ed-bf5b-914b730eb325), and maybe some additional config like how many times to replay, interval, replacement variables, etc. All deployment configuration would default to local kibana/es, but could be overridden with additional flags to say point to a cloud deployment. E.g.
geneve trigger-rule "Persistence via Update Orchestrator Service Hijack"

Which would perform the following:

Install/enable latest (since version not specified) prebuilt rule Persistence via Update Orchestrator Service Hijack (on local kibana instance)
Fetch query from rule, and generate sample source documents
Fetch index patterns from rule, generate mappings from source docs, push mappings as index patterns named on rule (to local es)
Ingest source documents into indices defined on rule (to local es)
Rule triggers on next execution 🎉

And with additional simple configuration to modify the flow:
geneve trigger-rule "Persistence via Update Orchestrator Service Hijack" --replay 5 --interval 3m --variable host.name=geneve

Which would do the same as above, but re-ingest the source documents 5 times, every 3 minutes, and replace the host.name name field with the value geneve.
And then of course some flags for choosing additional deployments:
Explicit local
geneve trigger-rule "Persistence via Update Orchestrator Service Hijack" --es http://elastic:changeme@<IP_ADDRESS>:9200 --kibana http://elastic:changeme@<IP_ADDRESS>:5601/kbn

Cloud
geneve trigger-rule "Persistence via Update Orchestrator Service Hijack" --es https://cloudy.es.europe-west1.gcp.cloud.es.io --kibana https://cloudy.kb.europe-west1.gcp.cloud.es.io:9243 --cloudID abcxyz

Hopefully this outlines this frequent use case from detection engineers, but let me know if you have any questions and happy to pair or expand further. Outside generating relevant source events, the mapping/index configuration is the next largest point of friction as we usually have to hunt down a specific mapping, either installing beats locally, specific endpoint integrations (that might not be easily configured), or a full agent.


Put in place procedure to extract reference docs and publish them to istio.github.io

We need to extract reference documentation for our config and push it into istio.github.io so that it shows up on www.istio.io.
We could have something that runs once a night, or once per commit to the repo. We need to figure out the right tools to extract the doc and what format to output, etc.

Also included here is extracting command-line options for our various commands.
The mixcol command we produce during a build can be used for this. You run this command and it'll output HTML describing the mixc and mixs commands by leveraging the Cobra library's ability to output nice docs for individual commands.

To be clear: the deliverable for the alpha is a static set of documents. Post alpha we'll tackle automatically generating them at some regular internval. Does that match your understanding @geeknoid?

Yes, I think we can tackle automation separately.
So it's about producing the docs and wiring them appropriately in istio.io.

What is the status here?  Are we able to close this (with the static docs we have now)?  Or do we need to wait until the final alpha cut?

I checked in the last mixer docs today (the CLI stuff), but we still need to track the larger "make this happen automatically" task.
There's still one more round of generation that needs to happen pending some bug fixes in the doc gen tool.

@geeknoid, is this issue still relevant?

All done.


Add an about page.

this page from mirror, mentioned by the bot, would be a good one, requiring little if any editing.

It is there for the taking. However, it was a suggestion only so PR might
not be accepted.
On Sun, Jun 5, 2022 at 9:31 PM Fernando @.***> wrote:

can I take this one
—
Reply to this email directly, view it on GitHub
https://github.com/MetricsDAO/xyz/issues/25#issuecomment-1146972672, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AARXIT23CPVTFHH6A42MBADVNVPI7ANCNFSM5X4KZDRA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Publish new image and helm chart version?

Thanks so much for this great project. It generally works really well, though sometimes I observe some funny behavior that I'm more likely to blame cloudflare on.
Still, it looks like a lot of improvements have been made since the 0.0.9 release in November. Would you mind cutting a new release image and helm chart?
Thanks again.

here we go!
https://github.com/STRRL/cloudflare-tunnel-ingress-controller/releases/tag/v0.0.10
BTW, there're some new codes that are not well tested, I would keep trying to improve that in the next weeks.
feel free to open a new issue if you encounter some unexpected behavior!
Thanks!


stdenv.hasLicense: ? supports nested lookup

Motivation for this change
minor performance gain
this avoids one copy of the attrset
supported since nix 1.0
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

outtake from evaluation statistics:

value
pre
post

time elapsed:
2.618
2.425

values allocated
1685932 (40462368 bytes)
1646089 (39506136 bytes)

number of thunks:
1391156
1378151

number of thunks avoided:
944109
903438

number of attr lookups:
423421
383578

number of primop calls:
220634
193796

total allocations:
203529544 bytes
202573312 bytes

total Boehm heap allocations:
245309136 bytes
244035280 bytes

Impressive speedup.

@Mic92 I only evaluated once so the time measurement is not accurate. But it should be faster :smiley:
The memory consumption is accurate though.


Product Feedback Wanted: CLI or REST API for setting data retention period?

Currently, setting a default data retention period requires executing a SQL command, e.g.,:
SELECT set_default_retention_period(180 * INTERVAL '1 day')
As a user, would you prefer to set this via a CLI or REST API instead?
Welcome any comments.

CLI seems to be a better approach. In future, if the configuration flags grow. We can add an option to provide a config file. This will help in passing all config using a single file.  (This approach needs a restart of connector for modifying retention period.)
REST API has its downside i.e. we never know what is the retention period if it's set/updated using the REST API.

I agree generally with the CLI approach; in particular it would be nice for it to just be a setting in the Helm Chart that gets read by the Connector and initialized/reset during startup in the same way that migrations currently are run.


[AJ-1277] select and delete rows

Jira Ticket: https://broadworkbench.atlassian.net/browse/AJ-1277

Summary of changes:

What

Adds support to select and delete rows in a WDS data table

Why

progress towards WDS feature parity

Testing strategy

[x] Unit tests
[ ] Manual tests against dev

If I run this branch against your AJ-1277_delete-records-capabilities WDS branch, I get an error when I try to delete a record - on WDS's end it shows that it gets the request with no errors, but the response returned to the UI is {   "error": "Bad Request",   "message": "Failed to read request",   "status": 400,   "timestamp": "2024-09-30T13:39:57.320+00:00",   "path": "/records/v1/f6f984a9-3bbe-48b9-9389-bf73f8d2f558/primary/delete" }.  Is there something further I need to do to get this set up to work?

Ok I think there's a mismatch between the format of the deleteRecordsRequest in the front end and backend.  In the backend, everything is camel case: recordIds, front-end is snake cake: record_ids.  But once I changed that there were still problems: recordIds should be a list of strings, the record ids, but the front end is passing in a list of objects with keys entityName and entityType.


Update Variation and VEP public documentation for e106

Hello @helensch , thanks for review.
I have updated the files accordingly.

Hi @nakib103 thanks for the updates. Looks good to me. @sarahhunt will review tomorrow

Thanks @nakib103 & @helensch


[BUG] nodes are not being deleted on the backend when a cluster is deleted through rancher

backport https://github.com/rancher/rancher/issues/34946

It's hard to reproduce this issue now. Move to v1.0.0.

To Test:

spin up the rancher-v2.6.3-rc1, bump the node-driver manually via Drivers -> Node Drivers -> Edit Harvester Node Driver

Edit the down URL and replace the version with v0.3.4 and remove the checksum

provision some cluster(s) (rke1/rke2) via the harvester node driver
deleting one of the clusters at some point while it is provisioning or after it comes to active state
both cluster and VM should be removed successfully after a period of time.

Verified fixed on master-d577bb6c-head with rancher v2.6.3-rc1 (node driver v.0.3.4)
Delete the RKE2 cluster while in provisioning and after it already deployed in active state.
Both the cluster and all VMs will be removed on rancher and harvester dashboard
Result
Delete 3 nodes RKE2 cluster while provisioning

All VMs will be removed on harvester

And if we delete cluster after deployment finished. All cluster and VMs will be deleted as well.
Test Information

Rancher version: v2.6.3-rc1
Node driver: v0.3.4
Harvester version: master-d577bb6c-head

Environment Preparation

Install Rancher v2.6.3-rc1
Update ui-dashboard-index and ui-offline-preferred in global settings
Import harvester
Edit harvester node driver and set to v0.3.4

Create cloud credential

Verify Steps

Environment preparation as above steps
Create 3 nodes RKE2 cluster

Wait for all RKE2 VMs running on harvester
Remove entire cluster from Rancher
Check both cluster and VMs can be removed correctly
10.Create a 3 nodes RKE2 cluster again
Wait for cluster finish deploy in running status
Remove entire cluster from Rancher
Check both cluster and VMs can be removed correctly

Additional Context
When the 3 nodes rke2 cluster in provisioning status, delete one node of cluster in rancher will not actually remove it.
The node status in rancher will change from Deleting then resume to provisioning
The rke2 node vm in harvester will change from  terminate to starting
Confirmed it's the expected behavior, just memo down these information for reference.
Delete one of the node in rke2 cluster from rancher dashboard

rke2 node vm was being terminated on harvester

But resume to start new rke2 vm on harvester