restore trimming with NONE compression

compressor == nullptr is a legal construction parameter for VulkanStateWriter (in the case there is no compressor) so remove an assert.

CI gfxreconstruct build # 1531 running.

CI gfxreconstruct build # 1531 passed.


Problem running bundle install

~/dev/testvizzuality$ bundle installFetching source index for http://rubygems.org/
Could not find cartodb-rb-client-0.1.1 in any of the sources
I can get cartodb-rb-client-0.2.0 but not sure if it will work.

Wrong project


Updates for v2 based on feedback

Summary
Updates based on comments on #380 & #381
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

@stevengill can you cherry-pick this commit for corresponding changes to Japanese docs? https://github.com/seratch/bolt/commit/37bfd07ee9ecbae8d8d528ad7fb08968332342c5


Cannot open local storage with mode=rw

Hi all,
I am trying to connect to server with remote mode as mentioned troubleshooting page but no luck.
I am checking with ps aux | grep -i orient and ps aux | grep -i server.sh if there is any other working instance but there is not.
I am stopping and starting server and then trying to connect via console or web but no luck. Still same error.

Connecting to database [remote:xxx.xxx.xxx.xxx/ViaApi] with user 'admin'...
Error: com.orientechnologies.orient.core.exception.OStorageException: Cannot open local storage '/opt/orientdb-community-2.1.8/databases/DemoDB' with mode=rw
Error: java.lang.NullPointerException

I am checking with lsof +D /opt/orientdb-community-2.1.8/databases/DemoDB -t but i am getting only one PID.
Any idea?
Thanks.

Check this out.
https://github.com/orientechnologies/orientdb-docs/blob/master/Troubleshooting.md#error-comorientechnologiesorientcoreexceptionostorageexception-cannot-open-local-storage-tmpdatabasesdemo-with-moderw
Scott

Hi, could you provide full stack trace, not only exception itself.

Close issue because of no reply. If you reproduce given issue and have information which is requested in issue feel free to reopen it.

I am also facing the same issue.
Caused by: com.orientechnologies.orient.core.exception.OStorageException: Can not open storage it is acquired by other process 	DB name="test"
Is this issue still there or is it solved?

@nishantkumar1292 two processes by design can not open the same database. But why you have it in ETL that is a good question. Could you open separate issue in ETL project?

I have a Rails application which communicates with OrientDB and renders many views and logics.
However I would like to do ETL on this database and for this I need to create json files and run data insertion. But I am getting the above error.


Additional sensors not added

Hi,
Thanks a lot for the add on. I tried to configure the other sensors as per below but still in the HA, there is only one sensor showing on off depending on the rate... Any advice what to correct? thanks a lot.

platform: predistribuce
receiver_command_id: 605
periods:

name: "HDO baterie 3h"
minutes: 120
name: "HDO baterie 4h"
minutes: 160

Here is how I got it work. But frankly I am not a programmer and this is what ChatGPT suggested so hard to say how clean this solution is.
binary_sensor.py
raplece
        self._attr_unique_id = f"{DOMAIN}-hdo-{conf_cmd}"
with
        self._attr_unique_id = f"{DOMAIN}-hdo-{conf_cmd}-{minutes}"
configuration.yaml
binary_sensor:
  - platform: predistribuce
    receiver_command_id: 565
    sensor_name: "PRE HDO"
    periods:
      - name: "HDO shower"
        minutes: 10
      - name: "HDO living room heating"
        minutes: 120

sensor:
  - platform: predistribuce
    receiver_command_id: 565

I would like too have also "HDO čas do vysokého tarifu" apart from "HDO čas do nízkého tarifu" but I couldn't make GPT to make it work.


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

Thanks a lot for spotting this!


Export RouterLink component

What problem does this feature solve?
I have a use case where I want to implement a custom <nav-link> component that builds on top of <router-link>. While this is perfectly possible, it requires me to replace all my <router-link> references with <nav-link> (and I have about 200 of them). Therefore it would be useful to be able to explicitly reference Vue Router's <router-link> in the <nav-link> component so that I can globally register my component as
import Vue from 'vue';
import Router from 'vue-router';
import NavLink from './nav-link.vue';

Vue.install(Router);
Vue.component('router-link', NavLink);

What does the proposed API look like?
I propose to explicitly export the <router-link> component (and perhaps <router-view> as well) so it can be imported like this:
// # nav-link.vue
<template>
  <router-link>
    <slot></slot>
  </router-link>
</template>

<script>
import { RouterLink } from 'vue-router';

export default {
  components: {
    RouterLink,
  },
};
</script>

I will file a PR for this.

Duplicate of https://github.com/vuejs/vue-router/issues/1976

Apologies!


Add CI check for enable LIBSPDM_RECORD_TRANSCRIPT_DATA_SUPPORT

Signed-off-by: Wenxing Hou<EMAIL_ADDRESS>

This patch will fix the libspdm issue: https://github.com/DMTF/libspdm/issues/774

Question: Can this detect pass/fail?

CI failed

The CI will pass after: the patch Fix the mut_hash inconsistent is merged in libspdm and  the spdm-emu sync the latest libspdm.


Update set-dbt-semantic-layer.md

What are you changing in this pull request and why?
Updating for package version

@mirnawong1 if this information is also reflected in the quickstart then yes, we'd want it updated there as well.

thanks @callum-mcdata ! i'm going to make that change in your branch if that's ok, so it's all consistent 🙏


Adding missing variables when MFEM_THREAD_SAFE is ON [bugfix/thread-safe-dev]

Adding missing variables when MFEM_THREAD_SAFE is ON

Hi @mlstowell,
Should this be marked as ready-for-review?
No rush, just checking 😄
Tzanio

I just hit this issue myself. Anything I can do to help push it along?

I just hit this issue myself. Anything I can do to help push it along?

Thanks @SallySoul, you just did. I'm afraid it just slipped through the cracks but you brought it back to our attention.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Merged in next for testing...


New version: BusinessDays v0.9.23

Registering package: BusinessDays
Repository: https://github.com/JuliaFinance/BusinessDays.jl
Created by: @felipenoris
Version: v0.9.23
Commit: 83835c678baffcabd397a7760d1af9a9bbc08dd4
Reviewed by: @felipenoris
Reference: https://github.com/JuliaFinance/BusinessDays.jl/commit/83835c678baffcabd397a7760d1af9a9bbc08dd4#commitcomment-132221131
Description: :calendar: A highly optimized Business Days calculator written in Julia language. Also known as Working Days calculator.

cancel


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1937

Questions ?
Please refer to the Backport tool documentation


Error: Try deleting the texture, if that does not help, Open an issue on the Github Repo

ERROR, EVEN TEXTURES ARE REMOVED, HELP

Have the same problem when i am importing a model exported from mixamo.

I have uploaded my own model to mixamo and autorigged it.
Then i exported the model from mixamo as fbx.
Then i imported it in Character-Animation-Combiner: thats the result:


Breaking change related to hCenter(CGFloat), hCenter(percent), vCenter(CGFloat), vCenter(percent)

vCenter(_ value: CGFloat) and vCenter(_ percent: Percent):
The value specifies the distance vertically of the view's center related to the superview's center in pixels. Previously it was related to the superview's top edge.

hCenter(_ value: CGFloat) and hCenter(_ percent: Percent):
The value specifies the distance horizontally of the view's center related to the superview's center in pixels. Previously it was related to the superview's left edge.

Plus:

Add a new example using hCenter(to: edge)

Codecov Report

Merging #81 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #81      +/-   ##
==========================================
+ Coverage   99.31%   99.31%   +<.01%
==========================================
  Files          15       15
  Lines        3653     3669      +16
==========================================
+ Hits         3628     3644      +16
  Misses         25       25

Impacted Files
Coverage Δ

Tests/JustifyAlignSpec.swift
100% <100%> (ø)
:arrow_up:

Tests/PinEdgesSpec.swift
100% <100%> (ø)
:arrow_up:

Tests/PinPointCoordinatesSpec.swift
100% <100%> (ø)
:arrow_up:

Tests/MarginsSpec.swift
100% <100%> (ø)
:arrow_up:

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 ec384ed...3c9c7d2. Read the comment docs.


[API] Support for OnPremise Connectivity

Add support for onpremise connectivity via destinations

Changes:

https://github.com/SAP/xsk/commit/c59e45ba1cf6359f3f69eabb9650f2f3737c5441
https://github.com/SAP/xsk/commit/8546ec29c23f5924b0e7e5be069ea65744b6100d

Changes in Eclipse Dirigible:

https://github.com/eclipse/dirigible/commit/fecf0e613ebfe7bdb618f9bff390a84e39dcc4a8
https://github.com/eclipse/dirigible/commit/c74d8d36f0b805a6e33f9a71c7c8b5a0d0df0abb
https://github.com/eclipse/dirigible/commit/cf5e3cd3c9b75165c3e90ca925e07561647560f7


Automation Toolkit Release v11

Automation Toolkit Release v11

I have read the CLA Document and I hereby sign the CLA


fix: recursively convert struct to dict

Description of your changes
Converting metadata struct to a dict should return a nested dict, rather than a dict with e.g. annotations as a struct.
I have:
Read and followed Crossplane's [contribution process](https://git.io/fj2m9).
- [X] Added or updated unit tests for my change.

unsure about whether or not we want to keep the previous behaviour as default, while allowing a "recursive" struct_to_dict via an additional argument :/

unsure about whether or not we want to keep the previous behaviour as default, while allowing a "recursive" struct_to_dict via an additional argument :/

Good question - I tend to think the existing behavior is "wrong" since I would have expected nested translation, but it could be breaking if people are already used to having to convert the child objects.   I'd still lean toward changing it though.
@negz any thoughts?


Use frozenset for Cnf.dis

So that we can compare two Cnfs, and have them being equal,
regardless of the order of operations that where applied:
The test introduced at bf755df in this PR fails:
>>> (v1 & v2) == (v2 & v1)
False

But the conversion to  frozenset rectifies that:
>>> (v1 & v2) == (v2 & v1)
True

Thank you!


Update sensor value translations NL

You removed the "dry / wash" prefix. It was add intentionally to prevent confusion when the same operations are available in washing machines, dryers and combo washing/dryers.

You removed the "dry / wash" prefix. It was add intentionally to prevent confusion when the same operations are available in washing machines, dryers and combo washing/dryers.

Rolled backup the prefixes ;)


Genshin Freezing Seconds Into Sign In

Describe the bug
Whenever I sign in to start playing genshin it goes to the loading screen and then breaks. It freezes and the sound plays for a while before it just fully crashes.
Screenshots
Just the opening GI Screen with sky and pillars.
System Information (please complete the following information):

macOS: 13.2 Ventura
Device: MacbookPro 14inch 2023
CPU: Apple M2 Pro
RAM: 16G

Additional context
This is my first time using yaagl and I am able to install the game fine I just can't open it to the main menu screen for more than a couple of seconds before crash.

Still persists?

No replies, I will close this issue. Feel free to open if this problem persists.


Update playbook_log_stdout to handle possible nil job

Currently the AnsiblePlaybookMixin#playbook_log_stdout method assumes that a job will always be present. However, if we look at service_ansible_playbook.rb, we see this call:
playbook_log_stdout(log_option, job(action))
And the job(action) looks like this:
service_resources.find_by(:name => action, :resource_type => 'OrchestrationStack').try(:resource)
We know from the try call that this could thus be nil. And, in fact, that's what @d-m-u hit while testing a variant of https://github.com/ManageIQ/manageiq/pull/20645 where there's a network interruption:
ERROR -- : Q-task_id([r88_service_template_provision_task_88]) The following error occurred during instance method <on_error> for AR object <#<ServiceAnsiblePlaybook id: 88, name: "drew", <snip>
[----] E, [2020-10-26T14:09:27.389968 #1580547:2ab9680952a8] ERROR -- : Q-task_id([r88_service_template_provision_task_88]) MiqAeServiceModelBase.ar_method raised: <NoMethodError>: <undefined method `name' for nil:NilClass>
[----] E, [2020-10-26T14:09:27.390025 #1580547:2ab9680952a8] ERROR -- : Q-task_id([r88_service_template_provision_task_88]) /var/www/miq/vmdb/app/models/mixins/ansible_playbook_mixin.rb:40:in `rescue in playbook_log_stdout'
/var/www/miq/vmdb/app/models/mixins/ansible_playbook_mixin.rb:34:in `playbook_log_stdout'

So this PR updates the method so that it skips logging job.name info if there isn't actually a name.
No specs for now, there aren't any for this mixin currently, and I wasn't sure if they were moved somewhere else.

CC @NickLaMuro, @d-m-u

I'm surprised we don't have a job as we create the job first before we kick off the run.  I think we need some more investigation into how we get into this situation before we band-aid it.

@Fryguy, @NickLaMuro I'm actually curious why there's a rescue clause at all in there. All it does is return or log. So, unless the logging itself fails, I'm curious how it would ever reach that condition.

@djberg96 not that this really answers your question, but looks like it has always been this way since it was introduced:
https://github.com/ManageIQ/manageiq/pull/16414

Dan and I discussed the issue and I don't think this PR will be necessary.

FWIW, I added some specs. So, if it turns out we just want a quick fix, this will still be here.

Dan and I discussed the issue and I don't think this PR will be necessary.

What was the conclusion?

Hi @Fryguy, It doesn't make sense that we don't have a valid job here.  I'm starting to look at the environment now.

After further investigation, this code change is important.
Here's why:

The check_connection Automate method is called in the pre5 state which is called prior to the execute state where the job is created.
The method times out after the max_retries = 4 which causes the pre5 state to end in an error.
The update_status Automate method is called on_error. It calls the ServiceAnsiblePlaybook on_error method:
https://github.com/ManageIQ/manageiq-content/blob/master/content/automate/ManageIQ/Service/Generic/StateMachines/GenericLifecycle.class/__methods__/update_status.rb#L64
Which calls:
https://github.com/ManageIQ/manageiq/blob/master/app/models/service_ansible_playbook.rb#L89
Which calls postprocess:
https://github.com/ManageIQ/manageiq/blob/master/app/models/service_ansible_playbook.rb#L93
which assumes a valid job exists.

It's important to note that customers will encounter this issue if they have custom Automate methods in any of the pre* states of this state machine that end in error.
Automate State Machine
/Service/Generic/StateMachines/GenericLifecycle/provision state machine

To me, then, this feels like the caller to playbook_log_stdout should be the one to change to check that the job is real.  If anything changes in playbook_log_stdout, IMO, it should be to raise an ArgumentError if someone passes nil.

@Fryguy ok, updated

Thanks @Fryguy for pointing that out.  That makes sense.

Thanks @djberg96

@djberg96 Can you squash the commits?  The commit history now shows a change to the method and then an unchange to the method.

@Fryguy commits squashed.

@djberg96 Can this be ivanchuk/yes (which implies jansa/yes and kasparov/yes)?

@dmetzger57 What say you?

@djberg96 I mean the compatibility. Are the changes in this PR compatible with ivanchuk branch that it's ok to backport?


Header title not centered when using left icon

I have a small issue im using a drawer navigation where i can click and open the drawer. if i add a title. The title is not centered im using expo iphone 7 device.
            <Header style={{backgroundColor:'#3a455c',height:80,borderBottomColor:'#757575'}}>
                <Left>
                    <Icon name="md-menu" onPress={() =>this.props.navigation.openDrawer()} style={{color:'white'}} />
                </Left>
                <Body>
                    <Text>My title</Text>
                </Body>

If i remove the  then its centered anyway how to fix this

Maybe not completely on topic here, but for anyone else trying to get rid of truncated titles in the header, I solved it by putting style={{ flex: 2 }} on the body tag. Also all <Left>, <Body> and Right is required, but <Right> can just be left empty.


[b19] Lumberjack golems cannot pathfind to trees

If a golem (with Breaker and Smart attributes) is in range of a Lumberjack seal, the golem will not chop down any trees in the seal's range if all available trees are more than one block away from where the golem is currently standing.
If the golem is placed, or is pushed, next to a tree, it will immediately center itself over the block it is standing on and begin chopping down all trees within reach of the golem and within the seal's range. However, the golem will not actually walk up to any trees to begin chopping them down. It appears that golems (acting on a Lumberjack seal) can detect trees, but cannot pathfind to them - even if the tree is only two blocks away.

@Azanor  It wasn't, but I can test that...

Setting the lumberjacking area to 2 blocks up/down allows Lumberjacking golems to pathfind to non-adjacent trees - but only after the tree has been stripped of leaves up to at least two blocks above ground level. I am using Oak saplings, which can generate trees which have only one block of exposed "trunk" at ground level - these "short trunk" Oaks are not detected/pathfound-to as trees (when non-adjacent) until their leaf blocks two blocks above ground level are removed. (I am using an indoor tree farm, so due to limited vertical clearance, I am growing a higher-than-normal fraction of "short trunk" Oaks.)
Setting the lumberjacking area to the height of the tree trunk or greater seems to allow Lumberjacking golems to detect non-adjacent tree trunks immediately, regardless of trunk exposure height - but also causes them to attempt to climb to the top of the tree before harvesting it, which undermines the purpose of their Burrowing-enchantment-like effect, and can cause fall damage to the golem when the leaves decay from under them.

With the update to golems in B24 onwards, did this behaviour improve at all?


[Suggestion] Add note about NOT registering command(s) in plugin.yml

The documentation/wiki is okay, but misses one crucial piece on information, which is to point out, that the command you set, shouldn't be registered through the plugin.yml as this will automatically override the registration of the framework and break the command entirely.

Fixed on cd9e732c533752f262c888a458ff1b52dd6a6535 you can now register in the plugin.yml fine!

Released 1.3 with this change.


Recent changes to perk display not compatible with Clarity 1.5.12

First of all, thank you for this addon. 👍
Do to some changes in how perks are displayed with the latest beta versions, the perks are misaligned and dim will crash when you attempt to change to grid mode.
In list mode:

After pressing to change to grid mode:

(It's fixed by using Reload App.)
Screenshots taken on v<IP_ADDRESS>0793 (beta), and Brave (chrome).

Fixed in 1.6.x also available in chrome store
https://chrome.google.com/webstore/detail/clarity-a-dim-companion/mbhfgfjjllobldiodabdmaoimehdkdjc?hl=en


Continuing to revise and rearrange content for clarity and reduced redundancy.

In the last merge with 2.0RC I had made too many changes to about_hubzilla.bb to figure out what the merge conflict was, so if you made the edit that I clobbered, please redo it or point me to what you did.
I'll make a similar pull request for dev.

We'll go with your changes. If I recall I just did some quick and dirty edits to tone down the politics and get rid of the constant references to 'users'.


Recent update broke deaths

Hi, since the update of this mod yesterday, the console throws an error on death and my character lays on the floor with no gravestone spawn, screen fades to black and then you cannot do anything until you log out of the world and back in, can you look into this please? When I disable this mod deaths function as normal.
Error on death blocking death/gravestone process: https://pastebin.com/hanJeQ2P
Thanks

Thanks for the report. Uploaded a new version with a fix. Sorry for the trouble!

Thanks for the report. Uploaded a new version with a fix. Sorry for the trouble!

Amazing, thanks for the help. :)


Option to disable notifications on spesific servers or channels

As of now, thelounge supports mentions that will trigger an notification as well personal message seems to trigger notifications. But it would be nice to be able to turn off notifications on certain servers or channels that is really active, in order to suppress notification "spam".
Notifications main purpose should be to notify the user about messages that have some sort of urgency.

See #85. Previous issues about this include #44 and #248.

Closing as duplicate, as @dgw mentioned


async hydration

Objective
make hydration async.
@trueadm requestIdleCallback/requestAnimationFrame where breaking the tests, how would you write async tests for these?

I'll merge this and play around with it on dev.


[experimental] printable hana::template_

If you would like, I can do this for the other Metafunctions for consistency, but first I wanted to gauge your reaction to giving them their own tags.
I think this would be useful for more than just Printable.

I made the suggested changes, but did not add any more implementaions. Perhaps the default should print the output from boost::core::demangle.

Random note: It's crazy and scary to think that any comment we made on the original diff disappears when we update the diff. Not-so-good job from GitHub on this.

Question: Why did you not implement it for other Metafunctions? Is it just a question of time, or is there any underlying issue that would prevent that?

Random note: It's crazy and scary to think that any comment we made on the original diff disappears when we update the diff. Not-so-good job from GitHub on this.

I'd bet the information is still there, but the revision is no longer displayed in the ui.

Question: Why did you not implement it for other Metafunctions? Is it just a question of time, or is there any underlying issue that would prevent that?

Actually I'm going to try doing a specialization for all hana::Metafunctions.

I tried implementing a print_impl with when<hana::Metafunction<...>..., but it was problematic getting it to match the variadic templates not to mention that metafunction_class has a different signature (ie it is not variadic).
I went ahead and added explicit specializations for each Metafunction and switched to using a regex to "prettyify" the output. If you don't want it pulling in <regex> I can change it back, but I think it is more robust this way.

That seems good. I don't mind the <regex> include. Can you please squash those two commits and I'll merge the PR?

I won't be getting to it immediately, but I would like to add Printable to the functions in Functional. Should merging be deferred and I add that here, or should I just do a new PR later?

Why do you need to print the functions in Functional? Printing a function properly is impossible in the general case.. In all cases, that should be attempted in a different PR.

Merged in 2b0ede886e922858e5c68b3732d52cbcad89a5c4.

Why do you need to print the functions in Functional?

In my case I have trees with types and templates in them. It is useful to be able to use something like hana::partial on the result of hana::template_ in some cases. So maybe it would look like:
partial(template<nbdl::StoreEmitter>, type<std::unordered_map>)

where nbdl::StoreEmitter is a template taking two types.
My current workaround has been to wrap the whole works in hana::type_c<...>, because otherwise print explodes.

Hmm. It would work fine when the function is a template_, but what about when the function is something arbitrary? For example, what would you expect hana::experimental::print([]{}) to output?

lol idk. I should probably play around with it and see what is feasible.

Sure; don't hesitate to create another PR or an issue if you think this is a valuable addition, and we'll discuss. I'm just a bit skeptical, just as I would be if someone proposed to make functions Comparable (impossible in the general case). I'm not saying that printing functions is not feasible, but it certainly is not obvious how to do it sensibly.


Adding list devices and get device methods

@bettirosengugi  hi Betti, can you please review this pull request?
CC: @irvinesunday @hafowler

@bettirosengugi  hi Betti, can you please review this pull request?
CC: @irvinesunday @hafowler

@hafowler please resolve the conflicts so we can merge this PR.
Thanks

@hafowler please resolve the conflicts so we can merge this PR.
Thanks

@bettirosengugi I believe I have resolved the conflicts. Please let me know if I have not.


Reflect errors from valid WGSL

After testing reflect, I got two errors from what I believe are valid wgsl code (it runs without warnings)
@compute @workgroup_size(64)
fn compute(@builtin(global_invocation_id) id : vec3<u32>) {

    // return void from a function
    if (id.x > 1000.) { return; }
    // error: Uncaught (in promise) TypeError: this.args is not iterable

    // vector type inference from abstract types
    let f = vec2(0.);
    // error: Uncaught (in promise) TypeError: Cannot read properties of null (reading 'isStruct')
}

Fixed and published npm update.

Thanks. All good on my side.


Passphrase for private key files

Hi
I was looking for passing passphrase of a private key file into below code snippet :
kafka = Kafka.new(
  ssl_ca_cert: File.read('my_ca_cert.pem'),
  ssl_client_cert: File.read('my_client_cert.pem'),
  ssl_client_cert_key: File.read('my_client_cert_key.pem'),
)

Any help ?

@iam404 sorry for the late response. I'm unfortunately not familiar with how you'd do that – @tcrayford would you know this?

@dasch it looks like http://stackoverflow.com/questions/235759/opening-an-rsa-private-key-from-ruby is the right thing - we'd need another parameter for the passphrase, that's all. @iam404 want to make a PR for that?

Ya sure , will test the above solution and create a PR. Thanks.


Revert "Restrict data plane bindings"

Reverts vespa-engine/vespa#24009

Will open new pr with revert for only 2nd commit


Virtual HID Framework (VHF): need xample

We need some example.

+1

There is one, but I can't get it to working, it's like I am misconfiguring lower filter to that driver or something, all hid reports get STATUS_SUCCESS but nothing changing in the USB Game Controllers
https://github.com/ms-iot/samples/tree/develop/HIDInjector

We need some example.

A more current version of HIDInjector is available here: https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/HIDInjector

+1


Don't use 'here' as link text

It's generally unhelpful to use a non-descriptive word such as 'here' as the link text. This disadvantages people who use screen readers. Link text should describe what the link does.
For example under the following section:
https://www-paulau.staged.apache.org/foundation/press/kit/#template-for-the-creation-of-powered-by-logos

This is corrected. Closing.

That is so weird, I could have sworn I committed that. Okay, it's fixed now, thanks!


URL querystring not parsed correctly in 0.7.0

It seems that since upgrading to 0.7.0, drf-flex-fields no longer parses expansions requested via URL querystring the same way.
I have been doing this:
class EphemeronViewSet(FlexFieldsModelViewSet):
    [...]
    def get_serializer(self, *args, **kwargs):
        if "expand" in self.request.query_params:  # add from querystring in URL
            kwargs["expand"] = self.request.query_params['expand']
        return super(EphemeronViewSet, self).get_serializer(*args, **kwargs)

which allows expanding fields like this:
curl '<IP_ADDRESS>:8000/api/ephemera/?expand=user'

But since upgrading to 0.7.0, the field no longer gets expanded in the output.
I think these changed lines are what resulted in the change in behavior. If I add a print(passed) just after that and compare previous behavior to 0.7.0:
Before:
{'expand': 'user', 'fields': [], 'omit': []}

After:
{'expand': ['u', 's', 'e', 'r'], 'fields': [], 'omit': []}

Perhaps these lines should be something more like [kwargs.pop("expand")] if "expand" in kwargs else [] instead of list(kwargs.pop("fields", []))?
(Or perhaps there's a better way to pass querystrings to drf-flex-fields than what I've been doing in my get_serializer() override as shown above? I have been doing it that way in order to expand fields in response to a POST request, if I recall recorrectly.)

Thanks, I'm looking into this.

I appreciate the detailed issue. Yes, I agree that those changes lines are responsible. Before, it seems like things worked when you passed a string value for expand when constructing a serializer:
serializer = EphemeronSerializer(object, expand='user')

As I understand from your issue, this used to work. However, I did not intend to support passing strings to the keyword serializer options (expand, fields, omit). Ensuring that you pass a list for the expand value should fix this for you.
serializer = EphemeronSerializer(object, expand=["user"])

But ... what you are doing in the get_serializer method may not be necessary because this package will automatically read the expand value from request's query params (if it is not passed explicitly as a kwarg to the constructor):
https://github.com/rsinger86/drf-flex-fields/blob/cef061c946bbc51b56897e4a4de43d0d7140fa97/rest_flex_fields/serializers.py#L226

I see! I'll look into other ways of expanding fields in response to POST requests. I see it was discussed on https://github.com/rsinger86/drf-flex-fields/issues/25.
Thanks, feel free to close!

Ah I see. Yes, the


x86 cant be recognized

win 10
sublime text2 3126
x86 : 无法将“x86”项识别为 cmdlet、函数、脚本文件或可运行程序的名称。请检查名称的拼写，如果包括路径，请确保路径正确，
然后再试一次。
所在位置 行:1 字符: 21

D:\Program Files (x86)\Sublime Text Build 3083 x64\Data\Package ...

Do you have a custom configuration set up for Sublime Terminal?

no just the original code.
I test the code
in terminal.py line 82:
            buf = create_unicode_buffer(512)
            if windll.kernel32.GetShortPathNameW(sublime_terminal_path, buf, len(buf)):
                sublime_terminal_path = buf.value
            os.environ['sublime_terminal_path'] = sublime_terminal_path.replace(' ', '` ')

the channge to short path cant work in my computer  win10

Ah, good eye. It looks like Windows should support environment variables up to 2048 characters:
https://blogs.msdn.microsoft.com/oldnewthing/20100203-00/?p=15083
@wbond Could you give us more context behind this code?

@twolfson This handles non-ASCII file paths in Sublime Text 2. The short path name in Windows is guaranteed to be ASCII, sidestepping issues with the bytes-only APIs that are prevalent in Python 2.x. These issues were one of the primary motivators for Sublime Text jumping to quickly from ST2 stable to ST3 beta. Python 3.3 resolved all sort of unicode issues, although some of the edge cases weren't fully fixed until Python 3.6, released just 9 months ago(!).


Upgrade the default dev environment to Ubuntu 20.04.2 LTS

Upgrade from Ubuntu 18.04 LTS to 20.04.2 LTS.

This isn't necessary as team members can use any setup that works.


Fix NPE for invalid world argument in gamerule cmd

Stumbled upon an NPE when using /mv gamerule. I realised it was because I had specified a nonexistent world. This simple PR should fix it.

Seems good. Thanks!


Install changes gist to github

I think the latest bundle-like install came with a little twist. Whenever there is a gist dependency in paket.dependencies running paket install it gets rewritten to github X/Y FULLPROJECT

Mhm that's not good.
On Jan 1, 2015 7:22 PM, "Tomasz Pluskiewicz"<EMAIL_ADDRESS>wrote:

I think the latest bundle-like install came with a little twist. Whenever
there is a gist dependency in paket.dependencies running paket install it
gets rewritten to github X/Y FULLPROJECT
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/498.

Mhm that's not good.
On Jan 1, 2015 7:22 PM, "Tomasz Pluskiewicz"<EMAIL_ADDRESS>wrote:

I think the latest bundle-like install came with a little twist. Whenever
there is a gist dependency in paket.dependencies running paket install it
gets rewritten to github X/Y FULLPROJECT
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/498.

do you have a public repo where I can reproduce this?

do you have a public repo where I can reproduce this?

Actually it seems the problem is not with install but rather with add. At least I can't reproduce now.
Try this repo and run src/.paket/paket.exe add nuget nhibernate
This will change gist into github in paket.dependencies

Actually it seems the problem is not with install but rather with add. At least I can't reproduce now.
Try this repo and run src/.paket/paket.exe add nuget nhibernate
This will change gist into github in paket.dependencies

Thanks for reporting. Fixed.


:arrow_up_small: added $resolved_proto map

Improve Protocol Forwarding Accuracy Using resolved_proto
This PR enhances the accuracy of protocol forwarding in Nginx Proxy Manager by introducing a resolved_proto map variable. The resolved_proto variable ensures that the X-Forwarded-Proto and X-Forwarded-Scheme headers consistently reflect the most authoritative protocol information, particularly in setups involving upstream proxies like Cloudflare or AWS.
Context
While learning Nginx, I encountered an issue where protocol mismatches occurred in setups using Cloudflare's proxy feature, leading to errors in applications like Laravel. Specifically, in my case, Laravel's Livewire file upload feature failed with unauthorized errors when the X-Forwarded-Proto header was incorrectly set to http instead of https.
After investigating further, I discovered that the proxy.conf file in Nginx Proxy Manager always sets X-Forwarded-Proto to $scheme, which can conflict with the upstream X-Forwarded-Proto header set by proxies such as Cloudflare. This issue is compounded because these lines are automatically included in the default location block, leaving no way to override them through the UI.
Changes in This PR
To address this issue:
A resolved_proto map is introduced:
map $http_x_forwarded_proto $resolved_proto {
    default $scheme;
    ~.+ $http_x_forwarded_proto;
}

X-Forwarded-Proto and X-Forwarded-Scheme headers now use $resolved_proto instead of $scheme in proxy.conf and _location.conf.
Benefits

Ensures that the X-Forwarded-Proto and X-Forwarded-Scheme headers correctly reflect the protocol information from upstream sources.
Resolves compatibility issues with upstream proxies like Cloudflare and AWS, ensuring seamless integration with applications relying on accurate protocol headers.

Notes
This PR serves as a suggestion and might not cover every edge case, as I’m still learning Nginx. However, it addresses a common issue many users face, as documented in this discussion, and many more I saw in Laravel, Livewire or Filament issues while researching.
any feedback is welcome to refine the implementation further.

This is a beautiful example of a well written PR comment :)
Thanks for looking into this - NPM was originally written with the concept that it would be the edge server and not behind another proxy.
CI is currently failing with:
16:42:43  nginx: [emerg] unknown "resolved_proto" variable

This is a beautiful example of a well written PR comment :)

Thank you very much :)
I'm trying to make an easy to use deployment script for Laravel apps and found NPM a very useful tool in doing so, still have a lot to learn though, if you know any good resource, let me know


app crash on iOS emulator right after install

Actions order

Execute flutter run on the App (the App successfully started on Android emulators and devices)
App successfully builded and installed on iOS simulator, but then crash.

Crash report and output of "flutter doctor" in attachment.
Please help with this problem.
I cannot understand the crash report and accordingly it is not clear how to solve this problem.
failure.txt
flutter_doctor.txt

@huycozy , good day,
in attachment. Thanks!
flutter_run_v.txt

@shaprinskiy From your logs, it seems the issue is caused by a runtime error since it was built successfully.
And I am unfortunately not sure how to resolve this issue.
So I would suggest you keep an eye on it and debug it step by step in the flow of implementation. Once you find the implementation that causes the issue, please write a comment and we can continue investigating this.

Thanks, I'll try to figure it out..

@huycozy
the application stopped crashing after removing the flutter_yandex_ads plugin (1.0.0+1)


Hello author, I like your desktop wallpaper very much, could you provide a complete picture or a link? Thank you so much!

Hello author, I like your desktop wallpaper very much, could you provide a complete picture or a link? Thank you so much!

@sawhney17, a user wants your wallpaper. Can you help?

Here's the wallpaper!

Thank you very much


Data spontaneously dropped from shard, retention policy possibly fails

Bug report
System info: influxdb:1.3.3, running in docker persisted via host mount
Steps to reproduce:

Write data to default database (starting using influx 0.10)
Upgrade database and continue to write
Change shard duration from 1 week to 3 months
Change retention policy to 3650d
Continue writing

Expected behavior:
Writes continue and data is persisted for 10 years in line with the retention policy (and the expiration date of the shards).
Actual behavior:

50% of the series from a shard (378 default      autogen          2017-01-16T00:00:00Z 2017-04-10T00:00:00Z 2027-04-08T00:00:00Z) are no longer queryable (there is a 3 month hole in all the data)
Writes continue to succeed (for the other 50% of time series)
The shard itself was not empty (300MB vs. 550MB before)
In the client code there were no "drop shard" commands used, delete from is used with specific time series (but never for exactly the shard period)

Additional info:
The relevant part of the output of show shard groups:
220 default      autogen          2016-12-19T00:00:00Z 2016-12-26T00:00:00Z 2026-12-24T00:00:00Z
197 default      autogen          2016-12-26T00:00:00Z 2017-01-02T00:00:00Z 2026-12-31T00:00:00Z
196 default      autogen          2017-01-02T00:00:00Z 2017-01-09T00:00:00Z 2027-01-07T00:00:00Z
195 default      autogen          2017-01-09T00:00:00Z 2017-01-16T00:00:00Z 2027-01-14T00:00:00Z
293 default      autogen          2017-01-16T00:00:00Z 2017-01-23T00:00:00Z 2027-01-21T00:00:00Z
378 default      autogen          2017-01-16T00:00:00Z 2017-04-10T00:00:00Z 2027-04-08T00:00:00Z
432 default      autogen          2017-04-10T00:00:00Z 2017-07-03T00:00:00Z 2027-07-01T00:00:00Z
433 default      autogen          2017-07-03T00:00:00Z 2017-09-25T00:00:00Z 2027-09-23T00:00:00Z
563 default      autogen          2017-09-25T00:00:00Z 2017-12-18T00:00:00Z 2027-12-16T00:00:00Z
564 default      autogen          2017-12-18T00:00:00Z 2018-03-12T00:00:00Z 2028-03-09T00:00:00Z

Output of show retention policies on "default":
name     duration   shardGroupDuration replicaN default
----     --------   ------------------ -------- -------
autogen  87600h0m0s 2016h0m0s          1        true

Can confirm, have the same issue after upgrade and transferring to tsm

When you write "Write data to default database (starting using influx 0.10)", did you upgrade directly from version 0.10 to version 1.3.3?  What was the upgrade path you followed?

In my case, I upgraded incrementally.  I can't say exactly which versions I went through exactly but 1.0, 1.1 and 1.2 were used on the way.  I'm also not sure the data wasn't dropped at the exact moment I upgraded to 1.3.3 or if it was a delayed response.

If you were upgrading from 0.10, did you do the meta store conversion described here?

In our case we upgraded from 1.2.4 to 1.3.0 directly, then incrementally to 1.3.5.

Yes, in out case, we did the meta store conversion as described.  It seemed at the time (probably about a year ago) that everything worked ok.  The actual issue occurred at 1.3.3, but at that time we had been off 0.10 for a long time.  The last upgrade we performed was from 1.3.0 to 1.3.3.

@daviskirk do you still have the data from 0.10?

We just did a clean influxdb 1.3.6(tsi1 enabled) reprojection of data in dev from 2016-12-26 to 2017-10-16 and were left with some gaps in the data again.  Where the data went in successfully but the data is not coming out on queries. I can provide the db and which specific series' have gaps

@mmuller99 that would be helpful. Can you snapshot the data directory in its current state before additional compactions take place.

Can you describe the process you use to load the data.
Did you perform any deletes?

I will take the entire db if you don't mind providing it and the queries too

@stuartcarnie where can I reach you? As I can't make the data available publicly

@stuartcarnie Sorry, unfortunately I don't have a backup of data from the 0.10 deployment.  The newer data I'm afraid I can't provide because of confidentiality issues.

@mmuller99 I'm going to find out how you can get the files to me. How big is the db when compressed?

@mmuller99 we're going to create a location for you to upload the data

@mmuller99 I have credentials for you – is your remotemetering.net email ok?

@daviskirk were you using the TSI1 index?

@stuartcarnie small subset of our data, compressed to 36mb. Yeah the remotemetering.net is good

Did a reprojection again with no drop series command beforehand and it seems to be fine.
In our normal operating environment we do need to do a drop series though before we do a reprojection, as in our case data changes historically and with a different time interval between points.

@stuartcarnie No, in the 1.3 versions we haven't upgraded to TSI1, we left the default (which should be still inmem in 1.3.3)

@mmuller99 can your provide the output of show shards too please?

@mmuller99 if you could provide the exact steps you use to reproduce the issue (every command), that would be incredibly helpful

@stuartcarnie will provide the steps in the ftp along with the data

@stuartcarnie can check the ftp

@mmuller99 narrowed the issue to TSI in your case. If I remove the index path and disable TSI, the data shows up.

The original issue reported by @daviskirk should be fixed by #8981.

@stuartcarnie Nice!

Fixed via #8981

@stuartcarnie @jwilder should this be fixed in 1.3.7 or only in 1.4.0? We have done a clean full reproject on production with a fresh 1.3.7 and still have the same problem

@mmuller99 are you still using TSI?

@stuartcarnie yes, we are

@mmuller99 TSI has undergone a series of significant improvements in 1.4

@stuartcarnie what do you propose we do?  Wait it out, and if we do, do you think the issue will be resolved?

@mmuller99 can you provide a list of steps that will repeatedly reproduce the issue with TSI enabled?

@stuartcarnie I have attempted several times to reproduce the problem by running the same processes on a test instance.  Writing, dropping, writing forward again, doing a full series re-project etc etc to no avail.  The issue has to have something to do with time passing like compactions.
The best I can give you is that sample DB that I sent you?

@mmuller99 Are you essentially writing to the same measurement/series that you previously dropped?  You can get inconsistencies currently with concurrent write/deletes to the same measurement/series while a compaction runs to evict tombstones series.  That is a different root issue than what was occurring in this bug though.
We're still working on a fix for that.  If that is happening for you, some workarounds you could try for now are to:

Allow the shards that have deletes pending (noted by *.tombstone files in the shard) to compact.  They are usually scheduled fairly quickly, but depends on what else is going on in the system.
If you see inconsistencies, you can rebuild the tsi index manually.

@jwilder that is correct, due to our data changing historically.  Before we did the full clean re-project exercise, we did a manual rebuild of the index of all the shards, due to experiencing #9025. After the re-index the gaps were still present and with the release of 1.3.7 we decided to do the clean run.
Is there any way that I can see if the compactions have been done?
Thanks for the response

@mmuller99 You can look in the shards dir for *.tombstone files.  If they exist, the deletes have not fully compacted yet you could wait to write the data again.

@jwilder no tombstone files present
DB files.txt

@mmuller99 The workaround I'm suggesting is to avoid the index getting inconsistent.   If won't fix it if it's already inconsistent.   If it's inconsistent now, you would need to rebuild it manually.  To avoid the inconsistency, you could try:

Drop your series
Wait for compactions to complete (if there are no tombstone files) in the shard dirs, then they should have compacted.
Then re-insert data again.

If the issue is due to index inconsistency, this may help.

@jwilder thanks, will give it a go.  We have been re-projecting instantly after the drop.

This is still happening in 1.3.7 (non - tsi), different deployment and different time period than the original bug filing but otherwise the same.  An entire shard just disappears.


getWorkspace

Describe the bug
getWorkspace() not returning the workspace. Produces an error in the console.
To Reproduce
Steps to reproduce the behavior:
Following the example in https://github.com/thewuhxyz/wallet-adapter-svelte/tree/main/packages/example

in +layout.svelte I wrap my Code in , providing it {network} and {idl}
in the onMount function of +layout.svelte I call "getWorkspace()" imported from @thewuh/wallet-adapter-svelte-anchor and it displays this error in the console.

client:34 Error: Function called outside component initialization
at get_current_component (chunk-M244JQKM.js?v=0cfc5fa6:1265:33)
at getContext (chunk-M244JQKM.js?v=0cfc5fa6:1304:10)
at getWorkspace (@thewuh_wallet-adapter-svelte-anchor.js?v=0cfc5fa6:67:10)
at +layout.svelte:62:14
at run (chunk-M244JQKM.js?v=0cfc5fa6:53:10)
at Array.map ()
at chunk-M244JQKM.js?v=0cfc5fa6:2174:50
at flush (chunk-M244JQKM.js?v=0cfc5fa6:1371:9)
at init (chunk-M244JQKM.js?v=0cfc5fa6:2252:5)
at new Layout (+layout.svelte:62:26)
Expected behavior
I would like a reference to the workspace.

Yes. getWorkspace will not work outside <AnchorConnection> because the context is set inside AnchorConnection. Hence following the example, you can call getWorkspace anywhere but the root layout.


Death among stage transition?

Hi, I'm sorry to be like a debugger, but I still encounter a death among stage transition.
Not like #22 , but when the character reach to goal, it immediate started from stage 1.
Is the stage size is limited?
I encountered on stage 29 -> 30. (I think, not sure.)
My environment is macOS 10.14.3, v1.2 and played by myself

There is no stage 29 or 30... The max is 24.
If the character completes level 24, it restarts at level 0.

I confirmed.
thank you!


Abort method with message parameter does not render the message itself as told in the docs unless debug mode is set to true, or the request expects json

Laravel Version: 8.0.4
PHP Version: 7.4.7
Database Driver & Version: postgis/postgis:12-3.0-alpine

Description:
Running abort method with message parameter does not render the message itself as told in the docs unless debug mode is set to true, or the request expects json

HTTP Exceptions
Some exceptions describe HTTP error codes from the server. For example, this may be a "page not found" error (404), an "unauthorized error" (401) or even a developer generated 500 error. In order to generate such a response from anywhere in your application, you may use the abort helper:
abort(404);
The abort helper will immediately raise an exception which will be rendered by the exception handler. Optionally, you may provide the response text:

abort(403, 'Unauthorized action.');

Steps To Reproduce:
Use the following code in Authenticate middleware
<?php

namespace App\Http\Middleware;

use Illuminate\Auth\Middleware\Authenticate as Middleware;

class Authenticate extends Middleware
{
    /**
     * Get the path the user should be redirected to when they are not authenticated.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return string|null
     */
    protected function redirectTo($request)
    {
        abort(404, 'The page is missing');                                      // The page is missing will not render, we will get classic blade 404 Not found view
        abort(422, 'The data you passed are invalid');                          // This will render a 'The server returned a "422 Unprocessable Entity".'
        abort(500, 'Devs are running out of coffee to fix it, please wait');    // This will render a view with "500 Server error"
    }
}

Steps To Fix:
While this is not directly a bug, its a misleading documentation. Documentation should mention that the message parameters work only for json requests and customized messages are described in next paragraph. Either update the docs or include the message parameter in your default error templates.
Edit: while looking at 403 error message there is that line:
@section('message', __($exception->getMessage() ?: 'Forbidden'))
that works as I would personally thing any or these error blade files should work

We can fix the documentation. Can you submit a PR.


Feature Request: Allow files/directories to be ignored by Atom Helper process.

Summary
Create a way to exclude directories from the project index, maybe use .gitignore or allow files/directories to be manually selected.
I noticed a CPU usage spike from the Atom Helper process every time I loaded a Rails page. The page load caused updates to the ./log/development.log file along with updates to ./tmp/cache/assets/sprockets... Both of these directories (./log and ./tmp) are in my .gitignore. I was able to avoid the CPU usage spike by moving my log and tmp directories out of the Atom project directory. The CPU spike was caused by updates to files that I never open in atom, but lived in my project directory.
In some worst-case testing, I held cmd+shift+r on my rails page to constantly refresh the page. With rails writing to ./log and ./tmp, I observed an Atom Helper Energy impact of 55-60 (system power draw of 38.8w). With rails writing to directories outside of the Atom project, I observed an Atom Helper Energy impact of 0.1-0.4 (system power draw of 32.5w).

Thanks for the suggestion -

Create a way to exclude directories from the project index, maybe use .gitignore or allow files/directories to be manually selected.

Unless I'm misunderstanding what you're describing, you can already do this with Settings > Exclude VCS Ignored Paths, can you see if you have this setting enabled?  Also see Settings > Ignored Names.
Also, please fill out the entire issue template when opening issues - the information is super helpful for us when triaging issues.

Hey @rsese, thanks for pointing out those features. I do have both those directories added to my .gitignore (they are greyed out in my project tree view). The Exclude VCS Ignored Paths was already enabled, so that particular feature doesn't seem to resolve this issue. I also added *.log and *.cache to my Ignored Names list and I am still getting high  Atom Helper CPU usage (these changes seem to have no effect on the issue I'd like to resolve with this feature). Where can I find the source code for the Atom Helper process? Maybe I could poke around and see if I can find what is consuming these cycles.

Thanks for the response @rsese, I will work on filling out the rest of the template. Exclude VCS Ignored Paths was already checked, and the ./tmp and ./log directories are greyed out in the project tree view. I updated my Ignored Names pattern and still observed the same behavior (high Atom Helper CPU usage when log file is written to and when files are created/updated/deleted in ./tmp).
Where can I find the source code for the Atom Helper process? I'd like to poke around and better understand how it works. Thanks again for your response and help.

Doing some more research and I found that Rails creates/modifies 1700 tmp files when loading my webapp for the first time when tmp has been cleared. My guess is that there is some sort of a filesystem watcher getting 1700+ events and maybe that's what is causing the CPU spike?

@edgartheunready @rsese I can confirm having the exact same issue, a temporarily AtomHelper process trying to use 100% of the CPU. It's not solved with any configuration or by starting Atom in safe mode.

It happens with any page reload in the browser, when there has been some CSS change, which causes:

Rails sprocket needs to recompile the affected styles (Asset Pipeline).
Rails will create a bunch of files in tmp/cache/assets/sprockets (even tho that directory is my .gitignore, and I have atom configured to Exclude VCS Ignored Paths)

If I close the Atom project before the reload (even if left Atom app still open), then page reload goes way faster (I guess bc now the CPU can be fully used to compile the assets).
Some stats about tmp/cache/assets/sprockets: it has 13,387 files in 1,445 directories, ~ 46 MBs in size.

Page reload with Atom open & with assets precompilation/update takes around 22 secs.

Page reload with Atom open & with assets precompilation/update takes around 30 secs (and AtomHelper trying to scan every file in tmp/cache and using 100% of my CPU).

I need to confirm if this is also an issue in Linux, will do that this week and post here.
@rsese what kind of logs/info would help you guys to see what could be happening?

@chalofa, glad to hear that I'm not alone. I was able to work around the issue by changing the logger and moving the Sprockets tmp directory. Here's what I added to my development.rb
Rails.logger = Logger.new STDOUT
config.log_path = '/tmp/'

config.assets.configure do |env|
 env.cache = Sprockets::Cache::FileStore.new(
     File.join('/tmp/cache/assets'),
     config.assets.cache_limit,
     env.logger
 )
end

It does seem like Atom should be able to completely ignore a sub-directory. In the mean time, those changes will help reduce the load on your CPU.

Sorry I missed your initial followup @edgartheunready - so just to clarify, the issue is that the project you're working on and have open in Atom includes a temp directory where a large number (thousands) of files are created when you load a page in your app.  Then when this happens, there's a large CPU spike (and this is even when you have the temp directory specifically ignored)?

Exactly
On Tue, May 7, 2019, 7:04 PM Robert Sese<EMAIL_ADDRESS>wrote:

Sorry I missed your initial followup @edgartheunready
https://github.com/edgartheunready - so just to clarify, the issue is
that the project you're working on and have open in Atom includes a temp
directory where a large number (thousands) of files are created when you
load a page in your app. Then when this happens, there's a large CPU spike
(and this is even when you have the temp directory specifically ignored)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/19057#issuecomment-490285278, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA2XFMK3I7GOQ4SPDBTTN2TPUIDGTANCNFSM4HBO7L2A
.

... the project you're working on and have open in Atom includes a temp directory where a large number (thousands) of files are created when you load a page in your app. Then when this happens, there's a large CPU spike (and this is even when you have the temp directory specifically ignored)?

yes, and this is the default setup for every Rails app, so it's not something only a few of us are facing (every Rails dev using a Mac and with a "normal" amount of CSS code).
After taking a closer look, this only affects macOS, with both Windows & Linux versions working like a charm (not sure bc of the fact that it's the only platform release that has an Atom Helper.app to run async code, like files/directory changes).
I also found a workaround with an Atom config that will prevent this issue:
core.fileSystemWatcher: "atom"
(@edgartheunready can you help confirming if it also works for you?)
The default setting for fileSystemWatcher = native, which I tracked in Atom' source code to use NSFWNativeWatcher (a directory watcher) is implemented different in each OS, as stated by the creator of the nsfw package in the link below (TL/DR: macOS uses FSEvents, Linux uses inotify, while Windows has native support):
https://blog.axosoft.com/nsfw/
So, @rsese, I believe the issue with the default fileSystemWatcher setting (NSFWNativeWatcher) is located here:
https://github.com/atom/atom/blob/master/src/path-watcher.js#L282-L288
IMO, there should be some check that the normalizedPath is not in the VCS Ignored Files or Ignored Names settings, kind of what the tree-view plugin does to show/hide those:
https://github.com/atom/tree-view/blob/master/lib/directory.js#L185
Should we do some kind of very basic project that reproduces the error, but with a bash script creating/updating a bunch of tmp files, so you can reproduce it easier without having that dependency on Ruby/Rails?

@chalofa, I updated my config.cson as you described and it did resolve the issue with an Atom process consuming 100% CPU while files are being created.
Here's my config.cson:

After taking a closer look, this only affects macOS, with both Windows & Linux versions working like a charm

@edgartheunready are you on macOS as well?
And thanks for all the details @edgartheunready @chalofa - coincidentally, the team is looking at providing a new default file watcher system:
https://github.com/atom/atom/pull/19244
I'll ask the team about this issue but the fact that this is only an issue on macOS is interesting so I do wonder how the new file watcher system will affect things - maybe y'all would be willing to test things out when that work is available?

I am also on Mac OS using a 2016 mbp
On Thu, May 9, 2019, 5:05 PM Robert Sese<EMAIL_ADDRESS>wrote:

After taking a closer look, this only affects macOS, with both Windows &
Linux versions working like a charm
@edgartheunready https://github.com/edgartheunready are you on macOS as
well?
And thanks for all the details @edgartheunready
https://github.com/edgartheunready @chalofa https://github.com/chalofa

coincidentally, the team is looking at providing a new default file
watcher system:

#19244 https://github.com/atom/atom/pull/19244
I'll ask the team about this issue but the fact that this is only an issue
on macOS is interesting so I do wonder how the new file watcher system will
affect things - maybe y'all would be willing to test things out when that
work is available?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/19057#issuecomment-491065626, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA2XFMJITBEE5QW6CEN6GLLPUSG2VANCNFSM4HBO7L2A
.

... the team is looking at providing a new default file watcher system: #19244

thanks for pointing in that direction!
so, I just ran atom --dev using @nathansobo ns/notify branch, and the Experimental watcher "mitigates" the original Atom Helper high CPU usage, but it's still slower than the emulated atom watcher and now I see another process with high CPU usage temporarily: notify-subprocess-darwin

fileSystemWatcher performance with page reloads & compiling assets:

atom = ~18 seconds:

experimental = ~25 seconds:

native = ~22 seconds:

@nathansobo: After a few page reloads, the notify-subprocess-darwin just started using high CPU until I had to manually kill it (quitting Atom didn't work).
There was something weird with it when continually monitoring these huge amount of temporarily files (a lot of the directories are removed after every page reload):

Love the idea of this new experimental watcher, but seems like there's no reason to "watch" a VCS ignored path.

I'll ask the team about this issue but the fact that this is only an issue on macOS is interesting so I do wonder how the new file watcher system will affect things - maybe y'all would be willing to test things out when that work is available?

Of course!
Thanks for your time & help @rsese so far, it's been a great digging inside Aton's code


I am sharing '658683be-f381-47fc-bbae-a1c5c0b0bfb6' with you

I am closing the issue as spam


kenji test

Testing thread for a GitHub bot I'm making to assist with the development of Disploy.
Please ignore :)

@kenjixo test

a

a

kenji ping

kenji ping

kenji ping

kenji ping

kenji ping

kenji benchmark https://github.com/Disploy/disploy main

kenji benchmark https://github.com/Disploy/disploy main

kenji benchmark https://github.com/Disploy/disploy main

kenji benchmark https://github.com/Disploy/disploy main


ci: implement a nightlies GitHub Actions workflow

Implement a GitHb Actions workflow in .github/workflows/nightlies.yml named Nightlies, which is scheduled to run once daily at 00:00 UTC.
At present the workflow includes one job named release, which is responsible for publishing prerelease GitHub releases and NPM packages. Each prerelease created (per package) will have a nightly semver identifier, and each successive nightly release will be paired with the nightly dist-tag on the NPM registry (per package).
During the release job, actions taken in this GitHub repository (commits, tags, releases) and on the NPM registry (package publication) will be performed using credentials associated with the following accounts:

https://github.com/embarkbot
https://www.npmjs.com/~embarkbot

For that purpose, corresponding secrets (link requires admin access) were created in this repository consisting of API tokens generated for the @embarkbot GitHub and NPM accounts. Logins for the @embarkbot accounts themselves are protected by 2FA.
Implement scripts/nightly-release.js, which is responsible for running lerna publish. The nightly-release.js script borrows heavily from the existing scripts/release.js, and the process of authoring and experimenting with it influenced refactors to the latter.
Use a --force-publish prerelease strategy to prevent major-version drift between packages in the monorepo. How it works: when the Nightlies / release job is run, if there are no qualifying changes since the previous release (whether stable or nightly) then no prerelease is made. Changes to .md files or in directories that aren't part of the workspace (e.g. site/) are not qualifying changes. If there was any qualifying change, then all packages will get the same prerelease version bump. When a prerelease is graduated to a stable release, all the packages will be bumped to the same stable version since they were all in the same prerelease series.
The reason for adopting this strategy (a decision which can be revisited and changed any time in the future) is based on a concern that downstream users would have a confusing developer UX if across embark-* packages there are differing major versions.
To understand how the major-version drift would happen, consider the following hypothetical scenario where --force-publish isn't used in prereleases: assume the current stable version is 6.5.4. A breaking change lands for embark-core. The next nightly release bumps embark-core and about 40 other packages to 7.0.0-nightly.0. However, embark-utils (and others) isn't bumped because it doesn't depend on embark-core. Later, without any intervening changes to embark-utils, the prerelease is graduated so that embark-core, etc. bump to 7.0.0. So then some embark-* packages are at major version 7 while others are still at 6. Note that this is the case even though this monorepo uses Lerna's "fixed" versioning mode. Inside the monorepo, lerna makes sure that everything is okay, i.e. with respect to automatically updating dependents' version specifiers for their dependencies that are within the monorepo. But for downstream users things are a bit more complex. If someone wanted to use embark-utils on its own and specified ^7.0.0 as the version range (after observing that embark itself is in a 7.x series) it won't work because embark-utils is still in 6.x. In the general case, users may have to manually cross-check major versions of various embark-* packages that they specify in their projects' package.json files. There are tools like npm-check-updates that can make the task easier, but there is still likely to be some confusion, especially given the large and growing number of packages in this monorepo. Another area of confusion would exist around the nightly dist-tag. In the scenario above, prior to the stable release, embark-core@nightly (and/or @nightly of its dependents, e.g. embark) would resolve to 7.0.0-nightly.0 but embark-utils@nightly would resolve to some 6.5.4-nightly.N (:bomb:), i.e. a prerelease version that predates the current stable 6.5.4 release of embark-utils (and might not include all changes that landed in embark-utils prior to that stable release).
By bumping all packages each time there is a nightly release, the problems described above are avoided. However, there is a downside. Given the frequency of commits on master, there will be a nightly release on most weekdays. And there will be multiple stable releases throughout any given year. Let's estimate it amounts to 300 releases (pre + stable) per year. And there are presently about 80 packages in the monorepo. So that means there will be about 300 GitHub releases and 24,000 package publications per year, and a large number of "Version bump only" entries in the packages' individual CHANGELOG files. The --force-publish prerelease strategy also seems to go against the spirit of semver, at least somewhat, i.e. for any given package there will be a great many version bumps that correspond to no changes in that package.
To see the --force-publish prerelease strategy in action take a look at the commit history for the nightly-release-workflow-tester repo together with the Versions tab of the NPM pages for the foo, bar, and quux packages. The exact same GitHub Actions workflow and release scripts were implemented in that tester repo, with the workflow running every five minutes to facilitate experimentation.
Refactor the existing scripts/release.js to make it more flexible generally and with respect to options that can be forwarded to lerna. In particular, it's now possible to run lerna version instead of lerna publish (the default behavior) by using the --version-only cli option; when combining that usage with --skip-qa and --no-push it's possible to conveniently and quickly experiment with the bump positional and additional options such as --force-publish, --conventional-prerelease, and --conventional-graduate, i.e. to better understand how lerna will update package versions. That ability should make it much simpler to figure out the best course of action to take locally (manually) when a nightly release completely or partially failed (which could happen for a number of reasons), as well for other scenarios such as making a minor/patch release in a previous line of major releases, or when making two/more successive stable releases without a nightly release having happened in the meantime.
An important change to scripts/release.js is that by default it makes use of the --create-release github option for lerna version|publish. For that to work, an environment variable named GH_TOKEN must be defined with a properly scoped GitHub personal access token (public_repo scope is sufficient for creating releases).
Delete the .github/PULL_REQUEST_TEMPLATE directory and the templates it contained. Unlike for GitHub issue creation, there is no prompt-page for picking from a repo's PR templates; to use a PR template a template=[name] query parameter must be appended to the URL of the PR creation page. So the PR templates ended up unused by the Embark Team and external contributors because it's not convenient to use them. Restore the default PR template we had in place some time ago (with some small revisions) since it seems like a helpful starting point, especially for external contributors. Consistently use all lowercase filenames for ISSUE/PR templates.

Made a few small improvements to the wording of the commit message (also re-copied into PR description) and fixed a spelling mistake. There were no changes to the code in my force pushed commit.


Ratings: Connect Frontend and Backend

Definition of Done - Check as you go!

[ ] Tasks have been implemented
[ ] Documented
[ ] Passing Tests for each task
[ ] Pull Request made
[ ] Code Reviewed

162_Bestagons.txt


Feature/api automation cucumber

Closed in favor of this https://github.com/opensrp/hapi-fhir-jpaserver-starter/pull/22


Add option to disable moderation notifications without disabling moderation entirely

Is your proposal related to a problem?
In our CMS, certain pages are related to a Region model, and moderators are assigned to one or more Regions at a time (this can change dynamically). When a page is submitted for moderation, we'd like to send out a notification email only to the moderators assigned to that page's Region at the time. Wagtail's built-in notification system sends emails out to all moderators with publish access to the page in question, which includes users not assigned to that page's Region.
Describe the solution you'd like
We've built our own notification system that listens on the workflow_submitted signal to handle sending of notifications to the relevant moderators, but we'd like to disable the built-in Wagtail notifications to prevent duplicate emails while still keeping moderation enabled.
Ideally this would be a setting like WAGTAIL_SEND_MODERATION_NOTIFICATIONS or something to that effect.
Describe alternatives you've considered
Using the built-in notification was considered but given the context described above was deemed unsuitable for our approach. Changing the design of the CMS to ensure that only moderators in Region X have publish permission on pages in Region X would require an overhaul of the entire CMS which is quite large and already running in a production environment, and in any case does not fit our use case as this introduces new and unnecessary restrictions to the moderators.
If there are any alternative approaches that might work for our use case without this feature then I would be glad to consider them. However I feel that even so this would be a useful feature for Wagtail to incorporate.

I'm pretty sure it should be possible to do this within the existing custom workflow support, but happy to reopen if it turns out there are requirements that aren't covered there.


Support for @Id

In Schema markup, there is an important attribute (if not the most important one), to support @Id for entities.
In webpages, mostly the @Id attribute is set to the URL (i.e. "https://example.com/about-us/") or URL derived from the web page's URL, such as "https://example.com/#organization"
I tried to set value in the front matter to {url}, which did not work. Is there a way that is not obvious? If so it would be great to document it.

P.S.: @Id is a very important attribute, so one can assemble schema from different pieces and amend schema defined in the header also in the body (affording the power of templating)

Interesting! I didn't know about that feature, so I've been reading more here: https://schema.org/docs/datamodel.html#identifierBg
I'll add this to the next release

An implementation note:

the URIs used as IDs are supposed to be http:// not https://
technically it is possible to use https, but the norm is http
that implies if one can utilize the url or base url as part of the value it should allow exchange of the scheme

See url_for in Flask framework for how this is supported there.


Visual Studio 2019 Support

Is there any indication of the progress on this? Google Cloud tools are something I use on a daily basis. Very excited and interested to get any indication of progress.

Same question. Any progress?

Checked the issue with GCP support, but they could not produce an anwer..

Thank you all for the feedback and interest, we currently a little short on resources but will try and get to this soon.  I will follow up shortly when I have a better answer, thank you for your patience!

Thank you all for the feedback and interest, we currently a little short on resources but will try and get to this soon. I will follow up shortly when I have a better answer, thank you for your patience!

Thanks for the feedback! I appreciate it a lot. Right now I am bouncing between VS 2017 and VS 2019 mainly because of this missing feature, and it would be great to go full on VS 2019.

Any updates on this? I noticed several commits were made yesterday in regards to fixes for VS2019. I tried the latest release via the appveyor seeing if maybe it was all fixed now, but it didn't work.

@creativeavatar We are currently working on this but are a little short handed, hopefully we will get something out the door soon.

Any updates on that?
Trying the method on https://devblogs.microsoft.com/visualstudio/how-to-upgrade-extensions-to-support-visual-studio-2019/ doesn't seem to work.
Using the Extension Manager 2017 / 2019 https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ExtensionManager2019 also doesn't seem to work.
I´ve never tried to manipulate VS Extensions before, so maybe I´m overlooking another possibility?

@s-richter I sent a PR to fix the project for Visual Studio 2017/2019 and after that, I can debug the extension within 2019.
Do you want to check the artifact built from my PR to see if it works on your Visual Studio 2019 and report back?

The latest release (2.0.3) now supports VS 2019.


Old enrolment options should be purged/anonymized

At activities, extra enrolments options can be added, like food, allergies or other questions/checks. Some of these enrolment options are personal data (i.e. allergies). Now, there are stored indefinitely, but they should be removed or anonymized after a certain period

Probably the best way to do this is to have a page where all activities that have not been anonymized are listed where board members can select activities that need to be anonymized. (Check if an activity is anonymized can be a simple boolean field in the activity).
Only enrollment options need to be removed or anonymized. Options which cost money cannot be deleted as it would change the personal tab balance, so for those the option itself needs to be anonymized to (Option 1, Option 2, etc.).


Navigation code behind not quite minimal

The navigation 'next' and 'previous' command handlers require further work since it is possible to navigate off the beginning and off the end of the data using them.

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

ID: 42c0fa43-0ca5-9c86-f8c4-4b3eb7176250
Version Independent ID: bb93e3ff-0d52-9e93-c3a8-545b16f03a30
Content: Create a simple data application with WPF and Entity Framework 6 - Visual Studio
Content Source: docs/data-tools/create-a-simple-data-application-with-wpf-and-entity-framework-6.md
Product: visual-studio-dev15
GitHub Login: @gewarren
Microsoft Alias: gewarren

@OldVSDeveloper Okay, thanks for the clarification that the article needs to be updated.

I suggest if you were to update the article, standard CRUD functionality should be addressed, including the situation where a customer has no orders, none of the customers have any orders  and where there are no customers and no orders (eg when the underlying database has just been created)

I have found this example immensely helpful in learning C#/WPF/EF6.
Recently I added TextChanged and SelectedDateChanged events which did some arithmetic that failed when I paged outside of my record set.  I paged outside the recordset because the tests  IsCurrentBeforeFirst and IsCurrentAfterLast are applied after you are out-of-bounds.
My solution is as follows.
`        private void NextOrgUnitAssetRskCommandHandler(object sender, ExecutedRoutedEventArgs e)               //Next record
{
numberOfOrgUnitAssetRskRecords = orgUnitAssetRskViewSource.View.SourceCollection.Cast().Count();    //  Count the records in the view.
if ((numberOfOrgUnitAssetRskRecords - 1) > orgUnitAssetRskViewSource.View.CurrentPosition)        //  Subtract 1 to compensate for zero-based CurrentPosition.
{
orgUnitAssetRskViewSource.View.MoveCurrentToNext();
selectedRecordPosition = orgUnitAssetRskViewSource.View.CurrentPosition;
}
}
    private void PreviousOrgUnitAssetRskCommandHandler(object sender, ExecutedRoutedEventArgs e)           //Previous record
    {
        if ((0) < orgUnitAssetRskViewSource.View.CurrentPosition)        //  0 to compensate for zero-based CurrentPosition.
        {
            orgUnitAssetRskViewSource.View.MoveCurrentToPrevious();
            selectedRecordPosition = orgUnitAssetRskViewSource.View.CurrentPosition;
        }
    }

`
Probably not very elegant but I'm struggling to get on top of this stuff.

I have found this application immensely helpful in learning WPF/EF6.  It is the best pattern I have been able to find.
Paging back and forward through the viewsource needs to be controlled to prevent the user paging out of bounds and executing SelectedDateChanged and TextChanged events with spurious data lurking outside the bounds of the viewsource..
Nevertheless a very valuable learning aid.

This topic gets about 7000 page views per month.

Well! Obviously the said article needs to be updated, it's worthy for sure!
However, while starting learning WPF with the same, came across to note that while I am debugging the same and the app is in running, at the same time if I change any value of a Northwind's table (via SSMS or Access Front-End) the WPF doesn't reflect the updated data via custViewSource.View.Refresh();
How to overcome this with an event like timer or a button click any other event?


Location of credentials should be configurable

Right now the only way we can pass in the credentials is by setting the appropriate environment variables. It would be better this was not hardcoded.

Edsko de Vries<EMAIL_ADDRESS>writes:

Right now the only way we can pass in the credentials is by setting
the appropriate environment variables. It would be better this was not
hardcoded.

Great point. Fix coming.

Fixed with toS3' and fromS3'


feat: Make documentation on hover configurable

This also implements deprecation support for config options as this renames hoverActions_linksInHover to hover_linksInHover.
Fixes #9232

I'll clean this up in a follow up then as this is big enough as is
bors r+

bors r-

Just to double check, are you sure we need deprecated functionality here? https://github.com/rust-analyzer/rust-analyzer/pull/9264#discussion_r655370227

Oh sorry I didnt see that actually

bors r+

bors r+


Solved issue #56 adding support on UIBarButtonItem on iPad

To support UIBarButtonItem on iPad, I needed to pass the sender object in the FDTakeController class so I have added this three methods in order to pass it:

(void)takePhotoOrChooseFromLibrary:(id)sender;
(void)takeVideoOrChooseFromLibrary:(id)sender;
(void)takePhotoOrVideoOrChooseFromLibrary:(id)sender;

FDTake still works the same as before with the corresponding methods without the sender.

Does this solution work for everyone else?

This solution simply solves the issue: it adds support for UIBarButtonItem on iPad. If you use an UIButton the UIActionSheet continues to appear in the left top corner.
Furthermore the behavior on iPhone does not change.


Code Cleanup

Remove all the console logs, shift each part of the App.tsx to a file Components/[name].tsx
I have properly commented it for example:

They all look cluttered in one page app.tsx so having a component based folder structure will help a lpt

Opened a pull request solving this issue #12


Add cartesian coordinate system in schwarzschild.py

Currently the module is only accepting spherical coordinates.
It would be better if there is an option of using cartesian coordinates.
New Classmethod : Schwarzschild.from_cartesian()

Adding necessary functions in utils to support the functionality.
See #44

#47. Added support to input cartesian coordinates in any units and return in SI units


Population growth and Taylor series

DP/dt = f(P)
f(0)=0.  Then first term is positive (if growth from small values exists) and assuming competition is next effect, the quadratic term must be negative.

Let us assume that $dP/dt = f(P)$ where $P$ is the size of a population.
Making reasonable assumptions about birth/death, when $P=0$, $dP/dt=0$, so $f(0)=0$.
Then if we expand $f$ as a Taylor Series, at linear order we have $P’=aP$.  This yields exponential growth.  As things grow exponentially, at some point the next term in the Taylor series shows up.
how do we interpret this biologically?  At small population size individuals are basically on their own and reproducing or dying without being affected by crowding.  However, as the density of individuals increases, they start to interact with one another.  In many biological situations, this would suggest that they are competing for resources.  So we would expect the interaction to have a negative impact.  So we expect something like $P’=aP - b P^2$ where $a$ and $b$ are positive


Resource property for enabling/disabling the ArcGIS Server service directory

Created this since I did not see this specific task in any existing resources.
Resource Usage:
Import-Module -Name ArcGIS
Import-DscResource -Name ArcGIS_Server_ServiceDir

ArcGIS_Server_ServiceDir disableServiceDir {
	Enabled = $false
	SiteName = 'arcgis'
	SiteAdministrator = $psaCredential
}

Lets move this resource functionality into the ArcGIS_Server resource as an additional boolean property.  Also dbl. check the file encoding. github detects as binary.  This can be fixed using .gitattributes

I will make this change. Any issue with the property name ServicesDirectoryEnabled?

the name is fine

@shailesh91  .. plz merge when convenient

@shailesh91 Fixed encoding as requested.

@shailesh91 Looks like this commit is missing at v2.0-dev release. Will it be added back at full release?

@PleaseStopAsking this commit was missed in the release I will create a PR soon to add this back.


Cannot configure multiple TLS certificates

I have multiple domains resolving to my Nginx server and I configured BounceBack to proxy to the Nginx server. But it doesn't support configuring multiple TLS certificates.

As I understood you have next architecture:
BounceBack (listening on one port for example.com and secondexample.com) -> Nginx -> your application.
If I'm wrong, please correct me.
As a solution you may use something like:
Nginx (listening on one port for example.com and secondexample.com and adding X-Forwarded-For header) -> BounceBack (with or without cert, no cense) -> your application.
My solution also will fix JA3S fingerprinting of golang server.
I'll mark your request as a feature request and later add support of multiple TLS certificates.

Yes,your understanding is correct. I'll try your solution and test if it meets my needs. Thank you very much for adding this feature.

Please, let me know, if my solution works for you.

Please, let me know, if my solution works for you.

Your solution works functionally, but there are still some issues. BounceBack is located  behind Nginx, then the Nginx server and the applications behind it are out of protection. Although my Nginx server has some restrictions,it still can't guarantee some unwanted traffic to access the Nginx and the application server.

BounceBack can fully work behind the nginx or any other reverse proxy (however, for IP and GEO filters you need to add X-Forwarded-For header on reverse proxy).
Please provide a more detailed example with nginx configuration and application you want to protect (if it possible).
Also, please provide some additional info:

What filter(s) does not work (for you)
How its intended to work (for you)
BounceBack configuration file
Any access/error logs if needed
Any other information that may help me understand your issues

Without understanding what is not working for you, I can't give you any advice/fix.

BounceBack can fully work behind the nginx or any other reverse proxy (however, for IP and GEO filters you need to add X-Forwarded-For header on reverse proxy).
Please provide a more detailed example with nginx configuration and application you want to protect (if it possible).
Also, please provide some additional info:

What filter(s) does not work (for you)
How its intended to work (for you)
BounceBack configuration file
Any access/error logs if needed
Any other information that may help me understand your issues

Without understanding what is not working for your updated setup, I can't give you any advice/fix.

My bad, this solution worked for me. I made a small mistake.

Add multiple TLS certificates support for single proxy. Documentation was updated and can be found here.
Thank you for your feature request. Closing issue.


Add Base Construction

can someone tell me why it doesn't merge? to fix it

Thanks, closing in favor of #1745, which fixes the command bumps the spec to v1.2 which is required to support subdirectories in an install_to property.

thanks


docs(book): remote ExEx chapter

Ref https://github.com/paradigmxyz/reth/pull/8890

Found this in mdBook for including files, maybe we could use it:
https://rust-lang.github.io/mdBook/format/mdbook.html#including-files

@Rjected yeah nice, I think we can have several intermediate .rs files and a final one that we'll compile as part of examples, and then include them in the book using {{#include file.rs}}

Hmm, we moved this example to a separate repo to get rid of a dependency on protoc, so there's no way to do the include now I'm afraid. Unless we want to clone this repo into the book dir in CI and include the code from there.

makes sense


[TableFooter] Fix adjustForCheckbox rendering

[ ] PR has tests / docs demo, and is linted.
[ ]  Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[ ] Description explains the issue / use-case resolved, and auto-closes the related issue(s)

Description
In the TableFooter, in the render function, having newDescendants as void 0 was breaking the cloneElement method of React.  I instead made it so that the newDescendants are always created but the cloneElement function is conditionally given newDescendants based on the adjustForCheckbox bool.
Before and after shots:

Wrong branch - please resubmit on master.


What are the future usage scenarios?  Will more aliasing scenarios for documents be added?

Not sure about the above user, but I personally would love to be able to choose to track other headings. As an example, all ## headings could be tracked, or both # and ### maybe.

@firinael Could you elaborate on the behavior you'd like?
Let's look at this as an example.
<!-- 2022-06-28-1104.md -->

# Garden
## Plants
### Squash
### Lettuce
## Insects
### Friends
### Foes

In the current behavior, the link suggestion would be [[2022-06-28-1104|Garden]]. Changing # Garden to # House garden would adjust the subheading link of [[2022-06-28-1104#Squash|Garden]] to [[2022-06-28-1104#Squash|House garden]].
Are you wanting to change ### Squash to ### Zucchini, and therefore want the link [[2022-06-28-1104#Squash|Garden]] to change to [[2022-06-28-1104#Zucchini|Garden]]?
Or is there a different behavior you want?

My notes use the title format YYYYMMDDHHMM This is a title
Is there a way for the plugin to generate an alias YYYYMMDDHHMM for the note?

It would be really good if the plugin can link to any and all headers. Complementer plugin suggests the titles of notes as suggestions when you are typing your content to backlink to. It would be awesome if the suggestions include the headers as well.
Use case scenario:
I put each concept under a same topic into separate headers. i.e. the topic is the title and each concept is a header. So if I'm writing about a new concept, I want suggestions to backlink to previous headers/concepts.


unixODBC connection failed after upgrade to 18.5.1

Clickhouse failed to connect to unixODBC datasource after upgrade from 18.1.0 to 18.5.1
Exception: Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = Connection attempt failed: Connection:Not applicable
Server:Not applicable
===========================
ODBC Diagnostic record #1:
===========================
SQLSTATE = IM002
Native Error Code = 0
[unixODBC][Driver Manager]Data source name not found, and no default driver specified

odbc.ini
[DEFAULT]
Driver = staffcop
[staffcop]
Description         = PostgreSQL connection to staffcop
Driver              = PostgreSQL Unicode
Database            = staffcop
Servername          = <IP_ADDRESS>
UserName            = staffcop
Password            = ***
Port                = 5432
Protocol            = 9.3
ReadOnly            = No
RowVersioning       = No
ShowSystemTables    = No
ConnSettings        =

/etc/clickhouse-server/filters_dictionary.xml
<yandex>
<dictionary>

<name>analytics_filter</name>
<source>
  <odbc>

analytics_filter

      <connection_string>DSN=staffcop</connection_string>
  </odbc>
</source>
<lifetime>
  <min>300</min>
  <max>360</max>
</lifetime>
<layout>
         <flat/>
          </layout>
          <structure>
                 <id>

                   <name>id</name>
                  </id>
                  <attribute>
                          <name>name_en</name>
                          <type>String</type>
                          <null_value></null_value>
                  </attribute>
                  <attribute>
                          <name>name_ru</name>
                          <type>String</type>
                          <null_value></null_value>
                  </attribute>
                  <attribute>
                          <name>category</name>
                          <type>String</type>
                          <null_value></null_value>
                  </attribute>
          </structure>
</dictionary>
</yandex>

OS: Ubuntu 16.04
Downgrade to 18.1.0 resolved this problem.

Can confirm I see this problem in 18.6 as well, and downgrading to 18.1.0 fixes it.
After some testing, I didn't have to downgrade all the way to 18.1.0; downgrading to 18.5.1 was enough.
I'm using the Docker images, so it's possible that 18.5.1 and 18.6 use different base images, so may have different versions of unixODBC, etc., although I haven't tested that.

We have added filtering of ODBC connection string (for security reasons, to disallow custom user specified path to .so etc), but it appeared to be overly aggressive. https://github.com/yandex/ClickHouse/pull/2772
For example, it wraps all parameter values to {} (example: Database={test}) but drivers don't understand that.
Then it was relaxed again. Now it should work fine in master, but there is no release yet.

According to git log, it is not in 18.5.1. Minimum version with regression is 18.6.0.

Version 18.10.3 should have this issue fixed.


Ip per container

Current coverage is 43.61% (diff: 55.11%)

Merging #67 into master will increase coverage by 0.09%

@@             master        #67   diff @@
==========================================
  Files            33         33
  Lines         10184      10341   +157
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           4432       4510    +78
- Misses         4728       4775    +47
- Partials       1024       1056    +32

Powered by Codecov. Last update 6bda95c...8929de3

LGTM   But is strange of  network named 'swan'

ping @pwzgorilla


Add Support to iOS 12 in MediaCapabilities polyfill

Maybe related to: #3530
Note: In iOS, since there is no support for MediaSource, if the type is 'media-source' it always returns false, but if the type is 'file' it is checked whether it is supported or not.
MediaCapabilities support: https://caniuse.com/mdn-api_mediacapabilities

@michellezhuogg can you review it?


[WIP]Create style json plugin

Resolves #959 Add a plugin that could transfer style json to Layer/Source object.

This plugin is on hold while we do some customer discovery of this feature on the core side first.

https://github.com/mapbox/mapbox-gl-native/issues/13467

cc @chloekraw


add: AlienMonk

Description
[Include a brief description of the changes you've made]
Related Issues
[Include any related issues or pull requests that this PR addresses or is related to. Use GitHub's shorthand syntax to link to them, like #1234.]
Changes Proposed
[Describe the changes you've made in detail. Be specific and include any relevant code snippets.]
Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@AlienMonk Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and help us grow even further!


support co-process

use coproc keyword

expose input/output file descriptor as UnixFD object

'coproc' returns Job object

add job object, in commit c57d12164a393e32249ce109728c42a1fd9e58b

add basic support in commit 75b14f08043486079eb25e22ce053971807967d9


Allow multiple blob_dir

A user said he would love to host more, but it's not easy for him to move to other/external hd.
This would allow users to host more content.

user can add additional blob_dir folders, mark default (like steam)
support freely moving blobs between blob_dir locations
handle disconnection of a blob_dir folder (external HD?) - mark db entries temporarily missing?

Add support to S3 buckets mayby :)

first version:

specify new folder (first of the list in the conf file)
if we have permissions and everything is good, use it
otherwise, warn and fallback to next
fails startup if all items fail

for now, moving blobs: stop sdk, move, start (we check on startup already)
Handling disconnection of a blob directory might be another issue as it can already happen if the current directory is an external drive. Not sure what to do here yet


Add support for mutable-content

This should support the new apns2 feature to have mutable content.
https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ModifyingNotifications.html

Good, thanks!


tstpassed() and tstfailed() wrong arguments

tstpassed() and tstfailed() are wrongly defined to take a char * as a parameter.
They should take no argument!.

Fixed on 0.3.1.

Fixed on 0.3.1-final


chore(dependabot): try to ignore some directories

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
https://github.com/dependabot/dependabot-core/issues/4364#issuecomment-2002406602
https://github.com/risingwavelabs/risingwave/pull/16101#discussion_r1548916995

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Why "try try"? 😄


Mistral AI Support

Describe the need of your request
It would be great if Mistral AI API would be supported: https://docs.mistral.ai/api/
Proposed solution
No response
Additional context
No response

The linked API indicates that it has at least the /v1/chat/completions endpoint. It should work with the Custom OpenAI service that was recently released. Are you able to test if that is the case?


Mark empty listings for optional hiding, per variation or globally

Add class name 'emptyListing' to listing body content and listing body header if no results.

@ksuess sorry for the delay!