End of the session

Hi! Is there any method to know when does a session end?
Especially for qualifying sessions, just wanted to know at what time of the session does the chequered flag appeared.
(it is to know if a driver crossed the line on time and by how much)
Thanks

Yes, there is. There is an api method for that in fastf1.api. See the docs here: https://theoehrly.github.io/Fast-F1/api.html#fastf1.api.session_status_data
You should be able to get the information you want from the data that it returns.
The function requires a parameter api_path. You can get that from a Session object. Therefore, you first create a session by calling get_session and then you can call fastf1.api.session_status_data(session.api_path).
Is that what you are looking for?

thanks for the reply! That's exactly what I was looking for. By the way, how accurate is this data?(That microseconds are right?)

Good question, but I'm sorry to say that I don't know for sure. I can just make assumptions there.
In short, I don't think the milliseconds are correct.
If you check start and end of a qualifying round, then you can see that the session would sometimes be close to half a tenth of a second shorter than the official length.
Now, the actual timing system at the track needs to be very capable, and I'm fairly sure that a session is exactly as long as it should be.
I do think that those timestamps denote the time at which their (way less critical) server system processed this event. I do know for sure that the same timestamps for laps are not accurate (lap start and end time). After all, it is not actually relevant, the way that they're presenting this data in the app.
I do optimize the laps timestamps as much as possible. But I can only minimize random jitter. There might be a constant offset by which all laps timestamps are off. I don't know, because I haven't yet found a good reference to compare that against.
And just to make this clear, the length of a lap, i.e. the lap time and sector times are 100% accurate. Those are the only data that I fully trust and I try to use it as much as possible to correct the timestamps for example.
If you have the time and motivation, you should try to find some reference and evaluate how accurate this is. I'd actually be very interested in the result.

Thanks again. Of course I would try to dig into it. But I don't know why the t0_date function always returns "none"
print(fastf1.get_session('2021','Spanish Grand Prix','Q').t0_date)
Am I doing something wrong?

No, not your fault. That's just badly documented, actually. You need to load laps with telemetry so that the t0_date can be calculated. The telemetry data is required for that, as inconvenient as it is.

Ok thanks. The problem of that is that telemetry is just available from 2018, isn't it? I was trying to search more in historical races and those things

Yes, correct. Unfortunately, there is no data earlier than the 2018 season

What I'm guessing is that the timestamps provided by the api are not created by the official timing system. I suppose they maybe are created when their api server processes the event. And there is no focus put on having them be fully accurate.
I do wish that all timestamps were accurate to the millisecond and that all data is perfectly synchronized. But it is just not possible. For lap start and end times a lot of effort is made to correct inaccuracies.
The session_status_data and track_status_data timestamps are not modified though. They are used exactly as they are received from the api. And I don't really see a way to make them more accurate.
I do find it curious that a race is always 220ms too long. 220ms is also the sample rate of the position data. Maybe this is just the interval at which their server processes events. And the end of the session is somehow processed one cycle too late.
Have you summed up the lap times of one drive for comparison? Does that match what they display on TV as the duration of the race?

@hash55 sorry for responding incredibly late. I needed to actually take some time to write a proper answer here. Anyway, synchronizing the data is a very interesting topic. But it is made difficult by our lack of data, accuracy and knowledge about the data.
First, do you know how close Gasly was (approximately) to not starting the lap in time? How far off is the timing of FastF1?
Second, I have previously tried various approaches to synchronize the telemetry data.
One approach was to use the finish line speed trap as a reference point. While this did work in principle, it did not work better  (see: https://www.f1technical.net/forum/viewtopic.php?p=919051#p919051).
The other method I tried was to synchronize the lap time to the finish line position (and sector position). The problem here is that we don't know the position of the finish line. The only assumption that can be made is, that the position stays the same.
What I did was to introduce a time offset at the beginning of all laps as a variable. The coordinates of the finish line crossing should be the same again every lap when adding the subsequent lap times. In theory, there should be one specific correct offset for which the finish line is in exactly the same place every lap. But you would expect the position to vary slightly for all other offsets. Therefore, this is a minimization problem with one dependent variable.
This approach did work in principle, too. But there was no one clear solution. The result was a range of coordinates for which the position jitter was close to zero, but not fully zero. That range was too wide to make any useful conclusions.
I did put this down to various issues. Among others, the low sample rate of the data. I also assumed that the car's internal clocks are not synchronized. This has now been confirmed by the AWS blog post that you have linked to.
With this additional uncertainty, there are now ten additional dependent variables to solve for, assuming that teams synchronize the clocks between their own cars. In theory, we have way more data than required to solve this problem. But the low sample rate (and potentially other things) introduce uncertainty to the data. Even in the AWS post, they describe how they calculate the reaction time of a driver as the median of a distribution of results.
I don't want to say that it is not possible, but exploring how feasible and accurate this is requires a lot of time.
Also, there may be other possibilities for synchronizing the data.
As an additional problem, we don't know if the timestamps we get are actually the ones created by the cars' on-board computer. Maybe they're generated by the API server when processing the data?
With regard to all these problems, there is currently no active synchronization of the data done. Only the lap start and end times are adjusted to match the lap times. But if we could actually synchronize the data properly, this would be much better.


CFE ES "StartupSyncSemaphore" subject to multiple race conditions

The "Startup Sync" mechanisms are based on a binary semaphore, a boolean flag, and a counter.
The handling of these various separate entities leaves several opportunities for race conditions to occur. At a minimum, this could cause "WaitForStarupSync" to pend incorrectly, but could have other more serious side effects (unknown) depending on how the apps are using this.
This is one problem that the EVA team at GRC are experiencing while deploying CFS on the Xilinx Microblaze platform.

Trac comment by jphickey on 2015-05-07 12:11:04:
The fundamental issue here is that the conditions are checked under the CFE_ES global data lock, but when the decision is made to pend on the semaphore, there is no way to atomically release the lock AND pend on the semaphore.
There is an opportunity after releasing the lock but before actually pending on the semaphore for the conditions to change.
Simply put, an OSAL binary semaphore is not going to reliably work here.
Although it is not as desirable, the best way to do this may be to simply poll for it, calling OS_TaskDelay so that the other threads can execute while waiting.  It is not ideal, but it will work and will not be subject to the issues of trying to have many tasks pending on the same event.
A correct pend-and-release operation that the startup sync is //trying// to do would require the equivalent of a POSIX condition variable, which OSAL does not expose or have an API for.

Imported from trac issue 40.  Created by jphickey on 2015-05-06T15:43:00, last modified: 2016-08-11T15:53:15

Trac comment by jphickey on 2015-05-08 13:33:11:
Pushed commit [changeset:2633a3d] for review
This modifies the CFE_ES_WaitForStartupSync() to use a simpler polling loop (with delay) rather than a semaphore.  This may cause some extra scheduling delays as the waiting tasks will be performing a delay rather than pending on a semaphore, but it will be reliable.  Any such delays will be confined to start up, and typically less than 50ms (the delay time), so it should not be a major problem.
This also adds calls into WaitForStartupSync from the core applications which was not done before.  This forces each core app to reach its respective main loop before the next core app will be started, regardless of what the platform has the priority set to.  This is really part of the fixes for trac #73, but it did not make sense to split it from this one as they depend on each other.

Trac comment by sstrege on 2015-05-15 15:15:36:
Recommend making the CFE_ES_STARTUP_SYNC_POLL_MSEC macro a configuration parameter.  This will provide some flexibility as processors are getting faster.

Trac comment by sstrege on 2015-05-15 15:37:48:
It appears the CFE_ES_ApplicationSyncDelay function will force the applications to delay for CFE_ES_STARTUP_SYNC_POLL_MSEC vs. the time the application specifies when making the call to CFE_ES_WaitForStartupSync.  This will make the application XX_STARTUP_SYNC_TIMEOUT configuration parameters obsolete.

Trac comment by sstrege on 2015-05-15 15:59:14:
Recommend changing the name of the CFE_ES_SYSTEM_STATE_APP_STARTUP macro to CFE_ES_SYSTEM_STATE_COREAPP_STARTUP or CFE_ES_SYSTEM_STATE_CORE_STARTUP.
This will make the source code more readable without having to reference the comments in es_apps.h.  On a fist look at the code the name of this macro was a little confusing as to whether the core applications were being started in this system state, the external applications, or both.

Trac comment by jphickey on 2015-05-15 15:50:39:
The total delay done by CFE_ES_ApplicationSyncDelay() still depends on the "TimeOutMilliseconds" parameter.
CFE_ES_ApplicationSyncDelay() calls OS_TaskDelay() in a loop, it just uses a shorter interval for polling - this is the CFE_ES_STARTUP_SYNC_POLL_MSEC value.  It will poll/delay repeatedly until the XX_STARTUP_SYNC_TIMEOUT is reached.
Note that this does suffer from the delay-extension problem, where scheduling delays are not factored into the delay calculation thereby extending it by some unknown quantity.  As this is confined to start-up, I don't expect that will matter in this case.

Trac comment by sstrege on 2015-05-15 16:10:24:
Also recommend making the CFE_ES_STARTUP_SCRIPT_TIMEOUT_MSEC a configuration parameter.

Trac comment by sstrege on 2015-05-15 16:23:58:
What is the rational for placing CFE_CORE_MAX_STARTUP_TIME in the private header file vs. the platform configuration header file?

Trac comment by sstrege on 2015-05-15 16:22:07:
Replying to [comment:6 jphickey]:

The total delay done by CFE_ES_ApplicationSyncDelay() still depends on the "TimeOutMilliseconds" parameter.
CFE_ES_ApplicationSyncDelay() calls OS_TaskDelay() in a loop, it just uses a shorter interval for polling - this is the CFE_ES_STARTUP_SYNC_POLL_MSEC value.  It will poll/delay repeatedly until the XX_STARTUP_SYNC_TIMEOUT is reached.
Note that this does suffer from the delay-extension problem, where scheduling delays are not factored into the delay calculation thereby extending it by some unknown quantity.  As this is confined to start-up, I don't expect that will matter in this case.

OK, yes, I see that now.  If all are OK with the "crude" timing, it would be worthwhile putting in a ticket to address the TBD in the future.

Trac comment by jphickey on 2015-05-15 16:26:42:
Regarding the CFE_ES_SYSTEM_STATE_APP_STARTUP -> CFE_ES_SYSTEM_STATE_CORE_STARTUP name change - I agree with this, will do that.
For the configuration parameters CFE_ES_STARTUP_SYNC_POLL_MSEC, CFE_CORE_MAX_STARTUP_TIME, and CFE_ES_STARTUP_SCRIPT_TIMEOUT_MSEC, we can make these platform config parameters, but this means that anyone who pulls in this changeset will need to also update their cfe_platform_cfg.h file accordingly or their build will break.
By putting these where they are now, it does not require any updates to cfe_platform_cfg.h
That is the only trade-off. If this is acceptable then I can take these defines out of the current spot and move them all into the platform config.

Trac comment by jphickey on 2015-05-15 17:13:25:
Replying to [comment:12 dheater]:

In cfe_es_start.c; It looks to me like CFE_ES_ApplicationSyncDelay will '''always''' return when there is a timeout. Even if you have not achieved the minimum system state. It is called from line 293 and the subsequent lines seem to assume that the core startup has completed although that condition is not confirmed.

CFE_ES_ApplicationSyncDelay() will return CFE_ES_OPERATION_TIMED_OUT if too much time elapses and the condition is still not met.
In the "new" spots where this is called (cfe_es_start.c lines 293 and 951) it is verified that the function returned CFE_SUCCESS before moving on.
However the existing "CFE_ES_WaitForStartupSync()" API already returned "void" and this API was not modified as part of this change.  Therefore this function does not confirm whether the conditions were actually met, it has no way of propagating this information, and existing apps were not handling it.
A logical/possible improvement here would be to make CFE_ES_WaitForStartupSync() return an int32 so it can propagate a timeout error up the call stack.  Existing apps that don't check the return value are not any worse-off than they already were.

Trac comment by dheater on 2015-05-15 17:03:43:
In cfe_es_start.c; It looks to me like CFE_ES_ApplicationSyncDelay will '''always''' return when there is a timeout. Even if you have not achieved the minimum system state. It is called from line 293 and the subsequent lines seem to assume that the core startup has completed although that condition is not confirmed.

Trac comment by dheater on 2015-05-15 17:18:24:
Nevermind. On line 278, you've already set SystemState to CORE_READY. Still maybe not the behavior one would expect from CFE_ES_ApplicationSyncDelay, but shouldn't cause an error in this case.
Replying to [comment:12 dheater]:

In cfe_es_start.c; It looks to me like CFE_ES_ApplicationSyncDelay will '''always''' return when there is a timeout. Even if you have not achieved the minimum system state. It is called from line 293 and the subsequent lines seem to assume that the core startup has completed although that condition is not confirmed.

Trac comment by acudmore on 2015-05-18 13:15:37:
Approve
I think we should put the defines in the system config file. Would it be worth keeping the defines in the source, but using #ifndef statements, or is that just asking for trouble?
I also agree that while the delay loop is not the best solution, it has minimal impact to a running system, and should be reliable. Being able to tune the delay in the system configuration will help. Some CPUs may support a very small delay.
Does this change require apps to use the WaitForStartupSync call? Do we want to require all apps to use this?
Finally, is there anything here that would break on an SMP system?

Trac comment by jphickey on 2015-05-19 17:15:58:
For those interested, I have pushed commit [changeset:eaa7c63] for further review.
NOTE: This commit is based off the current "master" branch, not the "development" branch
The commit has been rebased/backported to apply to the original cFE 6.4.1 release, and includes the following changes from the CCB discussion:

Rename the "APP_STARTUP" state to "CORE_STARTUP"
Include a CFE_ES_WriteToSyslog() with each state transition.  2 were added, the other 2 are just modifications to existing syslog calls to include the name of the state.
Move the timeout macro definitions to the "cfe_platform_cfg.h" files.  These have been added to the sample config files distributed under the "fsw/platform_inc" subdirectory.

Trac comment by jphickey on 2015-05-29 13:09:21:
Testing note - additional update in commit [changeset:ac557bef]
I have been testing with this trac in place and there is one discovery I made that I felt was significant enough to warrant an additional update.  In the particular test case, an application (intentionally) misbehaved and called neither {{{CFE_ES_RunLoop}}} nor {{{CFE_ES_WaitForStartupSync}}} as part of it's main function.
This (correctly) caused the startup sync in the main thread to wait for the timeout to occur before transitioning to the OPERATIONAL state.
However, the issue was that all of the CORE applications were also held off, in addition to the other external applications that were waiting for startup sync.  Everything got released and worked normally after the timeout expired and the system entered the OPERATIONAL state.
The problem is: during the time that the applications were held in a sync delay, messages from child threads (or other apps that did not need a sync delay) built up in the queues to the CORE applications, these were supposed to be running but were not.  Message limit/queue overflow errors eventually occurred, followed by a flood of activity once the tasks were released.
The referenced commit fixes this problem.

Trac comment by sstrege on 2015-05-27 17:42:25:
Approve

Trac comment by sduran on 2015-06-01 11:09:20:
Approve.

Trac comment by wmoleski on 2015-06-16 13:36:38:
cFE <IP_ADDRESS> was tested using an MCP750 running vxworks 6.4. All build verification tests normally executed on a cFE release were successfully executed. An additional test was performed in an attempt to verify that the race conditions identified did not appear. The UART (minicom) output for the test is attached to trac #81.

Trac comment by sstrege on 2016-08-11 15:53:04:
Merged to development on Wed May 20 09:39:24 2015 -0400


Java arm64 images, buster variants for back compat

As described in https://github.com/microsoft/vscode-dev-containers/issues/558#issuecomment-905117722, the situation for Docker on M1 macs is not ideal since both debian:buster nor ubuntu:focal experience segmentation faults due to an issue in libss1.1. It seems unlikely that buster will be patched now that bullseye is out (and buster therefore gets security fixes only).
Therefore this PR:

Adds arm64 builds for Debian bullseye
Adds buster variants that are x86 only for backwards compat.
Keeps the default image tags (8, 11, 16) at buster

@testforstephen @akaroml - Debian bullseye is pretty recent, but works on arm64. Would it make sense to default to stick with buster as is done here?  Java should be fairly abstracted from OS version updates, but I didn't want to make an update that could break users. Thoughts?
//cc: @joshspicer @2percentsilk @bamurtaugh @chrmarti

Looks good to me. Only one concern is how user can easily distinguish which Java variant to use when they use "Remote-Containers: Add Remote Development Configuration Files..." command to pick up a Java definition?
This is current dropdown for Java versions:

I assume the PR will add two more options like "11-bullseye" and "16-bullseye". Is it possible to show some details for these options to mention the architecture they support?

@testforstephen Yeah the list would include both buster and bullseye.  I could have the label ("Java version") mention that bullseye should be used for arm64 and M1 macs.

yes, since bullseye is very new and we can stay on buster as default for a while. But eventually we need to switch to bullseye at some point in future.


Error: failed to lookup link "br-39817017203e": Link not found during deploy on WSL 2

Hello,
I have tried to create the Quick Start lab (https://containerlab.dev/quickstart/) on WSL 2 but during the deploy I got this error message:
INFO[0000] Containerlab v0.55.0 started
INFO[0000] Parsing & checking topology file: srlceos01.clab.yml
WARN[0000] failed gleaning v4 and/or v6 addresses from bridge via netlink, falling back to docker network inspect data
Error: failed to lookup link "br-39817017203e": Link not found
Any ideas?

Hi
https://containerlab.dev/install/#windows-subsystem-linux-wsl


same function on "com.squareup.okhttp: okhttp: 2.7.0"

is it the same function using "com.squareup.okhttp: okhttp: 2.7.0" with the current version? if different can give me the tutorial for update using the current version
thank you

Please ask usage questions like this on stackoverflow.  The APIs are familiar enough that starting with existing code and changing imports will get you some way along.  Also if you use libraries like retrofit, then it's mostly changing a dependency.


Windows 10 file read failed

Running on Windows 10, I had trouble with file operations.  Made a few changes and it worked:
import os
class FileCommunication(Communication):
    def __init__(self, file_path):
        super(FileCommunication, self).__init__()
        if sys.version_info[0] >= 3:
            self.f = os.open(file_path, os.O_RDWR | os.O_BINARY)
        else:
            self.f = os.open(file_path, os.O_RDWR | os.O_BINARY)
    def _read(self, n, timeout=None):
        try:
            return os.read(self.f,n)
        except IOError as e:
            _logger.warning("failed to read")
            raise e
    def write(self, data):
        os.write(self.f,data)
    def close(self):
        os.close(self.f)

The Python 2 vs 3 case can be folded:
self.f = os.open(file_path, os.O_RDWR | os.O_BINARY)

Why do you catch the IOError for _read? The caller should take care of IO errors and do logging as needed.
Can you also post any exceptions/errors that prompted for these patches? Thanks :-)

I guess there was no good reason for trapping IOError for _read.
I thought about folding Python 2 vs 3 case, but thought I'd leave the cases split up like they were before, just in case they'd need to be handled differently since  I only tried it on Python 2.
The errors I got were:
Traceback (most recent call last):   File "lglaf.py", line 404, in <module>     main()   File "lglaf.py", line 386, in main     try_hello(comm)   File "lglaf.py", line 290, in try_hello     data = comm.read(0x20, timeout=HELLO_READ_TIMEOUT)   File "lglaf.py", line 148, in read     buff = self._read(need, timeout=timeout)   File "lglaf.py", line 189, in _read     return self.f.read(n) IOError: [Errno 0] Error

Isn't os.O_RDONLY | os.O_BINARY sufficient?

I doubt it would work with os.O_RDONLY since writing is required.
On Nov 6, 2016 6:44 AM, "Peter Wu"<EMAIL_ADDRESS>wrote:

Isn't os.O_RDONLY | os.O_BINARY sufficient?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Lekensteyn/lglaf/issues/6#issuecomment-258675661, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGgz25DCAtviz-yy280YvHXnxlqHvWo4ks5q7b2BgaJpZM4IEtaf
.

Oh, nevermind, thinko (r+ = O_RDWR).
Since you mentioned Python 2, I think that buffering could be a problem. From pydoc open:

The optional buffering argument specifies the file’s desired buffer size: 0 means unbuffered, 1 means line buffered, any other positive value means use a buffer of (approximately) that size (in bytes). A negative buffering means to use the system default, which is usually line buffered for tty devices and fully buffered for other files. If omitted, the system default is used. [2]

What if you just remove the if sys.version_info[0] >= 3: and else: ... lines completely, enabling the buffering parameter by default?
(Note to self: when adding such checks, add a comment why you exactly do it. I vaguely remember that buffering=0 gave some error on Windows, but do not know for sure.)

I think I tried different buffering options without success. When I get a chance I'll check it out. It probably was a python bug, and by now maybe the bug is fixed.

Is this not the same as this ?
https://github.com/steadfasterX/lglaf/pull/9


XPATH doesn't finish running

Hi,
I have instaled the newest versions of XPath and NodeJS on Windows 10. However when I try to run a cell it doesn't finish. Even with a "Hello " || "world"

What might be causing this failure?
Regards
Nuno

On my Windows test machine I have Windows 10 with NodeJS v<IP_ADDRESS>. With this setup I can't reproduce your issue, the XPath code cell runs and the result is shown.
Even though you have NodeJS installed it's possible that it's not installed globally. Try running node --version from the VS Code terminal window - what does this output?
If it's not a problem with your NodeJS installation then it may be some other extension is conflicting with the XPath Notebook extension in some way. Please try disabling all other extensions using the Disable all installed extensions command and then just enabling the XPath Notebook extension to see if the problem still persists.

Hi pgfearo,
Thanks for your fast answer! 👍
I was able to find the reason for this failure. I had an older version of NodeJS v11 installed before that was previous the new version v16 in the environment variables. Now XPath is working fine.
Thanks!
Regards
Nuno


erroranalysis: Fix the scenario when samples in dataset and string_indexed_data don't match

Description
For large data scenario, if the test set in provided at run time (after cohort filtering) it could have different number of samples than the test data used at the RAI computation time. The error analysis tree computation is such cases can fail with the following error:-
index 100 is out of bounds for axis 0 with size 100
Traceback (most recent call last):
  File "c:\users\gaugup\documents\github\responsible-ai-toolbox\raiwidgets\raiwidgets\responsibleai_dashboard_input.py", line 174, in debug_ml
    max_depth, num_leaves, min_child_samples)
  File "c:\users\gaugup\documents\github\responsible-ai-toolbox\erroranalysis\erroranalysis\analyzer\error_analyzer.py", line 367, in compute_error_tree_on_dataset
    min_child_samples=min_child_samples)
  File "c:\users\gaugup\documents\github\responsible-ai-toolbox\erroranalysis\erroranalysis\_internal\surrogate_error_tree.py", line 150, in compute_error_tree_on_dataset
    dataset_sub_names, max_depth, num_leaves, min_child_samples)
  File "c:\users\gaugup\documents\github\responsible-ai-toolbox\erroranalysis\erroranalysis\_internal\surrogate_error_tree.py", line 318, in get_surrogate_booster_local
    input_data[:, c_i] = analyzer.string_indexed_data[row_index, idx]
IndexError: index 100 is out of bounds for axis 0 with size 100

The fix is to compute string_indexed_data if the number of dataset samples is different from string_indexed_data.
Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #1915 (7e5a47f) into main (2351fae) will decrease coverage by 7.48%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1915      +/-   ##
==========================================
- Coverage   93.32%   85.85%   -7.48%
==========================================
  Files          93       29      -64
  Lines        4601      523    -4078
==========================================
- Hits         4294      449    -3845
+ Misses        307       74     -233

Flag
Coverage Δ

unittests
85.85% <ø> (-7.48%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...is/erroranalysis/_internal/surrogate_error_tree.py

erroranalysis/erroranalysis/analyzer/__init__.py

...onsibleai/responsibleai/serialization_utilities.py

...ai/responsibleai/rai_insights/rai_base_insights.py

...onsibleai/_tools/shared/attribute_serialization.py

...ai/responsibleai/_tools/counterfactual/__init__.py

.../responsibleai/modelanalysis/constants/__init__.py

erroranalysis/erroranalysis/_internal/utils.py

...bleai/responsibleai/_tools/causal/causal_result.py

...ibleai/_tools/causal/dashboard_schemas/__init__.py

... and 54 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Support Android SDK version 26

Due to changes affecting privacy in android API level 26 Im now getting the following when initiating baresip.
E/libc: Access denied finding property "net.dns1"
E/libc: Access denied finding property "net.dns2"
E/libc: Access denied finding property "net.dns3"
E/libc: Access denied finding property "net.dns4"

I've traced the issue to the following function, and Im suspecting this is might be in issue with libre rather than with baresip.
https://github.com/alfredh/baresip/blob/dacf1e515f57f5f0e57fa61d69084ee40f959574/src/net.c#L52
I've tried to set static dns servers in the configuration file. This allows me to initiate baresip but the error messages are still present.

Reopening this issue in the libre repo.


Kubernetes view breaks UI

Report: service_report.json.gz
Also, after the error, the UI doesn't recover (switching to other views doesn't work). I had to refresh the browser.


Adding links to index.rst

Problem
I am really new to this. I generated documentation using the theme 'sphinx.ext.autodoc'. Can Modules from 'Module index' be added on the Home page separately? It does not work by just adding * :ref:module.module in the index.rst. But I do not know what else is needed.
Give details on your issue.
Reproducible Project
Please give a link to a public reproducible project or provide an example of the Restructured Text that gives an issue.
Place RST code here (if any).

Error Logs/Results
Place any images or error logs that might be able to help solve the issue here.
Expected Results
Please describe how this should work properly.
Environment Info

Python Version:
Sphinx Version:
RTD Theme Version:

This is a question specific to sphinx and not this theme, please ask your question on stackoverflow or some other support system from https://www.sphinx-doc.org/en/master/


Refresh dashboards and recommended monitors for MongoDB

What does this PR do?

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Did you also modify a recommended monitor?

Did you also modify a recommended monitor?

No


Update: disable no-console lint rule

Summary
We have 63 warnings from no-console rule and since this is a command-line tool, we'll likely have more usage for console.log. Disabling the rule to cut the noise.
Test plan
Run yarn lint and make sure you see no errors nor warnings.

Thank you <3

Codecov Report

Merging #4101 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4101   +/-   ##
=======================================
  Coverage   60.34%   60.34%
=======================================
  Files         195      195
  Lines        6755     6755
  Branches        6        6
=======================================
  Hits         4076     4076
  Misses       2676     2676
  Partials        3        3

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 d2b7c2d...cd5f955. Read the comment docs.


Give hints access to any cell

In hints, we can currently access the current an next row, similar to how identities work. In #1306, this was a problem because I wanted to access the previous row to compute the hint in the current row. But I think in general, there could be use-cases where we'd want to access any row.
Not sure how to best implement it though.

We still have the explicit row parameter, right? So we could add a builtin eval_on where you pass an expr and a row number.


Update to identity proofing proposal

User Story
As a ReportStream teammate, I want to update the identity proofing proposal materials and documentation to include new information, so the larger team can strategize to make upcoming decisions about vendors, platforms, timelines, and more.
Background and context
As part of the design brief to add additional third-party authentication providers and abstract our authentication layers, we will need to consider identity proofing as a separate functionality from Okta authentication. As more and more Senders are added to the Universal Pipeline in the near and far future, we will need to prove that these organizations 'are who they say they are', and are not bad actors that could send faulty or fraudulent data into ReportStream.
Working links

Part of Authentication enhancements design brief
Authentication/verification information and process flows
Identity proofing proposal deck
[Previous ticket - Slide deck summarizing Authentication insights #10685] (https://app.zenhub.com/workspaces/engagement-6166edbd409257001e09f1b2/issues/gh/cdcgov/prime-reportstream/10685)

Acceptance criteria

[ ] Meet with security team to confirm required NIST / IAL standard
[ ] Update slide deck to include new relevant information about required NIST / IAL standard
[ ] Update proposal to include platforms and/or vendor that can accomplish this level
[ ] Share out proposal with team
[ ] Finalize after comments

Not in scope

Comprehensive decisions on authentication implementation
Go / no-go decisions on certain platforms and/or vendors

Met with @chris-kuryak to discuss next steps. Should ping JG for questions about downloadable / viewable data from website, and AD for downloadable / viewable data from the API.

@chinelo-ikejimba met with Mo this morning and it feels like we have next steps for the remaining quarter of 2023. As such, closing out of this ticket.


chore(starknet_sequencer_infra): add tracing test

Stack:

#2424
#2385
#2384
#2329
#2332 ⬅
#2328

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

✓ Commit merged in pull request #2424


Managed node group bootstrap.sh not run with custom ami

Description
Please provide a clear and concise description of the issue you are encountering, your current setup, and what steps led up to the issue. If you can provide a reproduction, that will help tremendously.
⚠ Note
Before you submit an issue, please perform the following first:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Terraform:
Terraform v0.13.4
Provider(s):

provider registry.terraform.io/hashicorp/aws v3.70.0
provider registry.terraform.io/hashicorp/cloudinit v2.2.0
provider registry.terraform.io/hashicorp/null v3.1.0
provider registry.terraform.io/hashicorp/tls v3.1.0

Module:
18.0.0

Reproduction

Steps to reproduce the behavior:
Converted to 18.0.0 from 17.24.0
I am following the instructions in the readme to use custom AMI that is EKS optimized. Whenever I apply my changes the bootstrap script does not seem to run and join the node to the cluster. I get the following terraform error:
Error: error waiting for EKS Node Group (<example>) to create: unexpected state 'CREATE_FAILED', wanted target 'ACTIVE'. last error: 1 error occurred:
	* <instance-id>: NodeCreationFailure: Instances failed to join the kubernetes cluster

If I SSH/SSM into the node and look at the cloud-init log this is what I see:
Cloud-init v. 21.4-0ubuntu1~20.04.1 running 'modules:config' at Thu, 06 Jan 2022 07:31:29 +0000. Up 28.96 seconds.
Pre-Bootstrap Script Init
Aliasing EKS k8s snap commands
Added:
  - kubelet-eks.kubelet as kubelet
Added:
  - kubectl-eks.kubectl as kubectl
Stopping k8s daemons until configured
Stopped.
Cluster "kubernetes" set.
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Exited with error on line 483
Cloud-init v. 21.4-0ubuntu1~20.04.1 running 'modules:final' at Thu, 06 Jan 2022 07:31:34 +0000. Up 33.42 seconds.
2022-01-06 07:31:38,605 - cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts)
2022-01-06 07:31:38,611 - util.py[WARNING]: Running module scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed

Code Snippet to Reproduce
AMI Source:
data "aws_ami" "eks_ubuntu" {
  most_recent = true
  owners = ["099720109477"] # Canonical (Ubuntu)

  filter {
    name   = "name"
    values = ["ubuntu-eks/k8s_1.21/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-*"]
  }

  filter {
        name = "virtualization-type"
        values = ["hvm"]
  }
}

Node group:
  eks_managed_node_groups = {
    project1 = {
      name_prefix      = "project1"
      description      = "project1 managed node group launch template"

      # Auto scaling group capacity
      desired_capacity = 1
      max_capacity     = 1
      min_capacity     = 1

      # Instance image and bootstrap options
      ami_id                     = data.aws_ami.eks_ubuntu.id
      platform                   = "linux"
      enable_bootstrap_user_data = true
      bootstrap_extra_args       = ""
      instance_types             = ["c5n.large"]

      pre_bootstrap_user_data = <<-EOT
        echo "Pre-Bootstrap Script Init"
      EOT

      post_bootstrap_user_data = <<-EOT
        echo "Post-Bootstrap Script Init"
      EOT

      iam_role_additional_policies = [
        "arn:aws:iam::aws:policy/CloudWatchAgentServerPolicy",
        "arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore",
        "arn:aws:iam::aws:policy/service-role/AmazonEC2RoleforSSM"
      ]

      # Node group taints
      taints = [
        {
          key = "dedicated"
          value = "project1"
          effect = "NO_SCHEDULE"
        }
      ]

      tags = {
        launch_template = "project1"
      }
    }

Expected behavior
The eks bootstrap script is run through the module
Actual behavior
The boostrap script is not run, I believe
Terminal Output Screenshot(s)

Additional context

@jallen-frb I haven't been able to go through all of the code changes introduced in v18.0.0 but if the behaviour is consistent with v17 then you either need to have the standard EKS bootstrap script in your AMI and set eks_optimized = true or you need to provide the whole user_data script.

just at first glance, a things you might check:

v18.x takes a minimalist approach in terms of security access - port 8080 is not open by default on the security groups created so if the ubuntu flavor of EKS AMI uses this port, you will need to add a rule to allow traffic on 8080 between the nodes and the control plane
With the use of the Ubuntu EKS AMI, does this flavor of AMI provided a bootstrap script at /etc/eks/bootstrap.sh? If so, you will need to opt into providing a bootstrap script by setting https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/examples/eks_managed_node_group/main.tf#L132 or provide your own bootstrap script/userdata
I see you have a NO_SCHEDULE taint - are there other nodes in the cluster that will allow the utility pods to be provisioned (CoreDNS, etc.)? if this is the only node group in the cluster, the utility pods that are required won't be able to provision and lead to a failure to join

@jallen-frb I haven't been able to go through all of the code changes introduced in v18.0.0 but if the behaviour is consistent with v17 then you either need to have the standard EKS bootstrap script in your AMI and set eks_optimized = true or you need to provide the whole user_data script.

@stevehipwell 18 gets rid of eks_optimized = true and replaces it with:
      enable_bootstrap_user_data = true
      bootstrap_extra_args       = ""

      pre_bootstrap_user_data = <<-EOT
        echo "Pre-Bootstrap Script Init"
      EOT

      post_bootstrap_user_data = <<-EOT
        echo "Post-Bootstrap Script Init"
      EOT

I am following the instructions as per 5. from the new readme: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/README.md#node-group-configuration

just at first glance, a things you might check:

v18.x takes a minimalist approach in terms of security access - port 8080 is not open by default on the security groups created so if the ubuntu flavor of EKS AMI uses this port, you will need to add a rule to allow traffic on 8080 between the nodes and the control plane
With the use of the Ubuntu EKS AMI, does this flavor of AMI provided a bootstrap script at /etc/eks/bootstrap.sh? If so, you will need to opt into providing a bootstrap script by setting https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/examples/eks_managed_node_group/main.tf#L132 or provide your own bootstrap script/userdata
I see you have a NO_SCHEDULE taint - are there other nodes in the cluster that will allow the utility pods to be provisioned (CoreDNS, etc.)? if this is the only node group in the cluster, the utility pods that are required won't be able to provision and lead to a failure to join

@bryantbiggs

I will look into the sq and port stuff
My AMI (ubuntu 20.04 eks optimized image direct from Canonical) has the bootstrap script correctly at /etc/eks/bootstrap.sh
I am using this in main part of the module:

  # Cluster addons
  cluster_addons = {
    coredns = {
      resolve_conflicts = "OVERWRITE"
    }
    kube-proxy = {}
    vpc-cni = {
      resolve_conflicts = "OVERWRITE"
    }
  }

@stevehipwell 18 gets rid of eks_optimized = true and replaces it with:

I just looked at the README and it was still present so sorry for that.

@stevehipwell 18 gets rid of eks_optimized = true and replaces it with:

I just looked at the README and it was still present so sorry for that.

@stevehipwell I do not see it there for version 18.0.0. Where are you seeing that?

@jallen-frb I miss read ebs_optimized as eks_optimized, apologies again. I still haven't fully worked through the changes made in v18.

I just confirmed the bootstrap script is not running correctly. If I go on to the system and manually run the bootstrap script it connects to the cluster.
If I grab this output from the cloud-init logs and run it as root user it connects fine:
      ami_id                     = data.aws_ami.eks_ubuntu.id
      platform                   = "linux"
      enable_bootstrap_user_data = true
      bootstrap_extra_args       = ""

      pre_bootstrap_user_data = <<-EOT
        echo "Pre-Bootstrap Script Init"
        export cluster_name=${module.eks.cluster_id}
        echo $cluster_name
        export endpoint=${module.eks.cluster_endpoint}
        echo $endpoint
        export cluster_auth_base64=${module.eks.cluster_certificate_authority_data}
        echo $cluster_auth_base64
        echo "/etc/eks/bootstrap.sh --b64-cluster-ca $cluster_auth_base64 --apiserver-endpoint $endpoint $cluster_name"
      EOT

BUT if I try to run the script in there I still get the cannot connect to localhost:8080. Are the variables not getting passed correctly? I feel like I am crazy.
      ami_id                     = data.aws_ami.eks_ubuntu.id
      platform                   = "linux"
      enable_bootstrap_user_data = true
      bootstrap_extra_args       = ""

      pre_bootstrap_user_data = <<-EOT
        echo "Pre-Bootstrap Script Init"
        export cluster_name=${module.eks.cluster_id}
        echo $cluster_name
        export endpoint=${module.eks.cluster_endpoint}
        echo $endpoint
        export cluster_auth_base64=${module.eks.cluster_certificate_authority_data}
        echo $cluster_auth_base64
        echo "/etc/eks/bootstrap.sh --b64-cluster-ca $cluster_auth_base64 --apiserver-endpoint $endpoint $cluster_name"
        /etc/eks/bootstrap.sh --b64-cluster-ca $cluster_auth_base64 --apiserver-endpoint $endpoint $cluster_name
      EOT

you can view the rendered user data to see if the variables are populated correctly by going to a launched instance in the console and viewing the user data for it

Yes the variables are populated correctly. I am starting to think it has to do with the bootstrap script or its permissions now.

I just find it odd that version 17.24.0 was running the same AMI and everything worked using pre_userdata:
    project1 = {
      name_prefix      = "project1"

      instance_types = ["c5n.large"]

      desired_capacity = 1
      max_capacity     = 1
      min_capacity     = 1

      create_launch_template = true
      ami_id                 = data.aws_ami.eks_ubuntu.id
      ami_is_eks_optimized   = true
      capacity_type          = "ON_DEMAND"

      # bootstrap_env = {
      # }

      taints = [
        {
          key = "dedicated"
          value = "project1"
          effect = "NO_SCHEDULE"
        }
      ]

      additional_tags = {
        launch_template = "project1"
      }

      pre_userdata = <<-EOT
        #!/bin/sh
        # enable htcp congestion control algo
        modprobe tcp_htcp
        # allow testing with buffers up to 128MB
        sysctl -w net.core.rmem_max=134217728
        sysctl -w net.core.wmem_max=134217728
        # increase Linux autotuning TCP buffer limit to 64MB
        sysctl -w net.ipv4.tcp_rmem="4096 87380 67108864"
        sysctl -w net.ipv4.tcp_wmem="4096 65536 67108864"
        # increase the length of the processor input queue
        sysctl -w net.core.netdev_max_backlog=250000
        # recommended default congestion control is htcp
        sysctl -w net.ipv4.tcp_congestion_control=htcp
        # recommended for hosts with jumbo frames enabled
        sysctl -w net.ipv4.tcp_mtu_probing=1
      EOT
    }

I figured it out. Ubuntu pushed a new AMI yesterday that had some changes that breaks the bootstrap. Not sure how quite yet, but I can confirm it is their EKS 1.21 optimized image that was pushed on January 5, 2021.

https://bugs.launchpad.net/cloud-images/+bug/1956620


Added the Edit vision modal component

[ ] Created a modal component for editing goals.
[ ] Created a folder called "Modal" that contains every other modal component.

Please resolve conflict

Conflict resolved


Replace TryUpdateShoot{Labels,Annotations} functions with Patch requests

How to categorize this PR?

/area usability
/kind cleanup technical-debt
/priority normal
What this PR does / why we need it:
This PR replaces the TryUpdateShoot{Labels,Annotations} functions with Patch requests to prevent undesired conflict updates that we anyways don't care about.
Which issue(s) this PR fixes:
Fixes #3351
Release note:

NONE

/squash

/squash

I had to rebase to resolve some merge conflicts.

I had to rebase to resolve some merge conflicts.


Handle JSON-RPC notifications

This PR adds JSON-RPC 2.0-compliant notification handling for JsonRpcEngine.

JSON-RPC notifications are defined as JSON-RPC request objects without an id property.
A new constructor parameter, notificationHandler, is introduced. This parameter is a function that accepts JSON-RPC notification objects and returns void | Promise<void>.
When JsonRpcEngine.handle is called, if a notificationHandler exists, any request objects duck-typed as notifications will be handled as such. This means that:

Validation errors that occur after duck-typing will be ignored. At the moment, this just means that no error will be thrown if the method field is not a string.
If basic validation succeeds, the notification object will be passed to the handler function without touching the middleware stack.
The response from handle() will be undefined.
No error will be returned or thrown, unless the notification handler itself throws or rejects.

Notification handlers should not throw or reject, and it is the implementer's responsibility to ensure that they do not.

If JsonRpcEngine.handle is called and no notificationHandler exists, notifications will be treated just like requests. This is the current behavior.

I think we should note that this is for "client side" sending notifications to the server. I believe "server side" notifications end up being an event emitter which isnt in json-rpc-engine but json-rpc-middleware-stream: https://github.com/MetaMask/json-rpc-middleware-stream/blob/main/src/createStreamMiddleware.ts#L71

@shanejonas not when I'm done with it 😎
https://github.com/MetaMask/json-rpc-middleware-stream/pull/24


AttributeError: 'ZStage' object has no attribute 'move_to'

Traceback
2017-08-03 15:03:39 [ERROR:mr_box_peripheral_board_plugin]: [mr_box_peripheral_board_plugin] Error applying step options.
Traceback (most recent call last):
  File "C:\Users\Ryan\MicroDrop\etc\microdrop\plugins\enabled\mr_box_peripheral_board_plugin\__init__.py", line 100, in apply_step_options
    self.board.zstage.move_to(position)
AttributeError: 'ZStage' object has no attribute 'move_to'

Fix
The correct call is: self.board.zstage_move_to(position), but we also need to enable/disable the motor. We can either do this in the plugin itself (.e.g., proxy.zstage.motor_enabled = True/False) or we could enable/disable it automatically within the firmware's zstage_move_to() method.

This issue was caused by the fact that I commits that I hadn't yet published.
As of v0.6, the Proxy.Zstage.move_to(position) method exists.

So we can close this issue then?


LLVM dependency version

rustc_codegen_nvvm v0.2.2 depends on LLVM7 which is somewhat outdated and not packaged for the latest ubuntu version (21.10). Adding the possibility of using LLVM9 or later would make it simpler to get started writing device code on Ubuntu 21.10.
What are the reasons for depending on specifically version 7? Would it be beneficial to change this?

This is because libnvvm requires llvm 7 bitcode or it does not work. In the future we will probably do what numba does and lower the textual ir from a higher version, but there are still a lot of issues. Are you sure llvm isnt present on ubuntu? This is what we do in CI and it works

Thanks for the explanation.

Are you sure llvm isnt present on ubuntu

It's available as a package with Ubuntu 20.04 LTS and Ubuntu 21.04. I'm sure your CI must be running one of those. I'm not able to find a package that works with Ubuntu 21.10, which was released just two months ago.
I'm sure it's possible, but I would be happy to not have to compile LLVM myself. If there are other users that have LLVM7 working on 21.10 it would be nice to hear how they solved it.


PowerRename runs for hours at high CPU without UI if invoked on certain areas of File Explorer

Microsoft PowerToys version
0.49.1
Running as admin

[X] Yes

Area(s) with issue?
PowerRename
Steps to reproduce
Summary:
If invoked on certain File Explorer elements, PowerRename starts, does not display any UI and runs at high CPU usage for hours.
Steps:

Start Windows File Explorer
In Navigation Pane, select "Quick Access"
From View menu select "medium size icons"
In main area, select and then right click on heading "Frequent folders"
From context menu, select "PowerRename"

✔ Expected Behavior
Option 1: PowerRename is not available in context menu
Option 2: PowerRename displays a user interface.
❌ Actual Behavior
PowerRename starts and runs at high CPU (as per Task Manager) but does not display any UI.
(I killed the lingering process after around 3 hours.)
Other Software
Windows 10 Pro (10.0.19043)

Maybe #14356
What resolution and the DPI scale are your monitor using?

What resolution and the DPI scale are your monitor using?

Dual monitor setup. 2560x1440; 27".
Scale setting is 100% if that's what you're asking. It's not a high DPI monitor.

Just to confirm, can you set your resolution to either lower than:

1600x900 with 125%
1920x1080 with 100%
And see if you can launch PowerRename. Thank you

to be sure, PowerRename works fine for normal usage. I raised the issue just in case the PowerRename context menu is registered/enabled for the Windows File Explorer items that aren't to be renameable, like special folders.

I confirm. Same problem with 1920x1080 @ 100%, when clicking on File Explorer > Quick Access > Frequent Folders.

After some more testing:

Same problem when I try to PowerRename a folder with a large subdirectory tree. So, it's not an issue specific to special folders or group headings.
SysInternals ProcessMonitor shows that PowerRename parses the directory tree in chunks, pauses for a long time after each chunk, then continues to parse.
At start, for a few seconds, there actually is a UI: An invisible (fully transparent) small window at the top left of the screen. It turns mouse cursor to "waiting" shape. Clicking invokes Windows "not responding; kill?" dialog.

"Expected behaviour":

For large file sets (intentional or accidental), PowerRename should start by showing a valid UI and then start parsing, preferrably in an interrruptible nad UI-responsive manner.
Maybe review implementation of UI builder or parser. There is no obvious reason for the long pauses between reading chunks of file info. Maybe it chokes on creating a crazy large UI.

@typpos Thanks for clarifying your issue! Sorry for misunderstanding. :)
Valid issue to fix. Thank you.

For me it sound that Powername is following the shortcut paths.

I had some issues a while back too. My solution is in this comment .

Same problem when I try to PowerRename a folder with a large subdirectory tree. So, it's not an issue specific to special folders or group headings.

This looks like high cpu&memory performance issue tracked here #14219. It's fixed and will be included in next PT release.
I tried renaming Frequent folders like shown in description and with latest fixes I'm able to do so. Of course it takes some tome as there are 60K+ items&subitems (in my case).. You might have a lot more items there.. possibly hundreds of thousands items so memory limit can be hit and PowerRename could crash in the end. If not it will take some time but it'll load items and UI will be shown.

For large file sets (intentional or accidental), PowerRename should start by showing a valid UI and then start parsing, preferrably in an interrruptible nad UI-responsive manner.

Regarding this, you have a good point and we have this in our backlog. Some kind of Progress bar/dialog will be added in near future.
Also, you're right once again, PowerRename can't rename special folders like e.g. "Downloads", Local disks, etc.

Closing as a duplicate of  #14219


Component to remove borders of a same color

Maybe we should convert the image to gray scale and remove lines of pixels (or columns) when its mean is close enough of black/white.

I think this one is implemented somewhere now?

It is, on GetBorderlessBox component. Closing it.


PL7H

Use the preview tab to see the example given below. Edit the relevant information and preview the changes before submitting. You may delete these instructions.

Key
Value

ID
PL7H

Source
Vaaran Bhai Gurdas Ji

Page
20

Line
gurmuiK AweI pMQu, inj Gru AwieAw [

Correction
THIS ≠ THAT

PROOF (EDITION)
Image:

Correction:
AwieAw ≠ pwieAw
Proof:
Vaaran Bhai Gurdaas Ji | November 2011 | Shamsher Singh Ashok | SGPC, Sri Amritsar
Image:


Number of fixes for ACL commands

Fixes #1283 #1282 #1284
I have put all fixes in single PR to minimize effort/hassle with reviews.
All commands can be reviewed and verified using the same 2 commands provided in the verification file.

#1282 is not being resolved.

rhoas kafka acl create --all-accounts --permission allow --operation all --topic all  -y
The following ACL rule is going to be created:

  PRINCIPAL      PERMISSION   OPERATION   DESCRIPTION
 -------------- ------------ ----------- --------------
  All accounts   ALLOW        ALL         TOPIC is "*"

⣻ Adding ACL to Kafka instance "test"

Done

Closes #1283 #1282 #1284

I canot figure out how to generate documentation. Locally documentation has no changes but CI does show them.

I canot figure out how to generate documentation. Locally documentation has no changes but CI does show them.

CI checks against main. Your local branch is behind main.

Approving assuming docs will be fixed before merging.


service.dial.no_terminators

For network troubleshooting efficiency, it would be beneficial to have a specific dial fail metric for 'service XXXXX has no terminators' type events (service.dial.no_terminators).  These failures are currently rolled into service.dial.error_other with other causes.

Totally agree. We should add add this.

Do we need to distinguish between "no terminators" and "no terminators for dial identity" if addressable terminators are in play?

I am for as much discrimination in failure reasons as possible, it can only help in troubleshooting and monitoring.


[drift_dev] Add the static getter actualTableNameStatic

Fixes https://github.com/simolus3/drift/issues/2623

I didn't modify any test. I suppose some generated files are being used as tests. Tell me if you want me to write a specific test for that

I suppose some generated files are being used as tests

Pretty much, yeah. You could write a test that invokes the static field somewhere and asserts it has the expected value. That makes it easier to remember that the field is part of the public API and shouldn't be changed in future versions of the generator.

I added a test in test: Add a test using .$name. Is it what you were expecting?


New operators : for-comprehensions

forEach2 and forEach3 for nested looping
LazyFutureStream.of(1,2,3)
						.forEach2(a->IntStream.range(10,13),
									a->b->a+b);

//LFS[11,14,12,15,13,16]

https://github.com/aol/simple-react/pull/91


Better feature detection for performance.now()

Closes #29

Wonder what's going on eslint-plugin-react in Travis...

Oh, right, I forgot include eslint-plugin-react!
Fixed in 1.0.9.


Misleading example in docs edited.

It took me some time to realize fileList and dirList should be wrapped in task object.

@nvoinov check this out, update the documentation


Option to disable the Fetch behavior of rendering raw data into HTML

Describe the problem
As in official document:

When fetch runs on the server, the resulting response will be serialized and inlined into the rendered HTML.

This behavior intercepts with my reason to use SSR on SvelteKit.
Because I don't want my server-side JSON response to be accessible by the client (other developers) as a raw JSON. I do it for preventing possible parsing of raw JSON data. And also to avoid visibility of some app-specific data (they are not security-related data).
Describe the proposed solution
I would like to have an option to disable rendering JSON as raw data into HTML. Just only rendering it to the template.
Alternatives considered
No response
Importance
i cannot use SvelteKit without it
Additional Information
No response

You could turn off client-side rendering. As long as your API is accessible on the web they could just hit your API directly to get the data, so taking it out of the page might not help you a lot

Or, alternatively, if you turned off ssr I think that might stop it from including it in the page. (I haven't tested)

I'm trying to solve this issue by making database queries from the .js file and then import it with the load function inside the module context. SSR is valuable for me, but I don't want anybody to see the raw JSON. Do you think that would work? I can't get it to work, though because of errors. Need some help

load cannot make database queries. it must call an HTTP endpoint

You could turn off client-side rendering.

I tested it, works. But other functionalities don't work which are very important for the page.

load cannot make database queries. it must call an HTTP endpoint

Can I just make a query with a .js file and export as a JSON object, and then import this exported JSON from the load function?

No. load runs on the client. It can't access your database no matter what you name your files.
You could also probably prerender your page so that the database is queried at build time and load doesn't need to run in the browser

It would be better to have partial hydration for these types of scenarios, I think. For example, type of load function which gives us a chance to make the queries or API calls on the server.

You could also probably prerender your page so that the database is queried at build time and load doesn't need to run in the browser

By doing this, the pages won't update when I edit data on the database right? That's a disadvantage for me as well.

Because I don't want my server-side JSON response to be accessible by the client (other developers) as a raw JSON. I do it for preventing possible parsing of raw JSON data. And also to avoid visibility of some app-specific data (they are not security-related data).

Are you somehow blocking or disabling the Network tab of the browser developer tools? Because otherwise, your clients (who will definitely know about the dev tools since they're other developers) will be able to see the JSON response from your server to their browser anyway, whether or not it's been included in the HTML of the page, simply by using the Network tab of the dev tools.
And since as far as I know there's no way for a web page to disable the client's access to the developer tools (if you know a way, I'd be interested to learn it), what you're trying to achieve (hiding the server's JSON response from your customers) is impossible. So in my opinion, it's not worth adding extra complexity to Svelte-Kit's fetch function for this use case, because it wouldn't actually get you what you want anyway.

Sorry for my poor explanation. The thing I want is simply to get access to DB (for making queries) from the load function.
By doing that, I think the raw JSON won't be accessible to the clients/devs from the network tab or anywhere else.

That's impossible. load runs in the browser. You can't access your database from the browser

@benmccann I wonder if I could ask for what @ulvidamirli was asking for but in a slightly different way as I think there was a bit of miscommunication:
Could it be possible in the future to get a function call like load() but one that will be only called during build time for pre-rendering.
As of today, if I enable pre-rendering with crawl with SvelteKit, it correctly generates HTML from API data. However, because load() is also called in the browser in addition to build/pre-rendering time, the benefits of pre-rendering for this static content are mitigated.
Problem with turning off hydration for a page is that then it ruins interactivity with the rest of the page that absolutely need hydration.
Basically, I would get everything I need if I’m able to have an exact clone of load() but one that would only be called in the compiler while pre-rendering. Bonus points if that compiler-only JS never makes it into the client/browser but this is not necessary.
Here’s my use-case: I’m developing an application like an encyclopedia/dictionary where the content is fairly static and doesn’t need to be updated instantaneously. We will rebuild the site as a regular cadence. I do have other parts of the page (like search/autocomplete/etc) that benefits a lot from Svelte’s conveniences. The API doesn’t need to be a secret or hidden, but as you can see, there’s a lot of reduction in traffic we can achieve if the API is only hit during build-time.
I’ve tried the trick where you import browser from $app/env and short circuit load() when in the browser, but that throws errors into console as the page attempts to hydrate and is missing that data it would have fetched in the load() call.
Right now, my solution is to run a python script that is executed before sveltekit build which will pull all the JSON files from the API. These files get put in the static directory. In essence these files serve as the site’s API “server” so visitors will never actually hit my API services. This is working well for now, but I would like to see if I can skip this middle step.
The only other way I can imagine implementing this is by utilizing something like jinja2 or another “code generation” tool that would read the API and actually generate Svelte code which then would be built by Svelte.
Both of these solutions fall far from the tree of what I would consider a good, long-term solution. SvelteKit and pre-rendering already does everything I want except for that “hydrate everything again in the browser”. So as soon as I get a lever where I can specify what doesn’t need to be hydrated again in the browser, I would be golden. Perhaps similar to what Deno’s Fresh is calling “islands” which are separate files of code that denote what needs to be hydrated in the browser. Basically, component-level configuration to enable or disable hydrating. Right now, it seems like it’s either the entire page or the whole site or nothing.

@keehun you're asking for partial hydration. There's a ticket for that here: https://github.com/sveltejs/kit/issues/1390

Yes, thanks! I edited my comment to refer to that as I was reading that thread while you were reading my comment I think. Thanks!


Resolves #17, Resolves #18, Support --destination-dir --out-file

ping @matklad :wink:
So the following is supported:
-o foo/bar/baz/book.pdf

Will create foo, bar and baz directories (if they don't exist).
-o ''

Will output the result (pdf content) to the console
-D foo/bar/baz -o book.pdf

Will create foo, bar and baz directories (if they don't exist).
-o book.pdf

Will create a file named book.pdf
Please note that for now we do not remove the temporary HTML file (to ease development/debugging).
Also the temporary HTML file is always created next to the input file. So you don't have to update the relative paths when you want to output the PDF file somewhere else.

-o ''

Hm, shoudn't this be -o -?

-o ''

Hm, shoudn't this be -o -?

I need to try, maybe if it's supported by https://github.com/yargs/yargs but if it is then yes we should use -o - to be consistent with the Asciidoctor CLI.

Thanks for your review @matklad (greatly appreciated). I will update my pull request 👍

-o ''

Hm, shoudn't this be -o -?

@matklad It's working with -o - :tada:


Added capabilities to have async header functions

A big part of uploading is to validate that the data doesn't get corrupted. One way to do it is to do a checksum and send it to the server as a part of the headers. Most checksum functions are asynchronous and this change would allow these types of functions to be added to the Filepond headers.
Example:
const server = {
    url: '/api/http-upload/chunk',
    patch: {
      headers: async (chunk) => {
        const { data, file, offset } = chunk;

        const md5 = async () => await hashwasm.md5(new Uint8Array(await data.arrayBuffer()));

        return {
          'Content-Type': 'application/offset+octet-stream',
          'Upload-Offset': offset,
          'Upload-Length': file.size,
          'Upload-Name': file.name,
          'x-checksum-md5': await md5()
        };
      }
    }
  };

Excellent idea.
Can you move these outside of the Promise, I guess we can set them before applying the headers.
        // set type of response
        if (options.responseType) {
            xhr.responseType = options.responseType;
        }

        // set credentials
        if (options.withCredentials) {
            xhr.withCredentials = true;
        }


Unhandled JS Exception: TypeError

[info][tid:main][RCTBatchedBridge.m:72] Initializing <RCTBatchedBridge: 0x61800019aa90> (parent: <RCTBridge: 0x6000002bb2a0>, executor: RCTJSCExecutor)
2017-04-04 14:10:58.478 [warn][tid:com.facebook.react.JavaScript][RCTBatchedBridge.m:507] Failed to execute source code: Unhandled JS Exception: TypeError
2017-04-04 14:10:58.479 [fatal][tid:main] Unhandled JS Exception: TypeError
2017-04-04 14:10:58.480 iMusica[65976:4706659] -[RCTJSStackFrame objectForKeyedSubscript:]: unrecognized selector sent to instance 0x608000854e20

@hramos I'm curious why this was closed? I assume because of bad formatting, but it's unclear.
I'm having the exact same issue + found Stack Overflow post about it + this issue. Seems like a new bug in RN v0.43.

This is happening to me as well, only when I build for release :(

@cooperka issues that do not use the template are likely to be closed without explanation per https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md

Wow, harsh policy @hramos. Seems like it hurts new contributors... explanations are always nice (e.g. the link you just sent is all that's needed).

The text from the link I sent is what populates every new issue. The very first line outlines the policy. With 1,336 issues open as of this writing, we have to be a bit more aggressive if we want to get the issue tracker back on track.

In my experience, most people just delete that text and don't read it. The issue template in general is a bad UX (on GitHub's end), but personally I don't think it's an excuse to ignore members of the community when they likely don't even realize they've done something wrong. Simply pasting that link is very helpful and can save others time and frustration.
"Hi, your description is missing required details and is being automatically closed. Please submit a new issue following the  and we'll be happy to take another look."
Just my opinion.

Hello did anyone find any solutions to this. I'm suddenly started facing this issue previously it was working. I'm using Xcode 8.3.2 and react-native 0.44 and react 16.0.0-alpha.6. These are all my dependencies:
{
  "html-entities": "^1.2.1",
  "moment": "^2.18.1",
  "react": "16.0.0-alpha.6",
  "react-native": "0.44.0",
  "react-native-contacts": "^0.8.1",
  "react-native-elements": "^0.12.2",
  "react-native-extended-stylesheet": "^0.4.0",
  "react-native-linear-gradient": "^2.0.0",
  "react-native-vector-icons": "^4.1.1",
  "react-navigation": "^1.0.0-beta.9",
  "striptags": "^3.0.1"
}

and my devDependencies:
{
  "babel-core": "^6.17.0",
  "babel-eslint": "^7.1.0",
  "babel-jest": "19.0.0",
  "babel-plugin-transform-class-properties": "^6.24.1",
  "babel-preset-es2015": "^6.18.0",
  "babel-preset-react-native": "1.9.1",
  "babel-register": "^6.16.3",
  "eslint": "^3.9.1",
  "eslint-config-airbnb": "^14.0.0",
  "eslint-plugin-import": "^2.2.0",
  "eslint-plugin-jsx-a11y": "^3.0.2",
  "eslint-plugin-react": "^6.4.1",
  "eslint-plugin-react-native": "^2.3.1",
  "jest": "19.0.2",
  "jest-react-native": "^18.0.0",
  "react-test-renderer": "16.0.0-alpha.6"
}

The line at which it's saying I'm getting error is this on line 1246:
1237  babelHelpers.toConsumableArray = function (arr) {
1238    if (Array.isArray(arr)) {
1239      for (var i = 0, arr2 = Array(arr.length); i < arr.length; i++) {
1240        arr2[i] = arr[i];
1241      }return arr2;
1242    } else {
1243      return Array.from(arr);
1244    }
1245  };
1246  })(typeof global !== 'undefined' ? global : typeof self !== 'undefined' ? self : this);
1247  __d(/* ehfood/index.ios.js */function(global, require, module, exports) {'use strict';

@shahankit I have React navigation and React native vector icons as well. For some reason I'm leaning towards a React navigation bug? Just a hunch. No real evidence though :/ I'm debating creating a new project and pasting everything over when I have some time or if it's still an issue when my app launches.

Things got solved after running the packager with --reset-cache:
node node_modules/react-native/local-cli/cli.js start --reset-cache


Leaving blank characters when setting an input's value

When the user inputs data, any character position can be left blank, with a placeholder in place.
Eg.: With a mask **-**, the user may skip the first characters and leave the input as __-AA.
When setting the input's value via JS, I cannot leave blank positions. The mask removes them.
Eg.: $('input').inputmask( 'setvalue', '__-AA' ) or anything similar, simply becomes AA-__.
This would be useful in case I have an incomplete piece of information for the user to fill in, where I can leave some positions blank and others preset.

Looks like this is still an issue as of version 5.0.0-beta.266.  I have an input that needs a mask of '99-999-9999' where all, none or some of the digits can be filled, for example: '__-100-____'.
Aside from using setValue, the problem also exists when trying to initialize the mask when the input's value is already set to '__-100-____'.
In either case the resulting value is formatted incorrectly to '10-0__-____'.
I was able to workaround this issue by using a regex for the mask that allows underscore characters in addition to digits.  For this particular example, I'm using '[0-9_]{2}-[0-9_]{3}-[0-9_]{4}'.
Hopefully this is helpful for anyone else who stumbles on this issue!


boards: riscv: longan_nano: Enable GPIO configuration by default

It is a small improvement.
I fail to compile some samples referencing the GPIO feature indirectly via pinctrl.
Require enabling GPIO feature to compile these.
--
GPIO is used by pinctrl function,
which is used by various peripherals initialization.
We should enable GPIO by default.

Hi @soburi ,
I don't think this is correct. Take a look at #41550. If GPIO is required by PINCTRL, there is missing a select GPIO at PINCTRL Kconfig.
Try see this way, each Kconfig will enable a SW feature that not necessary will be always required to put board to run. I understand that a GPIO is mandatory at board, for instance, when you need enable a DC-DC controller. Otherwise Apps should define that. However, some driver may require GPIO driver like SAM's SPI. In that case, driver should select GPIO, not the board.

Hi, @nandojve
Thank you for checking this PR.

Hi @soburi ,
I don't think this is correct. Take a look at #41550. If GPIO is required by PINCTRL, there is missing a select GPIO at PINCTRL Kconfig.

I understood it better to enable GPIO in each function that using it.
I'll takedown this PR and reconsider to better way.

I used gd32vf103v_eval_defconfig as a reference to make this PR.
It may be better also verify it...
https://github.com/zephyrproject-rtos/zephyr/blob/b374dc6a7fd8f841394ad6cf2364c7ceef05f3c7/boards/riscv/gd32vf103v_eval/gd32vf103v_eval_defconfig#L11


fix(cache): coerce schema_cache_timeout to None

SUMMARY
Fixes #21827
When a database is created schema_cache_timeout  property is set to empty string by default inside extra_json (or at least this is the case for older versions). This leads to the following error when calling get_all_schema_names which exptects an optional integer. This PR fixes this error.
redis.exceptions.ResponseError: value is not an integer or out of range

Additionally, these params don't seem to be used in get_all_schema_names. So maybe the best course is to remove them all together.
TESTING INSTRUCTIONS
Without this, the SQL Lab shows an error when fetching schemas

When it comes to the removal of the cache_timeout, it is being accessed by the decorator: https://github.com/apache/superset/blob/750ee48c32880163455826d56526c876a498c7da/superset/models/core.py#L693


oracle connection string

Hi,
I have run this command
vd oracle+cx_oracle://usr:pws

And I have an error "Non-existent file or directory: 'oracle+cx_oracle://usr:pws'.
Probably I must check plugin installation

Try removing the +cx_oracle section of the url, visidata doesn't handle that format of connection string properly. SQLAlchemy defaults to using cx_oracle for Oracle databases as it is so you don't need to specify the driver that way.

I need to do a complex connection as the annoying case here https://gist.github.com/DGrady/7fb5c2214f247dcff2cb5dd99e231483#the-annoying-case
Then I have tried using
vd oracle://myuser:pwd@cx_Oracle.makedsn('<IP_ADDRESS>', '1521', service_name='name')

but I have bash: syntax error near unexpected token ('`
If I run vd oracle://myuser:pwd@cx_Oracle@name I have
Traceback (most recent call last):
  File "/home/andrea.borruso/.local/bin/vd", line 6, in <module>
    visidata.main.vd_cli()
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/main.py", line 213, in vd_cli
    rc = main_vd()
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/main.py", line 133, in main_vd
    vs = openSource(src)
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/vdobj.py", line 37, in _vdfunc
    return func(visidata.vd, *args, **kwargs)
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/data.py", line 157, in openSource
    return vd.openPath(Path(p), filetype=filetype)  # convert to Path and recurse
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/data.py", line 122, in openPath
    return getGlobals()[openfunc](p, filetype=filetype)
KeyError: 'openurl_oracle'

I'm able to connect to it via python in this way
import cx_Oracle
import sqlalchemy
import pandas as pd
from sqlalchemy import create_engine

oracle_connection_string = (
    'oracle+cx_oracle://{username}:{password}@' +
    cx_Oracle.makedsn('{hostname}', '{port}', service_name='{service_name}')
)

engine = create_engine(
    oracle_connection_string.format(
        username='myusr',
        password='pwd',
        hostname='<IP_ADDRESS>',
        port='1521',
        service_name='name',
    )
)

Thank you

bash: syntax error near unexpected token (

That makes me wonder if you'd be able to just surround your connection string with quotes, if you don't bash will interpret the parentheses as part of a bash command.
ie. run vd "oracle://myuser:pwd@cx_Oracle.makedsn('<IP_ADDRESS>', '1521', service_name='name')"

ie. run vd "oracle://myuser:pwd@cx_Oracle.makedsn('<IP_ADDRESS>', '1521', service_name='name')"

Now I have
Traceback (most recent call last):
  File "/home/andrea.borruso/.local/bin/vd", line 6, in <module>
    visidata.main.vd_cli()
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/main.py", line 213, in vd_cli
    rc = main_vd()
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/main.py", line 133, in main_vd
    vs = openSource(src)
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/vdobj.py", line 37, in _vdfunc
    return func(visidata.vd, *args, **kwargs)
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/data.py", line 157, in openSource
    return vd.openPath(Path(p), filetype=filetype)  # convert to Path and recurse
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/data.py", line 122, in openPath
    return getGlobals()[openfunc](p, filetype=filetype)
KeyError: 'openurl_oracle'

If I do the same for a MySQL db
 vd mysql://name:pwd@DB

I have the same kind of error
Traceback (most recent call last):
  File "/home/andrea.borruso/.local/bin/vd", line 6, in <module>
    visidata.main.vd_cli()
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/main.py", line 213, in vd_cli
    rc = main_vd()
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/main.py", line 133, in main_vd
    vs = openSource(src)
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/vdobj.py", line 37, in _vdfunc
    return func(visidata.vd, *args, **kwargs)
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/data.py", line 157, in openSource
    return vd.openPath(Path(p), filetype=filetype)  # convert to Path and recurse
  File "/home/andrea.borruso/.local/lib/python3.6/site-packages/visidata/data.py", line 122, in openPath
    return getGlobals()[openfunc](p, filetype=filetype)
KeyError: 'openurl_mysql'

So this is related to how Visidata imports plugins in general. I installed the plugin manually and then added the line from plugins.generic_sql import * to ~/.visidatarc. This adds the openurl_ functions to the visidata init namespace properly. Try adding that line to your .visidatarc and see if that resolves things.
I'm going to do a little digging in the Visidata repo to see if I need to edit how the plugin is exporting these function or if this is something Visidata itself will need to address.

WOW using mysql works!!!
Now I try with Oracle

It works, thank you very much!!!


Add iOS instructions

Fiixes #122
Summary
I was getting an error while doing Pod Install, so updated instructions to fix that.

Test Plan
pod install gives:
Analyzing dependencies
[!] The version of CocoaPods used to generate the lockfile (1.9.2) is higher than the version of the current executable (1.8.4). Incompatibility issues may arise.
Downloading dependencies
Installing FBLazyVector 1000.0.0
Installing FBReactNativeSpec 1000.0.0
Installing RCTRequired 1000.0.0
Installing RCTTypeSafety 1000.0.0
Installing React 1000.0.0
Installing React-Core 1000.0.0
Installing React-CoreModules 1000.0.0
Installing React-RCTActionSheet 1000.0.0
Installing React-RCTAnimation 1000.0.0
Installing React-RCTBlob 1000.0.0
Installing React-RCTImage 1000.0.0
Installing React-RCTLinking 1000.0.0
Installing React-RCTNetwork 1000.0.0
Installing React-RCTPushNotification 1000.0.0
Installing React-RCTSettings 1000.0.0
Installing React-RCTText 1000.0.0
Installing React-RCTVibration 1000.0.0
Installing React-callinvoker 1000.0.0
Installing React-cxxreact 1000.0.0
Installing React-jsi 1000.0.0
Installing React-jsiexecutor 1000.0.0
Installing React-jsinspector 1000.0.0
Installing React-perflogger 1000.0.0
Installing React-runtimeexecutor 1000.0.0
Installing ReactCommon 1000.0.0
Installing Yoga 1.14.0
Generating Pods project
Integrating client project
Pod installation complete! There are 52 dependencies from the Podfile and 42 total pods installed.

Will do @anku255 👍

@anku255 , please have a look again.

Merging it then.


Implement metadata editing for gardens

As a user, I want to see the gardens that I own so that I can keep track of/find them/edit metadata easily.
Assumptions

A user needs to be logged in to see this page
This should show all gardens that a user is an owner of
A user should be able to edit metadata when viewing their own gardens
Use designs from issues #102 and #103

I changed the name to be more intuitive.

This involves creating the "my gardens" component on the user profile page
Being able to edit metadata on a garden

set up communicating with the backend
implement designs from #102

Jamie writing the hooks for this, but backend is ready

In staging


Lectern bugs the player out

Timings link
https://timings.aikar.co/?id=705e86b90bf6460086fe7850408aa721
Expected behavior
You should be able to walk over Lectern.
Observed/Actual behavior
Getting stuck unable to move.
Steps/models to reproduce
If you walk over or by a Lectern with ur character you get stuck or start to lag.
Purpur version
git-Paper-25
Agreements

[X] I am running the latest version of Purpur available from https://purpur.pl3x.net/downloads.
[X] I have searched for and ensured there isn't already an open issue regarding this.
[X] My version of Minecraft is supported by Purpur.

Other
No response

git-Paper-25
Looks like this is meant for Paper's issue tracker.


Absurd! Quang missing basic Quang Utils.

Quangjs has been severely deprecated. How is my Quang iOS app supposed to take off now? I can no longer leverage Machine Learning and AI applications for real-time Quang analyses.

Kubernetes containment inside containers passing serverless lambdas upstream and cloud agnostic.


feat: UI Changed

UI Changed
🛠 Fixes Issue
Closes #914

👨💻 Changes proposed

✅ Check List (Check all the applicable boxes)

[x] You have linked this PR to the correct issue.
[x] My code doesn't break any part of the project (Zero Octave-Javascript-Projects).
[x] This PR does not contain plagiarized content.
[x] My Addition/Changes works properly and matches the overall repo pattern.
[x] The title of my pull request is a short description of the requested changes.

@Anmol-Baranwal  sir please merge this


slow start config makes few pods have no QPS for sometime.

Title: slow start config issues on few pods
Description:
So earlier before 1.22 there was a bug because of which the slow start was not working in most of the cases.
https://github.com/envoyproxy/envoy/issues/19526
Hence we have recently shifted to 1.24.
We are seeing much better improvements in the working of the config, but still sometimes there are few pods which doesn't behave like other pods.
Before upgrading:

From the above image you can see there are few pods at the bottom. They were coming up and down, because they were not given traffic and suddenly they were given a lot of traffic (this is my presumption). Since the RPM is recorded by the application metrics, I don't have those in a concrete since the application under sudden load doesn't yield metrics, hence I am monitoring using the CPU usages.
After upgrade and changing nothing else in the application or configuration:

We can see that it is still there but in a much less quantity.

On zooming further this is how the graphs look closely.
Wanted to understand if I am missing something, we have the default configuration only just that we have slow duration set to 180s

cc @nezdolik

@anuragagarwal561994 How many endpoints are there in the cluster? Slow start does not scale well with large number of endpoints, it is based on edf scheduler where hosts in slow start will have high deadline compared to regular hosts and picked up rarely. You could try to increase min_weight_percent, default is 10%. That would increase the weight of host in slow start up to a certain timepoint within slow start window and increase probability of host being selected by edf scheduler.


provide an easy way to diagnose CI / CD pipeline failures

we've been finding some builds sometimes fail inside a CI / CD pipeline but not on a users laptop. So it'd be nice if folks had a way to try diagnose build failures a little easier.
Ideally long term we'd turn a build pod into a Che Workspace that folks could just open. Though there's the issue that build pods tend to be composed (maven + clients + jnlp) whereas Che workspaces tend to be one single docker image with all the CLI tools there.
So maybe we just provide a way to let folks fork a failing pipeline and add a dummy input step into the pipeline before the failure line; then re-run that pipeline; then let folks kubectl exec -it nameOfPod -c containerName bash  then they can cd into the folder and run whatever commands they need etc.
I wonder if we can improve on this somewhat? e.g. automatically generating the PR for the build failure with the input added? Automating the CLI commands to ssh into the paused build pod, cd to the right folder and run the last failing command?

I think CloudBees has a pause/resume/retry thingy but its not available in the OSS version AFAIK

then to test out a build, folks could just run this pod YAML then kubectl exec into the pod?

should this issue be moved here https://github.com/fabric8io/fabric8-pipeline-library, this repo looks to be deprecated.

DOH!  I meant to do that sorry ;) lemme do that now

replaced with https://github.com/fabric8io/fabric8-pipeline-library/issues/318


503 Status Code from website

Hi,
I am completely new to all of this and ran into an issue I can't seem to solve on my own. (if this is not the correct place to ask for help please forgive me)
I downloaded and installed everything and in general it works as I need it. However, there is one website i did not get any response from. So I added this line to the code:
console.log("Status code: " + res.statusCode);
The total code looks like this (not very different from the suggestion given here):
var Crawler = require("crawler");
var c = new Crawler({
maxConnections : 10,
// This will be called for each crawled page
callback : function (error, res, done) {
if(error){
console.log(error);
}else{
console.log("Status code: " + res.statusCode);
var $ = res.$;
// $ is Cheerio by default
//a lean implementation of core jQuery designed specifically for the server
console.log($("title").text());
}
done();
}
});
// Queue just one URL, with default callback
c.queue('https://de.wikipedia.org/wiki/Parser');
It turns out I receive a 503 Status Code. It seems to be just this one website, every other I tried worked fine. I thought, that maybe someone could help me understand why just the one website does not respond. When I try accessing the URL in Chrome in works of course. So the server is actually available. The robots.txt also does not seem to prohibit the crawling if I understand correctly:
User-agent: BLEXBot
Disallow: /
User-agent: AhrefsBot
Disallow: /
User-agent: *
Disallow:
Sitemap: https://www.karriere.at/sitemaps-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-arbeitgebersuche-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-berufe-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-brutto-netto-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-firmen-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-firmen-standorte-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-firmen-bs-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-firmen-bs-work-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-firmen-bs-jobs-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-gehalt-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-hr-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-jobs-https.xml
Sitemap: https://www.karriere.at/static/sitemaps/sitemap-karriere-tipps-https.xml
Sitemap: https://www.karriere.at/blog/sitemap_index.xml
I would need the crawler to work for just this one website though, so any help is highly appreciated.

This is not what crawler can do, you should check your 'User-Agent' I guess

Close due to inactive


cawemo enterprise saas release: process linking - Post added

Added a new blog post about the latest Cawemo.com release
Made some minor changes to the previous cawemo blog post:

adjusting the category
adding a missing headline

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


bumps deployment targets versions

Trying to upgrade to the latest version, I've stumbled on 'create_directories' is unavailable: introduced in iOS 13.0 and 'path' is unavailable: introduced in iOS 13.0 errors in cpp/utils.cpp
Bumping deployment targets fixed that. Alternatively, reverting the changes would avoid the bump, but 12.0 is not supported by many libs (Expo, as an example), so seams also like a viable approach

Thanks for finding this out! yeah, iOS 12 is old by now and doesn't appear to be a significant user base portion. LGTM.