Excuse me, what's wrong with this error, after I transfer several transactions in a row, it keeps reporting this error

Result{successful=false, response='{"error":"Bad Request","message":""transaction submit error ShelleyTxValidationError ShelleyBasedEraAlonzo (ApplyTxError [UtxowFailure (WrappedShelleyEraFailure (UtxoFailure (ValueNotConservedUTxO (Value 0 (fromList [])) (Value 9000000 (fromList []))))),UtxowFailure (WrappedShelleyEraFailure (UtxoFailure (BadInputsUTxO (fromList [TxInCompact (TxId {_unTxId = SafeHash \"0f30fd03f3c83b650f63d0b765ea8874772d112c8dbf59a801bb4bb9e5f91531\"}) 0]))))])"","status_code":400}', code=400, value=null}

I also encountered similar problems. I hope you can reply as soon as possible

@chaim-g The error "ValueNotConservedUTxO" is thrown when the total input utxo value doesn't match the total output value + fee.
You can enable DEBUG mode and check values in the final transaction output. Are you using high-level api like PaymentTransaction ?
Can you please check if the sender address has utxos with enough ada ?
One possible reason:

The address (at index=0) doesn't have enough ada , but the other addresses (at different index) have enough fund.
This may happen when you use the same account from wallet like Yoroi, Daedalus. During a transfer transaction, the change amount is usually returned to a different unused address by these wallets.

This library just checks utxos at the given sender address (most of the time address at index=0).
It doesn't scan all the addresses under an account like a wallet app does.
Btw, for better control, you can use low level transaction api instead of high-level apis.

I think there is something wrong with this node. I was also unable to transfer after a few tests.


UserNotice incorrect parsing

Hi, we are trying to add an issuer statement to a certificate.  When we use a null org.bouncycastle.asn1.x509.NoticeReference in org.bouncycastle.asn1.x509.UserNotice constructor UserNotice(NoticeReference,DisplayText) the CertificatePolicy extension is correctly parsed and displayed but when we try to use a not null NoticeReference with Organization and NoticeNumber the extension is not parsed correctly. Any ideas why?

What error are you seeing?

Hi, I should be able to see something like this:
[image: Inline image 1]
but instead I'm getting
[image: Inline image 2]
Thanks.
On Tue, Feb 27, 2018 at 6:15 PM, bcgit<EMAIL_ADDRESS>wrote:

What error are you seeing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bcgit/bc-java/issues/305#issuecomment-369061809, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AjMNsKBjPcDjuok73_uh-rNu-JFmlMvHks5tZIyQgaJpZM4SVlON
.

I'm sorry, but the screen dumps did not come through.

Hi, attached you will find two png's with the screenshots.
Thanks.
On Tue, Feb 27, 2018 at 10:28 PM, bcgit<EMAIL_ADDRESS>wrote:

I'm sorry, but the screen dumps did not come through.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bcgit/bc-java/issues/305#issuecomment-369109619, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AjMNsCgjuC89tBzPL4RFdyQ45OpxnFCAks5tZMfpgaJpZM4SVlON
.

Try emailing them to<EMAIL_ADDRESS>

Hi, I just did it.
Thanks.
On Wed, Feb 28, 2018 at 7:41 AM, Diego Garzón<EMAIL_ADDRESS>wrote:

Hi, attached you will find two png's with the screenshots.
Thanks.
On Tue, Feb 27, 2018 at 10:28 PM, bcgit<EMAIL_ADDRESS>wrote:

I'm sorry, but the screen dumps did not come through.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bcgit/bc-java/issues/305#issuecomment-369109619, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AjMNsCgjuC89tBzPL4RFdyQ45OpxnFCAks5tZMfpgaJpZM4SVlON
.

The screendumps didn't actually show anything related to Bouncy Castle. NoticeReference (as defined in the ASN.1 library) appears to correct though. It may be related to the tool being used for displaying the certificate.


Request: DNS Seeders wanted

Just an issue to keep track of DNS Seeds, and a place for potential contributors to contact us.

Is there still a need for DNS seeds?

Yes! @Tr0llhunt3r

If this is still needed then I would happily provide some! Let me know

Yes! @Tr0llhunt3r
I can run a few seeds. Say me if you need help. Thank you.


sorting seems ineffective

I tried to see how config.layout.sortChords and config.layout.sortSubgroups work.
A simple test I performed was to set the value to d3.ascending instead of the default d3.descending.
To my surprise I didn't see any visual change.
Did I miss the point or made some mistake?
Could you please elaborate on the rationale for those configuration parameters?
Thanks in advance

I found a typo in the charts sources around sortChors, but its still not working for me. Unfortunately I dont have time to dig deeper into this at the moment.

Well spotted!
I will have a look and try to understand the sorting code in layout.js (L81-L86 for groups, L88-L98 for subgroups).
Looking at the code and without trying to understand it, I have a doubt for line 313 in layout.js which maybe should use negation on chords:
if (!chords) resort();

I'll let you know of any discovery...

My observation about line 313 in layout.js doesn't hold...


Improve caching strategy for static assets season

Rabbit season

| Flaky Test | Failure Summary | Quarantined? | Logs |
| --- | --- | --- |
| [chromium] should navigate to the dashboard after login correctly. | The test timed out waiting for the dashboard to be displayed after login. |   | Logs ↗ |
| [chromium] should return list of users correctly. | The API call to get the list of users failed with a 404 Not Found error. |   | Logs ↗ |
| [chromium] should display error message for invalid login correctly. | The expected status code 401 was not received, instead a function was returned. |   | Logs ↗ |
| [chromium] should login with credentials correctly correctly. | The login request to the server failed with a 404 Not Found error. |   | Logs ↗ |
... and 1 more

View Full Report ↗


[BUG] Warn if test case names are not unique

Describe the bug

Related to pytest test case names.
To Reproduce

Expected behavior

Screenshots

Desktop (please complete the following information):

OS:
eRPC Version:

Steps you didn't forgot to do

[X] I checked if there is no related issue opened/closed.
[X] I checked that there doesn't exist opened PR which is solving this issue.

Additional context

Originaly from erpc pytest readme

Pytest will throw error. I think current solution is good.


collectstatic warns of colliding files

I have a project using django and DAL.
Whenever I run collectstatic, I get the following warning:

Found another file with the destination path 'admin\js\jquery.init.js'. It will be ignored since only the first encountered file is collected. If this is not what you want, make sure every static file has a unique path.

The jquery.init.js file from DAL then doesn't get copied to admin/js - instead, Django's original is copied.

Perhaps this is because of the order of INSTALLED_APPS ?

Hi, I just stumbled upon the same problem - both dal and dal_select2 are close to the top of INSTALLED_APPS, in any case above django.contrib.admin. Any idea what else might be causing this issue?

Could you paste the output of echo 'from django.conf import settings; settings.INSTALLED_APPS' | ./manage.py shell just to make sure ? Also the
outcome of ./manage.py findstatic for the different files you're having
issues with.

@jpic ok, my bad - I get the warning, but the right file (from dal) is getting pulled from the server. What threw me off was that it still doesn't work correctly, on localhost everything is fine, but on the server the widget is not working. I just saw that there are errors in the console:
Select2: An instance of jQuery or a jQuery-compatible library was not found. Make sure that you are including jQuery before Select2 on your web page.
So not related issue, thanks for getting me on the right track. If you have any ideas about the above, let me know.

Np :joy: could you grep script tags from the HTML output and paste them
here ?

Sure. I looked through this issue #900  and it seems to be the same problem, the dal scripts are all loaded after jQuery.
<script type="text/javascript" src="/static/admin/js/vendor/jquery/jquery.min.js"></script>
<script type="text/javascript" src="/static/admin/js/jquery.init.js"></script>
<script type="text/javascript" src="/static/admin/js/admin/RelatedObjectLookups.js"></script>
<script type="text/javascript" src="/static/admin/js/actions.min.js"></script>
<script type="text/javascript" src="/static/admin/js/urlify.js"></script>
<script type="text/javascript" src="/static/admin/js/prepopulate.min.js"></script>
<script type="text/javascript" src="/static/admin/js/vendor/xregexp/xregexp.min.js"></script>
<script type="text/javascript" src="/static/autocomplete_light/jquery.init.js"></script>
<script type="text/javascript" src="/static/autocomplete_light/autocomplete.init.js"></script>
<script type="text/javascript" src="/static/autocomplete_light/vendor/select2/dist/js/select2.full.js"></script>
<script type="text/javascript" src="/static/autocomplete_light/select2.js"></script>

... and it started working by itself. So I'm guessing some race condition with loading jQuery that disappears thanks to browser caching or something like that? I'll keep you posted if I manage to reproduce again. Thanks for the help!

While I'm happy for you that this seems fixed, it would be awesome if you
could reproduce and isolate. There is a fix contributed by @mpasternak you
can get with the latest 3.3.0-rc, it would be great to know if that works
for you.

@jpic I've had this code in use for almost a month now and the issue did not come up again

I think the fix on master currently only supports Django 2 because it
reuses static from django's new select2 widget, someone should perhaps
contribute back support for django 1 before we release ?
Le mar. 17 avr. 2018 à 22:51, michalpleszczynski<EMAIL_ADDRESS>a écrit :

@jpic https://github.com/jpic I've had this code in use for almost a
month now and the issue did not come up again
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yourlabs/django-autocomplete-light/issues/886#issuecomment-382141195,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFxrNDX-6joUz7_vEb40m66KltbwPLFks5tplXLgaJpZM4OV4wh
.


[WIP] Expose network stats for pods.

Fixes #368
Dirty: using leaky infra container name, regex for container name to pod mapping, but seems to work OK...
/cc @vishh @akash010 @smarterclayton @simon3z

If leaky is imported just to get pod infra container name, it's not worth it.  I'd just have it be a constant or parameter in this code.

retest this please

Removed leaky package dependency.

Got more work to do on this to expose via the API so changing to WIP - please don't merge.
@vishh @mwielgus Do you know if the Jenkins GCE e2e should pass? Seeing unrelated flake in logs:
No error is expected but got expected [gcm] sinks, found []

Yeah, the problem seems to be unrelated. BTW, we will have to redo this work in heapster-scalability branch.

@mwielgus Are you targeting the new metrics APIs in the scalability branch? Sorry I've not kept up to speed with it.

If the new API is delivered on time then yes we will switch, if not we will keep using the old one.

Ready for review please. Jenkins GCE e2e is flaky & needs to either disabled or fixed separately to this PR.

General structure LGTM. Thanks @jimmidyson !!

Network stats are now only sent to sinks, not retrievable via Heapster API as discussed with @vishh.

@vishh Please can you let me know what is outstanding for this PR to be merged?

The only issue with this PR is that of exposing the infra container. I'd prefer adding pod level metrics and exposing network as a pod level metrics.

This is how's it's been done in heapster-scalability branch & I'm not going to duplicate that functionality as this is just a quick fix until heapster-scalability branch becomes master.

Ok then. No issues in that case.
On Tue, Jan 12, 2016 at 8:00 AM, Jimmi Dyson<EMAIL_ADDRESS>wrote:

This is how's it's been done in heapster-scalability branch & I'm not
going to duplicate that functionality as this is just a quick fix until
heapster-scalability branch becomes master.
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/heapster/pull/852#issuecomment-170957230.

Thanks @vishh.
Merging.


I followed all  of the steps. For 1v1.lol and I still cant get it  work

Thanks

i ment to say its not working

Does speed work?


Use Flake8 extensions

Is there a way to include extensions for Flake8? If so, which extensions are available?

+1, Flake8 isn't very useful without it's modular extensions system. I'm not sure but I think this might be a matter of adding most/all of the extensions to this project's requirements.txt?
I'm seeing HoundCI crash when trying to run on my project with flake8 + extensions (flake8-docstrings, flake8-import-order)


METRON-357: Create Ambari Service Definition for Kibana

First iteration of the Kibana Service which is required to deploy Metron via Ambari.
Steps to test:
On a running Ambari-managed cluster:
copy metron-deployment/packaging/ambari/src/main/resources/stacks/HDP/2.4/services/KIBANA to /var/lib/ambari-server/resources/stacks/STACK-NAME/STACK-VERSION/services/KIBANA
copy metron-deployment/packaging/ambari/src/main/resources/common-services/KIBANA to /var/lib/ambari-server/resources/common-services/KIBANA
restart ambari-server
use the Add Service wizard to add Kibana to your cluster.
Note: STACK-NAME and STACK-VERSION need to be substituted for your environment. For example, if testing on HDP 2.4, STACK-NAME = HDP and STACK-VERSION = 2.4

Bump?

Sorry Dave!  I was sleeping on the job.  +1 by inspection, this looks good

Looks very cool. I am trying to test this.  In your instructions you have a placeholder called STACK-VERSION.
When I look at my install of Ambari, I see a clusterf* of possible STACK-VERSIONs.  How can I tell which STACK-VERSION I should be using?  Can I find that in the Ambari UI somehow?
[root@node1 ambari-server]# ls -l /var/lib/ambari-server/resources/stacks/HDP/
total 32
drwxr-xr-x. 4 root root 4096 May  2 16:55 2.0
drwxr-xr-x. 6 root root 4096 May  2 16:55 2.0.6
drwxr-xr-x. 4 root root 4096 May  2 16:55 2.0.6.GlusterFS
drwxr-xr-x. 5 root root 4096 May  2 16:55 2.1
drwxr-xr-x. 5 root root 4096 May  2 16:55 2.1.GlusterFS
drwxr-xr-x. 6 root root 4096 May  2 16:55 2.2
drwxr-xr-x. 5 root root 4096 May  2 16:55 2.3
drwxr-xr-x. 5 root root 4096 May  2 16:55 2.3.GlusterFS

I don't have an Ambari running right now, but it's somewhere under Stacks and Versions (then Stacks under that iirc).
Looks like yours will be 2.3.

Everything went smoothly with the Kibana installation.  Love the guided installation process.
I did get a warning when it tried to start Kibana and failed to.  I get the same error when trying to start Kibana through Ambari after the installation process.
I can login to the host and successfully start Kibana with a service kibana start.  I am assuming its an issue with the Ambari configuration, not the Kibana configuration that Ambari laid down.
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/KIBANA/4.5.1/package/scripts/kibana_master.py", line 86, in <module>
    Kibana().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 216, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/KIBANA/4.5.1/package/scripts/kibana_master.py", line 63, in start
    self.configure(env)
  File "/var/lib/ambari-agent/cache/common-services/KIBANA/4.5.1/package/scripts/kibana_master.py", line 50, in configure
    kibana()
  File "/var/lib/ambari-agent/cache/common-services/KIBANA/4.5.1/package/scripts/kibana.py", line 42, in kibana
    print "Master env: ""{}/kibana.yml".format(params.conf_dir)
ValueError: zero length field name in format

I was able stop Kibana from the command-line and after a minute or so Ambari reported Kibana as stopped (red) in the UI.  That's good stuff.

I suspect this requires Ambari 2.4 to work, there seems to be an issue with the params getting filled in otherwise. I'll dig into it a bit.

I can spin-up a cluster with the latest from master and try it out there, if you like.  If it is just an issue with my environment, and we're not aiming for backwards-compat, then maybe that makes sense.

I'm not really sure what the right answer is. I've been testing with 2.4 (that's the targeted version), but I would expect it to run on 2.3. Our current quick dev is actually <IP_ADDRESS>, so that could be an issue.

Yes, my testing was with quick-dev and <IP_ADDRESS>

I think I'll fire up a 2.3 and see if the problem occurs there as well.

I ran this up on 2.2 and 2.4 and both ran fine. There must be some sort of issue with <IP_ADDRESS>.

+1


QuerySelector Id canot start with number?

my code is
var parser = new HtmlParser();
var document= parser.Parse(firstHtml);
document.QuerySelectorAll("#1801_cxda_tab1_goid")
it throw
The string did not match the expected pattern.
AngleSharp.Dom.DomException
Id canot start with number?

Yes, the provided id is invalid. See: http://stackoverflow.com/questions/448981/which-characters-are-valid-in-css-class-names-selectors.
Have you tried it in any browser first?

Hope this helps.


[Bug][v0.5.0]: Benign error reported by Python multiprocessing resource_tracker

Your current environment
python collect_env.py
Collecting environment information...
PyTorch version: 2.3.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.4 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.29.5
Libc version: glibc-2.35

Python version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-6.5.0-35-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 12.5.40
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA H100 80GB HBM3
GPU 1: NVIDIA H100 80GB HBM3
GPU 2: NVIDIA H100 80GB HBM3
GPU 3: NVIDIA H100 80GB HBM3
GPU 4: NVIDIA H100 80GB HBM3
GPU 5: NVIDIA H100 80GB HBM3
GPU 6: NVIDIA H100 80GB HBM3
GPU 7: NVIDIA H100 80GB HBM3

Nvidia driver version: 555.42.02
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Address sizes:                      46 bits physical, 57 bits virtual
Byte Order:                         Little Endian
CPU(s):                             128
On-line CPU(s) list:                0-127
Vendor ID:                          GenuineIntel
Model name:                         Intel(R) Xeon(R) Platinum 8462Y+
CPU family:                         6
Model:                              143
Thread(s) per core:                 2
Core(s) per socket:                 32
Socket(s):                          2
Stepping:                           8
CPU max MHz:                        4100.0000
CPU min MHz:                        800.0000
BogoMIPS:                           5600.00
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cat_l2 cdp_l3 invpcid_single intel_ppin cdp_l2 ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect avx_vnni avx512_bf16 wbnoinvd dtherm ida arat pln pts hfi vnmi avx512vbmi umip pku ospke waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid bus_lock_detect cldemote movdiri movdir64b enqcmd fsrm md_clear serialize tsxldtrk pconfig arch_lbr ibt amx_bf16 avx512_fp16 amx_tile amx_int8 flush_l1d arch_capabilities
Virtualization:                     VT-x
L1d cache:                          3 MiB (64 instances)
L1i cache:                          2 MiB (64 instances)
L2 cache:                           128 MiB (64 instances)
L3 cache:                           120 MiB (2 instances)
NUMA node(s):                       2
NUMA node0 CPU(s):                  0-31,64-95
NUMA node1 CPU(s):                  32-63,96-127
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Enhanced / Automatic IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI BHI_DIS_S
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] torch==2.3.0
[pip3] transformers==4.41.2
[pip3] triton==2.3.0
[conda] Could not collect
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.5.0
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7    NIC0    NIC1    NIC2    NIC3    NIC4    NIC5    NIC6    NIC7    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      NV18    NV18    NV18    NV18    NV18    NV18    NV18    PIX     NODE    NODE    NODE    SYS     SYS     SYS     SYS     0-31,64-95      0               N/A
GPU1    NV18     X      NV18    NV18    NV18    NV18    NV18    NV18    NODE    PIX     NODE    NODE    SYS     SYS     SYS     SYS     0-31,64-95      0               N/A
GPU2    NV18    NV18     X      NV18    NV18    NV18    NV18    NV18    NODE    NODE    PIX     NODE    SYS     SYS     SYS     SYS     0-31,64-95      0               N/A
GPU3    NV18    NV18    NV18     X      NV18    NV18    NV18    NV18    NODE    NODE    NODE    PIX     SYS     SYS     SYS     SYS     0-31,64-95      0               N/A
GPU4    NV18    NV18    NV18    NV18     X      NV18    NV18    NV18    SYS     SYS     SYS     SYS     PIX     NODE    NODE    NODE    32-63,96-127    1               N/A
GPU5    NV18    NV18    NV18    NV18    NV18     X      NV18    NV18    SYS     SYS     SYS     SYS     NODE    PIX     NODE    NODE    32-63,96-127    1               N/A
GPU6    NV18    NV18    NV18    NV18    NV18    NV18     X      NV18    SYS     SYS     SYS     SYS     NODE    NODE    PIX     NODE    32-63,96-127    1               N/A
GPU7    NV18    NV18    NV18    NV18    NV18    NV18    NV18     X      SYS     SYS     SYS     SYS     NODE    NODE    NODE    PIX     32-63,96-127    1               N/A
NIC0    PIX     NODE    NODE    NODE    SYS     SYS     SYS     SYS      X      NODE    NODE    NODE    SYS     SYS     SYS     SYS
NIC1    NODE    PIX     NODE    NODE    SYS     SYS     SYS     SYS     NODE     X      NODE    NODE    SYS     SYS     SYS     SYS
NIC2    NODE    NODE    PIX     NODE    SYS     SYS     SYS     SYS     NODE    NODE     X      NODE    SYS     SYS     SYS     SYS
NIC3    NODE    NODE    NODE    PIX     SYS     SYS     SYS     SYS     NODE    NODE    NODE     X      SYS     SYS     SYS     SYS
NIC4    SYS     SYS     SYS     SYS     PIX     NODE    NODE    NODE    SYS     SYS     SYS     SYS      X      NODE    NODE    NODE
NIC5    SYS     SYS     SYS     SYS     NODE    PIX     NODE    NODE    SYS     SYS     SYS     SYS     NODE     X      NODE    NODE
NIC6    SYS     SYS     SYS     SYS     NODE    NODE    PIX     NODE    SYS     SYS     SYS     SYS     NODE    NODE     X      NODE
NIC7    SYS     SYS     SYS     SYS     NODE    NODE    NODE    PIX     SYS     SYS     SYS     SYS     NODE    NODE    NODE     X

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

NIC Legend:

  NIC0: mlx5_0
  NIC1: mlx5_1
  NIC2: mlx5_2
  NIC3: mlx5_3
  NIC4: mlx5_4
  NIC5: mlx5_5
  NIC6: mlx5_6
  NIC7: mlx5_7

🐛 Describe the bug
When running with tensor parallelism enabled on the multiprocessing backend (i.e. default with ray not installed) I see these errors:
Traceback (most recent call last):
  File "/usr/lib/python3.10/multiprocessing/resource_tracker.py", line 209, in main
    cache[rtype].remove(name)
KeyError: '/psm_10b3d52e'
Traceback (most recent call last):
  File "/usr/lib/python3.10/multiprocessing/resource_tracker.py", line 209, in main
    cache[rtype].remove(name)
KeyError: '/psm_10b3d52e'
Traceback (most recent call last):
  File "/usr/lib/python3.10/multiprocessing/resource_tracker.py", line 209, in main
    cache[rtype].remove(name)
KeyError: '/psm_10b3d52e'

They seemingly cause no issue during actual inference, but we should try to remove any reported errors even if benign.
Here is further context on when this is happening during creation:
/home/mgoin/venvs/vllm-rel/lib/python3.10/site-packages/huggingface_hub/file_download.py:1132: FutureWarning: `resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.
  warnings.warn(
WARNING 06-12 19:01:08 config.py:216] fp8 quantization is not fully optimized yet. The speed can be slower than non-quantized models.
INFO 06-12 19:01:11 config.py:623] Defaulting to use mp for distributed inference
INFO 06-12 19:01:11 llm_engine.py:161] Initializing an LLM engine (v0.5.0) with config: model='neuralmagic/Mixtral-8x7B-Instruct-v0.1-FP8', speculative_config=None, tokenizer='neuralmagic/Mixtral-8x7B-Instruct-v0.1-FP8', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, rope_scaling=None, rope_theta=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.bfloat16, max_seq_len=32768, download_dir=None, load_format=LoadFormat.AUTO, tensor_parallel_size=4, disable_custom_all_reduce=False, quantization=fp8, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), seed=1234, served_model_name=neuralmagic/Mixtral-8x7B-Instruct-v0.1-FP8)
(VllmWorkerProcess pid=2584199) INFO 06-12 19:01:16 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=2584200) INFO 06-12 19:01:17 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=2584198) INFO 06-12 19:01:17 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=2584198) INFO 06-12 19:01:21 utils.py:623] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=2584200) INFO 06-12 19:01:21 utils.py:623] Found nccl from library libnccl.so.2
INFO 06-12 19:01:21 utils.py:623] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=2584198) INFO 06-12 19:01:21 pynccl.py:65] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=2584200) INFO 06-12 19:01:21 pynccl.py:65] vLLM is using nccl==2.20.5
INFO 06-12 19:01:21 pynccl.py:65] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=2584199) INFO 06-12 19:01:21 utils.py:623] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=2584199) INFO 06-12 19:01:21 pynccl.py:65] vLLM is using nccl==2.20.5
Traceback (most recent call last):
  File "/usr/lib/python3.10/multiprocessing/resource_tracker.py", line 209, in main
    cache[rtype].remove(name)
KeyError: '/psm_10b3d52e'
Traceback (most recent call last):
  File "/usr/lib/python3.10/multiprocessing/resource_tracker.py", line 209, in main
    cache[rtype].remove(name)
KeyError: '/psm_10b3d52e'
Traceback (most recent call last):
  File "/usr/lib/python3.10/multiprocessing/resource_tracker.py", line 209, in main
    cache[rtype].remove(name)
KeyError: '/psm_10b3d52e'
(VllmWorkerProcess pid=2584198) INFO 06-12 19:01:24 custom_all_reduce_utils.py:179] reading GPU P2P access cache from /home/mgoin/.config/vllm/gpu_p2p_access_cache_for_0,1,2,3.json
(VllmWorkerProcess pid=2584199) INFO 06-12 19:01:24 custom_all_reduce_utils.py:179] reading GPU P2P access cache from /home/mgoin/.config/vllm/gpu_p2p_access_cache_for_0,1,2,3.json
INFO 06-12 19:01:24 custom_all_reduce_utils.py:179] reading GPU P2P access cache from /home/mgoin/.config/vllm/gpu_p2p_access_cache_for_0,1,2,3.json
(VllmWorkerProcess pid=2584200) INFO 06-12 19:01:24 custom_all_reduce_utils.py:179] reading GPU P2P access cache from /home/mgoin/.config/vllm/gpu_p2p_access_cache_for_0,1,2,3.json

Thanks for the report, I also noticed this in https://github.com/vllm-project/vllm/issues/5439 .
related code:
https://github.com/vllm-project/vllm/blob/1a8bfd92d5f35d638e3cfc8c4cd1779aeda0adfb/vllm/distributed/parallel_state.py#L433-L443
Initially I added this code because Python tracks the shared memory even if it is not the creator, and it will print many warnings. After I add this, it works fine in my machine.
Not sure why it errors in some other machines.

same here, H800

I will fix it tmr. Fortunately this is benign, and does not affect performance.

same here, A100, vllm 0.5.0 docker start

same error in 0.5.0.post1

https://github.com/vllm-project/vllm/pull/5512 is not included in 0.5.0.post1 . It will be included in the next release.
Note that this should not stop your program, so you can ignore the benign error. If you want to get rid of it, build from the latest code :)

same error here.
Traceback (most recent call last):
  File "/export/home/miniconda3/envs/vllm/lib/python3.9/multiprocessing/resource_tracker.py", line 201, in main
    cache[rtype].remove(name)
KeyError: '/psm_2ec8dce9'

esource_tracker.py", line 201, in main
cache[rtype].remove(name)
KeyError: '/psm_2ec8dce9'

#5512 is not included in 0.5.0.post1 . It will be included in the next release.
Note that this should not stop your program, so you can ignore the benign error. If you want to get rid of it, build from the latest code :)

same here


implement AddImport

Closes #19.
provides add import code action for unknown symbols.
...

[x] basic implementation for importing "modules" including submodules + members from loaded modules
[X] add tests
[X] add add import option [decide not to add option for now]
[X] add support for members from unloaded modules
[X] improve add import code action ordering a bit
[X] open related issue on a relative path (https://github.com/microsoft/python-language-server/issues/1707)
[X] provide abbreviation for well-known modules.
[x] handle context. ex) specific import based on context (only import type/function and etc)
[X] perf ex) cache lint result. run lint only for specific diagnostics and etc - now uses diagnostic service cache
[X] show quick fix in hover
[X] support reversed abbreviation for well-known modules
[X] support unique name on abbreviation

made not to load modules. can you take another look?

@MikhailArkhipov any more feedback?

@heejaechang Will it be possible to add an auto import feature? Importing with a quickfix is great, but it's the best when unresolved imports are auto imported on save.

There are so many options for what a particular unresolved name could be that it might be impractical to do it right on save with no user input, or in cases where the unresolved name is just a local error (and not intended to be an import). We're going to start simple and go from there.
(Also note that on-save is more of a formatting operation, which we don't currently have plans to handle directly.)

@heejaechang - I'd test it with Anaconda to be sure there are no performance issues and demo it to @Anapo14 to make sure behavior matches spec expectations. Otherwise LGTM.

thank you!

i see that https://github.com/microsoft/python-language-server/commit/254c8f17d1dcee3057203c94010efb542c4b3ec3 is not included in any releases, just master. does this mean it's not available in stable vs code?

See https://github.com/microsoft/python-language-server/issues/19#issuecomment-573902686 (where you also asked this). You can ignore the GitHub releases.


PerfView should inform the user the # of lost events for .nettrace traces

we should display the # of lost events for .nettrace files like we do with ETW traces. I have a trace with some very suspicious GCStats and it was due to lost events (it has 3 millions events with 15 million lost events based on the EventsLost from event pipe. happy to share the trace if you need.
also CC @noahfalk who helped me look at the lost events.

Please do share the trace. Happy to make this improvement.

done!


Add Crownpeak project

Hi, please add Crownpeak CMS to https://headlesscms.org/
Let me know if there are any issues with the pull request or project format/description.
Thank you!
Andrey Karpik
Director, Solution Architecture
<EMAIL_ADDRESS>

Awesome 👏


{Keyvault} Fix#7479: Add default value for disabled parameter

Fixes https://github.com/Azure/azure-cli/issues/7479,
Protection param has no default value, its None
Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Keyvault


Using aliases in imported markdown files doesn't work(?)

Hi,
I'm trying to use custom aliases in imported mdx-files, which doesn't seem to work.
Example: I have an mdx file that imports another mdx file, which also imports another mdx file, and I want to replace parts of the path to the imported file or a component inside that file with an alias. Aliases used in the initial mdx file work as expected, but the same alias doesn't work when it is used in an mdx file the initial file includes.
Docusaurus says: Module not found: Error: Can't resolve<EMAIL_ADDRESS>in 'C:\Users(...)
Is this something that should work and I need to do something extra in imported files, or was it just missed when developing this plugin? :)

👋 under the hood the plugin uses webpack aliases which works by replacing imports with the configured path. Anything valid with webpack aliases is also valid here.
@os.compos needs to map to a specific valid directory:
module.exports = {
  // ...
  plugins: [
    [
      "docusaurus-plugin-module-alias",
      {
        alias: {
<EMAIL_ADDRESS>path.resolve(__dirname, "../src/components/"),
        },
      },
    ],
  ],
};

Thanks for the quick reply!
I tried being clever and did the following:
<EMAIL_ADDRESS>path.join('/', '/src/components'),
<EMAIL_ADDRESS>path.resolve(__dirname, "../src/components/"),

Which results in:
<EMAIL_ADDRESS>"\\src\\components",
<EMAIL_ADDRESS>"C:\\Users\\[blah]\\docusaurus\\src\\components",

But even when using the latter alias it results in a "module not found" error ("Module not found: Error: Can't resolve<EMAIL_ADDRESS>in 'C:\Users...).
This is my import line:
import EditButtonR from<EMAIL_ADDRESS>Which sits in a 'partial' _document that is also imported.
Both aliases work in md/mdx files that are not partials!
I'm using the latest version of Docusaurus (2.0.0-beta.13). Are there any logs I could check to figure out what Docusaurus does with those aliases in partials?


"Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files." error

I solved the issue by:

Changing directly ExecutionPolicy value to "Bypass" under 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell"
Assigning Full Access permissions to the running account over the key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell" by right-clicking it and selecting Permissions
[Enter feedback here]

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

ID: 2c5aa434-8ccb-43a3-3f3b-f400e4663b2f
Version Independent ID: 8a7187a1-fe53-6bf0-b517-6225c8cb3233
Content: Connect to Exchange Online Protection PowerShell
Content Source: exchange/docs-conceptual/exchange-eop/connect-to-exchange-online-protection-powershell.md
Service: eop
GitHub Login: @chrisda
Microsoft Alias: chrisda

@RamkarUmmo, so are you saying that the steps already described in the topic didn't work for you? Bypass seems like a really bad security risk; worse than Unrestricted, if that's even possible.

Windows PowerShell needs to be configured to run scripts, and by default, it isn't. You'll get the following error when you try to connect:

Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.

To require all scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a Windows PowerShell window you open by selecting Run as administrator):
Set-ExecutionPolicy RemoteSigned

You need to configure this setting only once on your computer, not every time you connect.

That is correct, running Set-ExecutionPolicy RemoteSignedit did not work
for me even in elevated mode. That is why I focused on the registry
permissions. If you prefer to set any other suitable execution policy
setting then you can do it.
On Mon, Mar 23, 2020 at 4:26 PM Chris Davis<EMAIL_ADDRESS>wrote:

@RamkarUmmo https://github.com/RamkarUmmo, so are you saying that the
steps already described in the topic didn't work for you? Bypass seems like
a really bad security risk; worse than Unrestricted, if that's even
possible.

Windows PowerShell needs to be configured to run scripts, and by
default, it isn't. You'll get the following error when you try to connect:
Files cannot be loaded because running scripts is disabled on this
system. Provide a valid certificate with which to sign the files.
To require all scripts that you download from the internet are signed
by a trusted publisher, run the following command in an elevated Windows
PowerShell window (a Windows PowerShell window you open by selecting Run
as administrator):
Set-ExecutionPolicy RemoteSigned
You need to configure this setting only once on your computer, not
every time you connect.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/office-docs-powershell/issues/5143#issuecomment-602889537,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI2K42GRJFA3YKNTUSG4QA3RI7OYFANCNFSM4LSGS6UQ
.

@officedocsbot assign @yogkumgit

@chrisda  Thank you very much for the contribution and sharing this explanation. @RamkarUmmo
Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Supersedes/Replaces support

NNTP allows posts to be "edited" by using the Supersedes and Replaces headers. Not a super high priority since these have the same effect as just canceling and recreating the post, a workflow that is already possible to execute manually. The headers simply provide an in-post indicator that this was done, as opposed to having to check control.cancel.

Cleaning up old issues since this project is now unmaintained.


[Feature Request] Porting to Wechat MiniProgram

🚀 Feature

Motivation

Alternatives

Additional context

We do not have something planned for this and i am not familar with the complexity involved, but would be interestng to see if there are community members who want to tackle this

Maybe later.


Unable to use my own uploaded files

Unable to use my own uploaded files.

That's because we have reached our quota for openai service, we have increased it to see if it can work.

Hi, could you try it again with a smaller one?  I've tested it okay.

Hi, could you try it again with a smaller one? I've tested it okay now.

It still doesn't work.
Course.csv

I see. "Uploading" can work while "applying" it to the conversation fails in your case. It is because the file can't be decoded in utf-8.
We will try looking into that. You might also want to try other .csv which can work mostly.

I see. "Uploading" can work while "applying" it to the conversation fails in your case. It is because the file can't be decoded in utf-8. We will try looking into that. You might also want to try other .csv which can work mostly.

thx


Airlock manager can use user resources

Resolves #2499
What is being addressed
Allowing Airlock Manager to create and operate user resources.
Airlock Manager needs to have this capacity to be able to create VMs to perform Airlock Requests from.
How is this addressed

Add Airlock Manager to the list of allowed roles for all methods on user resources
Add Airlock Manager to the list of allowed roles for GET for workspace services and workspace service operations (otherwise, on the UI Airlock manager is going to see errors)
Restrict Research VM templates to only be used by WorkspaceOwner and WorkspaceResearcher
Made a change on the UI to allow Airlock Manager to see Connect button
Made a change in Guacamole to allow Airlock Manager to connect to VMs

/test

/test

/test-force-approve
No point in running tests as they don't use the new template

^ wrong PR! I do need to run tests on here

/test

/test-extended


Add FilePath to ChangeFeed

Description
Add FilePath directly on change feed to avoid costly hash matches when retrieving.
Related issues
Addresses [AB#104630].
Testing
Describe how this change was tested.

Missing code path to include file path in EndUpdateInstance.sql


Add timeout to CI golangci-lint

CI Linting job fails intermittently due to timeout.
Increase the timeout to 3m. The timeout issue and suggested
solution can be found at
https://github.com/golangci/golangci-lint-action/issues/297
Also update the golangci-lint version to 1.42 since
golangci-lint starts to build docker image with go1.17 with
version 1.42.1.
Signed-off-by: Jack Ding<EMAIL_ADDRESS>

/test e2e-aws

/cherry-pick release-4.10


Feature Request: Only optionally remove ExtraFieldPropagation headers from Kafka ConsumerRecords

This was originally posted here, but determined to be related to Brave rather than Sleuth; https://github.com/spring-cloud/spring-cloud-sleuth/issues/1083
The sample project uses Sleuth, but it's reproducible with just Brave as well: https://github.com/timtebeek/sleuth-kafkalistener/commit/eb68995605abdb1d9051b15cc5415e80f6b37cc4#diff-5af0c09fe0d657e3c92157a3a2dd42edR38
Short summary is:

I'm using a @KafkaListener & @Header
when I use ExtraFieldPropagation to propagate the value of @Header
then KafkaTracing removes the propagated header, leading to @Header to fail with:

org.springframework.messaging.MessageHandlingException: Missing header 'corporate_trace_id' for method parameter type [class java.lang.String]

The offending line is: https://github.com/openzipkin/brave/blob/master/instrumentation/kafka-clients/src/main/java/brave/kafka/clients/KafkaTracing.java#L143
which removes all propagated headers, including the extra propagated headers.
I'd like to be able to have Brave propagate my internal company headers, while still being able to access them with @Header. Can an exception be made configurable?

The primary reason headers are removed is to avoid something downstream from re-processing the trace. ExtraFieldPropagation is a bolt-on which makes the relationship of headers a bit murky.
I agree we don't need to drop "extra fields" right now, only the trace IDs. Let me think about if there is an easy way to change this without breaking something else.

PS I think this is more a bug than a feature request

https://github.com/openzipkin/brave/pull/784 fixes this

Awesome! Thanks a lot for the quick work! Sounds perfect! :)


Problem: CI is painfully slow

Solution: use a larger runner (4 cores, 16 GB RAM)

doesn't look like we have access to those runners so I canceled the workflow.
Lets revisit this another time when everyone is less busy


Table/Column annotations are empty in custom SqlServerMigrationsSqlGenerator

Consider the following EntityTypeConfiguration which, among others, adds Annotations to the EntityTypeBuilder:
public void Configure(EntityTypeBuilder<MunicipalityName> builder)
{
    builder.ToTable(TableName, Schema.Legacy)
        .HasKey(p => p.Id)
        .ForSqlServerIsClustered(false)
        .HasAnnotation("Foo", "Bar");

     builder.Property(p => p.Name)
        .HasDefaultValue("Foo!")
        .HasAnnotation("COLLATE", "Latin1_General_CI_AI");
 }

In this particular use case, I want to add a COLLATE clause to the column definition when a migration is executed. To do this, I created a custom SqlServerMigrationsSqlGenerator. In this Generator, I figured I could get a column's annotations and, if necessary, add additional SQL statements to the builder.
This is the custom SqlGenerator's Generate method:
protected override void Generate(CreateTableOperation operation, IModel model,
    MigrationCommandListBuilder builder)
 {
    Debugger.Launch();

    base.Generate(operation, model, builder);

    var tableAnnotations = operation.GetAnnotations();
    var columnAnnotations = operation.Columns.SelectMany(c => c.GetAnnotations()).ToList();

    // Additional logic, left out for brevity

Unfortunately, both tableAnnotations and columnAnnotations are always empty:

Note that the DefaultValue of "Foo!" does work:

Further technical details
EF Core version: 2.1.1
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system:  Windows 10 Enterprise
IDE: Visual Studio Enterprise 2017 15.7.5

You also need to override https://github.com/aspnet/EntityFrameworkCore/blob/release/2.2/src/EFCore.SqlServer/Migrations/Internal/SqlServerMigrationsAnnotationProvider.cs to transport annotation from model to MigrationOperations.


Is "Skolemizingblank nodes with Hash URIs" (#1187) a breaking change?

This is to flesh out whether PR 1187, which fixes https://jira.duraspace.org/browse/FCREPO-2108, constitutes a breaking change.  If not, then it could be released as 4.8.0 4.7.x.
See discussion here:

Minutes:  https://wiki.duraspace.org/display/FF/2017-04-13+-+Fedora+Tech+Meeting
Comment: https://wiki.duraspace.org/display/FF/2017-04-13+-+Fedora+Tech+Meeting?focusedCommentId=83236786#comment-83236786

A few notes (extracted from above and added):

It does not appear to make any change to the published Fedora API.
Existing resources will not change, but hash uris would be used for new resources employing blank nodes
Deleting a resource that used a blank node, leaves the .well-known URI behind in the repository.
It is possible to curl -X DELETE a .well-known resource (a blank node) and remove only the .well-known resource (blank node). `curl -X DELETE' against a hash URI will of course delete the 'parent' resource, not just that 'hash'ed resource.
It is possible to GET a .well-known URI and only receive a representation of the .well-known resource.  This change means a client might get unexpected (more verbose) output from a GET against a 'hash' uri.

The last three points raise issues when a client encounters unexpected behavior from the current implementation.

Hydra doesn't use blank nodes in FCREPO specifically because of the difficulty in handling the .well-known behavior. So, :+1: for minor release from me.

FYI: This change will break my downstream JSON-LD implementation of blank nodes to create ordered lists with the fromRDF method.   The way that the JSON-LD  processor creates @lists from RDF depends on the conventional bnode _:string representation in the RDF.   So, I have patched the JSON-LD library with a simple function that parses subjects and objects for the .well-known prefix and rewrites the URI as a _:.  This method can probably be adapted to the new #genid convention.  From my point of view, the critical thing is that there is a standard semantic that identifies an internal resource representaion as a blank node that can be made anonymous again in downstream processors.  I have yet to test my implementation with #1187

I am testing this and have found that 4.8.0 (somehow) changes the expectations of acrepo-connector-triplestore.  @acoburn may know more about the cause.  I do not know if this constitutes a breaking change, but for me, it no longer works.  I will continue to investigate.

As a note, @christopher-johnson , the master branch of fcrepo4 includes a couple of other "breaking change" commits, which likely are playing a role in the behavior you are seeing.
If we were to do a 4.8.0 release, it would involve a port of https://github.com/fcrepo4/fcrepo4/pull/1187 to the 4.7-maintenance branch.

@christopher-johnson So you believe this could be a minor release versus part of a major release?

Can someone remind me what "major release" means? Does that mean 4.8.0?

Right.  I suddenly find myself confused too.
Harking back, I believe we agreed that semantic versioning does not officially start until release 5.0, which would be when the software aligns with the API.  If that is correct, then "major release" in this sense (that is, a breaking change) would warrant a 4.8.0 release.  A non-breaking change would result in the next 4.7.x release (and perhaps back-ported to 4.6.x?).  But I though it had been decided there would be no "major" release until later this year.
If what I just wrote is accurate, it means I was wrong in the opening post to this Issue.  I should have written 4.7.x (I updated the original above).
It seems that @awoods has opened the door to a 4.8.0 release in his comment above and that, in such a scenario, this particular PR would be backported to 4.7.x.  In that situation, however, I would think this PR had been deemed backwards compatible and therefore we could just release a 4.7.x.

Thanks, @kefo, that makes sense.

Yes, @kefo, I was in the semantic versioning mindset when I mentioned 4.8.0 above (meaning a minor release)... I have also updated my comment for clarity.
We will stick with the non-semantic approach until 5.0.0.

Since the existing .well-known representation is not documented as part of the API, I do not think that modifying it can be a considered a breaking change (as per semver).  However, I think that #1187 can be leveraged towards documenting it as a standard for internal (skolemized) resource representation sourced from RDF that contains anonymous resources.  And creating a new documented standard could be significant for the community who may build implementations that depend on it, particularly in the context of "ordering RDF".  @awoods perhaps anonymous resource "skolemized representation" could be documented in the API specification or the ontology?
btw, the spring consolidation is what I initally observed to affect my implementation of the triplestore connector via a stand-alone activemq, as the master context has been changed.

Andrew started that his was non-breaking in the Jira issue if paid with another issue. Both of which were resolved and as Fedora 6 is now the LTS version, I'm closing this


Running website on Android device - the step with react-native is unclear

Website is running fine on my computer. Now I want to deploy that Website to my Android device. So I did it exactly like the Running On Device tutorial said:

Enable Debugging over USB

all fine

Plug in your device via USB

my list looks like this:

       List of devices attached
       5141a720        device

So this looks good.

Run your app

but here I have an issue because I have no idea what react-native means
npx react-native run-android
results in react-native is not known

Could it be that my project is not a react-native project and that's why react-native is not a proper solution for my case?
How to run that website on my Android device without transforming it as APK file?

Got it working. But the project is incompatible. You need to change several things to get it running as it's not react-native here.


Property 'includes' does not exist on type 'string'

if I hover on it property includes only show: "any".  it not reconize ES6

but the same code using other starter, I have intellisense on that, why ?

add this:
"lib": ["es6", "dom"],
to tsconfig.json


fix(version): update ngx-fabric8-wit to 6.17.4

@fabric8cd snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-707.int.rdu2c.fabric8.io

:tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


scraping followers/following also includes "who to follow" users

While scraping followers/following it also includes the "who to follow" users

Thank you. I fixed this issue


XML escape descriptions in parser

the current parser is generating invalid xml with attributes containing "<" and ">". this change will escape {><&} in descriptions when outputting XML

@petelliott thanks for the review but I prefer to address this issue on raylib.h than increasing parser complexity considering this kind of side cases.


Add sbt alias to run all tests everywhere

Fixes https://github.com/http4s/http4s/issues/5236. @rossabaker can you try locally? Although you will need a ton of stuff installed (Node, Firefox, Chrome, geckodriver, chromedriver).

I would like to identify all those things and get them in the nix-shell so they're there on all my machines and for any other nix folks who happen along.  I don't even know what two of them are, but I'll chip away at it.

Would this be a good time to spin off the browser modules into their own repo?  Since they're not being maintained in upstream branches, it seems that those could get a head start on The Great Schism.

Yep. This is what I was saying earlier today in https://github.com/http4s/http4s/issues/5230#issuecomment-923063605.

Ah, I don't think I fully understood what that meant yet.  Preparing this release is the first time I've had to get all this machinery running locally, so I'm only gradually beginning to understand it.  I think that would make a lot of sense.  It'll be the first thing that has a different release cycle than 1.0, but it'll give us some runtime getting used to those problems before the modules that are widely in production hit it.  I think it will be good for everything.

As I'm learning how you do things here I think so too, the dom modules are a sore thumb in the main repo. Daniel was ecstatic when we moved a lot of the browser testing in cats-effect to scala-js-macrotask-executor although we couldn't completely purge it.

What's an appropriate name? http4s-browser?  http4s-dom?  Do all of these modules belong in their own?

I'd say http4s-dom. These modules can all go together.

Superseded by #5241.


NR 24C3 gRPC APIs and adding Split APIs

What does this Pull Request accomplish?
Updates niRFmxNR in grpc-device-scrapigen to 24.8.0
Updates the gRPC Scrapigen Device Code for NR Evm Trace APIs.
Added new Split APIs for niRFmxNR  as part of the WI: https://dev.azure.com/ni/DevCentral/_workitems/edit/2820766
Why should this Pull Request be merged?
Updated to match the upcoming release of niRFmxNR 24.8.0
What testing has been done?
Copied files from grpc-device-scrapigen/out/rfmxnr/export/ to grpc-device/source/codegen/metadata/nirfmxnr/ and built grpc-device successfully.
Manually inspected nirfmxnr.proto file.

Please review this PR as I need to submit this on priority.
@reckenro @astarche @maxxboehme


Format the API gateway resource policy to match NGAP's policy

Working with NGAP support, it seems that we can format the API gateway resource policy to match the NGAP-defined policy and this will not trigger a replacement. This will allow us to make sure the deployed API stage is in sync with Terraform and not produce unexpected behavior preventing API access.
The resource policy includes many IP CIDR ranges, 2 VPC networks, and 1 VPC Endpoint. These values can be stored as GitHub Actions secrets and referenced by the Terraform code via variable to prevent sensitive data from being shared.

@nikki-t do you know if it is static for all environments or will it need to change based on environment? Or how often they update the policy on their side?

According to NGAP support, the resource policy should be fairly static where the CIDRs, VPCs and VPC endpoint shouldn't change.
I am investigating whether these values change based on environment as well as if NGAP could host the resource policy as an IAM policy or store it in an SSM parameter that we can retrieve in our Terraform.

@frankinspace What do you think about using the Terraform meta-argument ignore_changes as documented here? I could do some testing to see if this impacts the API stage deployment.

Yeah I think that could be a reasonable workaround as we continue to ask for support from platform


Python debugging not working

Debugger is not starting. It is just showed and disappear immediately. No error no message. At the same run button work as expected. It worked fine last week.
I have reinstalled python extension but issues still exist.
It is similar to bug raised in: https://github.com/microsoft/vscode-python/issues/7927
0 Starting Session:
{
    "name": "Python: File",
    "type": "python",
    "request": "launch",
    "program": "c:\\Data\\t.py",
    "logToFile": true,
    "console": "integratedTerminal",
    "__configurationTarget": 5,
    "python": "C:\\ProgramData\\Anaconda3\\python.exe",
    "debugAdapterPython": "C:\\ProgramData\\Anaconda3\\python.exe",
    "debugLauncherPython": "C:\\ProgramData\\Anaconda3\\python.exe",
    "cwd": "c:\\...\\JupyterNotebookProjects",
    "envFile": "c:\\...\\JupyterNotebookProjects/.env",
    "env": {
        "PYTHONIOENCODING": "UTF-8",
        "PYTHONUNBUFFERED": "1"
    },
    "stopOnEntry": false,
    "showReturnValue": true,
    "internalConsoleOptions": "neverOpen",
    "debugOptions": [
        "ShowReturnValue",
        "FixFilePathCase"
    ],
    "justMyCode": true,
    "workspaceFolder": "c:\\...\JupyterNotebookProjects"
}
20 Client --> Adapter:
{
    "command": "initialize",
    "arguments": {
        "clientID": "vscode",
        "clientName": "Visual Studio Code",
        "adapterID": "python",
        "pathFormat": "path",
        "linesStartAt1": true,
        "columnsStartAt1": true,
        "supportsVariableType": true,
        "supportsVariablePaging": true,
        "supportsRunInTerminalRequest": true,
        "locale": "en-us",
        "supportsProgressReporting": true,
        "supportsInvalidatedEvent": true,
        "supportsMemoryReferences": true
    },
    "type": "request",
    "seq": 1
}
385 Error:
{}
385 Exit:
Exit-Code: 2
Signal: none

You right - rolling back to 2021.12 solve the issue for me as well.

Duplicate of https://github.com/microsoft/vscode-python/issues/18436
If your conda version is older than 4.9.0, please update conda.


Fixing some aspects of the theme

@ascott this addresses:

alerts
buttons
tabs (incomplete)

Coverage decreased (-0.09%) to 81.345% when pulling eb43a8f2064da087cffb8b110400392d2d740547 on fix_theme into d6bb8c6935b5e9dc8f8464c314ff35f2c02191d8 on master.


docs(README): replace link Notifier App

Fix #60

:tada: This PR is included in version 1.2.11 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Strange issue running image fedora 36 vs 37 - rocker/rstudio::devel works, as does home build

I have just switched my base OS from Fedora 36 to 37 and encountered the following:

When executing
  podman run \
    -d \
    -p <IP_ADDRESS>:8787:8787 \
    -v /tmp:/tmp \
    -e ROOT=TRUE   \
    -e DISABLE_AUTH=TRUE \
    docker.io/bioconductor/bioconductor_docker

the container comes up fine, but using a browser, the RStudio server instance can't be reached. The spinner shows up, but then:

Could not connect to the R session on RStudio server.
Unable to connect to service (1)

When doing the same thing using docker.io/rocker/rstudio:devel, the base image to the bioconductor one, all is fine.

Additionally all is fine when I build the bioconductor image locally...

I have been unable to debug this. Does anyone have any insight into why Fedora 37 might bulk at the BC image from dockerhub (and all containers that are based on it and still around from before the 36/37 switch).

Could you give ghcr.io/bioconductor/bioconductor:RELEASE_3_16 a try? The dockerhub images might be the problem especially where you say rebuilding locally works. I've been using GHCR images since taking over, and they might be out of sync. I am looking at resyncing them now

That image gives me exactly the fame trouble as does the docker. Io one...
On March 8, 2023 6:36:38 PM UTC, Alexandru Mahmoud @.***> wrote:

Could you give ghcr.io/bioconductor/bioconductor:RELEASE_3_16 a try? The dockerhub images might be the problem especially where you say rebuilding locally works. I've been using GHCR images since taking over, and they might be out of sync. I am looking at resyncing them now
--
Reply to this email directly or view it on GitHub:
https://github.com/Bioconductor/bioconductor_docker/issues/70#issuecomment-1460669444
You are receiving this because you authored the thread.
Message ID: @.***>

I am not entirely sure what the problem could be in that case... Did the podman version change between the two VMs?
I found this issue which might be related https://github.com/containers/podman/issues/11528  ?
If you haven't already, perhaps try with -p 8787:8787 instead of -p <IP_ADDRESS>:8787:8787

As I wrote above: using the docker.io/rocker/rstudio image (which the bioconductor one uses as a base) works fine ... the port remapping issue should hit both ...

The issue persists as of 2023/03/31, BUT docker.io/bioconductor/bioconductor_docker:devel actually works!?

I am still not sure what this could be, as it works okay whenever I try to run it...
One thing to note, but again this is largely a guess, this issue might be related? https://github.com/containers/podman/issues/8132
I can confirm the new image does have empty layers, as we're using that to support various bases for arm64 vs amd64 architectures. The only change in the current devel vs 3.16 published images is the lack of support for arm64, so my best guess is it's either related to the fact that images exist for both archs, or the new build file with empty layers...

@r-cheologist Is this still persisting?

Oh boz. I have been neglecting this, but Now I switched from fedora 37 to 38 and end up having exactly the same issues AGAIN!? For both the latestand develimages from docker.io.
The starting call above does not work in my unpriviledged podman setup, neither does setting the password and forgoing the DISABLE_AUTH - as I am unpriviledged using user root and password as given by the environmental variable should work, but it doesn't.


Allow pkgconfig acquisition and fix some packages for its use (1/3)

This acquires pkg-config lite (the version without additional requirements) and fixes libsndfile, flac, fftw3 and ffmpeg for its use.
This is the first PR in a group of interdependent PRs: pkgconfig, waf -> aubio
While pkg-config may be questioned as not vcpkg conform I think it is useful for backwards compatibility. I think packages with broken pkg-config support (like the ones touched here) could be gradually updated as required.

One big issue with pkg-config (as far as I'm aware) is that it isn't relocatable. The .pc files have hardcoded paths which will break as soon as you try to use Vcpkg over a network share or move it to a new directory or use subst to remount it.
Another is that this will probably not handle debug mode includes correctly. In every port that generates CMake package config files, we have to fix this. I believe pkg-config will have the same issue, but with far less motivation to fix it.
What about simply generating the .pc files on demand inside the aubio build? You could just stamp out .pc files that match exactly what's required (and individually for debug and release!), which would completely fix the problem.

One big issue with pkg-config (as far as I'm aware) is that it isn't relocatable. The .pc files have hardcoded paths which will break as soon as you try to use Vcpkg over a network share or move it to a new directory or use subst to remount it.

Both are good points. I didn't think of relocation. I was a aware of the includes issue, but thought it might not relevant because vcpkg provides the corrects paths anywas. Aubio finds its header in the debug build too...
So construct fake pc-files on the fly? That's a creative and amusing idea, I'll give it some thought! ;)

I'm also going to take a stab at a buildsystem replacement for aubio -- it looks like it's honestly just "*.c"[1], which makes for an extremely short CMakeLists.txt :).
[1] https://github.com/aubio/aubio/blob/3c230fae309e9ea3298783368dd71bae6172359a/src/wscript_build#L15

As to portability: at second though I am not sure there is a problem: at build-time the pc-files are generated from templates which use the proper paths for the build, of course, the prefix is generated as required for the build (except for include in debug, and in practice it doesn't seem to be an issue). At runtime (which is where relocation is relevant, right?) they are not used anymore?
To create fake ones nevertheless seems attractive, it makes the build independent of future changes...
As to the include problem: feels like the fact that you don't have includes in the debug branch might be a problem in other cases too? I guess you're trying to avoid code duplication? But I've been wondering what happens if somebody just want's to add the debug branch installed/triplet/debug to a build via cmake_prefix_path - there is a potential problem, isn't there? At least for simplicity... Maybe it would make sense to create junctions to the release include-folder in the debug branch as well?

@ras0219-msft , sounds great! ;)

I think we can currently continue on our strategy of buildsystem-replacement for libraries that currently rely on pkgconfig (I believe there's diminishingly few of these).
Thanks for the PR anyway!


Issue with TwigBridge for Laravel 6

Hi, first of all, this is my first post on GitHub so please, be indulgent with me :)
For couple of days, I’m trying to upgrade my Laravel app (was under 5.4) by going step by step for upgrading it.
Now, I'm trynna upgrade to Laravel 6.x and it loooks like that TwigBridge is causing conflict. Plus, I'm having conflict with illuminate/view that I'm not getting.
Here's is my composer.json, and my terminal output
composer.json
{     "name": "laravel/laravel",     "description": "The Laravel Framework.",     "keywords": ["framework", "laravel"],     "license": "MIT",     "type": "project",     "require": {         "php": ">=7.2.0",         "barryvdh/laravel-dompdf": "^0.8.0",         "dompdf/dompdf": "^0.8.3",         "laravel/framework": "6.0.1",         "laravel/tinker": "~1.0",         "laravelcollective/html": "^5.3.0",         "neutron/temporary-filesystem": "^2.2",         "phpoffice/phpspreadsheet": "^1.29",         "rcrowe/twigbridge": "^0.9.4",         "tinymce/tinymce": "^7.4"     },     "autoload": {         "classmap": [             "database"         ],         "psr-4": {             "App\\": "app/"         }     },     "autoload-dev": {         "psr-4": {         }     },     "scripts": {         "post-root-package-install": [             "php -r \"file_exists('.env') || copy('.env.example', '.env');\""         ],         "post-create-project-cmd": [             "php artisan key:generate"         ],         "post-install-cmd": [             "Illuminate\\Foundation\\ComposerScripts::postInstall",             "php artisan config:cache",             "php artisan route:cache"         ],         "post-update-cmd": [             "Illuminate\\Foundation\\ComposerScripts::postUpdate",             "php artisan config:cache",             "php artisan route:cache"         ]     },     "config": {         "preferred-install": "dist",         "sort-packages": true,         "allow-plugins": {             "kylekatarnls/update-helper": true         }     } }
Output errors
`# composer update
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- rcrowe/twigbridge v0.9.12 requires illuminate/view 5.5.|5.6.|5.7.|5.8. -> satisfiable by illuminate/view[v5.5.0, ..., v5.8.36].
- rcrowe/twigbridge v0.9.10 requires illuminate/view 5.5.|5.6.|5.7.|5.8.x -> satisfiable by illuminate/view[v5.5.0, ..., v5.8.36].
- rcrowe/twigbridge[v0.9.7, ..., v0.9.11] require illuminate/view 5.5.|5.6.|5.7. -> satisfiable by illuminate/view[v5.5.0, ..., v5.7.28].
- rcrowe/twigbridge v0.9.6 requires illuminate/view 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.* -> satisfiable by illuminate/view[v5.0.0, ..., v5.6.39].
- rcrowe/twigbridge v0.9.5 requires illuminate/view 5.0.|5.1.|5.2.|5.3.|5.4.|5.5. -> satisfiable by illuminate/view[v5.0.0, ..., v5.5.44].
- rcrowe/twigbridge v0.9.4 requires illuminate/view 5.0.|5.1.|5.2.|5.3.|5.4.* -> satisfiable by illuminate/view[v5.0.0, ..., v5.4.36].
- Only one of these can be installed: illuminate/view[v5.0.0, ..., v5.8.36], laravel/framework[v6.0.1]. laravel/framework replaces illuminate/view and thus cannot coexist with it.
- Root composer.json requires laravel/framework 6.0.1 -> satisfiable by laravel/framework[v6.0.1].
- Root composer.json requires rcrowe/twigbridge ^0.9.4 -> satisfiable by rcrowe/twigbridge[v0.9.4, ..., v0.9.12].
`
I already thanks yall for answers :)

Ok, I finally solve the issue by upgrading illuminate/html


Regarding the new sorting function, should there be time sorting by adding mods?

Regarding the new sorting function, should there be a time to add mods for sorting.
I add a lot of mods, but I'm used to managing it by the time I add the mods myself. Because the more newly added a mod is, the more I need to test its functionality and stability. But sometimes using the sorting function of the software will disrupt the order of my mods, and my original order of use can never be restored, which makes it difficult for me to identify which one is my newly added mod.

Fixed by 7b6f40fb151bc64a75b973dd4a72a58efc95a3ef which makes sorting only apply to the view and doesn't change the underlying mod order. This means that when sorting is disabled, the underlying order will be visible which will show most recently added mods at the top and allow manually re-ordering like before.


Adding Cluster Scaling Documentation

Why:

Adds documentation showing how to deploy cluster auto scaling w/ AWS

This change addresses the need by:

Closes #9

Orginal Issue Requirements:

[x] Add new master and worker nodes pro-actively

Master is going to be much harder due to horizontal scaling not directly correlating to more scale. This IMO should be part of cluster upgrading, Bring up new masters with original desired state, shift traffic over shut down old cluster. Thoughts?

[ ] Add new worker nodes based upon application alerts

I would assume this relates to HPA + Cluster Autoscaling - HPA notices app metrics causing it to scale, then the resource offers extending beyond the cluster available resources causing CA to add additional nodes. Thoughts?

[x] Add new workers nodes if a certain application can be deployed because of lack of resources

@arun-gupta updated based on the feedback. 🚀


Slack community link is no longer active

Slack community link is broken -
https://github.com/opensearch-project/project-website/blob/8f05bc4ed4c40fb505fe2129967899a823e27613/_includes/redesign_buttons.html#L172
What I see when I go by the link:

Hello @eliskovets - thanks for letting us know - will work to resolve today

https://opensearch.org/slack.html now has an updated invite link - thanks again @eliskovets


sources: pass the library dir to the sources

The idea is that source can themselves spawn other modules, esp. new secrets modules. For this they need to know the library dir, aka 'libdir' throughout the osbuild source. Therefore change the SourceServer to directly get the library directory instead of just the sub-directory to the sources. Then pass the library directory to via the JSON API to the source.
Adjust all usage of the SourceServer, including the tests.
If it goes in before #405, it can be changed to use that instead of the __file__ hack.

This does not hard-conflict with #405. Therefore, I am going to merge this. We can fix #405 after merge, or as part of the PR. I am fine either way.


Enable "comma-dangle" rule

I would like to enable the ESLint comma-dangle rule using the always-multiline configuration (see http://eslint.org/docs/rules/comma-dangle#always-multiline).
To prevent this from becoming a huge bike shedding discussion I would like to focus on the pros and cons of trailing commas. Feel free to complete the list in the comments.
from https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Trailing_commas:

Trailing commas (sometimes called "final commas") can be useful when adding new elements, parameters, or properties to JavaScript code. If you want to add a new property, you can simply add a new line without modifying the previously last line if that line already uses a trailing comma. This makes version-control diffs cleaner and editing code might be less troublesome.
JavaScript has allowed trailing commas in array literals since the beginning, and later added them to object literals (ECMAScript 5) and most recently (ECMAScript 2017) to function parameters.
JSON, however, disallows trailing commas.

Pro

less work when adding new items to a list or object
easier to read version control diffs

Con

not supported in old browser (irrelevant thanks to Babel)
not supported in JSON (ESLint doesn't work in JSON, and single quotes don't work there either but we still use them)

I don't have a strong opinion in favor or against this rule. I can definitely see the pro's, though I think it's not that big of an issue regarding interpretability of the diff. But enabling the rule would be ok for me.
I abstain from voting, though I think we should enforce either one, as having ignore is confusing since both ways are allowed.

No strong opinion from my side either and agreeing with @pangratz, that setting it soon is better than staying ambiguous on that rule. I'd be for trailing commas if this means that we can write this one down

FWIW https://github.com/ember-cli/ember-cli/blob/master/.eslintrc.js#L61

I don't like it, mostly for aesthetic reasons.

This makes version-control diffs cleaner and editing code might be less troublesome.

While this sounds like it makes sense I have never seen any of the 2 problems occur in reality. I certainly never have been troubled by having to add a comma when adding a new element to a list ;)
Obviously this is a topic that people tend to have strong feelings about like everyone used to have about tabs vs. spaces (maybe there are communities where the debate is still ongoing even) and I have no interest in getting into a long discussion about a detail that doesn't really matter much anyway. So if it's a majority decision to add it let's add it.
Another reason I don't like this though is that the concept of "If in the future I might ever do x then if I do y now that will make things easier" generally leads to a lot of bad things in software engineering (I'm aware that saying this in this context is as much an exaggeration as using the word "troublesome" in the Mozilla docs quoted above 😉).

While this sounds like it makes sense I have never seen any of the 2 problems occur in reality

they do occur daily, but apparently you're not quite as annoyed by them as others 😉

So if it's a majority decision to add it let's add it.

👍


How to improve speed for real time face recognition

Hi ,
I extracted the embedding of my own dataset and feed it to a knn classifier, using the opencv as described in the tmp scripts im doing recognition on a video file with 20FPS and its frame resolution is 2688*1520 what i found is on y system (Nvidia 960M) anf GPU system (Tesla k80) the performance is same. below are my observations
All these observations is under the Ubuntu 16.04 OS
  in Nvidia 960m (640 cuda cores) with 4GB memory
  on 4mp 20ps 2688*1520 video file
  factors: 1 minute original video

 detection factor 0.8: 862.42 S, 1.47 FPS, 3393 faces
 detection factor 0.5: 412.88 S, 3.06 FPS, 1983 faces
 detection factor 0.25: 298.35 S, 4.24 FPS, 1400 faces

  in Nvidia Tesla k80 (2496 cuda cores) with 12GB memory
  on 4mp 20ps 2688*1520 video file
  factors: 1 minute original video

  detection factor 0.8: 941.46 S, 1.34 FPS, 3393 faces
  detection factor 0.5: 434.76 S, 2.91 FPS,  1983 faces
  detection factor 0.25: 315.38 S, 4.01 FPS, 1400

im using the prebuilt tensorflow pip package only. Is there any improvements when i built from sources? What is the factor that effects on performance.

 How to improve detection part.

20 fps is about what I'm getting as well on my 1060.
But this seems pretty fast already no? What would be your target?

20 fps is about what I'm getting as well on my 1060.
Really? can you share our code.

I didn't say that im achieving the 20 FPS in my issue, I say that I'm working on 20 FPS video file (as input).

@fgervais , on which resolution you are achieving the 20 FPS as output.

Thinking about it now, I was mistaken.
I do get about 20 fps of video output but I only run face detection on 1/3 of the frames. So I must be at about 6 or 7 face detection per second.
As for the resolution, I must say that I don't know. I looks quite small on my 3440x1440 monitor so it might be 640x480 of something like that. I'll let you know next time I get to work on this project.
The code is available here https://github.com/davidsandberg/facenet/pull/450.

I just verified, my input resolution is 640x480.

I got the nvidia 1080 below are the results
  in Nvidia 1080 (2560 cuda cores) with 8GB memory
  on 4mp 20ps 2688*1520 video file
  factors: 1 minute original video

  First time:
  detection factor 0.8: 486.30 S, 2.60 FPS, 3393 faces
  detection factor 0.5: 219.90 S, 5.75 FPS,  1983 faces
  detection factor 0.25: 152.52 S, 8.29 FPS, 1400

@fgervais, Do you have any idea to improve the fastness?

Has anyone look into it.

As I do is: using tracking and then search face images only in ROI. Tracking also help you to group face images of same user in one folder and then you can perform recognition + vote on this folder to get user's name more correctly.


Update global state with TXs once hare terminates

When the Hare protocol terminates on layer j, if the global state is updated to layer j-1, we update it according to the blocks in the Hare output set. If not, we wait until all (open) Hare consensus processes in previous layers terminate, then we update the state, after updating layer j-1.
Possibly, the logic was already applied here: https://github.com/spacemeshos/local-testnet/issues/10

Currently Hare consensus processes can run simultaniously, up to hdist consensus processes.
For V2 of the protocol, we will heavily rely on hare consensus and update global state when hare is terminated
To do so, we need to implement some new features to hare consensus process.

[] Implement event for consensus process termination
[] implement receiver function that listens to hare termination and updates state in consecutive order
[] test new mechanism and edge cases
Important note: this will change the logic of state update and will not update state if our assumptions are broken and hare does not terminate, and will basically freeze global state forever.
@gavraz @barakshani please review and add you comments

A small comment: it is true that it makes sense to run at most hdist CPs, however the hare-iteration-limit is an independent parameter, so it may be bigger.
For you note at the end, sure, it is also the case with the Tortoise. Research works on a more robust Hare. Future tasks (not under this epic) will include assertion by the Tortoise, and reversion of the state in case the Tortoise outputs a different state (set of contextually valid blocks).


Migrated test_check_waagent_log from os-tests.

Also added a test_util function to filter log files. It will be useful
for similar test cases (in os-tests there was also an auxiliary function
for that).

Did the test run in CI?

Could you build the container with this code so it runs on our CI (I hope this is the last time you have to do it, automation coming!)


Improving Dev UX for K8s updates

Even I (who wrote the stuff) regularly mess up K8s updates because they require coordinating a bunch of different things.
Quick checklist for how it's done currently:

Replace the the 1 at the start of the K8s version number with a zero (1.24.2 => 0.24.2) and search/replace that version number in go.mod
Replace the entry for k8s.io/kubernetes manually by putting the normal version number
Update the KUBERNETES_ version numbers in build/print-workspace-status.sh
go mod tidy
bazel run //:gazelle-update-repos

This is easy to screw up and should be documented and/or improved as much as possible.

The Kubernetes version number is now automatically derived and we've now done this multiple times so people can just look at past CLs. Serge and Tim have also successfully done this at least once so we have multiple people with experience.


Updates boost to version 1.61, add the date_time module

Updates boost to version 1.61 and adds the date_time module. The date_time is needed for the ReliableTopic implementation.

Test PASSed.

Test PASSed.


Possibility to add traces to an existing chart

Description
Without a refresh, the chart will not show the three traces after clicking the button. After a refresh, it shows the three traces. The goal would be to avoid refreshing the page to show the traces.
from taipy.gui import Gui

data = {
    "x": [1, 2, 3],
    "y": [1, 2, 3],
    "y2": [4, 5, 1],
}

properties = {
    "x":"x",
    "y[1]":"y",
    "y[2]":"y2",
}

def change(state):
    state.data['y3'] = [14, 15, 11]
    state.properties['y[3]'] = "y3"
    state.refresh('properties')
    state.refresh('data')

Gui("<|{data}|chart|properties={properties}|> <|change|button|on_action=change|>").run()

Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%
[ ] Propagate any change on the demos and run all of them to ensure there is no breaking change
[ ] Ensure any change is well documented

property rebuild ?

Not working with rebuild as well

does this work if you do not use the properties ?

And how can I do that?

It does not work because, typically, I don't know that there is a third trace (or fourth, fifth...). I just discover it in runtime. But maybe, it is not the correct way to add a trace, they are maybe better ways

I must there might be a slight bug as it's working half time 👿😗

I was thinking about this when I said it is maybe not the correct way to create to add a trace. If it can work everytime, it is even better

That's the way to do it and it's supported for a long time.
Bugs happen...

Do we have to create another issue for this one ?

No

looks like it was a bug in plotly ...
I'll push a PR to make sure that we pick up the right plotly version (2.32.0)


l2 norm + Normalization

Hi, thank you for the nice implementations!
I have a question on running l2 norm application with data normalization.
While data is normalized, it seems like the perturbation \epsilon is not scaled wrt data.std.
Correct me if i'm wrong.
Thank you in advance
~ Lee

@sungyoon-lee Can you provide more details? Which python script you are using for L2 norm robust training? Thanks.

@huanzhang12
I meant  https://github.com/KaidiXu/auto_LiRPA/blob/master/examples/vision/simple_training.py
I've run another code for IBP under l2 norm 36/255 in CROWN-IBP (https://github.com/huanzhang12/CROWN-IBP/blob/master/train.py). When data is normalized, as mentioned in https://github.com/huanzhang12/CROWN-IBP/blob/master/train.py#L128, I think I should use different eps (Correct me if i'm wrong). For example, if std=(0.2,0.2,0.2), then I have to use eps=36/255/0.2 instead of eps=36/255. Thus, when I fix the eps=36/255 and use different setting "training_params:loader_params:normalize_input=true/false", they have shown significantly different results. However, most of the loader (e.g. CIFAR-10: std = [0.2023, 0.1994, 0.2010]) uses different std's per channel.
Similarly in https://github.com/KaidiXu/auto_LiRPA/blob/master/examples/vision/simple_training.py#L75, it seems like there is no difference. Do I have to manually change the loader to have same std's per channel in https://github.com/KaidiXu/auto_LiRPA/blob/83206c7c4620174da4bb4e3d5e72ef211076e10c/examples/vision/datasets.py#L58
Maybe I should have make this issue in CROWN-IBP. I hope this can provide enough details. Thank you in advance!

I see. Indeed in simple_training.py we did not add normalization for other norms. I only tested to train L2 perturbation on MNIST/Fashion MNIST so this has not been handled for CIFAR.
When the input is normalized, the network receives a scaled input but we still need to guarantee the L2 perturbation is less than epsilon on the original, unnormalized input. Essentially, this makes the perturbation epsilon ball becomes an ellipsoid instead of a ball for the normalized input. You will need to slightly modify here: https://github.com/KaidiXu/auto_LiRPA/blob/master/auto_LiRPA/perturbations.py#L114 to use a vector of eps as input considering the perturbation is an ellipsoid rather than a ball.
A simpler solution would be using a normalizing factor like 0.2, 0.2, 0.2 so the scaled epsilon ball is still a ball, and you can directly use eps/0.2 as the effective eps for training.

Thank you!


Question

Hi.
Thanks for making.
So is this need to be installed at my(game publisher's) own VPS(virtual server hosted)? (ubuntu mostly?)
How to do it?

Hello, yes, you have to use a VPS to host a fork of this API using your own data, I'd recommend using a private fork to prevent exposing sensitive information on internet.


added new projects to page

added the changes where I though they would take effect. Npm run start yields errors so I was not able to run it locally.

no i did not run npm install, That could be the source of everything.
On Mon, Sep 5, 2022 at 9:19 AM Frank @.***> wrote:

@.**** approved this pull request.
Looks good to me. To be sure, did you run npm install first? (see
README.md)
Also, what were the errors?
—
Reply to this email directly, view it on GitHub
https://github.com/gomtl-consulting/gomtl-consulting.github.io/pull/1#pullrequestreview-1096446576,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO7E73WFK63HH6NWTAG7EYLV4XXNJANCNFSM6AAAAAAQENQMTE
.
You are receiving this because you authored the thread.Message ID:
<gomtl-consulting/gomtl-consulting.github.io/pull/1/review/1096446576@
github.com>


[Feature]: I can add back to top button for readme file as it is quite lengthy.

🔖 Feature description
A button to navigate to top of the repo
🎤 Why is this feature needed ?
To take less time and navigate easily
✌ How do you aim to achieve this?
I will submit a pr
🔄 Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?

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

Are you willing to submit PR?
Yes I am willing to submit a PR!

I have submitted a pr #690 to complete this please check.


pass error message in channel

Current failures on interacting with the API just return null which is not super useful. Passing in the error message can give context as to what went wrong.

Thank you :)


how to create directory 'bm_50maxdist_2num_car'

hello
i tried to train btcdet. but error occured.
error message :
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/BtcDet/data/kitti/detection3d/bm_50maxdist_2num_car/1788_0.pkl'
do you know how to create directory and *.pkl files?

I think the code has a bug and multifindbestfit generates bm_50maxdist_2num_Car where it should be bm_50maxdist_2num_car. So either rename the folder or change the code to look for capitalized Car

To fix it, modify "CAR_MLT_BM_ROOT" of the file in BtcDet/tools/cfgs/model_configs/btcdet_kitti_car.yaml from
CAR_MLT_BM_ROOT: bm_50maxdist_2num_car
to
CAR_MLT_BM_ROOT: bm_50maxdist_2num_Car


[bug] Fix UI crash due to K8s context search in modal

Signed-off-by: Pranav Singh<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

There are some more consideration to fix.
Like only one keystroke is registered at a time and then the cursor moves out of the text field. @MUzairS15 could you please tie-off the remaining search issues related to it?
https://user-images.githubusercontent.com/73700530/196959803-366b91d7-8e4b-465a-8d2f-d6184a8984a3.mov

There are some more considerations to fix.
Like only one keystroke is registered at a time and then the cursor moves out of the text field. @MUzairS15 could you please tie-off the remaining search issues related to it?
Screen.Recording.2022-10-20.at.6.49.18.PM.mov

Yes sure @theBeginner86 , since it is not complete converting to draft.

@theBeginner86 Let's merge this, since it fixes the UI breaking when using search, I will address other things. I thought it might be a quick fix.


Add releasing guideline

Take https://github.com/OpenZeppelin/openzeppelin-solidity/blob/master/RELEASING.md as an example

Handled via lerna


Initial suggestions

@yaacovCR deprecation has the advantage that the fields are decommissioned in subschemas. Support for both would be nice (directives and deprecation).

Also, custom directives are difficult to support in languages that don’t include them (like ruby). Would be nice if everything remained possible without needing custom directives.

Quick look but my gut responses are:

a @requires directive should probably match the federation signature. Otherwise, awkward.
custom directive offers no solution for “turning a field off” in the subschema and activating it in the gateway, which is kind of a cool aspect of deprecation. Maybe we could support both?
deprecation is extremely cross-language friendly, while custom directives are harder to support outside of node apps. It would be nice to have an SDL that was pretty easy to opt into across languages (one major strike against federation).
some kind of @merge directive would be a nice direction to go for marking merge services; been thinking about that since last night and have some ideas for a schema it could use; will propose.

Then... to the point of “on by default” of computed services, YES!! Love it. We do still have that issue of delegation references though. To address that, how about the ability to give subschemas a name string? When performing isolation, both versions could retain the same name and be treated as an array. It would actually be a better dev experience in setting up delegation if you could simply provide a name string rather than a tangible subschema object (less bookkeeping for the developer).

The more I think about the deprecation scenario, the less strongly I feel about it. Custom directives would be the more “proper” way to do this, and language support is a problem that probably doesn’t make sense to be constrained by. There are always those deprecation transforms that could be used by a developer, and could have a documentation footnote. So, I think we’re good on that point.
So, my two major thoughts distilled from all of the above:

the custom directive SDL needs some tuning. We’re so close to the federation @requires directive that it’s hard to justify not making those interoperable because they do the same thing (although merging doesn’t need that silly @key!). Also, the SDL should be expressive without getting bogged down by internal implementation details.

having isolation run as part of stitchSchemas is REALLY good. It avoids a lot of strange documentation in favor of having things “just work”. That said, we should probably put a system in place to handle the delegation reference issue. If named subschemas don’t work (I suppose there needs to be some direct reference to the schema itself), then perhaps the permutations could just hold a circular reference to each other; or a parent/child reference established. Any of these patterns would allow the developer to only hold the original subschema config, while delegation could inspect it to get the full faceted schema.

I like the fields or selectionSet option.
Named subschemas would work fine, but would not be backwards compatible, so I suggest adding as separate PR.
Would suggest changing logic internally to delegate to both SubschemaConfig when delegating in stitched schema to a schema that has been split, then merging result. Metadata about all schemas saved to schena.extensions.stitchingInfo, can just add more metadata there.
Agree that directives way to go. A directive from / to comment converter may be useful in general to support languages without directives.
Agree in terms of isolating by default, think we can drop isolate property/argument altogether and just always isolate.

Although allowing fields or selectionSet means we cannot make argument required, which is a bummer for correctness, but what are you gonna do...

Been updating the docs...

We could put type level selectionSet and other config options in SDL as well...
Not to confuse things too much, should that be requires on type rather than key?

Would suggest changing logic internally to delegate to both SubschemaConfig when delegating in stitched schema to a schema that has been split, then merging result.

Actually we need to delegate to the non-computed schema and then type merging will take care of the rest

i think we can consider a flag though to disable the isolating behavior on the subschema level (rather than the field level) as some subschemas will never have this problem because they will never return stub data, and they might still want to offload expensive keys using a field selection set, as in the original field selection set examples -- at least from what I understand. That can be a later performance improvement, doesn't need to be a blocker.

Another small point: rather than isolated: true as the setting, I think it makes the most sense just to call it required: true to match the corresponding directive. It documents fairly intuitively that way: https://github.com/ardatan/graphql-tools/pull/1989/files#diff-112839495c94df82bbbb7843b4e71b31R409-R426

I took out the isolated field, actually, and am just enabling it whenever a field selection set is present.
If the schema is written so that any items of the stub type actually can supply the required field, then my thought is that this behavior should be disabled on a per subschema basis.
Meaning, either your schema can resolve all of its fields, or it can't. We assume it can't to be more flexible, but if it can, my thought would be for end users to disable this isolation approach on a per subschema basis. This property on the subschema would be something extremely catchy like disableFieldSelectionSetIsolation
I would also add a caveat in the docs that computed fields are not necessarily recommended, and that it may be simpler just to use query batching.

There’s a strongly worded “disadvantage” statement in the docs making clear light of the shortcomings. I didn’t go so far as to say “not recommended” because they do things that are not possible with other aspects of the system. If you need to do those things, you need this approach, and should be aware of the disadvantages.

Sounds good, just in terms of plumbing, do you want to merge this into your PR, or should I just rebase this against master?

As for @key — I waffle on that one because, as you say, merging could fulfill the fields at the type-level as the base selection set, but doesn’t need to. The downside is that it’s easy to confuse the policy with federation, where @key is a loaded field that is required for arcane purposes. One of the beautiful aspects of merging is its simplicity, so it’d be a shame to confuse that and make it look more confusing than it is.
I’d say let’s leave out @key for now and explore it in a separate PR that might also add a @merge directive for merge services. This SDL syntax is a really good direction to head in as it allows fully-encapsulated service definitions.


[DO NOT MERGE] New004

@kc611 @stuartarchibald -- here is the solution to the issue you are facing regarding preservation of git-history.

Make three branches, each does a git mv of pythonapi.py to old_pythonapi.py, new_pythonapi.py and preservepythonapi.py respectively.

Use an octo-merge to merge all three branches.

Make an additional commit that does git mv preserve_pythonapi.py pythonapi.py to restore the original file for editing.

You can then edit all three files as needed and history will be retained through git blame without having to use -C and this should show up on GitHub.

Hope this helps.

To be used in https://github.com/numba/numba/pull/9446 -- this does a double copy of a file whilst preserving the original and retaining the history visible through git blame.

closing now as purpose has been served


Catapult indicator

catapult indicator

@Optimus-Q - what is this branch versus infertrade_new_rule_based_ta?

I created this branch for catapult indicator.
Do I need to put all new strategies in the same branch infertrade_new_rule_based_ta?