OpenGL warnings

Some bugs with Unbuntu after installation.
Seems like another Electron bug.
https://github.com/Jam3/devtool/issues/2#issuecomment-173252481
Some error after simple installation on Ubuntu (With VirtualBox)
$ devtool
pci id for fd 15: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
[8871:0120/170708:ERROR:buffer_manager.cc(342)] [GroupMarkerNotSet(crbug.com/242999)!:D06E021D8F330000]GL ERROR :GL_INVALID_ENUM : glBufferData: <- error from previous GL command
[8871:0120/170709:ERROR:texture_manager.cc(1995)] [GroupMarkerNotSet(crbug.com/242999)!:D062021D8F330000]GL ERROR :GL_INVALID_ENUM : glTexImage2D: <- error from previous GL command

Is it possible that this is a result of running in a VM that doesn't have 3D acceleration enabled? (or maybe it does, but can't support some features?)

@molokoloco are you still getting this on the latest version? We updated to the newest Electron.
You can update like this:
npm i devtool -g

Sorry, tried again today..
Updated to latest version
Always some webgl notices...
But worked, i was able to use the devtools..
After one or two variables inspection (in the source) encountered a crash...
Plus, wasn't able to load my global npm dependency but only local (i have seen a new issue on that)

Thanks, what version are you using?
devtool -v

I'm on a Virtual Box, with Ubuntu 64bits LTS
devtool -v > 1.3.0
Attached, this afternoon,

and tonight (Here it's 00:00pm ;)

About the WebGL here the start of the long errors traces
ubuntu1@ubuntu1-VirtualBox:~$ devtool -v
1.3.0
ubuntu1@ubuntu1-VirtualBox:~$ api
ubuntu1@ubuntu1-VirtualBox:~/www/bytel_api$ devtool app.js -s
pci id for fd 15: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
...


Can the debugger extension be loaded quicker?

I temporarily added a Console.Beep() call to the package initialization method and it looks like the debugger extension is loaded at somewhat random times after Visual Studio is started, sometimes several seconds after VS has finished loading the solution and sometimes we're loaded when the initial VS screen asking what you want to do is presented.
Is it possible to have VS load us earlier?

This is from 2013 but may be of some help:
https://www.mztools.com/articles/2013/MZ2013027.aspx

There doesn't seem to be a way to prioritize loading our extension.  MSFT has been trying hard to prevent this sort of thing to improve VS performance.


Improve design of "Connect automatically"

Fixes: https://github.com/oVirt/ovirt-web-ui/issues/207
Depends on: https://github.com/oVirt/ovirt-ui-components/pull/43


Log entry search API

In parallel with developing core.utils component that holds APIs for interacting with devices, services, sensors and readings an addition to core.log component should be developed that will provide a simple API for accessing log records.

Since support for logging to the database is dropped this feature is no longer relevant.


Do posts get updated when using get_hashtag_posts?

Hello,
I was wondering if posts meta-data is updated when using the get_hashtags_posts function? I want to update likes and comments count if the post already exists.
Thanks!

get_hashtag_posts does not write or update anything. It is a generator of Post instances of the posts that are currently returned for the given hashtag.
When using the Instaloader CLI, the json files and the txt metadata files are updated with each run. There is a feature suggestion, #224, to provide a way to control this behavior.


How to set ATOTI_HIDE_EULA_MESSAGE

Description
Hello, I did not find a better way to set this ATOTI_HIDE_EULA_MESSAGE variable, is there one?

Since it looks like you're on Windows, you could use the dedicated Control Panel UI for that.

Oh thanks! In fact this is a good way. I did not understand that the variable was related to the OS environment instead of the conda environment.

Looking at the message, this is still ambiguous on my opinion: You can hide this message by setting the ATOTI_HIDE_EULA_MESSAGE environment variable to True.
Because there are conda enrivonment variables:
https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#:~:text=Setting environment variables,-If you want&text=To list any variables you,%3A conda activate test-env .

The link to the Conda docs you shared is to interact with environment variables that are only visible inside the current Conda environment. They are still environment variables. If you use them correctly, it would have worked as expected:
~
❯ echo $FOO

~
❯ conda activate my-env

~ via 🅒 my-env
❯ echo $FOO

~ via 🅒 my-env
❯ conda env config vars set FOO=bar
To make your changes take effect please reactivate your environment

~ via 🅒 my-env
❯ echo $FOO

~ via 🅒 my-env
❯ conda activate my-env

~ via 🅒 my-env
❯ echo $FOO
bar

~ via 🅒 my-env
❯ python
>>> import os
>>> os.environ["FOO"]
'bar'

~ via 🅒 my-env took 11s
❯ conda deactivate

~
❯ echo $FOO

~
❯

Do you still think the message is ambiguous?

No, not anymore, thank you for the clarification!


Monkey command does not run

I setup Security monkey on AWS ... I went through the full quickstart quide. But when I try to run the command "monkey db upgrade" there is no command called monkey.
Has anyone seen this problem before ...

Are you in the venv?

No I am not in venv ....

So I have to run it always in virtualenv ...

@mikegrima  thanks for your feedback

I will try venv ...

All security monkey commands must be run within the venv.

@mikegrima thanks that worked ...

I have the same issue even issue "monkey db upgrade" in venv environment. any help is appreciated.

@Leectan Did you perform your pip installs from within the venv?

mike, thanks for the unexpected quick response.
yes I did, I've tried to run ALL the pip install commands all over again and now I have this error message.

That says that it can't find the config file at /usr/local/src/security_monkey/env-config/config-deploy.py.

Thanks, I went and config the setting in the config-deploy.py file to point to the AWS DNS name per Quickstart guide and I got this error?

You're in the wrong directory.
I would suggest reviewing: https://github.com/Netflix/security_monkey/blob/develop/docs/installation/03-install-sm.md

Thanks mike, I re-configure the whole process and seems like everything is working well until this part. I've made sure along the way that nginx is working through https and port 443 is open for it in SG. This part seemed to be the part holding me up.

Any idea what I'm missing here??? google doesn't seem to know this issue here.

Check that you can curl the localhost on 443 on the instance. If you can, then verify that the security group configuration is correct to ingress your source IP.

mike, thanks

failed to curl localhost and the dns for the SM instance, I also realized that as soon as I log in, it is under private IP now instead of the public IP? any advise?

this is my /etc/hosts file


List out the appropriate dependencies for users

Is your feature request related to a problem? Please describe.
Currently, there seems to be no documentation on the dependencies required to run the Community Notes program, making it more difficult for normal users to match Twitter's internal environment and causes build errors along the way.
For example, the constants.py and process_data.py files now uses some numpy objects that are now considered deprecated and throws out errors due to that. Additionally, process_data.py assumes that Python will open TSV files using UTF-8, which is true for *nix environments, but not Windows.
Describe the solution you'd like
Document the necessary dependencies (along with the versions) to run Community Notes.
Describe alternatives you've considered
I've not considered any alternatives.
Additional context
No additional context available.

Yes the code is expected to work on *nix environments. We'd welcome a documentation PR that explains steps to run it on other platforms.

This answer does not fully address the issue raised here.
It would still be helpful to know what versions of Python and the main dependencies are used. Not only to run the code without getting warnings but also for proposing potential improvements to the code.


Separate out in DI the singleton Client from the explicit Clients

The RestService client is a single and wouldn't likely to be used at the same time as the explicit clients, so let people use only what they need.
Also the singleton client can remain backwards capatible but seems like the HttpClient (Pool) is going to need to be managed via injection.

Release 0.3.1


Fix permissions script does not recursively chown directory

This could lead to permission errors on the server directory.
FIX: Make chown call recursive

Fixed


Check the state

Hello,
The SpotifyOAuth class accepts an optional state parameter to be added to the authorization URL. However, this parameter wasn't checked when echoed back upon the redirection from Spotify, which pretty much made its usage useless. This PR simply adds the necessary check when state is used. I also refactored the extraction of the authentication code from the URL so that it's the same between interactive way and local server way.

Verify that the state received alongside the authorization code is consistent with the one that was sent
Refactor URL parsing for the local server way and the interactive way
Add tests for interactive way
Allow state to be given to util.prompt_for_user_token

Hey, sorry about removing the public methods, that completely went over my head. I resurrected them!

No worries @foobuzz, thanks a lot for the fixes, merging!


IE9 Support

Hello, I've been looking for a library to do cross tab communication, I've looked at: Intercom, DuelJS, crosstab, page-bus and IWC.
I really like IWC but no IE9 support is a deal breaker for me, could you please talk about what's missing on IE9 or what needs to be implemented in order to support it?

Hello. Thanks for your comment. It's nice to know that you like it.
IE9 doesn't provide key and value of changed localStorage item in onstorage event. I didn't manage to encapsulate a fix in SJ.localStorage. So, all subscribers shouldn't rely on key/value in event handlers. This requires to revise all IWC functionality. IE is an evil.
I also have requirement in my project to support IE9. So, if you can wait, I'll try to implement IE9 support in one week.

That would be great, thank you very much.

I've added IE9 support. In case of any problems, please, notify me.


🐛(courserun) fix empty date on opened course run

opened course run show '...' when date is empty
Purpose
Help fix issue #2063
Proposal
Verify if value is empty before displaying it

New test added to check for forever open course. Needed Nathan's commit to have open_ongoing courserun when end date and enrollment_end date are empty.

I just merged the other fix PR, feel free to request another review once it is ready :) !

Ready for review 😄

All good, @2018D it just needs a rebase in order to be merged. I tried to do it by myself but I don't have the permission to do it on your branch so you will have to do it 😅

Rebase completed


NTR: Laboratory

OBIB team is requesting the term, 'laboratory'
Label: laboratory
Textual definition: An organization that performs research, provides services, or processes materials.
Definition source: eagle-i resource ontology
Parent: organization
Related trackers:
https://github.com/biobanking/biobanking/issues/83
https://github.com/obi-ontology/obi/issues/408

Discussed 2021-10-18. Not necessarily research organization. Need to elaborate on "services". Suggested definitions: An organization that develops or uses technologies to advance human understanding, An organization that performs assays, processes specimens, analyses data and similar services. May need related facility term. May want 'biomedical laboratory' as label. Will discuss with OBIB to improve definition. Children of this term in OBIB are helpful in improving definition: http://www.ontobee.org/ontology/OBIB?iri=http://vivoweb.org/ontology/core%23Laboratory

Laboratories included in OBIB are ones which acquire, evaluate, and characterize tissues including analyzing components such as DNA/RNA. Of the proposed definitions from the 2021-10-18 OBI call, this one fits best: "An organization that performs assays, processes specimens, analyses data and similar services." Biomedical laboratory would be an appropriate label.
Alternatively, could have a more specific "tissue laboratory" which is "An organization which acquires, evaluates, and/or characterizes tissues including analyzing components such as DNA/RNA."

OBI proposes:
Label: Biomedical laboratory
Textual definition: An organization that performs biomedical assays, processes biospecimens, analyses biomedical data and conducts similar planned processes.
Definition source: OBIB
Parent: organization
Discussed possibility of adding class axioms but will defer that at this time.

may I suggested having the restriction to biomedical being reflected in the label?

Here's a counter proposal from OBIB:
An organization that performs assays, processes specimens, analyses data and conducts planned processes relevant to the life sciences.

Should this be a subclass of ENVO's laboratory facility?

Or to avoid confusion between a facility (human construction) and an organization perhaps use label "biomedical laboratory organization".

2023-02-06 OK with updated label & definition (Chris & Bill). Jie will update PR.

OBI dev call Feb. 13, 2023. No objections. All approve. OK to update PR accordingly.


Improve foreign key support

This PR improves Swift-Kuery's support for foreign keys.
With the changes it is now possible to specify multiple foreign keys on a table.
It should be noted that a user will still need to ensure their tables are built correctly to allow the use of composite keys.

Codecov Report

Merging #133 into master will decrease coverage by 0.1%.
The diff coverage is 85.52%.

@@            Coverage Diff             @@
##           master     #133      +/-   ##
==========================================
- Coverage   84.49%   84.39%   -0.11%
==========================================
  Files          43       44       +1
  Lines        3606     3640      +34
==========================================
+ Hits         3047     3072      +25
- Misses        559      568       +9

Flag
Coverage Δ

#SwiftKuery
84.39% <85.52%> (-0.11%)
:arrow_down:

Impacted Files
Coverage Δ

Sources/SwiftKuery/Table.swift
82.17% <100%> (+0.19%)
:arrow_up:

Sources/SwiftKuery/ForeignKey.swift
75% <75%> (ø)

Continue to review full report at Codecov.

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


Added support for PUSH/POP instructions

This pull request fixes #182 (ping @krytarowski) and includes several changes:
Changes
Added a register cache to the instruction emulator (c799252)
This implements a cache for reading/writing GPRs in the instruction emulator: Register reads will be stored in ctxt->gpr_cache, and writes will be stored in ctxt->gpr_cache until they are explicitly flushed by gpr_cache_flush so that the actual register access, as defined in em_vcpu_ops_t, is performed.
Aside from minor performance gains, this change will make easier to introduce instructions with "side effects", e.g. push/pop modifying the stack pointer. The reason is that due to our model of PENDING/FINISHED flags to handle memory accesses, the logic of em_emulate_insn is executed few times, but we don't want to apply these "side effects" few times, e.g. decrementing/incrementing the stack pointer at every execution.
By placing a gpr_cache_flush, we "commit" the changes on the "done" label, and ensure that side effects occur only once. Note that for REP/REPE/REPNE instructions we also need to flush the GPR cache on each iteration, as such instructions are meant to execute the emulation logic multiple times, e.g. to repeatedly decrement the ~accumulator~ counter.
Verbose error descriptions in emulator tests (25478d7)
Previously, we added EXPECT_EQ(memcmp(&vcpu, &vcpu_expected, sizeof(test_cpu_t)), 0); as a simple check at the end of EmulatorTest::run. While this was enough to catch implementation issues in the emulator, it did specify where the exactly was the mismatch happening. Consequently, we often turn to the debugger and manually diff both test_cpu_t structures which is time consuming.
This patch adds a dedicated EmulatorTest::verify function that checks each register individually and reports any issues to the stderr, before comparing and asserting the equality of both structures. Note that the previous EXPECT_EQ has been replaced with ASSERT_EQ, as there is no point in keep trying other instruction variants if there's one broken already.
Allow emulator tests in 16-bit and 32-bit protected mode (7860a02)
Now we can customize in the em_context_t::mode in each test, and provide the run_prot16, run_prot32, run_prot64 methods to assemble, decode and emulate instructions. The previous run method now defaults to run_prot64.
Added support for PUSH/POP instructions (6d962ac)

Implemented push/pop instructions in the emulator.
Added INSN_STACK instruction flag to signal push/pop instructions, since the operand size behaves differently than in other instructions.
Returning em_status_t from software-emulated instructions to allow calling operand_read/operand_write within them.
Adding ctxt->b to the emulation context members, since certain variants of push/pop require reading the opcode byte to get the register index.
Added tests for push/pop instructions.

Also, I've just found a small bug. It didn't affect any previous instruction, but it did affect pop instructions in the current implementation. It has been fixed here:
Fixed missing flags in grouped instructions (9d7a927)
After finding the opcode structure corresponding to the current instruction, we cache opcode->flags into the flags variable and perform several checks for particular flags such as INSN_BYTEOP and INSN_STACK.
The issue here is that for instructions that belong in a group, see INSN_GROUP, we need to merge the group flags and the flags of the actual opcode before performing such queries. Consequently we need to reposition all (flags & INSN_*) statements after we have dealt with groups.
The only exception here is (flags & INSN_MODRM) since we need to fetch the ModRM byte in order to figure out which instruction we are dealing with within that group.

This pushes booting OpenBSD/i386 6.4 further but another instruction is missing in the emulator and I will send a dedicated report for it.

By the way, I forgot to mention how the current verbose errors (during VCPU checks) look like:
Register mismatch on: btr [ecx + 0x08], eax
vcpu_obtained.gpr[REG_RAX]: 0xFFFFFFFFFFFFFFF1
vcpu_expected.gpr[REG_RAX]: 0x0000000000000000
Register mismatch on: btr [ecx + 0x08], eax
vcpu_obtained.gpr[REG_RDX]: 0x0000000000000000
vcpu_expected.gpr[REG_RDX]: 0x000000000000FFFF
Expected: memcmp(&vcpu, &vcpu_expected, sizeof(test_cpu_t))
      Which is: 1
To be equal to: 0

where previously it was simply:
Expected: memcmp(&vcpu, &vcpu_expected, sizeof(test_cpu_t))
      Which is: 1
To be equal to: 0

which was not very informative.

All issues fixed @ 6c27fc2.

@raphaelning I've updated my last commit to reflect what you said at: https://github.com/intel/haxm/pull/185#discussion_r259390717.

@PatrickvL Good catch, thank you. It's fixed on 3105e83.

What host platforms are supported?
Hardware and software breakpoints don't work on NetBSD so far.

@krytarowski What do you mean? Maybe you are referring to a different issue/pull request?

@krytarowski What do you mean? Maybe you are referring to a different issue/pull request?

Wrong haxm tab! My older message is deleted.

@raphaelning All fixed!
Since my fixes to decode_op_reg (now called decode_op_opc_reg) involved adding support for AH/CH/DH/BH registers, I've decided to cherry pick the patch from #191 into this branch, and add all requested changes on top of it.

@raphaelning All fixed!

I had to remove the asserts from the emulator. Since emulate.c is shared both in kernel and user tests, managing dependencies there is a nightmare. In any case, we already do the index checks in ctxt->ops->read_gpr and ctxt->ops->write_gpr, and the size+shift issue is realistically not going to happen.

Thanks!

Could you split it? I think the cosmetic changes can stay in this PR, and the rest go into a separate PR (like the way you did at first)

@raphaelning I was reluctant to split the commit, because the last commit contained changes without which PUSH/POP emulation was essentially broken. I've investigated the cause of this issue, and turns out I didn't to invalidate the read-flags from the GPR caches after a MMIO exit.

Hopefully it's now all fine. And right we have now quite many things depending on this PR, better to not create extra work of splitting it up.

@AlexAltea Thanks. The new change (gpr_cache_invalidate()) looks good, although I wonder why it is necessary (more on this later). But first of all, are you sure 8f64789 has fixed the issue? I've pulled the latest PR, but I still get the same black screen when booting Ubuntu ISO with virtio-net... The problem goes away as soon as I revert the last commit (git revert 8f67489).
@krytarowski I asked @AlexAltea to split the last commit because I thought that would allow us to merge the first 6 (good) commits now, as well as make it easier for us to identify the offending change that causes the Ubuntu ISO regression. Of course, if someone can fix this PR without splitting it, I'll be more than happy to merge the fixed PR.

Can one of the admins verify this patch?

sorry,please disregard my previous comment.

@raphaelning Sorry for the late reply. Last month was incredibly busy, and had no time to go thoroughly debug this issue. Turns out this was a subtle bug introduced while modifying the decode_op_modrm_reg and decode_op_modrm_rm operand decoders.
This happened probably because I misunderstood the specification. If you look at the table "Table 3-1.  Register Codes Associated With +rb, +rw, +rd, +ro", in the REX.B column, and AH/BH/CH/DH rows it's said that these are not "Not Encodable". However this actually means that no REX prefix is allowed at all, and not just that REX.B is not allowed (otherwise it would say just "None", I suppose).
One of the guest instructions that were executed in your Ubuntu image shows this issue:
40 88 3E        mov  byte ptr [rsi], dil

Here the REX prefix is 0x40, meaning rex.b=0, rex.x=0, rex.r=0, rex.w=0. With the previous implementation this meant that the instruction was decoded as: mov  byte ptr [rsi], bh instead. Now the entire REX value is tested, not just the relevant bit, as you can see in the diff.

With this diff applied to intel/master, OpenBSD/i386 is failing to boot up on NetBSD for me
The guest system fails in a later stage in kernel bootup (after disk initialization etc.)
The error in the guest console is:
uvm_fault(0xd09bbad8, 0x4d92000, 0, 1) -> e
```,
then many of those messages:
```fatal page fault (6)trap [swapper]0/0 type 4: sp d02e2397 not inside 0-0```
after a second or so, the guest system resets back into bootloader and the same thing happens again, but without the page fault messages visible (it would initialize up to the same point, then reset to bootloader again)

There aren't any messages in dmesg.
I have checked the addresses in the guest kernel log against the kernel executable with gdb, `0xd0e87e04` is not a valid address:
```(gdb) disas 0xd0e87e04,+10
Dump of assembler code from 0xd0e87e04 to 0xd0e87e0e:
   0xd0e87e04:	Cannot access memory at address 0xd0e87e04```
and `0xd09bbad8` is in a range full of `add    %al,(%eax)`, ie. zero bytes:
```$ rasm2 add    '%al,(%eax)'
00```

@polprog Is OpenBSD/i386 working before without this patch on intel/master? Just asking to figure out whether the patch is ready to be merged, or whether you found a regression and further work is necessary.

@polprog Is OpenBSD/i386 working before without this patch on intel/master? Just asking to figure out whether the patch is ready to be merged, or whether you found a regression and further work is necessary.

It didn't work earlier.. however it's not possible to state whether this patch is helping or not. Assuming that there are no setup mistakes by polprog, at least we no longer see undefined instruction fault.

@AlexAltea I propose to check it yourself with OpenBSD/i386. Changing unspecified instruction to vm fault is suspicious.

@AlexAltea With this patch, openbsd/i386 boots farther than ever

@krytarowski According to @polprog this patch causes no known regressions, and it allows OpenBSD/i386 to boot further. If there's any other issue beyond that point I'd suggest to simply create another issue. This patch was simply meant to fix #182, and should be ready to be merged.

OK, so as @polprog claims that it breaks now much later we can stop blocking it.

All: Sorry about my late reply! I was first on vacation and then in an internal workshop. Now that I'm back to clear my backlog of HAXM work, I'm glad to see the great progress made on this PR. Thanks @AlexAltea for finally fixing the regression. I'll try to finish the review ASAP, but it's been a while, so please give me a couple of days.

This happened probably because I misunderstood the specification. If you look in the Intel SDM Vol. 2A at the table "Table 3-1. Register Codes Associated With +rb, +rw, +rd, +ro", in the REX.B column, and AH/BH/CH/DH rows it's said that these are not "Not Encodable". However this actually means that no REX prefix is allowed at all, and not just that REX.B is not allowed (otherwise it would say just "None", I suppose).

Yes, I also find this table very confusing. For me, the register encoding table from https://wiki.osdev.org/X86-64_Instruction_Encoding#Registers is a much better reference. I believe it's applicable to all instruction fields that encode a GPR: modrm.reg, opcode.reg, and modrm.rm (when modrm.mod = 11b).
Also, the following paragraph from Intel SDM Vol. 1, Section <IP_ADDRESS> (General-Purpose Registers in 64-Bit Mode) gives further explanation as to why AH/BH/CH/DH are sometimes not encodable in 64-bit mode:

In 64-bit mode, there are limitations on accessing byte registers. An instruction cannot reference legacy highbytes (for example: AH, BH, CH, DH) and one of the new byte registers at the same time (for example: the low byte of the RAX register). However, instructions may reference legacy low-bytes (for example: AL, BL, CL or DL) and new byte registers at the same time (for example: the low byte of the R8 register, or RBP). The architecture enforces this limitation by changing high-byte references (AH, BH, CH, DH) to low byte references (BPL, SPL, DIL, SIL: the low 8 bits for RBP, RSP, RDI and RSI) for instructions using a REX prefix.

At first glance, I thought the new insn_mov test added by bd7439f violated the above rule, because it references both CH and RDX in 64-bit mode (run_prot64()):
mov ch, [rdx]

But that's actually a valid instruction, because the encoding of RDX does not require the REX prefix at all. In fact, Keystone assembles the instruction into 0x8a 0x2a, where:

opcode = 0x8a  // MOV r8, r/m8
modrm.mod = 00b
modrm.reg = 101b  // r8 = CH (cf. Intel SDM Vol. 2A, Table 2-2)
modrm.rm = 010b  // r/m8 = [EDX] (cf. Intel SDM Vol. 2A, Table 2-2)

Since this is a 64-bit instruction, the default address size is 64 bits, thus [EDX] becomes [RDX]. As soon as I replace [rdx] with [r8] (which requires the use of the REX prefix), the test fails:
LLVM ERROR: Cannot encode high byte register in REX-prefixed instruction

@raphaelning Good to know! Thanks for investigating this in detail! :-)


Getting traceloop qualified on Elastic

Hello we noticed that Elastic was not on your list of supported and tested destinations. We offer native OTel support, and are now heavy contributors to OTel (ECS donation, Profiling agent donation, and more). We don't require a specific SDK or collector. You can instrument directly with standard Otel (python, java etc) and set the endpoint with auth to an elastic stack. Traces, metrics etc all show up natively in our APM capabilities.
https://www.elastic.co/observability-labs/blog/tag/opentelemetry
https://www.elastic.co/observability-labs/blog/getting-started-opentelemetry-instrumentation-sample-app
https://www.elastic.co/observability-labs/blog/auto-instrumentation-python-applications-opentelemetry
https://www.elastic.co/observability-labs/blog/manual-instrumentation-python-apps-opentelemetry
and more.
What can we do to help you get us supported on your list?

Hey @bshetti! Would love to get you on the list! Can you add it to our docs repo? https://github.com/traceloop/docs

@nirga thanks. So if I branch and pull a PR with the MDX, what other steps will this go through?
I will add something to here - https://github.com/traceloop/docs/tree/main/openllmetry/integrations

That's it. You can run it locally to make sure it works (see readme for instructions).


Minor changes to simplify CI

Stop depending on auto-merge, because dependabot also provides a similar function
Remove Ghooks which isn't working as expected (after ghooks runs, husky will not run because .git directory already has hook script files)
Bump up the version of Gradle for testing

@spotbugs/everyone please review this change to merge. Thanks in advance!


Upgrade to lcobucci/jwt 4.x

This PR upgrades lcobucci/jwt to v4 with all the necessary changes.
This was needed for my project where I use lcobucci/jwt v4 and PHP 8.1. I think it's safe to say this fixes #28.
I got all the unit tests to pass and there don't seem to be any breaking changes expect for some return type changes.

@steverhoades Can we expect this MR to be merged? :)

This PR was released as v2.0.0. Thank you very much for the contribution.

@steverhoades @inoric thank you both very much!


Use rtcscore-go to calculate audio/video score

Audio scores are based on modified E-model
Video scores are based on logarithmic regression
Signed-off-by: shishir gowda<EMAIL_ADDRESS>

@shishirng A few more comments. Sorry, this is dragging a bit.


Option to reduce baud rate for burning firmware

Thanks for this great tool! When trying to burn the firmware to an Adafruit Feather board, I was running into continuous problems. It turned out that some USB chips require a slower baud rate, like 115200 baud, see also here: https://github.com/cnlohr/espusb/issues/8
It would thus be good to be able to set the baud rate in the configuration, so that you can use e.g.
$ esptool.py --port /dev/cu.SLAB_USBtoUART --baud **115200** write_flash --flash_size=detect 0 ~/.upiot/firmwares/esp8266/esp8266-20180511-v1.9.4.bin 2>&1
Before report an issue, please make sure it hasn't been reported before.
Operating system
OSX 10.11.6
Board used
Adafruit Feather
Description of problem
Burning firmware fails due to too high baud rate.
Error(s) in ST Console? (View > Show Console)
Running esptool.py --port /dev/cu.SLAB_USBtoUART --baud 460800 write_flash --flash_size=detect 0 ~/.upiot/firmwares/esp8266/esp8266-20180511-v1.9.4.bin 2>&1

esptool.py v2.2
Connecting........_
Detecting chip type... ESP8266
Chip is ESP8266EX
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...

A fatal error occurred: Timed out waiting for packet header

[Finished in 7.0s with exit code 2]

Steps to Reproduce
Actual Results
Expected Results
Additional info
You can edit the text above according to your need

A quick solution would be locate the json file located in uPiotMicroPythonTool/boards an edit the --baud parameter manually. You should edit the file corresponding to your board/firmware

Thanks, I found that in parallel and tried, but it did not really help. Currently, ampy on the command-line works fine, but the same functionality inside Sublime Text does not.
That is a pity, because in theory this plug-in is exactly what I need - a Sublime-based integrated workflow for MicroPython development that works via the USB UART.
Has anybody this running with Adafruit Feather boards (ESP8266)?

This plugin uses a modified version of ampy, but it shouldn't be a problem.
You are having problem to burn the firmware or to run the ampy commands?


E2E: go schedule main SLSA3 config-ldflags-main

Repo: https://github.com/ianlewis/example-package/tree/main
Run: https://github.com/ianlewis/example-package/actions/runs/2460693934
Workflow name: go schedule main SLSA3 config-ldflags-main
Workflow file: https://github.com/ianlewis/example-package/tree/main/.github/workflows/e2e.go.schedule.main.config-ldflags-main.slsa3.yml
Trigger: schedule
Branch: main
Date: Wed Jun  8 10:07:25 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2460804016
Workflow name: go schedule main SLSA3 config-ldflags-main
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.schedule.main.config-ldflags-main.slsa3.yml
Trigger: schedule
Branch: main
Date: Wed Jun  8 10:31:04 UTC 2022


Make session id refresh configurable

SessionManager.swift has a hard coded timeout period set to 30 minutes. This should be configurable.

sessions should also have a maximum duration


[PIP-82]  Fix attach ResourceGroup to Namespace REST api

The REST api to attach a ResourceGroup to namespace takes the name of ResourceGroup in the body of the HTTP request.
Since it is a simple string we should modify the REST api to take the name of the ResourceGroup in the URL itself instead of the payload. This will also fall in line with the other REST apis under the Namespace hierarchy.
(If this PR fixes a github issue, please add Fixes #<xyz>.)
Fixes #
(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)
Master Issue: #
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as (please describe tests).
Existing ResourceGroup feature tests exercise this api quite a bit.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
For contributor
For this PR, do we need to update docs?
No, this feature is still under development
For committer
For this PR, do we need to update docs?

If yes,

if you update docs in this PR, label this PR with the doc label.

if you plan to update docs later, label this PR with the doc-required label.

if you need help on updating docs, create a follow-up issue with the doc-required label.

If no, label this PR with the no-need-doc label and explain why.

@jerrypeng please take a look.

LGTM.

/pulsarbot run-failure-checks


Support cross compilation for Windows

This PR brings the ability to create windows binaries via mstorsjo/llvm-mingw Linux container for the following architectures:

x86_64
i686
aarch64
armv7

It's based on the curl-static-cross.sh script with some changes: https://github.com/stunnel/static-curl/pull/59/commits/bedb403b9b898bb5340f47ca3a184fddb84f1b32

Thank you, great job.
I tested the compilation and it compiles fine, do you have anything else to submit?
I'll update the workflow for release.

do you have anything else to submit? I'll update the workflow for release.

@travislee89  In the last change I added Mozilla CA certificates bundle and enabled winidn by default.
So we could proceed futher.


HW 19.10.2016 Image Loader

https://github.com/Andrei1993ak/NewFAmilyFinances/tree/master/FamilyFinances/app/src/main/java/com/gmail/a93ak/andrei19/familyfinances/imageLoader

Resolve issues

see https://github.com/deniotokiari/training-epam-2016/issues/186


Repository detail add collection

Adds ability to add collection to particular repository at repositories -> detail -> tab collection versions.
Button Add Collections in toolbar or empty state opens a modal that allows selection of collections. After clicking Confirm button, collections are added as one request to server (endpoint modify).
What is hard in this PR is multiple modals - that required changes in the framework, because collections has repository selector filter, that has browse button, that opens another modal. So ToolbarAsyncBuilder (single and multi) has to be enhanced to not uses setDialog function, but pushDialog and popDialog props that can handle multiple modals.

Clicking Manage columns in the modal closes it.


Sometimes Backspace does not work

On some runs, cannot delete characters in a buffer with backspace.
Some runs it works as expected.
WASM seems to work fine consistently (sample size of 10 refreshes, two builds)

It inconsistently broken on my machine: on some app runs I can remove by backspace, on others can't.

Being intermittent makes me think it's a scheduling issue, which would be inconsistent across builds for definite, I think the schedule can change the order of systems across runs too

Yep, most likely.


Cleaned up messy sentence

Removed the Viewer hint, which was a copy and paste error probably.
The step is now in accordance with Example 3, where the guide also does not specify in detail which permission to choose.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.


Update NumberGuessingApp

I found errors in NumberGuessingAPP inside Projects folder.
Can you please assign me to solve the errors and make the program more beginner friendly?
Thank You

I found errors in NumberGuessingAPP inside Projects folder. Can you please assign me to solve the errors and make the program more beginner friendly?
Thank You

sure 👍

merged


Only allow Sandbox Task to shutdown a POD shim

Signed-off-by: Justin Terry (VM<EMAIL_ADDRESS>

@jhowardmsft - FYI before handling this the first task to exit would cause the cleanup logic to run issuing a shim shutdown which in most cases is the correct call. But in a unified shim the shutdown is incorrect. Problem is that the caller doesnt know its a unified shim at all so it cant have this logic.


Fix bugs with top level binding deletion code action and comments

This PR fixes a couple of bugs with code changes introduced in #657 :

Top-level binding deletion code action produces code edit that also deletes the haddock comment (or any comment) for the successive binding (which should not happen)
Top-level binding deletion code action produces code edit that fails to remove the haddock comment associated with the current binding

I tried using GHC API to fix those problems, but I found it is not possible to get the nodes for comments or haddock comments: DocD never appeared in a hsmodDecls (as per documentation https://hackage.haskell.org/package/ghc-8.10.1/docs/GHC-Hs-Decls.html#t:HsDecl)
I added a code that does a reversal on an array of lines un current file - it's linear - this addition should not hit performance hard.
I will be glad to hear how I can improve this

@pepeiborra raises a good point. This is the difference between Opt_Haddock and Opt_KeepRawTokenStream. For the former you get DocD nodes whereas for the latter you get annotations

Small update: was able the start seeing some parsed comment tokens inside my code action handler after I added Opt_KeepRawTokenStream flag (thanks for the link). Current issue is that not all tokens have the location attached to it (SrcSpan) so I see [(<no location info>,\n  [AnnLineComment \"-- | This should be deleted\",\n   AnnBlockComment \"{-# OPTIONS_GHC -Wunused-top-binds #-}\"])].
Still trying exactly when this happens and if there is way to avoid getting that <no location info>

@serhiip the comments are normally attached to the nearest enclosing AST element.  The ones at the top and bottom of the file cannot be associated with anything specific, so they are  captured against the  span.  Which is effectively the top of the file.

And you might be better off using ghc-exactprint for this, which already manages comments, alignment and so on. And is used for various formatters and retrie too.

@alanz indeed, when I changed my test ta have following input
    (T.unlines [ "{-# OPTIONS_GHC -Wunused-top-binds #-}"
               , "module A (some, some2) where"
               , ""
               , "some2 = ()"
               , ""
               , "-- | This should be deleted (new)"
               , "documented :: Int -> Int -> Int"
               , "documented _ b = let a = 1"
               , "                 -- comment"
               , "                 in a + b"
               , ""
               , "some = ()"
               , "-- irrelevant"
               ])

it gives me back
[(/private/var/folders/rv/fvmp1h3x2yn40ptnsbpz2fl40000gn/T/extra-dir-45990137941/A.hs:(8,18)-(10,25),\n  [AnnLineComment \"-- comment\"]),\n (<no location info>,\n  [AnnLineComment \"-- irrelevant\",\n   AnnLineComment \"-- | This should be deleted (new)\",\n   AnnBlockComment \"{-# OPTIONS_GHC -Wunused-top-binds #-}\"])]

Which is not really helpful for what I am trying to do (delete top level binding and it's documentation annotation).
I will look into ghc-exactprint (looks promising)
Thanks for clarification and suggestion

Note that $710 reimplements the deletion code action and presumably fixes all the issues, except that it doesn't try to address comments

closing due to inactivity


📃: Currency Converter

🔴 Title : Currency Converter
🔴 Tech stack : Html,css,js
🔴 Objective : Real-time data fetching, input handling, conversion calculations
🔴 Summary : an interactive gallery that displays images in a grid layout, with options for filters, sorting, and image preview
📸 Screenshots
N/A

✅ Details to Include When Taking the Issue:
Name : Vivek Kumar Garg
Participant Role (Specify the Open Source Program name, e.g., GSSOC, Hacktoberfest, etc.): GSSOC Contributor

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

already have


Integer Error?

Hello, I am not sure what version of python you are using (I am using 3.12) but I got an error when passing the PORT to the Console client
raised an exception: TypeError: 'str' object cannot be interpreted as an integer

It's odd because it's set as an int in the env file.
As a work around, I just cast the str to an int.
self.port: int = int(port)

Maybe I am missing something.
https://github.com/KOOKIIEStudios/PalCON-Discord/blob/1e597b922d40dbd69ab1809f5e5505112753b50e/client.py#L33
Thanks for the awesome work!

That's an interesting error, I'm personally on python 3.12.1 (The latest version)

and don't see anything too breaking in the latest python patch that would cause this problem.
Are you on an older version of the bot?
What operating system are you on?
Thanks for your cooperation!

I'm using 3.12 as well, and the TOML parser in the standard library interpreted the data type properly for me
I genuinely have no clue why it might be throwing errors for you 🤔

Can't help but notice that your repo uses env rather than toml
os.envron uses strings only (see the docs]) so if you're getting this issue with your repo and not this repo specifically, that might be the reason

os.envron uses strings only (see the docs) so if you're getting this issue with your repo and not this repo specifically, that might be the reason.

This was the problem! Thank you both for the quick reply! <3
Again nice work on the bot!


Template localization

I'd like to support different language mutations for my website. Urls would have a domain.com/{lang}/{page} format.
How should I achieve this with Saber.js, if I want to have the pages generated statically?

Something like ./routes/en/index.vue ./routes/jp/index.vue?

Yes, but I meant how should I do this without copying index.vue manually and without having to manage all of them separately.

You can use this instead https://github.com/egoist/saber.js#adding-routes-programmatically


Update on france.tv extractor to fix thumbnail URL

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[ x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[ x] Searched the bugtracker for similar pull requests
[x ] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[ x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x ] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Fix the thumbnail URL. The issue was here for many years, never fixed. It's done ! :-)
Example : https://www.france.tv/france-2/de-gaulle-l-eclat-et-le-secret/de-gaulle-l-eclat-et-le-secret-saison-1/2035247-solitude.html
failed thumbnail url generated : http://pluzz.francetv.fr/staticftv/ref_emissions/2020-11-02/EMI_1104da66f533cc7dc5d0d07a181a18c2e2fe1d81_20201014122553940.jpg
right thumbnail url fixed : https://sivideo.webservices.francetelevisions.fr/staticftv/ref_emissions/2020-11-02/EMI_1104da66f533cc7dc5d0d07a181a18c2e2fe1d81_20201014122553940.jpg

prefix the commit with [francetv] and keep the commit message short and to the point.


[REQUEST] Suppress Tracebacks for libraries

How would you improve Rich?
Rich has an excellent Traceback module that improves the formatting and readability of Tracebacks ✨
However, sometimes you don't just want nice formatting, you actually just want to remove parts of the traceback. This is most common when you are using infrastructure that you know is almost never "relevant" to the traceback itself.
It would be useful if it were possible to suppress Tracebacks for certain libraries/modules/etc, so that a traceback showed more relevant information for users (at the library author's discretion).
Some context in this twitter thread :-) https://twitter.com/willmcgugan/status/1439494982180737025
What problem does it solve for you?
There's a specific use-case here that might be quite common: using rich in combination with click. If you're using click to build your CLI, then tracebacks will dump several levels of click modules in addition to the error that is in your codebase. It would be most-useful to me if I could just say "Don't show any of the click stuff" :-)
Did I help
If I was able to resolve your problem, consider sponsoring my work on Rich, or buy me a coffee to say thanks.

How about something like this:
import click
from rich import traceback

traceback.install(hide_module=[click])

Then Rich would suppress any stack frame under click.__file__ ?

That sounds pretty reasonable to me. It would solve my immediate challenge, I think.

I'm wondering if the frame should be entirely removed, or if you would want to leave in just the path?

Good point. Hmmm...if you like I am happy to try testing something out in a branch.
I think keeping the paths would help, unless it effectively nullified the benefits of the suppression. I like the idea of having those paths displayed so that there is less "magic" going on (and i guess it follows the old "explicit is better than implicit" adage)

Here's what it looks like with the suppress paths present.

It doesn't look great but all the information is there.
Another possibility would be to replace the suppressed frame with a message like " ... 4 frames suppressed ..."
Or just omit them, which would be the simplest option.

You know, I might tweet this to brainstorm.

Have a look at the suppress-frames branch if you want to test. Add suppress=[click] to traceback.install()

I tried to install it locally but got a weird No module named 'setuptools' error when trying to install

Before
╭─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/bin/jupyter-book:33 in     │
│ <module>                                                                                │
│                                                                                │
│   30                                                                                │
│   31 if __name__ == '__main__':                                                                  │
│   32 │   sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])                       │
│ ❱ 33 │   sys.exit(load_entry_point('jupyter-book', 'console_scripts', 'jupyter-book')())         │
│   34                                                                                │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/lib/python3.7/site-package │
│ s/click/core.py:829 in __call__                                                                  │
│                                                                                │
│    826 │                                                                                │
│    827 │   def __call__(self, *args, **kwargs):                                                  │
│    828 │   │   """Alias for :meth:`main`."""                                                     │
│ ❱  829 │   │   return self.main(*args, **kwargs)                                                 │
│    830                                                                                │
│    831                                                                                │
│    832 class Command(BaseCommand):                                                               │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/lib/python3.7/site-package │
│ s/click/core.py:782 in main                                                                      │
│                                                                                │
│    779 │   │   try:                                                                              │
│    780 │   │   │   try:                                                                          │
│    781 │   │   │   │   with self.make_context(prog_name, args, **extra) as ctx:                  │
│ ❱  782 │   │   │   │   │   rv = self.invoke(ctx)                                                 │
│    783 │   │   │   │   │   if not standalone_mode:                                               │
│    784 │   │   │   │   │   │   return rv                                                         │
│    785 │   │   │   │   │   # it's not safe to `ctx.exit(rv)` here!                               │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/lib/python3.7/site-package │
│ s/click/core.py:1259 in invoke                                                                   │
│                                                                                │
│   1256 │   │   │   │   Command.invoke(self, ctx)                                                 │
│   1257 │   │   │   │   sub_ctx = cmd.make_context(cmd_name, args, parent=ctx)                    │
│   1258 │   │   │   │   with sub_ctx:                                                             │
│ ❱ 1259 │   │   │   │   │   return _process_result(sub_ctx.command.invoke(sub_ctx))               │
│   1260 │   │                                                                                │
│   1261 │   │   # In chain mode we create the contexts step by step, but after the                │
│   1262 │   │   # base command has been invoked.  Because at that point we do not                 │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/lib/python3.7/site-package │
│ s/click/core.py:1066 in invoke                                                                   │
│                                                                                │
│   1063 │   │   """                                                                               │
│   1064 │   │   _maybe_show_deprecated_notice(self)                                               │
│   1065 │   │   if self.callback is not None:                                                     │
│ ❱ 1066 │   │   │   return ctx.invoke(self.callback, **ctx.params)                                │
│   1067                                                                                │
│   1068                                                                                │
│   1069 class MultiCommand(Command):                                                              │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/lib/python3.7/site-package │
│ s/click/core.py:610 in invoke                                                                    │
│                                                                                │
│    607 │   │   args = args[2:]                                                                   │
│    608 │   │   with augment_usage_errors(self):                                                  │
│    609 │   │   │   with ctx:                                                                     │
│ ❱  610 │   │   │   │   return callback(*args, **kwargs)                                          │
│    611 │                                                                                │
│    612 │   def forward(*args, **kwargs):  # noqa: B902                                           │
│    613 │   │   """Similar to :meth:`invoke` but fills in default keyword                         │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/jupyter_book/cli/main.py:177 in build       │
│                                                                                │
│   174 │   use_external_toc = True                                                                │
│   175 │   found_config = find_config_path(PATH_SRC_FOLDER)                                       │
│   176 │   BUILD_PATH = path_output if path_output is not None else found_config[0]               │
│ ❱ 177 │   dfsa                                                                                │
│   178 │   # Set config for --individualpages option (pages, documents)                           │
│   179 │   if individualpages:                                                                    │
│   180 │   │   if builder != "pdflatex":                                                          │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
NameError: name 'dfsa' is not defined
ERROR: InvocationError for command /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/bin/jupyter-book build -W -n --keep-going --builder html docs/ (exited with code 1)

After
─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/bin/jupyter-book:33 in     │
│ <module>                                                                                │
│                                                                                │
│   30                                                                                │
│   31 if __name__ == '__main__':                                                                  │
│   32 │   sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])                       │
│ ❱ 33 │   sys.exit(load_entry_point('jupyter-book', 'console_scripts', 'jupyter-book')())         │
│   34                                                                                │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/lib/python3.7/site-package │
│ s/click/core.py:829 in __call__                                                                  │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/lib/python3.7/site-package │
│ s/click/core.py:782 in main                                                                      │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/lib/python3.7/site-package │
│ s/click/core.py:1259 in invoke                                                                   │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/lib/python3.7/site-package │
│ s/click/core.py:1066 in invoke                                                                   │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/lib/python3.7/site-package │
│ s/click/core.py:610 in invoke                                                                    │
│                                                                                │
│ /home/choldgraf/github/forks/python/ebp/jupyter-book/jupyter_book/cli/main.py:177 in build       │
│                                                                                │
│   174 │   use_external_toc = True                                                                │
│   175 │   found_config = find_config_path(PATH_SRC_FOLDER)                                       │
│   176 │   BUILD_PATH = path_output if path_output is not None else found_config[0]               │
│ ❱ 177 │   dfsa                                                                                │
│   178 │   # Set config for --individualpages option (pages, documents)                           │
│   179 │   if individualpages:                                                                    │
│   180 │   │   if builder != "pdflatex":                                                          │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
NameError: name 'dfsa' is not defined
ERROR: InvocationError for command /home/choldgraf/github/forks/python/ebp/jupyter-book/.tox/docs-update/bin/jupyter-book build -W -n --keep-going --builder html docs/ (exited with code 1)

In my opinion, this is a really big improvement either way.
For deciding one way or another, I suspect that the right default behavior would be to show the file paths. If I were using Rich as a part of teaching, I would probably want to suppress them entirely, but maybe that is too much of an edge case? (or maybe it can be a feature one day if there seems to be demand?)

You will need to do poetry install to install locally.
I'll go with showing the paths for now. Open to adding a switch down the line to completely remove the suppressed frames.

That's in v10.11.0
Thanks for prompting me to do this. Its a very worthwhile addition!

Yahoo! Thanks for the iteration, it was fun 🙂


Questions about dataset "An EEG dataset recorded during affective music listening"

Hi! Your project looks awesome, and I'd like to ask a question about the dataset "An EEG dataset recorded during affective music listening" as I saw in your readme that you used the dataset:). I'm working on a music project using the dataset but failed to identify which specific song they gave to each participant. I saw in the json files like "sub-**_task-runx_events.json" that they have
	"301-360":
	{
		"LongName":	"Music stimuli",
		"Description": "The piece of music that was played. To identify which .mp3 file was played to the participants subtract 300 from this code and append .mp3, for example for code '305' the file '005.mp3' was played to the participant. The corresponding mp3 files can be downloaded from https://www.jyu.fi/hytk/fi/laitokset/mutku/en/research/projects2/past-projects/coe/materials/emotion/soundtracks/Index"
	},

and I downloaded the soundtrack files from the link, but I'm still having trouble determining which soundtrack they used for each subject. Will really appreciate it if you figured this out in your project or if you have any advice on this. Thank you!

Hi, thanks!
We didn't use this information in our project, so unfortunately we don't have any advice for you. Best of luck with your project :)

Hi, thanks!
We didn't use this information in our project, so unfortunately we don't have any advice for you. Best of luck with your project :)

Thanks still! I'll try to reach out to the authors for more information!


Switch networks at runtime

Description
Migrate renterd from separate binaries for Mainnet and Zen to a runtime config option like the other apps. This will reduce confusion of managing binaries with the same name, makes it possible for users using the Linux and Homebrew installation methods to use the testnet, simplifies the CI steps, and the Dockerfile.
Version
No response
What operating system are you running (e.g. Ubuntu 22.04, macOS, Windows 11)?
No response
Anything else?
No response

NOTE: Have to make sure using the wrong flag on an existing node returns an error instead of nuking the database


Baresip build on Debian Wheezy fails | GTK related

Relevant build log section:
modules/gtk/gtk_mod.c: In function ‘notify_incoming_call’:
modules/gtk/gtk_mod.c:271:2: error: unknown type name ‘GNotification’
modules/gtk/gtk_mod.c:278:2: warning: implicit declaration of function ‘g_notification_new’ [-Wimplicit-function-declaration]
modules/gtk/gtk_mod.c:278:2: warning: nested extern declaration of ‘g_notification_new’ [-Wnested-externs]
modules/gtk/gtk_mod.c:278:15: warning: assignment makes pointer from integer without a cast [enabled by default]
modules/gtk/gtk_mod.c:284:2: warning: implicit declaration of function ‘g_notification_set_urgent’ [-Wimplicit-function-declaration]
modules/gtk/gtk_mod.c:284:2: warning: nested extern declaration of ‘g_notification_set_urgent’ [-Wnested-externs]
modules/gtk/gtk_mod.c:288:2: warning: implicit declaration of function ‘g_notification_set_body’ [-Wimplicit-function-declaration]
modules/gtk/gtk_mod.c:288:2: warning: nested extern declaration of ‘g_notification_set_body’ [-Wnested-externs]
modules/gtk/gtk_mod.c:289:2: warning: implicit declaration of function ‘g_notification_add_button_with_target_value’ [-Wimplicit-function-declaration]
modules/gtk/gtk_mod.c:289:2: warning: nested extern declaration of ‘g_notification_add_button_with_target_value’ [-Wnested-externs]
modules/gtk/gtk_mod.c:293:2: warning: implicit declaration of function ‘g_application_send_notification’ [-Wimplicit-function-declaration]
modules/gtk/gtk_mod.c:293:2: warning: nested extern declaration of ‘g_application_send_notification’ [-Wnested-externs]
modules/gtk/gtk_mod.c: In function ‘denotify_incoming_call’:
modules/gtk/gtk_mod.c:305:2: warning: implicit declaration of function ‘g_application_withdraw_notification’ [-Wimplicit-function-declaration]
modules/gtk/gtk_mod.c:305:2: warning: nested extern declaration of ‘g_application_withdraw_notification’ [-Wnested-externs]
modules/gtk/gtk_mod.c: In function ‘message_handler’:
modules/gtk/gtk_mod.c:442:2: error: unknown type name ‘GNotification’
modules/gtk/gtk_mod.c:455:15: warning: assignment makes pointer from integer without a cast [enabled by default]```

Seems to be related to the libglib2.0-0 package, where on Debian 8 the package libglib2.44.X is beeing used.

thanks for the report :)

@clehner could you have a look at this one plz ?

wheezy has glib 2.33.12, and jessie has 2.42.1. GNotification depends on glib 2.40. Before glib 2.40, libnotify was used for notifications. I will add some code to fall back to libnotify if glib is < 2.40.

Thanks to Charles, this issue has now been fixed!
https://github.com/alfredh/baresip/pull/73


set CC environment variable

Building rustc needs the tuple's vendor of toolchains to be empty, however, the vendor is set to unknown when cross-compiling rust codes, making projects like curl-rust unable to select the correct compiler.
So we can set CC to enable most build systems to choose the correct toolchain. (I'm not sure whether the lines should be added here but it did work for me.)

r? @huonw
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks for the PR! I don't think I quite understand the motivation here, however, and there's a number of concerns I have with this PR:

Setting an environment variable in a process is a pretty invasive operation to do, it's much more targeted to set the environment variable for specific children spawned.
It's not clear that a linker is always suitable as a C compiler (e.g. some platforms, like MSVC, use a raw link.exe as the linker instead of a C compiler)
This unfortunately hinders cross compilation because one run of Cargo may compile applications for both the host and the target architecture, and CC in this case is only appropriate for one, not necessarily both.

Could you elaborate a little more on the problem you're trying to solve? It may be the case that there's already conventions for solving it today!

@alexcrichton Oh, you were right, I forgot those stuff about msvc and I agree this is more like an ugly hack but not a normal fix.
I think the proper way to solve the problem is:

Unify the toolchain names. Here in my situation, I need arm-linux-gnueabihf-gcc to compile rustc however the matching configuration is actually called arm-unknown-linux-gnueabihf and it will be passed as the host to the configuration script of curl. Then, of course, the script will look for arm-unknown-linux-gnueabihf-gcc, which doesn't exist, and choose gcc instead. (This is why I specified arm-linux-gnueabihf-gcc in cargo config and tried to pass it to the configuration script. I don't want the redundant symbol links of the same toolchain.)

Furthermore, a flexible method to add aliases of a configuration should be provided. I've seen some similar discussions before, in the cargo issue page or the rustc I can't recall clearly. My toolchain was originally named armv7-rpi2-gnueabihf for Raspberry Pi 2 and I tried to make a modified copy of arm-unknown-linux-gnueabihf.mk but failed to compile rustc finally. Well, this can be solved by renaming the toolchain if you have only one toolchain for each configuration, what if you've got more such as arm-cortexa5-linux-uclibcgnueabihf? Is there any way to do this now? Did I miss anything?

On my system, I have 5 versions of clang and 3 versions of gcc installed, for x86 and x64. And I have multiple arm-none-eabi toolchains. I set $CC and $CXX when invoking cargo to choose which toolchain to use. Not only would cargo clobbering $CC be not backward compatible, but it seems like it would result in a reduction in functionality.
Also, usually when you need $CC set, you need $CXX, $AR, and $LD, at least, set. It doesn't make sense to me to set only $CC.

@briansmith So I think it would be nice to create aliases when compiling rustc and pass the proper host to the configuration script, enabling it figure out the correct toolchain itself.

@Frederick888
It sounds like the problem is boiling down to compiling C code in a build script for a library, and then that C code also happens to need to be cross compiled for an architecture the default gcc doesn't handle. It then also looks like you've configured target.foo.linker for Cargo to pass -Clinker to the Rust compiler, and you basically want that configuration available to the build script by default? (does that sound right?)
If so, I think that makes sense to me. It certainly reduces the number of points of configuration you'd need for cross compilation, which is always a win! I don't think we'd want to name the environment variable CC, however, because of how ubiquitous that is. Instead something like CARGO_TARGET_LINKER or something like that may be a good choice. That way the build script could continue to use CC as usual if it were set explicitly, and when probing for a compiler it could fall back on that option if set (which it may not be).
That way crates like gcc-rs could automatically take this into account and would end up doing the right thing!

@alexcrichton That is exactly what I meant. For gcc-rs, it's a little more complicated but it'll work as you said.
I'm just a little confused about the platform naming rules now in Rust. If we had unified the file names of the configurations, the CROSS_PREFIX in the configurations and the targets in the custom cargo configuration all together to a more common one, something like this PR would never have been needed.
But to say the least, unlike arm-linux-gnueabihf and arm-unknown-linux-gnueabihf, in the situation of the PR above, x86_64-w64-mingw32 may be somehow inappropriate as it contains the name of the compiler and x86_64-pc-windows-gnu we are using currently seems to be more accurate. So we can give developers more choices without losing the accuracy. What kinds of toolchains you've got? How many of them? Doesn't matter! Make the right configurations and compile your own rustc.
I have to say that I'm not familiar with the rustc itself and I'm not clear about how difficult it will be to achieve this. But I'll greatly appreciate it if you could get this done.

Ah yeah the handling of "target triples" has quite the long and storied history! (even around Windows). Right now we're following the conventions of LLVM which seem to be relatively standard at this point, and they're pretty ingrained throughout the community so they probably won't be changing much. I believe triples like w64-mingw32 are "GNU triples" rather than "standard triples", but I also haven't quite seen a standard along these lines...
Regardless, though, this change to Cargo seems to be about informing build scripts about the linker the compiler is using, so perhaps it could be updated to do that in a targeted manner (e.g. only at subprocesses) and also with a different environment variable?

@alexcrichton Yes. Overall, there're two problems now.

A series of new environment variables such as CARGO_TARGET_CC, CARGO_TARGET_LINKER are needed to inform the Rust build script of the correct tools for the subprocesses. (Priority from the highest: env var -> auto decision referring to the target -> default, this would be handled by the build script.)
A way to freely add targets to Rust is needed. Otherwise even we have built the correct external libraries, the program in Rust itself may not be compiled for the correct platform.

Hm, I think some concerns may be getting conflated here. Cargo, for example, knows nothing about a C compiler, it's just got knowledge about a linker which it passes to the compiler. Cargo also has no knowledge of targets whatsoever, so some of this is more related to the compiler rather than Cargo itself.
Along those lines, I don't think there's actually a large set of environment variables Cargo needs to set. The linker should be the only one as it's the only one Cargo may know about. Adding targets to Rust is more of a compiler thing, but custom target specifications get us basically 90% of the way there!

@alexcrichton Yep, actually adding custom targets is more significant than those environment variables. What we need is to get things done with a simple command but not a long series of variables.

Hm ok, I'm a little confused at this point about where you'd like to go with this PR. Would you still like to merge it in some form? In general cross compilation is something I definitely want to be super easy in Rust, and I agree that we have a good deal of work to do on that front, but here's probably not the best location to discuss all the minute details :)

@alexcrichton Well, I think this PR has become unnecessary since you're going to deal with the Rust first, so let's bring the discussion here to an end :+1:


Distroless based image

Currently, there are small runtime images of corretto using Alpine Linux. Is there any appetite for images based on distroless? I've been playing with a Dockerfile for it here
Distroless includes glibc so will work with boringssl (for example when used with gRPC / other Netty frameworks) while being about as small if not smaller than the Alpine-based linux. It doesn't include a package manager either so has a bit less of a security surface.

@anuraaga Thanks for the idea. This is something that's come up in conversations but we don't have a roadmap item for it (yet). Does the image you have work as expected? Any problems you've observed?
If you can share, we'd also like to know what influences your choice to use distroless vs e.g. Alpine Linux for deployments. That also helps us to choose and prioritize upcoming features.

@davecurrie Thanks! Yeah I have used that image in some sample apps and have not run into any issues. Using the :debug variant feels very much like Alpine since it provides busybox for troubleshooting scenarios.
A very similar image, which uses zulu instead of corretto but otherwise set up in almost the same way, has also worked great in production across Zipkin and its various storage backends (cassandra, kafka, elasticsearch). I think in general, this approach doesn't have gotchas (at the risk of speaking too soon :P)
https://github.com/openzipkin/docker-jre-full/blob/master/Dockerfile#L7
As for distroless vs Alpine Linux, most of my apps use gRPC or some other Netty-based framework. I have found Netty's TCNative-BoringSSL to perform at least as well as Java 11+ TLS, the bigger difference tends to be on apps with larger payloads. So it's a goto library for me and that requires a base image that includes glibc, meaning it doesn't work with Alpine. This is the #1 deciding factor for me and unfortunately is a hard yes / no, as opposed to e.g., comparing the image size itself. Other than that, less apps, such as Alpine's apk, means less chance of container security scanners triggering for the image - I think this is nice too but not a dealbreaker since Alpine is already quite small.
Hope this helps, let me know if you need anything more from me.

For what it's worth, we'd also be interested in this. We also need glibc and generally prefer images without any additional software for increased security.


GLib-CRITICAL  Failed to set scheduler settings: Operation not permitted on Ubuntu

Background
When starting my app with mix phx.sever I get this error. The full logs:
$ mix phx.server
12:09:51.772 [info] Running WebInterface.Endpoint with cowboy 2.9.0 at <IP_ADDRESS>:4000 (http)
12:09:51.779 [info] Access WebInterface.Endpoint at http://localhost:4000
[watch] build finished, watching for changes...
Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal
12:09:51.848 [info] Showing http://localhost:4000?k=I3LDV2CNHV6M5DPPQEGLDMRZSONPZHNKVADRVX7IGWAAQFGFN4TA
12:09:52.193 request_id=Fu_cpaC35r2iVAUAAAAC [info] GET /
12:09:52.202 request_id=Fu_cpaC35r2iVAUAAAAC [debug] Processing with Phoenix.LiveView.Plug.Elixir.WebInterface.Live.Window/2
  Parameters: %{"k" => "I3LDV2CNHV6M5DPPQEGLDMRZSONPZHNKVADRVX7IGWAAQFGFN4TA"}
  Pipelines: [:browser]
12:09:52.242 request_id=Fu_cpaC35r2iVAUAAAAC [info] Sent 200 in 49ms
12:09:52.292 [info] CONNECTED TO Phoenix.LiveView.Socket in 38µs
  Transport: :websocket
  Serializer: Phoenix.Socket.V2.JSONSerializer
  Parameters: %{"_csrf_token" => "c3cgHBY0F0NWIywNAQA6IyIdDSl4ez5-9-izSCe10j_hulbMEKDMLBk4", "_mounts" => "0", "_track_static" => %{"0" => "http://localhost:4000/assets/app.css", "1" => "http://localhost:4000/assets/app.js"}, "vsn" => "2.0.0"}

(process:28942): GLib-CRITICAL **: 12:09:53.252: Failed to set scheduler settings: Operation not permitted

My Ubuntu version:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.4 LTS
Release:        20.04
Codename:       focal

To be fair, the application still launches and still works. But since this is Gnome related, I believe the reason I see the error is because there is a lib that needs to be updated withing this project.
This is a bug that seems to have been fixed recently:

https://answers.launchpad.net/ubuntu/+source/glib2.0/+question/689162

The new version:

https://launchpad.net/ubuntu/+source/glib2.0

Which supports my analysis.
Please let me know if this is not the correct place to post this report.

This is happening based on wxWidgets imports and is nothing I can affect in the elixir-desktop project, unfortunately. Based on your findings probably a wxWdigets rebuild with a newer glib would solve this?


Add Win7 Jumplist support

Windows 7 supports Jumplists of recent documents and other commands.
We should track recent documents and display them in the jump list.

Implemented


Using bazel Clion plugin misses external libraries directories

Description of the bug:
Use bazel plugin in Clion (Remote Development)
wrong perform:

Use CMakeLists.txt in Clion (Remote Development)
correct execution:

Which category does this issue belong to?
CLion
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

prepare a small bazel c++ project
sync project with bazel CLion plugin
check external libraries directories (no files)

click "Select Opened File" button (cannot navigate the file to clion editor)

Which Intellij IDE are you using? Please provide the specific version.
CLion 2024.3 RC (Remote Development)
What programming languages and tools are you using? Please provide specific versions.
C++
What Bazel plugin version are you using?
2<IP_ADDRESS>.3-api-version-243
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response

@jiaquanyan unfortunately, Bazel for CLion does not setup information about external includes like CMake integration does.


Cannot debug using a custom Python interpreter

Likely to be fixed by PR in #8856 - in that issue's comments it was speculated this issue is caused by a timeout while validating the Python interpreter.
Environment data

VS Code version: 1.53.0
Extension version (available under the Extensions sidebar): v2021.2.531887795-dev (as suggested in #8856)
OS and version: openSUSE Tumbleweed 20210205
Python version (& distribution if applicable, e.g. Anaconda): 2.7.18, custom distribution
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Value of the python.languageServer setting: jedi (but also tried MS and pylance with the same results)

Expected behaviour
Python debug processes work fine
Actual behaviour
I use a custom Python interpreter that takes 2-3 seconds to come up due to its extensive bootstrapping. When trying to start a debug configuration, I always get the error message "The Python path in your debug configuration is invalid.". The log shows Invalid Python Path '/home/XXX/YYY/ZZZ/bin/CUSTOM'.
Up until recently, I was using vscode-python 2019.9.1, which seems to be the latest version that works with my custom interpreter. Now, VSCode January 2021 seems to break compatibility with the older vscode-python:
Debugger Error: The number of constructor arguments in the derived class s must be >= than the number of constructor arguments of its base class.

If I use the custom interpreter to start a debugpy process in another terminal and connect to it with a debug configuration, everything works just fine.
Steps to reproduce:
I can't distribute the custom interpreter. But it should be rerproducible with vanilla Python if you can introduce a small lag in the bootstrap process.

"The Python path in your debug configuration is invalid." this is a check that we have been planning on relaxing the restrictions. We need to see if the error surfaces correctly if the user uses an invalid python path in the debug configuration. If it surfaces correctly, then we can remove this check.

I am facing a similar problem. The debugger doesn't start with a custom python interpreter.
While using extension version v2021.1.502429796 with VS-Code 1.53.0, I get the following warning when starting the debugger with custom python interpretor:
Extension Host

    Debugger Attached

    WARN UNRESPONSIVE extension host, 'ms-python.python' took 99% of 227.741ms.
    Array(2)
        0:
            id: "ms-python.python"
            percentage: 99
            total: 226511
            __proto__: Object
        1:
            id: "self"
            percentage: 0
            total: 1125
            __proto__: Object
            length: 2

@NumanIjaz Do you get any error messages other than this log entry?
Note that, in order for debugger to work, the custom Python interpreter must behave as a regular Python interpreter would. In particular, it has to accept the same command-line arguments, and must not interfere with stdin/stdout/stderr of the process. If you have some custom logic there that e.g. prints stuff out on launch, that would break it.

In my case, the standard Python output is given, but only after a first vendor-specific line. Also, not all parameters are exposed in the custom interpreter.
I don't want to sound rude, but I don't see the value in validating the runtime (e.g. collecting metadata). And if you have to do it, it should be robust and not break your IDE's primary feature.
I could live very well with VSCode reporting "Python 0.0.0" or "unknown custom Python" to me, as long as I don't lose any features I already had.

It's not just about validating the runtime. Even if you can get past that check, the debugger itself will fail, because DAP uses stdin/stdout as the underlying transport for its JSON protocol. If your custom interpreter is writing random stuff to stdout, it'll break that (and any other Python app that's assuming that it has full control over the standard pipes).
On the other hand, writing random stuff to stderr should be fine - and if validation logic complains about that, we should fix it.

Sorry, I was not very specific. Yes, the startup output prints to stderr. I am not aware of any other output by the interpreter.

@karthiknadig, sounds like the validation code triggers the default Node behavior of throwing if spawned process writes anything to stderr? Or is there some tool plumbing that relies on stderr being sacrosanct as well, and so the validation checks for that?

We exit if anything gets written into stderr when getting python info:
https://github.com/Microsoft/vscode-python/blob/db8e1e2460e9754ec0672d958789382b6d15c5aa/src/client/pythonEnvironments/info/interpreter.ts#L68
    const result = await shellExec(quoted, 15000);
    if (result.stderr) {
        if (logger) {
            logger.error(`Failed to parse interpreter information for ${argv} stderr: ${result.stderr}`);
        }
        return undefined;
    }

This results in validation failure here https://github.com/Microsoft/vscode-python/blob/48d66bd5b2943f155a9d63a1b951628c15831c1d/src/client/application/diagnostics/checks/invalidPythonPathInDebugger.ts#L88
Which eventually result in the message that you see.


message_multi_string property for DynamicMessageSign of SwzDeviceFeed (pr #208) empty string value is misleading

Issue name: “message_multi_string property for DynamicMessageSign of SwzDeviceFeed (pr #208) empty string value is misleading”
Summary
In PR #208 the SwzDeviceFeed contains a DynamicMessageSign with a message_multi_string property, and states that the value can be an empty string if the NTCIP MULTIString value is an error. A non-error blank message can also be represented by an empty string value. See related: IS #218
Motivation
An empty string value for the message_multi_string property is misleading.
Proposed changes
Either:

Change the type of message_multi_string property to allow either a String or a new integer-based enumeration and add a new integer-based enumeration value type such as ValueError where, for example, 0 = NTCIPError (this resolution would also allow for handling other NTCIP errors or other externally-sourced data errors in other portions of the WZDx specification, if applicable)
Retain empty string values for either condition and add an additional key, such as message_multi_string_descriptor to the DynamicMessageSign object that allows for a description of the message_multi_string property value, perhaps where the value of this additional key is fixed to a new enumeration such as MULTIStringDescriptor with one possible value being, for example, "ntcip-error" (this resolution would also allow for additional descriptors as may be useful, such as "includes-binary" when a MULTIString cannot be represented by a JSON String, see related: IS#218)

This issue seems to be directed towards the equipment manufacturer and vendors as to the direct operation of the DynamicMessageSign.  I am wondering if we can get some feedback from @sergebeaudry @petekrikelis and other manufactures as to how much of an issue this is and does it happen frequently for us to have to make the changes?  Thanks!

I work at Ver-Mac with @sergebeaudry and already debated at length with @dxpack in #218. He is right by saying that the NTCIP definition of the multi string node could include binary data, but in my experience this is extremely rare. That's why I was proposing to keep the value as string because seeing the measage's content in the feeds as a readable format is preferable to seeing a byte array. This issue was created to accomodate @dxpack in the situation that he have binary data he can't display as text and still want to convey that something is displayed on the sign. In the case of our products, this isn't something possible.
Same for errors, if the multistring doesn't pass the validation state, it can't be transferred to what NTCIP call the "current buffer", so it's impossible to have an invalid/errored multistring on display. And if there's material error causing the display to get corrupted after the message was set (pixel failures or any equipment failure preventing the message to be shown), our product blank the display automatically so in our case reporting an empty string would be correct without the need for any other information. The cause of the errors themselves can be filled in the exisiting fields (status_messages) in the core_details object.
That said, even if for us this is not required, I think @dxpack suggestions is perfectly valid. I would not want to prevent anything. I have absolutely no objection at adding a description field or enumeration to accomodate other manufacturers at relaying more information.

I work at Wanco, we do have scenarios where the MULTIString value contains binary data. It is rare, and particularly so for a work zone scenario. But it is possible. In addition, I generally favor allowing for error conditions. For example, as @Dunge notes it is invalid for an NTCIP compatible message board to include an invalid message in the current buffer. If such a board did include an invalid message in the current buffer, it would therefore be in an error state. As much as I wish otherwise, hardware devices sometimes get into error states.
At present, the WZDx spec would represent all of the above with a blank message or an incomplete NTCIP MULTIString value (of the ASCII portions if present), which is misleading to the consumers of the WZDx feed.

Upon further consideration, the error handling is not necessary or consistent with the rest of the WZDx spec in regards to device data. Wanco currently excludes devices that would otherwise show up in our WZDx 4.0 feed, if the device is in an unhandled error state.


refactoring BioCharacteristics

Following discussions during a meeting at UCSC, this PR changes the BioCharacteristics object structure by removing one object level and changing assignment to phenotypes, diseases ... to a label.

@david4096 @kozbo Please check - this addresses the structural simplification for the ontology wrappers.

@kozbo I know; but this is still in a branch & has never seen master => ?!

@mcourtot Thanks for the comment; I did change the attribute name before, now to scope.

Consolidating this into metadata-integration as the staging branch.


Feature without a use case

I don't get it. This seems to enable you to join a device to a domain and to azure! We have this already, it's called joining a domain + having auto hybrid join configured on said domain.
If this was hybrid join from anywhere on the Internet, we would have a useful feature.
Am I missing something?

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

ID: 12823601-7426-a768-e72f-866b150baccd
Version Independent ID: c1f993e3-a405-6860-8ab1-7b3d387b4631
Content: Hybrid AAD Join
Content Source: windows/deployment/windows-autopilot/user-driven-hybrid.md
Product: w10
GitHub Login: @greg-lindsay
Microsoft Alias: greg-lindsay

@officedocsbot assign @mypil

@fergusstrachan - Thank you for submitting feedback.
From our understanding, the issue you raised has been answered by egallagh. If you feel it hasn't been answered, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

The reply was simply a clarification of the purpose of the connector.
What I was getting at in my 2nd para was that if the connector enabled hybrid join without the requirement to have the device on the same LAN as domain controllers (e.g. from a user's home or a guest network) this would be useful.
Is this a consideration for the next version?

@fergusstrachan - Thank you for your response. Let me loop in the doc owner to get their inputs.
@DulceMontemayor - Can you please share your insights on this issue?
Thank you.

@DulceMontemayor - We would like to follow up on this. Can you please share your insights on this issue?
Thank you.
cc: @Dansimp

@DulceMontemayor @greg-lindsay - We would like to follow up on this. Can you please share your insights on this issue?
Thank you.
cc: @Dansimp @AndreaBarr

Please see the notice at the bottom of the page when making comments. There is a choice: send feedback about 1) this product or 2) this page. Others have provided answers about the product even though the discussion should be about the content of the page. I'm sorry but we can't engage in a long discussion about the product on each page. If you have further questions, I suggest using the product feedback button. Thanks!


Upgrade to fluent-bit 2.0.10

Description
Fixes b/273520012.
Related issue
b/273520012
How has this been tested?
Will let the presubmits run.
Checklist:

Unit tests

[x] Unit tests do not apply.
[ ] Unit tests have been added/modified and passed for this PR.

Integration tests

[x] Integration tests do not apply.
[ ] Integration tests have been added/modified and passed for this PR.

Documentation

[x] This PR introduces no user visible changes.
[ ] This PR introduces user visible changes and the corresponding documentation change has been made.

Minor version bump

[x] This PR introduces no new features.
[ ] This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
[ ] This PR bumps the version.

Everything passed except SLES; rerunning


Microsoft Certification for Teams

Asked in DND-513
"I wanted to know if there are plans for the company to undergo Microsoft certification of the draw.io Teams add-in?
Here is the link to the Microsoft Certification program.
https://docs.microsoft.com/en-us/microsoft-365-app-certification/docs/enterprise-app-certification-guide

Realisitically, this is a no.