Problems Window - Error States "Unable to open: File not found"

Posted this in VS Code first and they said that this was a C# extension issue and to post here.
This happens every now and then but often enough. I'll be shown errors and clicking on some will state that the file does not exist. There is a duplicate set of the same errors from the same file below. Both show a slightly different path. Have no idea what's happening here.
Is this workaround what you have to do with every project to ensure you don't get this issue?
In the .csproj add true inside

VSCode Version: 1.33.1
OS Version: 1803

Steps to Reproduce:

Very hard to reproduce. Seems random. Been running the same .Net Core app all day. All of a sudden this happened.
Doesn't seem like it has steps to reproduce.
Occurs with all extensions disabled.

Does this issue occur when all extensions are disabled?:

@DanJ210 This sounds like a duplicate of https://github.com/OmniSharp/omnisharp-vscode/issues/1197 -- can you try the workaround discussed in that issue?

It sounds like the same issue. I suppose I can try the workaround.

Issue #1197 suggests this has now been fixed but I am still seeing the issues in v1.21.5 of the C# Extension

Cannot reproduce this with the current release.


retrieve predicted keypoints

Just for understanding:
Is there a possibility of retrieving the key points along with the bounding boxes?

Retinaface？https://github.com/bubbliiiing/retinaface-pytorch

Thank you for the response. The question was in the context of 3D objects. Is it possible to get the Keypoint information also?


Carthage

carthage support

@halseth thanks for submitting this.
Can this be reopened? Is there anything missing?

It was submitted by a mistake, but if you are interested I can create a new PR. It is for support with Carthage.

Yes I'm interested, please do :-)

On Oct 26, 2015, at 5:30 PM, halseth<EMAIL_ADDRESS>wrote:
It was submitted by a mistake, but if you are interested I can create a new PR. It is for support with Carthage.
—
Reply to this email directly or view it on GitHub.

will open a new one with the correct branch


support recursive autocomplete

I have idea for a new feature for jQuery Terminal
When user press TAB for autocomplete for this current directory, after pressing '/' we will run function to calculate the next folder sub-directories / files and TAB will present the new data for this folder.
If the user removes the '/' from the command-line, reverse the auto-compete to the previous array of the current folder data.

It will be hard to do on top of the terminal, you will never know if user typed whole command by hand or using completion, deleting "/" and removing everything to previous slash may be confusing.
But of course you can implement your own tab completion that will work just like you want. There are two API functions .complete() and .before_cursor() that you can use and change TAB keymap to implement your own completion. You will also need to add keydown and implement backspace.

I added keybinding to /, and when the user press / I calculate the next folder content and add it to the completion array concatenated with the current path(for example: if I am in /var and I have all it content, and I chose to auto-complete the folder foo, then the user press /, I calculate all /var/foo/ content and add it like: /var/foo/NEW_CONTENT to the completion array, now it contain all /var and /var/foo content). You can add another array that responsible only for the next auto-complete, and when the user press / it call to function to calculate it and change it value.

This is something very non standard, do you have any example application that work like this? If you want to modify the the next completion you can just add something like this:
var completion = [];
keymap: {
  '/': function() {
       // modify completion array
  }
},
completion: function() {
   return completion;
}

you don't need any extra code in the library to modify next completion after you press /.

Yes this is a great idea!
I implemented this just as @jcubic suggested, but the problem is that the autocomplete now expects files in sub-directories to start with the directory name.
For example, if i have a file named "exFile" in a folder named "exDir" I'd have to add it to the autocomplete array as "exDir/exFile" instead of just "exFile".
Basically I'm trying to simulate how auto completion in a real terminal would work and this is obviously one of the things any terminal would do.

Yes, this is exactly what I did, but if you start writing the first folder (for example: foo) and press / and your function modified the completion array, the TAB doesn't auto-complete the next folder content because the new completion not start with foo/...

When I have time I will create example, you just need to modify the completion so the array have foo in front, not just push the value to the array.

The other solution is to write everything in completion function and parse what user typed, see how this works in my GIT Web Terminal. where cd complete the whole directory structure.
https://github.com/jcubic/git/blob/gh-pages/js/main.js#L1381

You can test completion in GIT Web Terminal at https://jcubic.github.io/git/
type:
git clone https://github.com/jcubic/jquery.terminal.git

and try cd "jqu" TAB ".g" TAB


telegram-text v0.1.1

Codecov Report
Base: 93.40% // Head: 93.01% // Decreases project coverage by -0.39% :warning:

Coverage data is based on head (1f588f8) compared to base (9ed12ba).
Patch coverage: 95.65% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #23      +/-   ##
==========================================
- Coverage   93.40%   93.01%   -0.40%
==========================================
  Files           6        6
  Lines         182      186       +4
==========================================
+ Hits          170      173       +3
- Misses         12       13       +1

Impacted Files
Coverage Δ

telegram_text/bases.py
85.91% <83.33%> (-0.66%)
:arrow_down:

telegram_text/__init__.py
100.00% <100.00%> (ø)

telegram_text/elements.py
96.96% <100.00%> (ø)

telegram_text/markdown.py
100.00% <100.00%> (ø)

telegram_text/styles.py
96.55% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


docs(two-column-layout-example): add datasets

Summary
This PR adds the datasets (records, settings, and rules) used for the two-column layout example as JSON files in the example folder.
Right now, the datasets are hosted on Algolia’s latency application, and therefore, you can't use them to create your own indices.
List of all the files:
Products (records, settings, and rules)
Note: The number of records has been reduced to 500 products to keep the JSON file size acceptable.

products.json
products_settings.json
products_rules.json

Product query suggestions (records and settings)

products_query_suggestions.json
products_query_suggestions_settings.json

FAQ (records)

faq.json

Articles (records)

articles.json

Would it make more sense to add those to https://github.com/algolia/datasets/?
This way we don't add weight to the repo.

We discussed this point with @seafoox, we think these datasets are tight to the example (fake FAQ and articles for examples) and not generic enough yet to be added to the datasets repository, so we think it makes more sense to add them within the example folder.
Right now, the total weight for the datasets folder is 1.4 MB, if weight is a concern, I can lower it down by removing more products.
WDYT?

@FabienMotte Could we try to find a better name for this flagship code sample which people internally / externally could easily refer to without confusion? My understanding is that it's not just about the two columns here, for which we already have a demo, right?
I was thinking about something eg. "Ecom rich federated example", but would love additional inputs from the team about its name, so we name it right.

Thanks for sharing your thoughts!
Closing this in favor of https://github.com/algolia/datasets/pull/12


Can't override base_url to connect to local PubSub simulator

GoogleApi.PubSub.V1.Connection
uses:
plug Tesla.Middleware.BaseUrl
instead of
Tesla.Middleware.BaseUrlFromConfig
As a result, it's impossible to try and direct commands to the local Pubsub simulator.

Thanks, for the report.
It looks like BaseUrlFromConfig is being removed from Tesla so we'll need to find a different approach to allow configuring the base url.

FWIW, Tesla, like Faraday that it's based on, introduced a ton of complexity for what looked like very little value. Perhaps with this swagger code generator you have there's something it adds, but I'd personally consider dropping it in favor of using the HTTPoison.Base macro instead.  Short of that, it looks like tesla needs to be flexible enough to take it's various plug parameters as function definitions, and invoke them at runtime to allow things to be configurable.  ¯_(ツ)_/¯

We just released new versions of the client libraries which includes the fix from #81


Remove obsolete note

This PR

removes an obsolete note concerning adoption. The note referenced NEP 37; however, that proposal has not seen the requisite movement necessary to change either the specification's use of __array_namespace__ or the experimental implementation in NumPy. Accordingly, this PR chooses to remove the note to avoid creating any uncertainty regarding the preferred mechanism of exposing a conforming array implementation as a separate namespace.

cc @rgommers for visibility.

Will merge. If further changes are necessary, they can be made in follow-up PRs.


Add README

This is my first pass at the basic README so far.  Let's see what else we think is needed.

I think the GitHub Action checks are not running automatically.  If I had to guess it's because we need to enable non-Homebrew actions but I'm not sure.

The workflow is not running because of the paths defined. You only modified README here and this file does not fall into what is defined in workflow triggers.


Fix: SQLAlchemyDTO default handling with Sequence defaults.

Fixes handling of columns defined with Sequence default values.
This PR ignores the SQLAlchemy default value for a Column when it is a Sequence object. This is because the SQLAlchemy sequence types represent server generated values, and there is no way for us to generate a reasonable default value for that field from the Sequence object without making a database query, which we cannot do during deserialization.
Closes #1851
Supersedes #1864
Pull Request Checklist

[ ] New code has 100% test coverage
[ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR

Description
Close Issue(s)

@MatthewNewland this is based off your branch - so all your commits will still be attributed.


Redisson concurrent locking may occasionally cause one of the threads to acquire a timeout, resulting in lock failure

Expected behavior
Concurrent locking theoretically means that after one thread locks and releases the lock, another thread should be able to acquire the lock
Actual behavior
The phenomenon we see now is that after one thread in production locked and released, another thread did not acquire the lock (occasionally)
Steps to reproduce or test case
In the tryLock (long waitTime, long leaseTime, TimeUnit) method of redisson, is there a situation where the semaphore for the first thread to release the lock has been issued, but the other thread has not yet established a subscription relationship, resulting in the following logic not waiting for notification?
...... current = System.currentTimeMillis();         CompletableFuture<RedissonLockEntry> subscribeFuture = subscribe(threadId);         try {             subscribeFuture.get(time, TimeUnit.MILLISECONDS);         } catch (TimeoutException e) { .......
Redis version
5.0
Redisson version
3.17.6 & 3.19.3
Redisson configuration

Make sure that it's not the same thread. Since the lock is reentrant.

Make sure that it's not the same thread. Since the lock is reentrant.

is there a situation where the semaphore for the first thread to release the lock has been issued, but the other thread has not yet established a subscription relationship, resulting in the following logic not waiting for notification?

No, since a new attempt is made right after subscription.

My question is that before the second thread subscribes, the first thread has already released the lock and published the event of releasing the lock. Will the second thread not receive notification of releasing the lock in the following code, resulting in continuous blocking?
CompletableFuture<RedissonLockEntry> subscribeFuture = subscribe(threadId);

If it's subscribed after the event was published then it won't get a notification. I don't see the reason of continuous blocking here.

Perhaps it's not the reason for this code. Today, we tested in a testing environment and applied for locks on 10000 locks simultaneously within one minute, with each lock being applied for four times by different threads. In this scenario, it is common for some threads to acquire locks and timeout every time. Is it normal for lock timeout to occur in this concurrency scenario? We use write locks.

Our locking code is roughly like this:
RLock lock = redissonClient.getReadWriteLock(key).writeLock(); boolean lockSuccess = lock.tryLock(waitTime, LEASE_TIME, TimeUnit.MILLISECONDS);


fix: image disortion on privacy policy page 🧑🏻🏭🛠

Close #1300

Description

Fixed the image disortion on privacy policy page

Screenshots

FIRST SECTION
SECOND SECTION

Checklist:

[x] I have linked the PR to the correct issue.
[x] I have read the Contribution Guidelines
[x] I have built and tested the changes, and they do not break or show any errors.

@Vaishnavi-Patil2211 Please merge this PR.


Documentation formatting

8 or spaces of indentation create a code block in markdown, but wasn't intended

good catch. Indenting it into the blocks seems to improve readability in the source thoug ;-) I think the way I've changed it now is best readable in source and working as markdown.


Update bindings_intro with updated steps

I installed a clean venv:
py -m venv venv
venv\Scripts\activate.bat
pip install -r requirements-dev.txtp

And with this, I could run external\imgui_md\bindings\generate_imgui_md.py.
The step of installing srcML does not seem to be needed anymore.

Hi,
This is perfect, thanks a lot. I'm happy to see that you discovered the generator!
In fact, I did recently make the installation of the generator much easier, together with some nice doc. This is why it is not required to install srcML anymore (since I provide a native wheel that encapsulates it).

Hi,
This is perfect, thanks a lot. I'm happy to see that you discovered the generator! In fact, I did recently make the installation of the generator much easier, together with some nice doc. This is why it is not required to install srcML anymore (since I provide a native wheel that encapsulates it).

Thanks!


[Feature Request] Visible indicators for Covers

hey, thanks for the package, it's super cool and i hope to use it. the name was a bit strange (much + light = ??) but it makes sense with the projector lore.
when 1. attending lectures and viewing them asynchronously, as well as in a recording, i am at times caught off-guard by the introduction of elements in the fashion which is available at present, with Cover or with Only, which seems to exacerbate this issue as there are no animations which may guide the viewer (i.e. me) as to where  the content will be, and 2. when a prof or someone has an empty slide that starts with like one large bullet point, a large title, a small title, a large sentence, a small sentence (size here refers to the area it occupies on a slide, not length) it is ambiguous how much content there will be on the slide (by the end of sort of revealing or showing all the content) which, in a time-constrained environment causes explainability to suffer (fighting with technology doesn't help...)  as there is no visual indicator with which i can gauge prior to the reveal of the whole or entirety of the slide.
i suppose i could share mockups if you'd like, in order to get the meaning across if i haven't communicated it well.
vis-à-vis solutions; i was thinking some kind of filter with some of the following qualities in part or in conjunction: blurring/diffuse effect, a rounded light grey (or other color) rectangle sort of like how censored stuff or confidential cia stuff looks but less harsh and less distracting, i have other stuff but i think i've written enough...

#91 might be part of what you would like. Blurring filters etc. are currently not supported by Typst. Similarly, proper animations are not something you can do with PDFs.
I am closing this issue for now. Feel free to reopen it or add another comment if you feel like more discussion is needed.


add merge filter

something with a '=' in the arg, like:
--filter 'event_description="3x3 CFOP"'

added in<PHONE_NUMBER>2a55d7baaffc940067929dc2db620f


all: announce end of support for old Linux versions

New Linux versions get released over time, and old ones cannot be supported indefinitely. This is the tracking recurring issue for announcing end of support for very old versions that we decide to drop support for. (The corresponding tracking issues for macOS and Windows, the other two OSes that have first class ports, are #23011 and #52188.)
The most recent change was applied in Go 1.18, where proposal #45964 increased the minimum Linux kernel version requirement from 2.6.23 to 2.6.32. See https://go.dev/doc/go1.18#linux.
CC @golang/release.

Just a note that the case for Linux is a bit different than that for macOS and Windows, as Linux does not have a sole vendor.  We need to identify organizations that distribute older versions of Linux that are supported and used.  For example, I believe that we should continue to support all versions of Linux that are actively supported by commercial organizations, such as RHEL or Suse Linux Enterprise Server, and also all versions of Linux that are actively supported by communities supporting stable versions, such as Rocky Linux.  Of course the nature of Linux is such that the set of active organizations changes over time.

3.10 could be a reasonable target.
For reference some facts about distros, and the kernel changes tangential to Go and userland.
Centos 7 - Linux 3.10
Centos 7: Released: 2014-07-07 , Full updates ended: 2020-08-06, Maintenance updates EOL:  2024-06-30
(Centos 8 is in maintenance for about a year now, and Centos 9 is current version)
Debian 9 - Linux 4.9
Debian 9.0 (codename Stretch) was initially released on June 17th, 2017. Last major update was Debian 9.13 was released [July 18th, 2020. Stretch had Long Term Support (LTS) until the end of June 2022.
Current stable Debian is version 12.2. So Debian 9.x is really ancient actually.
Debian 8 (Jessie), from 2015, had Linux 3.16.7-ckt9 in the 8.0
Ubuntu 16.04.7 LTS (initial relase of 16.04 - 2016-04-21; with latest minor bump 16.04.7 - August 13, 2020) - End of standard support: April 2021, EOL: April 2026
OpenSUSE 13.1, released 2013-11-19, end of life 2016-01, Linux 3.11.6
Oracle Linux 7 - initial release, Jul 2014, about same time as RHEL 7/ Centos. Extended support, Jun 2026. But if you pay, they will support you indefinitively (even on older version than 7), and it is likely there are people having such support in various industries.
Also of note is that Oracle Linux 6.x, latest release, 6.10 from July 2018, has updated kernels, including 4.1.12, 2.6.39, and not just 2.6.32 (as RHEL 6).
These are the major ones that might be running and be sometimes hard to upgrade. Other distributions are more desktop and normal user focused, and update way faster, and earlier, and do not have LTS often. So it is close to 0% they would use old system or kernel.
For example, 3.10 would be like 20 major releases ago in world of Fedora, or Ubuntu.
The biggest risk would be probably various mobile and embedded arm devices, like Android, SBCs, routers, etc.
Linux 3.10 was release 30 June 2013, and was 10th LTS release. EOLed November 2017. Red Hat was maintaining own version of 3.10 (with backports from newer kernels, including some syscalls that were not originally in any upstream 3.10 release)  until very recently.
Personally, I do not use any of these ancient systems. (Where I work, we migrated from Centos 7, about 2.5 years ago, and almost migrated from Centos 8 to Centos 9 to, already on some parts of our infra, but migrate on demand slowly instead). In other places, I run Debian 12, and still few Debian 11 systems, that could be updated anytime, but just wait their time.
Notable features added between 2.6.32 and 3.10, that might be semi related to userland go runtime
3.10:

memory mapped netlink I/O
Add new "perf mem" command for memory access profiling
POSIX and high-resolution timers support a new clock (CLOCK_TAI) which operates in international atomic time
Applications within control groups can now request memory pressure notifications when the system is running low on available memory
Make madvise(MADV_WILLNEED) support swap file prefetch

3.9

TCP and UDP sockets have a new option, SO_REUSEPORT, that allows multiple sockets listening for new connections or packets (respectively) at the same time
The PowerPC architecture supports a new set of transactional memory instructions; at this time, only user-space support is provided

3.8  (2012)

Support more page sizes for MAP_HUGETLB/SHM_HUGETLB, as some large applications want to use 1GB huge pages on some mappings
tmpfs: support SEEK_DATA and SEEK_HOLE lseek() flags
perf: x86: Make hardware event translations available in sysfs /sys/devices/cpu/events/
SCTP: support per-association statistics
386 support dropped. Minimum is 486
The ptrace() system call has a new option flag, PTRACE_O_EXITKILL, which causes all traced processes to receive a SIGKILL signal if the tracing process exits unexpectedly.

3.7

TCP Fast Open (server side)  (Client side on Linux 3.6)
The epoll_ctl() system call supports a new EPOLL_CTL_DISABLE operation to disable polling on a specific file descriptor.
Applications on the s/390 architecture can now make use of the System zEC12 hardware transactional memory feature.
perf trace, an alternative to strace
Providing protocol type via system.sockprotoname xattr of /proc/PID/fd entries (commit)
default loopback interface MTU raised to 64K
Add generic netlink support for tcp_metrics

3.6

TCP Fast Open (Client side)

3.5

Introduce /proc//task//children entry, which provides information about task children
Report file/anon bit in /proc/pid/pagemap
epoll(): Add a flag, EPOLLWAKEUP, to prevent suspend while epoll events are ready
fuse: add fallocate() operation

3.4

The pipe2() system call permits a new flag, O_DIRECT, that creates a pipe that operates in "packet" mode. Each write() to the pipe creates a distinct packet, and each read() reads exactly one packet
The new PR_SET_CHILD_SUBREAPER prctl() operation allows userspace service managers/supervisors mark itself as a sort of 'sub-init', able to stay as the parent for all orphaned processes created by the started services. All SIGCHLD signals will be delivered to the service manager
Mark thread stack correctly in proc//maps
Implement IP_UNICAST_IF and IPV6_UNICAST_IF socket options  - This is mostly for Wine tho
Introduce the SO_PEEK_OFF sock option, implemented for datagram, seqpacket and stream sockets
MSG_TRUNC support for dgram sockets
Add missing getsockopt for SO_NOFCS

3.3

Android merge
Add BLKROTATIONAL ioctl, which permits applications to query whether a block device is rotational
Add a few /proc entries and prctl() codes to future checkpoint/restart support

3.2

sysctl: add support for poll()
Cross memory attach
ipv4: gc_interval sysctl removed
Support for transmission of IPv6 packets as well as the formation of IPv6 link-local addresses and statelessly autoconfigured addresses on top of IEEE 802.15.4 networks
crypto: Add userspace configuration API

3.1

tcp: Lower the default initRTO from 3secs to 1sec, as per RFC2988bis. It falls back to 3secs if the SYN or SYN-ACK packet has been retransmitted, AND the TCP timestamp option is not on
tcp: Compute protocol sequence numbers and fragment IDs using MD5 instead of MD4, as is inline with both RFC1948 and other OS
Add SEEK_HOLE and SEEK_DATA flags in lseek()
ptrace: implement PTRACE_INTERRUPT  PTRACE_LISTEN , PTRACE_SEIZE , TRAP_NOTIFY
ipc: introduce shm_rmid_forced sysctl
x86: vsyscall emulation rework, and boot options to disable

3.0

sendmmsg
BPF JIT
Unprivileged ICMP_ECHO
setns() syscall
Alarm timers
tmpfs: implement generic xattr support
Allow no-cache copy from user on transmit
sctp: implement socket option SCTP_GET_ASSOC_ID_LIST, implement event notification SCTP_SENDER_DRY_EVENT
cgroups; remove the Namespace cgroup subsystem. It has been replaced by a compatibility flag 'clone_children', where a newly created cgroup will copy the parent cgroup values. The userspace has to manually create a cgroup and add a task to the 'tasks' file; Make 'procs' file writable

2.6.32 - 2.6.39 - Various / A lot / Not listed here.
I also looked at some man pages, and found few bits, for Linux above 2.6.32:
vdso:
   aarch64 functions
       The table below lists the symbols exported by the vDSO.
       symbol                   version
       ──────────────────────────────────────
       __kernel_rt_sigreturn    LINUX_2.6.39
       __kernel_gettimeofday    LINUX_2.6.39
       __kernel_clock_gettime   LINUX_2.6.39
       __kernel_clock_getres    LINUX_2.6.39

syscalls:
       bpf(2)                      3.18
       clone3(2)                   5.3
       close_range(2)              5.9
       copy_file_range(2)          4.5
       epoll_pwait2(2)             5.11
       execveat(2)                 3.19
       faccessat2(2)               5.8
       finit_module(2)             3.8             ireelavant (this is mostly for Android for loading kernel modules)
       fsconfig(2)                 5.2
       fsmount(2)                  5.2
       fsopen(2)                   5.2
       fspick(2)                   5.2
       get_tls(2)                  4.15          ARM OABI only, has __ARM_NR prefix
       getrandom(2)                3.17
       io_pgetevents(2)            4.18
       io_uring_enter(2)           5.1
       io_uring_register(2)        5.1
       io_uring_setup(2)           5.1
       kcmp(2)                     3.5
       kern_features(2)            3.7           SPARC64 only
       kexec_file_load(2)          3.17       irrelevant
       landlock_add_rule(2)        5.13    irrelevant
       landlock_create_ruleset(2)  5.13    irrelevant
       landlock_restrict_self(2)   5.13    irrelevant
       membarrier(2)               3.17
       memfd_create(2)             3.17
       memfd_secret(2)             5.14
       move_mount(2)               5.2
       name_to_handle_at(2)        2.6.39
       open_by_handle_at(2)        2.6.39
       open_tree(2)                5.2
       openat2(2)                  5.6
       or1k_atomic(2)              3.1           OpenRISC 1000 only
       pidfd_getfd(2)              5.6
       pidfd_send_signal(2)        5.1
       pidfd_open(2)               5.3
       pkey_alloc(2)               4.8
       pkey_free(2)                4.8
       pkey_mprotect(2)            4.8
       preadv2(2)                  4.6
       prlimit64(2)                2.6.36
       process_madvise(2)          5.10
       process_vm_readv(2)         3.2
       process_vm_writev(2)        3.2
       pwritev2(2)                 4.6
       quotactl_fd(2)              5.14
       recvmmsg(2)                 2.6.33
       riscv_flush_icache(2)       4.15          RISC-V only
       rseq(2)                     4.18
       s390_runtime_instr(2)       3.7           s390 only
       s390_pci_mmio_read(2)       3.19          s390 only
       s390_pci_mmio_write(2)      3.19          s390 only
       s390_sthyi(2)               4.15          s390 only
       s390_guarded_storage(2)     4.12          s390 only
       sched_getattr(2)            3.14
       sched_setattr(2)            3.14
       seccomp(2)                  3.17
       sendmmsg(2)                 3.0
       setns(2)                    3.0
       statx(2)                    4.11
       switch_endian(2)            4.1           PowerPC64 only
       syncfs(2)                   2.6.39
       userfaultfd(2)              4.3

Extra syscall options:
mmap

       MAP_SHARED_VALIDATE (since Linux 4.15)
       MAP_FIXED_NOREPLACE (since Linux 4.17)
       MAP_HUGE_2MB, MAP_HUGE_1GB (since Linux 3.8)
       MAP_SYNC (since Linux 4.15)
       MAP_UNINITIALIZED (since Linux 2.6.33)            irrelevant, requires special kernel config, for embeded single-user devices

open

       O_PATH (since Linux 2.6.39)
       O_TMPFILE (since Linux 3.11)

Since  Linux  2.6.33,  proper  O_SYNC support is provided.

Since Linux 6.1, O_DIRECT support and alignment restrictions for a file can be queried using statx(2), using the STATX_DIOALIGN flag.

linkat

       AT_EMPTY_PATH (since Linux 2.6.39)

execve

can no longer fail with EAGAIN error (i.e. due to switching to a different user, and exhausting max number of processes limits).

clone3 options

               u64 set_tid;      /* Pointer to a pid_t array
                                    (since Linux 5.5) */
               u64 set_tid_size; /* Number of elements in set_tid
                                    (since Linux 5.5) */
               u64 cgroup;       /* File descriptor for target cgroup
                                    of child (since Linux 5.7) */

flag masks

       CLONE_CLEAR_SIGHAND (since Linux 5.5)
       CLONE_INTO_CGROUP (since Linux 5.7)
       CLONE_NEWCGROUP (since Linux 4.6)
       CLONE_NEWUSER  semantic fianlized between 2.6.23 and 3.5
       CLONE_PIDFD (since Linux 5.2)

returns:

EINVAL and and some other could be returned, some in relation to new flags, or to previously unhandled wrong combinations of flags.

       epoll_pwait2() was added in Linux 5.11.

epoll_ctl

       EPOLLWAKEUP (since Linux 3.5)
       EPOLLEXCLUSIVE (since Linux 4.5)

clock_gettime

       CLOCK_REALTIME_ALARM (since Linux 3.0; Linux-specific)
       CLOCK_TAI (since Linux 3.10; Linux-specific)
       CLOCK_BOOTTIME (since Linux 2.6.39; Linux-specific)
       CLOCK_BOOTTIME_ALARM (since Linux 3.0; Linux-specific)

   preadv2() and pwritev2()  # preadv2() and pwritev2() first appeared in Linux 4.6.
       RWF_DSYNC (since Linux 4.7)
       RWF_HIPRI (since Linux 4.6)
       RWF_SYNC (since Linux 4.7)
       RWF_NOWAIT (since Linux 4.14)
       RWF_APPEND (since Linux 4.16)

sendmsg

       MSG_FASTOPEN (since Linux 3.7)

recvfrom

      MSG_TRUNC (since Linux 2.2)
              For raw (AF_PACKET), Internet datagram (since Linux 2.4.27/2.6.8), netlink (since Linux 2.6.22), and UNIX datagram (since Linux 3.4) sockets: return the real length of the packet or datagram, even when it was longer than the passed buffer.

setsockopt

       TCP_USER_TIMEOUT (since Linux 2.6.37)
       TCP_FASTOPEN (since Linux 3.6)
       TCP_FASTOPEN_CONNECT (since Linux 4.11)

       SO_ATTACH_FILTER (since Linux 2.2), SO_ATTACH_BPF (since Linux 3.19)
       SO_BINDTODEVICE  (can do getsockopt since Linux 3.8)
       SO_DETACH_FILTER (since Linux 2.2), SO_DETACH_BPF (since Linux 3.19)
       SO_ATTACH_REUSEPORT_CBPF, SO_ATTACH_REUSEPORT_EBPF
       SO_INCOMING_NAPI_ID (gettable since Linux 4.12)
       SO_PEEK_OFF (since Linux 3.4)
       SO_REUSEPORT (since Linux 3.9)
       SO_RXQ_OVFL (since Linux 2.6.33)
       SO_SELECT_ERR_QUEUE (since Linux 3.10)
       SO_BUSY_POLL (since Linux 3.11)

       IP_BIND_ADDRESS_NO_PORT (since Linux 4.2)
       IP_NODEFRAG (since Linux 2.6.36)

The prlimit() system call is available since Linux 2.6.36.

mlock2() is available since Linux 4.4

MCL_ONFAULT (since Linux 4.4)

Some limit account bugs fixed in 4.9

pkey_mprotect() first appeared in Linux 4.9

futex

       FUTEX_LOCK_PI2 (since Linux 5.14)

timerfd_create

can use boottime and realtime alarm / clocks

              TFD_IOC_SET_TICKS (since Linux 3.17)

sendfile

       Before Linux 2.6.33, out_fd must refer to a socket.  Since Linux 2.6.33 it can be any file.  If it is a regular file, then sendfile() changes the file offset appropriately.  (Just like in 2.4.x and earlier).

copy_file_range

Since 5.19, can use for cross-filesystems copy, if src and dst file systems are the same and support it

Significantly improved error return codes in 5.3 and 5.19

pipe2

       O_DIRECT (since Linux 3.4)

O_NOTIFICATION_PIPE
              Since Linux 5.8,

fcntl

       F_SETPIPE_SZ (int; since Linux 2.6.35)
       F_GETPIPE_SZ (void; since Linux 2.6.35)

       F_ADD_SEALS (int; since Linux 3.17)
       F_GET_SEALS (void; since Linux 3.17)
       F_SEAL_FUTURE_WRITE (since Linux 5.1)

       F_GET_RW_HINT (uint64_t *; since Linux 4.13)
       F_SET_RW_HINT (uint64_t *; since Linux 4.13)
       F_GET_FILE_RW_HINT (uint64_t *; since Linux 4.13)
       F_SET_FILE_RW_HINT (uint64_t *; since Linux 4.13)
       RWH_WRITE_LIFE_NOT_SET
       RWH_WRITE_LIFE_NONE
       RWH_WRITE_LIFE_SHORT
       RWH_WRITE_LIFE_MEDIUM
       RWH_WRITE_LIFE_LONG
       RWH_WRITE_LIFE_EXTREME

Lost locks on NFSv4 mounts, are correctly detected in 3.12 in all cases, when using default nfs kernel module params.

statfs

       ST_NOSYMFOLLOW (since Linux 5.10)

       From Linux 2.6.38 up to and including Linux 3.1, fstatfs() failed with the error ENOSYS for file descriptors created by pipe(2).

Thanks for the suggestion above.
We've entered the release freeze for 1.22 and there aren't announcements to make for this release, moving to the next for now.

FWIW, it looks like Rust bumped their minimum Linux version to 3.2 last year, to align with glibc:

The new baseline requirements were picked as the least common denominator among long-term-support distributions that still have active support. This is currently RHEL 7 with glibc 2.17 and kernel 3.10. The kernel requirement is picked as 3.2 instead, because this is the minimum requirement of glibc itself, and there is little relevant API difference between these versions.

https://blog.rust-lang.org/2022/08/01/Increasing-glibc-kernel-requirements.html

Filed https://github.com/golang/go/issues/67001 for Linux 3.2.

CL 589015 added a pre-announcement to Go 1.23 release notes. Moving to the next milestone.

CL 622015 added an announcement to Go 1.24 release notes. CC @cagedmantis. Moving to the next milestone, unless there's more I missed.


There is a latency of approx. 2 seconds in video call

I am working on the sample code of video chat and I noticed a voice/video reaches after 2 seconds on the other side.
this is my configuration:
static MEDIA_OPTIONS = {
audio: true, video: {
facingMode: 'user',
width: { min: 144, ideal: 1280, max: 1980 },
height: { min: 176, ideal: 720, max: 1080 }
}
};

Is it p2p or Conferencing code sample?

It is p2p, just 2 person

this one? https://github.com/ConnectyCube/connectycube-reactnative-samples/tree/master/RNVideoChat
you are trying to use HD quality,
could you try some SD/LD and let us know how it works

Yes I am using sample code from [https://github.com/ConnectyCube/connectycube-reactnative-samples/tree/master/RNVideoChat]
these are configuration that I have tested:
static MEDIA_OPTIONS = {
   audio: true, video: {
     facingMode: 'user',
     width: 1980,
     height: 1080
   }
};

 static MEDIA_OPTIONS = {     audio: true, video: {       facingMode: 'user',       width: Dimensions.get("window").width,       height: Dimensions.get("window").height     }   };
 static MEDIA_OPTIONS = {     audio: true, video: {       facingMode: 'user',       width: 144,       height: 176     }   };
But still, I am facing latency of at least 2 seconds which increases with time.
Moreover, my internet bandwidth is: download: 10.7mbps  upload: 1mbps.
While video chatting internet speed (consumption as shown on the status bar) is 30kbps to 70kbps on the basis of quality, whereas while playing youtube video speed is 500+ kbps (for HD)

Closed due to inactivity. Please create a new issue if needed.


Terrible mistake on default service settings

According to the documentation every time you create a new SQL server on Azure there are few services coming as default ON.
"Enable automatic tuning on server
On the server level you can choose to inherit automatic tuning configuration from "Azure Defaults" or not to inherit the configuration. Azure defaults are FORCE_LAST_GOOD_PLAN is enabled, CREATE_INDEX is enabled, and DROP_INDEX is disabled."
I have just create a new server and the settings by default are different as the documentation points it out:
FORCE_LAST_GOOD_PLAN is enabled
CREATE_INDEX is disabled
DROP_INDEX is disabled
This is terrible due to the exam DP-200 is based on the documentation but my hands-on experience tell me otherwise, so what the heck here Microsoft?

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

ID: 5ef45327-7cdf-fc60-2a04-b785bc12f4cf
Version Independent ID: b4f8c915-9651-14df-92d7-fa1387780a41
Content: Enable automatic tuning - Azure SQL Database
Content Source: articles/sql-database/sql-database-automatic-tuning-enable.md
Service: sql-database
Sub-service: performance
GitHub Login: @danimir
Microsoft Alias: danil

@AndresUrregoAngel please provide a link to the document which you are following so that we can help fix this.

Over this link the documentation is wrong : https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automatic-tuning-enable
Now , here you point out that from March 2020 there is a new behavior over the CREATE_INDEX: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automatic-tuning
Now the million question which one should I pick if this come into my DP-200 exam? thanks @MarileeTurscak-MSFT

@AndresUrregoAngel Thank you for bringing this to our attention. It appears the screen capture provided in the document needs to be updated. Here are the default values for both server level and database level.
Server Level:

Database Level: (Inherited from Server)

Let me have the content team review this and make an appropriate update.

@AndresUrregoAngel On the main Automatic Tuning page, there is a HUGE announcement that these settings will be changed in March, there was also an official Azure update, so this is expected. The settings are being rolled out gradually to millions of databases. Once all settings land in, all pages will be updated.

Guys I totally get it we can fix it quickly , now my question more towards what should I do in the DP-200 exam in the case the configuration at server level will still consider the previous configuration, should I rely in how that was before or move forward with the new default settings?

The roll-out is not yet complete. For the exam you can respond with the old defaults. This really is not a question for the product group, but for the people who are administering the exam.

We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


create process timeout after 120 seconds

Followed the tutorial not changing a single thing...
Got this in the logs:
create process timeout after 120 seconds
And it keeps trying and trying to create a pvc volume...
I can see that there's no pv created too...
Do I need to create the folder /opt/local-path-provisioner manually? (even doing that it doesn't work)
Did anyone have the same issue?
Thanks!

@meyerbro Can you provide with the log with the local path provisioner pod? You shouldn't need to create /opt/local-path-provisioner manually.

Sure @yasker, here it is:
kubectl -n local-path-storage logs -f local-path-provisioner-d8d9bffb6-47b6s time="2019-08-14T16:14:34Z" level=debug msg="Applied config: {\"nodePathMap\":[{\"node\":\"DEFAULT_PATH_FOR_NON_LISTED_NODES\",\"paths\":[\"/opt/local-path-provisioner\"]}]}" time="2019-08-14T16:14:34Z" level=debug msg="Provisioner started" time="2019-08-14T16:14:51Z" level=debug msg="config doesn't contain node shared-jenk-24.sandbox.local, use DEFAULT_PATH_FOR_NON_LISTED_NODES instead" time="2019-08-14T16:14:51Z" level=info msg="Creating volume pvc-a32c81ba-beae-11e9-8212-002590fb4cd4 at shared-jenk-24.sandbox.local:/opt/local-path-provisioner/pvc-a32c81ba-beae-11e9-8212-002590fb4cd4" E0814 16:16:52.202355       1 controller.go:701] error syncing claim "default/local-path-pvc": failed to provision volume with StorageClass "local-path": failed to create volume pvc-a32c81ba-beae-11e9-8212-002590fb4cd4: create process timeout after 120 seconds time="2019-08-14T16:17:07Z" level=debug msg="config doesn't contain node shared-jenk-24.sandbox.local, use DEFAULT_PATH_FOR_NON_LISTED_NODES instead" time="2019-08-14T16:17:07Z" level=info msg="Creating volume pvc-a32c81ba-beae-11e9-8212-002590fb4cd4 at shared-jenk-24.sandbox.local:/opt/local-path-provisioner/pvc-a32c81ba-beae-11e9-8212-002590fb4cd4" E0814 16:19:07.535033       1 controller.go:701] error syncing claim "default/local-path-pvc": failed to provision volume with StorageClass "local-path": failed to create volume pvc-a32c81ba-beae-11e9-8212-002590fb4cd4: create process timeout after 120 seconds time="2019-08-14T16:19:37Z" level=debug msg="config doesn't contain node shared-jenk-24.sandbox.local, use DEFAULT_PATH_FOR_NON_LISTED_NODES instead" time="2019-08-14T16:19:37Z" level=info msg="Creating volume pvc-a32c81ba-beae-11e9-8212-002590fb4cd4 at shared-jenk-24.sandbox.local:/opt/local-path-provisioner/pvc-a32c81ba-beae-11e9-8212-002590fb4cd4" E0814 16:21:37.876760       1 controller.go:701] error syncing claim "default/local-path-pvc": failed to provision volume with StorageClass "local-path": failed to create volume pvc-a32c81ba-beae-11e9-8212-002590fb4cd4: create process timeout after 120 seconds

@meyerbro The creation process will create a helper pod on the host to help with setup the directory. It seems the pod doesn't finish after 120 seconds. Can you check why the helper pod stuck there? The name of the pod is create-<volumename>

Hi @yasker, just checking that, currently no logs yet... Will wait the full 120 seconds and update here.

After the 120 seconds the only that happened was that the container was terminated and after some seconds a new one with no logs is created...

a0ac37b5d22a        rancher/pause:3.1                                 "/pause"                 4 seconds ago        Up 2 seconds                            k8s_POD_create-pvc-0de20954-bf73-11e9-8212-002590fb4cd4_local-path-storage_615625fe-bf73-11e9-8212-002590fb4cd4_0
# docker logs -f a0ac37b5d22a
Shutting down, got signal: Terminated

I decided to give a try on hostpath from rimusz-charts to see if it's something wrong only on my cluster but it actually worked fine... I would prefer using yours as we have RKE here...

@meyerbro When you see the create- pod started, it will change to running later? or is it always in pending state? Can you try kubectl describe for the pod? Something stopped the helper pod from working.

Not sure if the root cause is the same as for @meyerbro , but I am seeing similar issues on CentOS Linux release 8.1.1911 (Core) with SELinux set to Enforcing and it looks like the local path directory's creation is blocked:
type=AVC msg=audit(1590840690.471:714): avc:  denied  { create } for  pid=17975 comm="mkdir" name="pvc-f349b28b-12cd-42c1-ad7b-f1bf018f9171" scontext=system_u:system_r:container_t:s0:c228,c866 tcontext=system_u:object_r:container_var_lib_t:s0 tclass=dir permissive=0
type=SYSCALL msg=audit(1590840690.471:714): arch=c000003e syscall=83 per=400000 success=no exit=-13 a0=7ffd8cb6676d a1=1ff a2=7ffd8cb6679b a3=1ff items=0 ppid=17862 pid=17975 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="mkdir" exe="/bin/mkdir" subj=system_u:system_r:container_t:s0:c228,c866 key=(null)^]ARCH=x86_64 SYSCALL=mkdir AUID="unset" UID="root" GID="root" EUID="root" SUID="root" FSUID="root" EGID="root" SGID="root" FSGID="root"

After setenforce 0 to disable SELinux temporarily, the problem is gone, the PVCs are bound.

Hello @yasker, should I open a separate issue for my SELinux related root cause in https://github.com/rancher/k3s-selinux ? The SELinux policy RPM is installed by the way.
Thanks a bunch.

@cruizer Yes, can you create a separate issue. It's clear that your issue is caused by SELinux.

@cruizer Yes, can you create a separate issue? It's clear that your issue is caused by SELinux.

OK, done, I have opened: https://github.com/rancher/k3s-selinux/issues/9
Thank you!

Hi @yasker , Same issue is happening for me as well. Is it because of the multi-node cluster?

Yes seeing the same for RKE2 cluster for backup-operator-pvc @cruizer @yasker
Warning   ProvisioningFailed             persistentvolumeclaim/backup-operator-pvc                        failed to provision volume with StorageClass "local-path": failed to create volume pvc-a1a56725-86c9-49a3-9d8b-cd5a9b8f67d7: create process timeout after 120 seconds

This works now when using version 0.0.21 instead of master. Solution: https://stackoverflow.com/a/71605241/18577365

@ClenchPaign
The error in the stackoverflow ticket is fixed.
You can try the master branch as well, but 0.0.21 is the latest stable version.


Added Quantize option

Merging existing Onnx inference with Quantize option.
This request is based Huggingface nootbeook . Also Microsoft has similar notebook.

Thank you for this awesome feature @yusufcakmakk !
Could you send a PR from a different branch than master ?
This needs few changed we could do it on that branch and then merge.

Let me know if you are busy, I will work on it and include you as co-author :)
Thanks again!

I will try to update as you mentioned. By the way you are welcome. I hope it will be useful 😊


localhost is invalid url

http://localhost is invalid if validate a string with SimpleSchema.RegEx.Url
http://<IP_ADDRESS>/video.mp4 has same problem as well.

This was an intentional decision at some point to err on the side of caution, since most people expect URL validation to be more strict. You can come up with your own expression for your needs. There are some more permissive expressions in https://github.com/aldeed/simple-schema-js/blob/master/package/lib/regExp.js that may be helpful.


Fix imposter student bug

Resolves #238
No new test cases added as both lines 83 and 87 are hit by existing test cases

Codecov Report

Merging #272 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #272   +/-   ##
=========================================
  Coverage     83.89%   83.90%
- Complexity     1098     1100    +2
=========================================
  Files           148      148
  Lines          3204     3205    +1
  Branches        392      391    -1
=========================================
+ Hits           2688     2689    +1
  Misses          421      421
  Partials         95       95

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/tutorspet/model/student/Student.java
97.87% <ø> (-0.05%)
22.00 <0.00> (-1.00)

...pet/logic/commands/student/EditStudentCommand.java
96.87% <100.00%> (+0.10%)
15.00 <2.00> (+3.00)

Continue to review full report at Codecov.

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


[ACR] Rename enums ArtifactTagOrderBy and ArtifactManifestOrderBy

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[x] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@annelo-msft Were these CI checks added recently? Not sure what the error INVALID_TYPE means here?

Hi, can you please add the following payload to stable/2021-07-01/examples/DeleteAcrRepository.json and retry?
{
    "manifestsDeleted": [
        "sha256:85ee06962c4884be762687e1abf7f8bdb6e6545476bb1d47159c472336522bdf"
    ],
    "tagsDeleted": [
        "v2"
    ]
}

It looks like its still failing. I think the body is a nested component in that example so it needs to look like.
{
"parameters":
{
"url": "acrapi.azurecr-test.io",
"name": "nanoserver",
"api-version": "2021-07-01"
},
"responses":
{
"202":
{
"body":
{
"manifestsDeleted":
[
"sha256:85ee06962c4884be762687e1abf7f8bdb6e6545476bb1d47159c472336522bdf"
],
"tagsDeleted":
[
"v2"
]
}
},
"404": {}
}
}
The other errors I see are not super clear to me. I went over them and the DISCRIMINATOR_PROPERTY_NOT_FOUND errors are not clear to me from the explanation so not sure what to do about them, I also don't see why INVALID_TYPE is appearing but it can apparently appear as a result of other errors so lets start with the above fix

Thanks @estebanreyl. I updated the example .json and it resolved several errors. There are still a few that remain.
At this moment, we are going to add a transform on the client side to expedite the process of releasing the SDK.
We can use this PR to fix the remaining issues and merge the changes. Once that happens, we will remove the transforms.

Hi, @Mohit-Chakraborty. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.


Remove unused import and add .idea on gitignore

The propose of this pull request is fix CI

.idea should be added to your .gitignore_global file, not on a per-project basis.

@pgrau Thanks for your PR. As @trowski said, we usually don't cover IDE or user setup dependent files in our .gitignore files, but recommend to use a global .gitignore for that instead. You can learn how to setup a global .gitignore here.
I've just fixed the code style in master, so I'm closing this PR now.


V0.2 explorer

Description
Redesign of exploration abstraction
Linked issue(s)/Pull request(s)

Issue 171

Type of Change

[ ] Non-breaking bug fix
[ ] Breaking bug fix
[x] New feature
[ ] Test
[ ] Doc update
[ ] Docker update

Related Component

[ ] Simulation toolkit
[x] RL toolkit
[ ] Distributed toolkit

Has Been Tested

OS:

[ ] Windows
[ ] Mac OS
[x] Linux

Python version:

[ ] 3.6
[x] 3.7

Key information snapshot(s):

Needs Follow Up Actions

[ ] New release package
[ ] New docker image

Checklist

[ ] Add/update the related comments
[ ] Add/update the related tests
[x] Add/update the related documentations
[ ] Update the dependent downstream modules usage

Codecov Report

Merging #198 (ca15318) into v0.2 (298c155) will decrease coverage by 0.90%.
The diff coverage is 31.92%.

@@            Coverage Diff             @@
##             v0.2     #198      +/-   ##
==========================================
- Coverage   71.23%   70.33%   -0.91%
==========================================
  Files          89       90       +1
  Lines        4203     4294      +91
==========================================
+ Hits         2994     3020      +26
- Misses       1209     1274      +65

Flag
Coverage Δ

unittests
70.33% <31.92%> (-0.91%)
:arrow_down:

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

Impacted Files
Coverage Δ

...topologies/single_learner_multi_actor_sync_mode.py
40.47% <ø> (ø)

maro/utils/exception/error_code.py
100.00% <ø> (ø)

maro/rl/learner/simple_learner.py
23.94% <8.82%> (-7.21%)
:arrow_down:

maro/rl/actor/simple_actor.py
28.57% <12.50%> (-3.01%)
:arrow_down:

maro/rl/exploration/epsilon_schedule.py
15.00% <15.00%> (ø)

maro/rl/agent/simple_agent_manager.py
35.18% <28.57%> (-0.11%)
:arrow_down:

maro/rl/agent/abs_agent_manager.py
44.82% <32.00%> (-10.73%)
:arrow_down:

maro/rl/agent/abs_agent.py
46.15% <42.85%> (-3.85%)
:arrow_down:

maro/rl/exploration/epsilon_greedy_explorer.py
44.00% <44.00%> (ø)

maro/rl/actor/abs_actor.py
69.23% <50.00%> (ø)

... and 7 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 298c155...ca15318. Read the comment docs.


feat: transaction

Implemented transaction both online mode & zkvm mode

lets do A. value parse from proof B. step optimization in next PR -- it gets huge


grep from / crashes container and Docker service

So, this seems to happen only for this baseimage. If I simply do
cd / && grep -niIr "foobar" .
both the current container and the docker service as a whole crashes. In fact, it crashes on a kernel level, so I cannot reboot my machine without using the reset/power button.
When I do the same on any other image, I can simply Ctrl+C out of the command without any issue.
If I contain it to /etc for example, the crash doesn't happen.
I'm on Mint Linux 17.1.

That is definitely a Linux kernel bug. Please report it to the Linux kernel team.

While I would agree with you that Docker (and by redirection the Linux kernel) shouldn't allow this to happen, it only happens with your baseimage. None of the other baseimages exhibits this behavior. I therefore think it would be most correct if you guys engaged in the issue, given that you guys "own" the baseimage and the Docker "recipe".
Who knows, maybe it's your baseimage's special Init causing the issue? I don't have the slightes idea, which means you're probably in a better position to raise the issue, or figure it out and work around the issue in your own image.
That's my 2c. I won't bring it further..

We can't reproduce the issue though, so we're not in a position to raise a bug report. Our init system doesn't do anything special from a POSIX API point of view and a kernel point of view; everything we do is very standard.

Furthermore, you trigger the crash through a grep. This suggests that the bug probably lies in the filesystem, which probably means AUFS.

Ok, thanks for checking, might be a Mint Linux/Docker issue then.
On 9/4/2015 8:18 PM, Hongli Lai wrote:

We can't reproduce the issue though, so we're not in a position to
raise a bug report. Our init system doesn't do anything special from a
POSIX API point of view and a kernel point of view; everything we do
is very standard.
—
Reply to this email directly or view it on GitHub
https://github.com/phusion/baseimage-docker/issues/247#issuecomment-137891042.


Port sol-socket to RIOT so we can use sol-coap there

It's less RFCish, but there's still plenty that can be improved. It works well
enough for the time being though.

+1 overall, just try to make the socket class const

Merged with const fixes


Avoid creating certs dir in Appscope working dir

Avoid create certs dir in Appscope working dir
Calling scipt:
/opt/test/bin/testssl.py create_certs
Results with the creation of certs dir - owned by Docker
container user - root. Later trying to remove certs dir
as a user different than root results with permission denied.
Alpine integration test working directory is always
/opt/appscope this results in the creation of the certs dir
outside of the container and the certs dir will be available
after the test.
Removing the certs directly from the host (outside the Docker
container) results with permission denied and issues with
cleaning up the test environment for future test runs.
Changing the test working directory to /opt/test solve the
initial problem.

Fantastic.  Thanks @michalbiesek!  Merging.


fail fast when there is no available sinks

I have run into a situation where i configure an es cluster to store Kubernetes events and the es configuration is invalid. After checking that eventer is running through systemctl --user status eventer.service, i leave it there to run. After some days, when i need to query es about the recent events, nothing was collected.
I turns out that the es configuration is invalid and an error is logged, but eventer continues to run without fail. As es is the only sink i configured, this makes eventer got no valid sinks and even Kubernetes emits some events, the events will not be sinked to es.
This PR will make eventer and heapster fail faster when there is no valid sinks.

This change is

@piosz  PTAL.

@DirectXMan12

Heapster can run fine in sinkless (in-memory-only) mode, though.  It's useful for testing, or if you only want to support the HPA, and have a different metrics collection method.

@DirectXMan12 You're right. I will change the PR later. :)

@DirectXMan12 PTAL.

/cc @mwielgus

@piosz @DirectXMan12 @mwielgus It seems that we can merge this. :)


Fix inconsistency of fill argument

Both of resize_contain and random_expand have an argument to specify the value of padded pixels.
However, the designs of this argument are different from each other.

In resize_contain

The name is bg_value
It takes only a scalar value

In random_expand

The name is fill
It takes a scalar, a tuple, or an array

I fitted resize_contain to random_expand.
This PR is based on #108. I will rebase this PR after #108 is merged.

I rebased this PR on master.

Thanks for PR!
I totally agree with your proporsal.

LGTM


Compilation issues in Unity 2022

OculusSettings.TargetQuest no longer exist must use TargetQuest2
Int OVRDeviceSelector.isTargetDeviceQuest line 44

@vincismurf thank you for the find, an update has been pushed! It looks like there are a few new issues when opening in new versions of Unity. We'll resolve these shortly.


Add ability to insert links and images in text overlay panel

You can add links by entering the markdown syntax on the texts overlays. We decided to keep images as a separated element but we could think on unifying...


Fix loss of precision in X11 device info.

range_min_x, range_min_y, range_max_x and range_max_y are used to extract the min and max values from the XIValuatorClasses of a device. However, based on the XIQueryDevice's man page, these values are doubles not ints.
This is unlikely to be causing any issues, because, fortunately, they are currently only used to calculate a resolution in the unlikely event that the device doesn't report one:
https://github.com/godotengine/godot/blob/74d432117239d07d497bea5368600acee5ef5af4/platform/linuxbsd/display_server_x11.cpp#L299-L310
I doubt that this is a valid calculation, but that's for another day.

Related to #35802.

Thanks!

Cherry-picked for 3.2.2.


Allow injected dependency fields within dependencies

Currently the only way of injecting dependencies into other dependencies is to define a constructor like;
@Inject
public DependencyWithDependencies(SingletonDependency singletonConstructor, MultipleDependency multipleConstructor)
You should also be able to annotate fields with @Inject as you can with InjectableObjects and have them set through DI.

Issue resolved by commit 06562f7


Modify the wallets Transactions function to use binary search

This looks pretty good, but it will probably conflict with #2417. Once we merge that, we can fixup this PR

Seems like changing the locking order in this PR didn't fix the random TestRemoteFileRepair bug.

Is this guaranteed to return every transaction at a given height?

Should be fine. According to the documentation it finds the smallest index for which the condition is true.
https://golang.org/pkg/sort/#Search


Dismiss view.

How can i dismiss the popup by a button action.
using the same transition style.

Hi @bharathi91,
I think you are looking for this?
[self.popupController dismissWithCompletion:nil];

Yes thanx.
This Works.
Thank u very much.


incompatible function arguments for set_option

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 16.04

Kernel Version (Linux Only)
4.8.0-36-generic

Platform
PC

SDK Version
<IP_ADDRESS>5

Language
python

Segment
Robot

Issue Description
I am trying to run the export_ply_example.py script included in this repository, but it is complaining about the set_option call linked below
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/export_ply_example.py#L40
I get the following error:
Traceback (most recent call last):
  File "generate_ply.py", line 40, in <module>
    ply.set_option(rs.save_to_ply.option_ply_binary, False)
TypeError: (): incompatible function arguments. The following argument types are supported:
    1. () -> pyrealsense2.pyrealsense2.option

The script works if I remove both of the set_option calls (though the resulting point cloud doesn't seem accurate, which may be unrelated).
These pages don't produce any search results:
https://intelrealsense.github.io/librealsense/python_docs/search.html?q=option_ply_binary
https://intelrealsense.github.io/librealsense/python_docs/search.html?q=option_ply_normals
Has this script fallen out of date? How can I find the options that this will accept?

I have the same issue. The resulting point cloud is very different to the point cloud I get if I export the point cloud via realsense-viewer. Any update?

I have the same issue with original example code. Any update?
There are little bit differect logs between 2.33.1 and 2.31.0

pyreansense2 version '2.33.1' in windows notebook
---> 38     ply.set_option(rs.pyrealsense2.save_to_ply.option_ply_binary, False)
39     ply.set_option(rs.pyrealsense2.save_to_ply.option_ply_normals, True)

TypeError: (): incompatible function arguments. The following argument types are supported:
1. () -> pyrealsense2.pyrealsense2.option
Invoked with: <class 'pyrealsense2.pyrealsense2.save_to_ply'>

pyreansense2 version '2.31.0' in Nvidia TX2
---> 33     ply.set_option(rs.save_to_ply.option_ply_binary, False)
34     ply.set_option(rs.save_to_ply.option_ply_normals, True)
35

TypeError: (): incompatible function arguments. The following argument types are supported:
1. () -> pyrealsense2.option
Invoked with: <class 'pyrealsense2.save_to_ply'>

Hi @bfouts-kindred
Are you still experiencing this? We cannot reproduce this issue on the latest librealsense ver 2.36.0. The sample generates 1.ply and can be read successfully by supported software. Also the set_options works as well and are defined here:
https://github.com/IntelRealSense/librealsense/blob/f7cdf6e8961e1709f6d864bdb33095c00a671ca7/wrappers/python/python.cpp#L33
Thanks

Hi,
Will you be needing further help with this? If we don’t hear from you in 7 days, this issue will be closed.
Thanks


How to setup or choose category in an event?

Hello, how can I set up categories to choose from, when entering a new event? I can't find a place to do that, so I can only choose "Uncategorized".
I am using VS TS.

You just type something, and it will create a new category for you with a random color, if I recollect correctly.

It works, thanks!

Thanks! I also asked myself how to add categories... maybe you need to make it clear in the release notes..

It wasn't easy to find it out :)

It wasn't easy to find it out :)


Block Groups and Scheduling Constraints

Added the functions and classes needed to be able to group blocks together and then evaluate where they can be placed in a schedule. This also contains a change to how blocks are stored/modified when scheduling.

Comments on the changes:
The TransitionConstraint needs to be modified from its current state if it is to be useful in scheduling.   (it isn't written for an array of times, and so doesn't make use of vectors)
The SchedulingConstraint still needs work because a 'consecutive' block will completely fail if one of its group is scheduled but the previous and subsequent blocks aren't; even though it may be able to be scheduled if evaluated a few blocks later. (this could be fixed if consecutive blocks scheduled themselves, though that may not be user/developer friendly).
The group_blocks function works by adding attributes to the blocks, which the SchedulingConstraint reads. It doesn't explicitly prevent somebody from trying to group a single block into multiple groups of the same type, but it overwrites some of the information.


Ammo.btConvexHullShape Support

Added support for Ammo.btConvexHullShape. To use set the 'useConvexHullShape' physics imposter option.
Example: mesh.physicsImpostor = new BABYLON.PhysicsImpostor(mesh, BABYLON.PhysicsImpostor.MeshImpostor, { mass:1, useConvexHullShape: true});

Yo @deltakosh ... Why am i getting failing checks on the PR ???

Is it the Whats New thing... I gotta place something in Whats New or something like that ???

The PR is failing because you need to update the what's new with all PR:
https://github.com/BabylonJS/Babylon.js/blob/master/dist/preview release/what's new.md
(best way to make sure the what's new is up to date)

Please update the documentation:
https://github.com/BabylonJS/Documentation/blob/master/content/How_To/Physics/Using_The_Physics_Engine.md


Failing to decode StripeEvent

Environment:
Xcode 14.2
Swift 5.7.2
vapor 4.69.2
stripe-kit 17.0.0

When responding to a webhook from Stripe, currently coming from the CLI for testing, I find an issue when attempting to decode to a StripeEvent. The Vapor console outputs the following warnings:

Value of type 'Dictionary<String, Any>' required for key 'request'. (This happens twice)
Cannot initialize StripePaymentIntentStatus from invalid String value requires_source for key data.object.status

When wrapping the decoding in a do catch block it outputs the following from error.localizedDescription

The data couldn’t be read because it isn’t in the correct format.

The data received from the Stripe web hook is below:
{
  "id": "evt_REMOVED",
  "object": "event",
  "api_version": "2016-07-06",
  "created":<PHONE_NUMBER>,
  "data": {
    "object": {
      "id": "pi_REMOVED",
      "object": "payment_intent",
      "allowed_source_types": [
        "card"
      ],
      "amount": 2000,
      "amount_capturable": 0,
      "amount_details": {
        "tip": {
        }
      },
      "amount_received": 0,
      "application": null,
      "application_fee_amount": null,
      "automatic_payment_methods": null,
      "canceled_at": null,
      "cancellation_reason": null,
      "capture_method": "automatic",
      "charges": {
        "object": "list",
        "data": [

        ],
        "has_more": false,
        "total_count": 0,
        "url": "/v1/charges?payment_intent=pi_REMOVED"
      },
      "client_secret": "pi_REMOVED_secret_REMOVED",
      "confirmation_method": "automatic",
      "created":<PHONE_NUMBER>,
      "currency": "usd",
      "customer": null,
      "description": "(created by Stripe CLI)",
      "invoice": null,
      "last_payment_error": null,
      "latest_charge": null,
      "livemode": false,
      "metadata": {
      },
      "next_action": null,
      "next_source_action": null,
      "on_behalf_of": null,
      "payment_method": null,
      "payment_method_options": {
        "card": {
          "installments": null,
          "mandate_options": null,
          "network": null,
          "request_three_d_secure": "automatic"
        }
      },
      "payment_method_types": [
        "card"
      ],
      "processing": null,
      "receipt_email": null,
      "review": null,
      "setup_future_usage": null,
      "shipping": {
        "address": {
          "city": "San Francisco",
          "country": "US",
          "line1": "510 Townsend St",
          "line2": null,
          "postal_code": "94103",
          "state": "CA"
        },
        "carrier": null,
        "name": "Jenny Rosen",
        "phone": null,
        "tracking_number": null
      },
      "source": null,
      "statement_descriptor": null,
      "statement_descriptor_suffix": null,
      "status": "requires_source",
      "transfer_data": null,
      "transfer_group": null
    }
  },
  "livemode": false,
  "pending_webhooks": 2,
  "request": "req_REMOVED",
  "type": "payment_intent.created"
}

The code in my project is hardly anything but the basic Vapor template; just trying to hack together a better understanding of how everything comes together between the code and Stripe. The controller used to respond to webhooks can be found below:

Is there something blatant that I am overlooking in my code, or has Stripe recently changed something on their end? I greatly appreciate any insight on this issue of mine, thank you!

StripeKit currently only supports API version 2020-08-27 you're likely using an API version higher than that. A future version with full async await support will be updated to support the latest version of 2022-11-15 https://github.com/vapor-community/stripe-kit/pull/152

I appreciate your timely reply! Looking over the Stripe Dashboard, I am only seeing the ability to use the 2016-07-06 or 2022-11-15 API versions, nothing in between.
My current use only makes use of signature verification and models to extract customer information from the intent. I would assume this would rule out the usage of the Stripe-Version: XXXX-XX-XX header. Is there a known way to specify an exact version for webhooks?

@lorenalexm I don't think so, what I can recommend for now is forking the current branch and add the new enum type of requires_source to the status property of the StripePaymentIntent type until the new version is ready to go.

Thanks for the suggestion. I will run with that and keep plugging away for now. Quite grateful for your time, thanks!

@Andrewangeta I just wanted to say thank you again. I was able to get webhook processing taken care of by adding the requires_source to the StripePaymentIntentStatus and also by changing public var request: StripeEventRequest? within the StripeEvent struct to a optional String type.


Broker statefulset no accounted for in PulsarSQL configmap

The pulsarSql configmap assumes broker is a deployment by using .Values.broker.component https://github.com/datastax/pulsar-helm-chart/blob/014a542e11cd01843c7e7fe65d88314d6da33a99/helm-chart-sources/pulsar/templates/pulsarSql/configmap-coordinator.yaml#L75
When using brokerSts, PulsarSql can not find the broker because it's .Values.brokerSts.component.

Thanks for opening this issue @ddieruf. I think there are multiple places in the helm chart with this bug. the easiest solution is to configure .Values.brokerSts.component: broker. A better solution would use a templating function to figure out the "right" component name to use without duplicating the logic everywhere. Is this issue blocking you? Are you interested in contributing a fix?

I'll just use the workaround for now, thx.
On Tue, Nov 15, 2022 at 11:24 AM Michael Marshall @.***>
wrote:

Thanks for opening this issue @ddieruf https://github.com/ddieruf. I
think there are multiple places in the helm chart with this bug. the
easiest solution is to configure .Values.brokerSts.component: broker. A
better solution would use a templating function to figure out the "right"
component name to use without duplicating the logic everywhere. Is this
issue blocking you? Are you interested in contributing a fix?
—
Reply to this email directly, view it on GitHub
https://github.com/datastax/pulsar-helm-chart/issues/267#issuecomment-1315556096,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBJG3BANZ45FTEGBBAJ353WIO2LJANCNFSM6AAAAAASBBQT54
.
You are receiving this because you were mentioned.Message ID:
@.***>


Make time-related variables more readable

Make time-related variables more readable

It seems that the failure of those jobs is not related to this PR. Can someone please help me to restart them? (job#415047952 / job#415047956)

@asdf2014 thanks! I've left some comments and restarted the failed jobs.

Nice! :+1: after changes @jihoonson suggested


[Suggestion] cdk8s.yaml config file should support object version overrides

Is your feature request related to a problem? Please describe.
Right now, with the CLI you can specify specific versions of k8s objects. For example,
cdk8s import k8s --language typescript --include io.k8s.api.extensions.v1beta1.Deployment

To specify the latest k8s version, except to include the v1beta1 version of Deployment
Describe the solution you'd like
This should be possible in the cd8ks.yaml config.
Describe alternatives you've considered
I think there's a couple ways to do this:
app: node index.js
language: typescript
imports:
  -<EMAIL_ADDRESS>--include  io.k8s.api.extensions.v1beta1.Deployment

app: node index.js
language: typescript
imports:
  -<EMAIL_ADDRESS>include:
  -  io.k8s.api.extensions.v1beta1.Deployment

app: node index.js
language: typescript
imports:
  -<EMAIL_ADDRESS>overrides:
  - import<EMAIL_ADDRESS>    override: io.k8s.api.extensions.v1beta1.Deployment

Additional context
Of these, I'd go with the 2nd or 3rd. The 2nd simply mimics the current functionality, while the third extends it.
I think in the future, when, say, the knative API objects are supported, then 3 would be the best way to do this. That being said, 2 solves the problem now, and 3 can be implemented when needed.
I'd choose (2).

Looks like this was resolved by https://github.com/awslabs/cdk8s/pull/39


Add missing media context in revisions_revert view

Fixes #8505.
Kindly review @gasman @kaedroho, thanks!

Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Merged in 2006b94be8ee0ce59d334d31ded15b4248035f50 (main) / b6d811287c8799c91d054ba9e1457c4958031aff (stable/3.0.x).


hana-cloud-mission-trial-9 - Grant Access to Calculation Views

Tutorials: https://developers.sap.com/tutorials/hana-cloud-mission-trial-9.html
ERROR: Error: (dberror) [258]: insufficient privilege
i could not execute Step 4 on this tutorial.

User Managment
A error message appears with the following text:
Could not execute 'CREATE USER report PASSWORD  NO FORCE_FIRST_PASSWORD_CHANGE set usergroup default'
Error: (dberror) [258]: insufficient privilege: Detailed info for this error can be found with guid
'5FDD8805A3CD7B49807519B96E168578'
Due to the error on SQL console, i created the user REPORT via the HANA Cockpit - UserManagement area with DBAdmin user.
It works and i could see the user via the screen and via a select statement at the database explorer.

Grant the user access to the role
Same error message pops up:
Could not execute 'GRANT <SCHEMA_NAME>."PublicAccessSchema" to report'
Error: (dberror) [258]: insufficient privilege: Detailed info for this error can be found with guid
'B94B0CA8660B094EB7B7D4B0E40F211C'
I tried to assig the role to the user via the Role Management at the HANA Cockpit, but here i got the same error with
insufficient privileges.

What can i do or how to solve this issue ? Is it an environment issue ?
How could i found more informations for this errors ? I didn't find a info how to use this guid's to do a deep dive.
Kind regards
Jürgen

Hi Jürgen,
please open a connection with the DBADMIN user in database explorer to execute the statements.
Best,
Jan

Thanks Jan,
I solved it but the screenshot is misleading.
I was able to run the commands after connecting to the HANA DB with the DBAdmin user.
In my opinion, the screenshot suggests that the commands should be executed at the SharedKeyDB level. Even when connected as DBAdmin this doesn't work.
Regards
Jürgen

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.