PyOCD cannot connect to ARM SWDAP probe with STM32F767ZI target.

I'm an OpenOCD defector, making my first steps in the world of PyOCD. But I can't get my microcontroller board to work. Please help.
1. Setup
1.1 Probe
I've got the official SWDAP probe from ARM (bought at L-Tek https://www.l-tek.com/web-shop/l-tek-swdap-interface/):

I flashed the latest 0254_lpc11u35_0x0000.bin DAPLink firmware to my probe (see https://github.com/ARMmbed/DAPLink/releases). So the SWDAP probe is up-to-date.

1.2 Microcontroller board
I've got a self-made board with an STM32F767ZI microcontroller. The board is powered from a USB-micro connector (which is for power only, no data). I've got a 10-pin Cortex Debug connector for SWD flashing and debugging:

I connect the SWDAP probe to my board with the ribbon cable that was shipped with my SWDAP probe.

1.3 Desktop
My desktop computer runs 64-bit Windows 10 with the latest Python 3.8. I just installed PyOCD today. I did not use pip install but I cloned the PyOCD GitHub and issued the command:
$ python setup.py install

So I got the latest development version of PyOCD. I also put the libusb dll next to python.exe in my Python 3.8 installation folder, as requested in the installation instructions.

2. Running PyOCD
2.1 Find probe
First I check if PyOCD finds the probe:
$ pyocd list

      #   Probe              Unique ID
    ---------------------------------------------------------------------------
      0   ARM CMSIS-DAP v1   000000800a0c882800000000000000000000000097969902

So that seems allright.

2.2 Download pack for STM32F767ZI
Unfortunately the STM32F767ZI microcontroller is not in the builtin targets. I issued the command pyocd list --targets and couldn't find it. So I download the corresponding pack Keil.STM32F7xx_DFP.2.12.0.pack from http://www.keil.com/dd2/pack/.

2.3 Start GDB server
I issue the following command to make PyOCD connect to my microcontroller and start a GDB server:
pyocd gdbserver --target=stm32f767zi --pack="C:/ ... /packs/Keil.STM32F7xx_DFP.2.12.0.pack"

PyOCD immediately prints out:
    0000874:INFO:board:Target type is stm32f767zi

So I believe it's time to start the GDB client.

2.4 Start GDB client
I open another Windows console, and issue the command:
$ arm-none-eabi-gdb

    (gdb) target remote localhost:3333
    localhost:3333: No connection could be made because the target machine actively refused it.
    (gdb)

I've got no luck here.
After a few seconds, I notice the following output in the first console (the one running PyOCD):
# Note: this is output from the first console - the one running PyOCD
# -------------------------------------------------------------------

0020877:CRITICAL:__main__:Read timed out
Traceback (most recent call last):
  File "C:\Python38\lib\site-packages\pyocd-0.23.1.dev10-py3.8.egg\pyocd\probe\cmsis_dap_probe.py", line 151, in open
    self._link.open()
  File "C:\Python38\lib\site-packages\pyocd-0.23.1.dev10-py3.8.egg\pyocd\probe\pydapaccess\dap_access_cmsis_dap.py", line 580, in open
    self._packet_count = self._protocol.dap_info(self.ID.MAX_PACKET_COUNT)
  File "C:\Python38\lib\site-packages\pyocd-0.23.1.dev10-py3.8.egg\pyocd\probe\pydapaccess\cmsis_dap_core.py", line 135, in dap_info
    resp = self.interface.read()
  File "C:\Python38\lib\site-packages\pyocd-0.23.1.dev10-py3.8.egg\pyocd\probe\pydapaccess\interface\pywinusb_backend.py", line 162, in read
    raise DAPAccessIntf.DeviceError("Read timed out")
pyocd.probe.pydapaccess.dap_access_api.DAPAccessIntf.DeviceError: Read timed out

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "C:\Python38\lib\site-packages\pyocd-0.23.1.dev10-py3.8.egg\pyocd\__main__.py", line 343, in run
    self._COMMANDS[self._args.cmd](self)
  File "C:\Python38\lib\site-packages\pyocd-0.23.1.dev10-py3.8.egg\pyocd\__main__.py", line 571, in do_gdbserver
    with session:
  File "C:\Python38\lib\site-packages\pyocd-0.23.1.dev10-py3.8.egg\pyocd\core\session.py", line 291, in __enter__
    self.open()
  File "C:\Python38\lib\site-packages\pyocd-0.23.1.dev10-py3.8.egg\pyocd\core\session.py", line 367, in open
    self._probe.open()
  File "C:\Python38\lib\site-packages\pyocd-0.23.1.dev10-py3.8.egg\pyocd\probe\cmsis_dap_probe.py", line 163, in open
    six.raise_from(self._convert_exception(exc), exc)
  File "<string>", line 3, in raise_from
pyocd.core.exceptions.ProbeError: Read timed out

3. Conclusion
I tried several times to get the connection working. But I keep getting the same 0020877:CRITICAL:__main__:Read timed out error (with the whole traceback after it). In fact, it doesn't matter if I do or don't start the GDB client. PyOCD throws this error after perhaps 10 or 20 seconds - no matter what I do.
Note:
The problem is not related to my board. I've flashed this board successfully with other probes using OpenOCD. So the hardware is OK.

Hello @kristofmulier :-) I don't have this Target so not sure how to help here, sorry. Can you verify your setup with another Target that is known to work (i.e. K64 or nRF51/52)? :-)

Hi @cederom ,
That's a good idea. So I need a board with such a microcontroller (the K64 or nRF51/52) and a 10-pin Cortex Debug Connector, such that I can connect it to my SWDAP.

10-pin Cortex Debug Connector:

Where can I buy such a board? If you have a Farnell / Mouser / DigiKey number, that would be great :-)

NXP FRDM-K64F board on Mouser
The traceback for the "Read timed out" error indicates that the first USB transaction is failing. I'll try to reproduce when I get a chance.

Thank you @flit

This appears to be the exact same situation you posted at https://electronics.stackexchange.com/questions/465577/daplink-firmware-doesnt-operate-with-openocd - if you are going to post an issue in multiple places, you should link to the previous instance and give the context that you gave there.
Specifically you should have shared here as you did on EESE the fact that this board worked with  OpenOCD with its original firmware, broke when you flashed these binary firmwares you found online, was repaired when you went back to the original firmware, and then broke again because you insisted on using this series of firmware binaries without any actual justification such as a feature they could allegedly provide which the original could not.  That the mystery firmware also does not work with PyOCD is not particularly surprising under the circumstances - the more interesting question would be if you have identified any tool with which it does work.
Especially in light of @flit's analysis that this is a USB timeout, what you are describing appears to be a difference in the USB protocol between what is commonly understood by tool authors to be how the protocol is supposed to work, versus what the firmware actually does - or possibly even a gross error in its implementation in this particular binary build.
To actually address this issue, it would be necessary to debug the USB communication between PyOCD (or OpenOCD) and the probe firmware.
But given that the firmware for the probe is itself open source, efforts should also include examining the commit history of the probe's firmware, and building the probe firmware from source so that the functionality it is supposed to present is actually known, and perhaps debug output from the probe's point of view can be provided as well.
Alternately, you should at the very least run a USB packet capture of the attempt and attach that to your issue.  If there is any tool that does work with this firmware, comparing a packet capture of that would be useful too.

 Go away and stop bullying @kristofmulier. If you don't do this on purpose just be aware that it looks like this. We don't want this here. You also criticized me and my answers pointing to pyOCD as the solution, so what are you doing here? Not cool :-(
Kris mentioned in point 1.1 that he works on a stock firmware (0254_lpc11u35_0x0000.bin). We suggested environment verification by obtaining several boards that are known to work and report back. Let's wait for the results.

@cstratton , I admit that your post here on GitHub is not aggressive (aside from a few subtleties). However, you were flagged on StackOverflow for being rude/unkind in your comments. Those flags have been accepted by the moderators, so you should have gotten a warning.
Therefore, I ask you kindly to ignore me on fora like StackOverflow, GitHub, ... I don't like to be followed by you.
Thank you @cederom for your support.
I've bought the LPC812-LPCXpresso Board (OM13053UL) board:
https://be.farnell.com/nxp/om13053ul/evaluation-lpcxpresso-cortex-m0/dp/2254492
It has an LPC3154 interface chip to convert USB into JTAG. The target is the LPC812-TSSOP20 chip. However, you can break off the interface LPC3154-part from the target part. This way, I can actually test the target with my SWDAP probe :-)

@kristofmulier no worries you will get into point where things start working for you.. you are kind of good writer and explorer so document all those steps for people that will have first contact with our tools in future :-)
Please try first with something that is 100% known to work - for instance NXP FRDM-K64F - as suggested by @flit - you will have a working DAPLink and Target pair on a single board for verification if all is fine with your machine/environment/pc setup.. also you will have one-click-to-compile examples to use, compile, flash, and debug using MBED ONLINE COMPILER. Use those in the first place to see if things work as expected. Then you can modify and alter configurations of the hardware. Otherwise there may be 842932 different reasons for things not to work. Use stable base, that works, then small steps of changes, and verification after each one of them. Skipping too much will cause unpredictable and hard to track problems :-)
Here is a full list of supported boards by ARM MBED OS, pick some of them, preferably those which have lots of ready-to-use examples in MBED ONLINE COMPILER:
https://os.mbed.com/platforms/


'solo key update' complains about multiple solo keys

I have one solo key installed and one Yubikey 5 key installed.
This happens:
$ solo key update

Multiple Solo keys are plugged in! Please:
  * unplug all but one key

When I removed the Yubikey the error went away.

Same here.

I have one solo key installed and one Yubikey 5 key installed.
This happens:
$ solo key update

Multiple Solo keys are plugged in! Please:
  * unplug all but one key

When I removed the Yubikey the error went away.

Me too. Unplugged the Yubikey and update worked.
I got the same output from solo1 ls though in both states:
solo1 ls
:: Solos
########: SoloKeys Solo 4.0.0


how to generate new dataset for TF records

I am trying "dpc" as a generator of point cloud for new category.
To generate ground truth point clouds is obvious(dpc/densify/densify.py or chenhsuanlin/3D-point-cloud-generation's densify/densify.py).
But I cannot find a way of a new train/test/val dataset creation, especially sources of TF records.
How do I prepare a train/test/val dataset to create TF records?

Hi @netalkative
This is described in the instructions: https://github.com/eldar/differentiable-point-clouds/blob/master/README.md#prepare-training-data Please follow them carefully, there is a script that generated TF records out of the images.

Thank you for replying, @eldar
I am afraid that "prepare-training-data" is not enough.
"prepare-training-data" requires camera_?.mat , depth_?.png and render_?.png from -renders.tar.gz that you prepared in advance.
I want to know, how to create camera_?.mat , depth_?.png and render_?.png from my 3D model data.
When you created -renders.tar.gz for airplane, car and chair, how did you?
Best Regards.

Hi @eldar
I'm afraid I have the similar questions.
The numbers in the camera_.mat really confused me.
Could you tell me the meanings of the extrinsic, K, pos, quat in the mat files?
Thank you very much!


feat: upgrade got

BREAKING: upgrading to next major of Got.

Current dependencies on/for this PR:

main

PR #11   👈

This comment was auto-generated by Graphite.


Change conditional to point to username field in client config

https://github.com/StackStorm/st2/pull/3219 changed the logic of when a token is retrieved from the API by looking for the 'credentials' field of the configuration.
However, when this section is missing (or when the config is omitted entirely, like it is in CI), this field is set to an empty dictionary, and then because both username and password default to None and then are added to this dict, the statement if credentials: will never evaluate to False, because this dict will never be empty.
In CI, this causes problems We want to skip this step when the config is missing, because in CI this is expected and other API methods will work just fine because auth is disabled. This change proposes looking at just specifically the username field, because even though st2 login omits the password field by default, it still writes the username field so can be relied upon.

Codecov Report

Merging #3226 into master will decrease coverage by -0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3226      +/-   ##
==========================================
- Coverage   77.86%   77.81%   -0.06%
==========================================
  Files         433      433
  Lines       22421    22421
==========================================
- Hits        17458    17445      -13
- Misses       4963     4976      +13

Impacted Files
Coverage Δ

st2client/st2client/base.py
80.3% <100%> (-2.02%)
:x:

st2api/st2api/controllers/v1/triggers.py
71.43% <ø> (-4.93%)
:x:

st2common/st2common/bootstrap/rulesregistrar.py
74.34% <ø> (-4.42%)
:x:

st2common/st2common/transport/consumers.py
86.32% <ø> (-3.16%)
:x:

st2common/st2common/models/db/init.py
94.15% <ø> (-0.98%)
:x:

st2api/st2api/controllers/resource.py
86.78% <ø> (-0.83%)
:x:

st2common/st2common/rbac/resolvers.py
88.62% <ø> (-0.79%)
:x:

st2api/st2api/controllers/v1/packs.py
91.36% <ø> (-0.62%)
:x:

st2actions/st2actions/container/base.py
90.59% <ø> (-0.59%)
:x:

... and 9 more

Continue to review full report at Codecov.

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

Considering all efforts and discussions around this bug, do you think it's possible to include a test case for this particular scenario?

Thanks, good catch.
And yes, I agree, we should add a test case for that (so it doesn't try to authenticate when: 1. no credentials are set, 2. only password is set but not the username).

In short, if we are "in a rush" with v2.2.0, I would be fine with merging this and then work on additional robustness + test cases mentioned in https://github.com/StackStorm/st2/pull/3226/files#r101514299 in the very near future (and we can release that as v2.2.1).
(I looked into more "quick fixes" + tests myself, but it requires more time to do it correctly and not something which should be rushed so we either ignore that for now or make it a blocker for v2.2.0 and delay the release)

Thanks all for the discussion. In the interest of moving 2.2 forward, I'm going to merge this, but I created https://github.com/StackStorm/st2/issues/3232 to ensure we address additional testing and corner cases in 2.2.1


Joining tables with same underlying column name causes conflict

Environment
Knex version: 0.17.6
Database + version: PostgreSQL 11.3
OS: macOS 10.14.5
Bug
The query:
db('users')
    .select({ user_id: 'users.id' }, { otp_id: 'otps.id' }, 'otps.*')
    .leftJoin('otps', 'users.id', 'otps.user_id')
    .where('users.phone_number', formattedPhoneNumber).first();

produces the sql:
select "users"."id" as "user_id", "otps"."id" as "otp_id", "otps".* from "users" left join "otps" on "users"."id" = "otps"."user_id" where "users"."phone_number" = ? limit ?

as expected. Everything works fine when the user has an OTP entry. However, if there is no OTP associated with some user then knex returns:
{
  user_id: null,
  otp_id: null,
  id: null,
  created_at: null,
  updated_at: null,
  otp: null,
  verified_at: null,
  expires_at: null
}

i.e. the user_id is null even though a user entry exists. Running the sql query directly on the DB (via psql) returns the expected results.
If I change the query to:
db('users')
    .select({ user_id: 'users.id' }, { otp_id: 'otps.id' }, 'otps.otp', 'otps.verified_at', 'otps.expires_at')
    .leftJoin('otps', 'users.id', 'otps.user_id')
    .where('users.phone_number', formattedPhoneNumber).first()

then everything works as expected so I suspect the issue is some sort of conflict when parsing the db response given that there are two columns with the same underlying name ('id').
In fact, if I swap the ordering of the select from:
select({ user_id: 'users.id' }, { otp_id: 'otps.id' }, 'otps.*')

to
select('otps.*', { user_id: 'users.id' }, { otp_id: 'otps.id' })

then the user_id has the expected result; which does strongly suggest that the user_id is getting overwritten by the otps id (this wouldn't happen in the second case because I assume the fields are being processed in the order that they're passed to the select).
Not sure why this isn't an issue when there's a entry in both the users and otps field.

Doesn't look like knex issue, but just how database / pg driver behaves in this particular case. If complete reproduction code is provided allowing other to verify the issues, this can be reopened.

Relevant code is:
const db = Knex({
    client: 'pg',
    connection: CONFIG.DB_CONNECTION_URL,
    pool: { min: 2, max: 10 }
});

db('users')
    .select({ user_id: 'users.id' }, { otp_id: 'otps.id' }, 'otps.*')
    .leftJoin('otps', 'users.id', 'otps.user_id')
    .where('users.phone_number', formattedPhoneNumber).first();

and for reference, the DB schema:
CREATE TABLE users (
    id uuid PRIMARY KEY,
    created_at TIMESTAMPTZ NOT NULL DEFAULT now(),
    updated_at TIMESTAMPTZ NOT NULL DEFAULT now(),
    first_name TEXT NOT NULL,
    family_name TEXT NOT NULL,
    phone_number VARCHAR(255) UNIQUE NOT NULL,  -- VARCHAR(255) can be indexed (unlike TEXT)
    email CITEXT,
    token_updated_at TIMESTAMPTZ,
    num_token_requests INTEGER NOT NULL DEFAULT 0
);

CREATE TABLE otps (
    id uuid PRIMARY KEY,
    created_at TIMESTAMPTZ NOT NULL DEFAULT now(),
    updated_at TIMESTAMPTZ NOT NULL DEFAULT now(),
    user_id uuid UNIQUE NOT NULL REFERENCES users(id),
    otp VARCHAR(255) NOT NULL,
    verified_at TIMESTAMPTZ,
    expires_at TIMESTAMPTZ NOT NULL
);

As I said, DB init data is important and thats not complete example, that will still require maybe 10 minutes to run it and still wouldn't be sure if it even works as is...
https://github.com/tgriesser/knex/blob/master/CONTRIBUTING.md#what-is-minimal-code-to-reproduce-bug-and-why-i-have-to-provide-that-when-i-can-just-tell-whats-the-problem-is

as expected. Everything works fine when the user has an OTP entry. However, if there is no OTP associated with some user then knex returns:

Queries for both of the cases would be needed

Running the sql query directly on the DB (via psql) returns the expected results.

And the plain query which was used to get expected results (bacause it couldn't have been the one produced by query builder or it wouldn't have worked).


More clarity required on Office 2016 versions

This page includes Office 2016 or later for Windows (build 16.0.6769+) in the section about supported platforms.
This requires some elaboration, as per my understanding only Office 2016 which comes as part of an Office 365 subscription actually supports this (see https://github.com/OfficeDev/office-js-docs-pr/issues/906).

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

ID: 2f18702b-d735-f775-62db-3ddc9187a11f
Version Independent ID: 5fc534d7-db48-745e-d2bb-c19e6c2f65a9
Content: Add-in commands for Excel, Word, and PowerPoint - Office Add-ins
Content Source: docs/design/add-in-commands.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@rocketraman we've already submitted doc updates for this doc (and another) as part of PR #914, so you should see updated info rendered in the docs later this week. (Doc updates get published twice a week, and these updates are in the queue for the next publication.) I'm going to go ahead and resolve this issue now (since doc updates are already pending publication), but please feel free to comment again here if the updates that get published later this week don't fully resolve this issue. Thanks!

Thank you, I didn't notice those changes last time I looked at the pull request, but do see them now. Cheers.


removes force cache from avatar requests

Signed-off-by: andrew<EMAIL_ADDRESS>

The data for the URL will be loaded from the originating source. No existing cache data should be used to satisfy a URL load request.


[UX] Cannot enter an amount from keyboard

When added to cart the product amount can only be adjusted by clicking + and - buttons which is extremely unaccessible.

This app was created only for demonstration purposes and not designed with UX accessibility in mind
Feel free to open your own PR


shuffle Log error status if exchange is shutdown early

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Switch to RTD v2 config

This approach is a trimmed-down version of #2433 that attempts to take on one change at a time (adopting v2 config) while also attempting to keep the config as trim as possible.

The rtd-bot is activated, but no .github/config.yml found in this repository.
Make sure that you have it in your default branch.

I tried activating this app for pypa for all repos (as it was for virtualenv only), but that didn't have the intended effect and I don't think it's the right app, so I switched it back to virtualenv only.

I tried activating this app for pypa for all repos (as it was for virtualenv only), but that didn't have the intended effect and I don't think it's the right app, so I switched it back to virtualenv only.

It's third-party and outdated. RTD don't have a GitHub App, they use per-repo webhooks to get events about the PRs.
To enable PR builds, toggling just one checkbox (per project) is necessary: https://docs.readthedocs.io/en/latest/guides/autobuild-docs-for-pull-requests.html.

I don't think the other formats were ever intentional. I suspect they were just generated as defaults. Now the defaults are just html, I guess.


How to reproduce the model deeplabv3_xception.h5?

Hi, I'm trying to train deeplabv3 with xception backbone on voc + SBD dataset. You provided the voc pretrained model deeplabv3_xception.h5. But If I want to reproduce your training result, I should not use it as pretrained model, right? So I comment out the line in train.py to not loading pretrained weights. But after 100 epochs, my model accuracy is poor, compared with your model. Did I miss something, do I need something like an ImageNet pretrained model or COCO pretrained model? Thanks!

@bubbliiiing

It will be difficult to reproduce the results of xception, and it should require a large memory of the graphics card for training.I remember that the effect of xception as the backbone in the paper should be about 80%. My previous pre training weight comes from https://github.com/bonlime/keras-deeplab-v3-plus. Its feature extraction effect is good.
If you want to start with backbone, you may need to know this https://github.com/keras-team/keras-applications/blob/master/keras_applications/xception.py

@bubbliiiing do you mean you used cityscapes pretrained model: https://github.com/bonlime/keras-deeplab-v3-plus/releases/download/1.2/deeplabv3_xception_tf_dim_ordering_tf_kernels_cityscapes.h5 to finetune on pascal voc? Let me try it. I'm not going to reach SOTA, but just to reproduce what you did to generate the voc model myself.

thanks! I can get reasonable accuracy with cityscapes pretrained model.
===>background:	mIou-92.38; mPA-95.9
===>aeroplane:	mIou-85.0; mPA-88.47
===>bicycle:	mIou-40.77; mPA-91.49
===>bird:	mIou-82.09; mPA-94.45
===>boat:	mIou-58.61; mPA-86.91
===>bottle:	mIou-71.73; mPA-86.56
===>bus:	mIou-89.62; mPA-91.48
===>car:	mIou-87.12; mPA-93.32
===>cat:	mIou-89.15; mPA-94.4
===>chair:	mIou-34.24; mPA-60.78
===>cow:	mIou-60.49; mPA-64.41
===>diningtable:	mIou-51.83; mPA-59.9
===>dog:	mIou-87.77; mPA-93.22
===>horse:	mIou-81.91; mPA-88.78
===>motorbike:	mIou-81.64; mPA-91.21
===>person:	mIou-82.8; mPA-88.29
===>pottedplant:	mIou-41.24; mPA-78.89
===>sheep:	mIou-84.88; mPA-95.24
===>sofa:	mIou-43.24; mPA-56.91
===>train:	mIou-77.98; mPA-86.84
===>tvmonitor:	mIou-66.68; mPA-81.11
===> mIoU: 71.01; mPA: 84.22

closing now.

3Q


suggestions comes from server?

your plugin is awesome man Thank you,
what if my suggestions comes from server so i had to display what the server returns?

I suggest you to check BLoC Pattern.
Here some helpful links. Those are explanations with examples made by Didier Boelens :
The basics with streams and BLoC pattern (Reactive Programming - Streams - BLoC)
A bit deeper and practical exemple (Reactive Programming - Streams - BLoC - Practical Use Cases)
A comparison between BLoC, ScopedModel and Redux (BLoC - ScopedModel - Redux - Comparison)
It helped me a lot and I hope you will find what you want too.

I am looking for something similar. It would be great if there is a feature that also allows you to make API requests.

Same here. I would be great if we can update the suggestion list after received the response from api request

Anything new here ?

Hi @Wizzel1,

Anything new here ?

Yes, there are always new great things are created.
If you assign a key object to your AutoCompleteTextField / SimpleAutoCompleteTextField widget, you can call something like this on your key whenever you want to update Suggestions ===>
key.currentState.updateSuggestions(List items).
I hope this help.

Hi @Wizzel1,

Anything new here ?

Yes, there are always new things are happend.
If you assign a key object to your AutoCompleteTextField / SimpleAutoCompleteTextField widget, you can call something like this on your key whenever you want to update Suggestions ===>
key.currentState.updateSuggestions(List items).
I hope this help.

@nabil-hfz thanks !

@Karlheinzniebuhr
Can you please, provide the full code you use ??
Best reagrds.


get_search_corpus not defined

add more descriptive error message to task_types that aren't supported yet.

recipe and data for search ranking task are available now.


After updating VS code to latest version Code sysntax color not working

Your file is set to plaintext mode. Try changing the language mode to js: https://code.visualstudio.com/docs/languages/overview#_changing-the-language-for-the-selected-file

[image: Inline image 1]
can you tell me why it's showing red line and no color syntax
Chirag Patel
Sr.Software Engineer
Mobile: +1<PHONE_NUMBER>
Email<EMAIL_ADDRESS>Connect With Me On:
https://www.linkedin.com/in/erchiragpatel  [image: http://is.gd/p0yarn]
http://is.gd/p0yarn
On Thu, Jul 20, 2017 at 4:21 PM, Matt Bierner<EMAIL_ADDRESS>wrote:

Your file is set to plaintext mode. Try changing the language mode to js:
https://code.visualstudio.com/docs/languages/overview#_
changing-the-language-for-the-selected-file
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/31154#issuecomment-316818702,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGsZ1glMdCqQgMh9M-P1UWUOoJqmyoAmks5sP7bVgaJpZM4OejDQ
.

You are using the typescript language mode. Try javascript or typescriptreact if this really is TS code


Code submission for FLIP fest 'Playground: Fix client-side errors in the playground frontend #58' - Milestone 0.5

Closes: #163 #164 #165 #166
Description
The Examples.tsx component had unnecessarily been including a 'key' prop in components nested inside of the main component that was being created by the map function. I believe one 'key' prop applied to the main component is sufficient.
The series of Redirects from reach router used in the project provider caused a cascade of errors as described in the four bug issues that I submitted. I'm currently investigating how this can be optimized. For now, the use of 'noThrow' in reach router suppresses the errors in the console. As explained in the reach router docs for the 'Redirect' feature:
"""
Redirect works with componentDidCatch to prevent the tree from rendering and starts over with a new location.
Because React doesn’t swallow the error this might bother you. For example, a redirect will trigger Create React App’s error overlay. In production, everything is fine. If it bothers you, add noThrow and Redirect will do redirect without using componentDidCatch.
If you’re using React < 16 Redirect will not throw at all, regardless of what value you put for this prop.
"""

For contributor use:

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the standards mentioned here.
[n/a] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[n/a] Added appropriate labels

@MrDSGC @alse can you look into this if it's still relevant to our current work?


Pods are schduled to hosts that are unknown

kubectl get minions
NAME                                                   LABELS              STATUS
...
host1                 Unknown
Pods are getting scheduled to host1 despite it being in an unknown state:
Mar 17 13:40:04 master kube-scheduler[7477]: I0317 13:40:04.525316    7477 factory.go:303] Attempting to bind my-hostname-density100-1d67cbee-ccab-11e4-b5ba-ecf4bbc72672qp4v to host1
This is further worsened by the controller-manager periodically deleting all pods on host1:
Mar 17 14:32:26 master kube-controller-manager[7478]: I0317 14:32:26.237110    7478 nodecontroller.go:426] Delete all pods from host1
The controller-manager seems to do this every 10 seconds.  Pods shouldn't be scheduled to a machine that can't run them.

Please add to performance and reliability label.

labeled

Why NodePhase is Unknown? cc/ @ddysher

In our case the node is one that has been configured via KUBELET_ADDRESSES on the controller-manager but has not checked in or been started up.  This could happen with nodes dropping out of the cluster due to hardware/networking issues.

More color, the node was in the list for a while but was only online/reachable recently due to our private provisioning issue.

This function doesn't seem to filter out nodes without conditions:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/plugin/pkg/scheduler/factory/factory.go#L233
			// If no condition is set, we get unknown node condition. In such cases,
			// we add nodes unconditionally.
			nodes.Items = append(nodes.Items, node)

nodes without conditions != node condition Unknown.  (the comment is a bit misleading)   However, when printing node status, if node has no conditions, we simply print Unknown.   Can you look at etcd and see the status of the node?  If it has no status, then @yujuhong gives the right anwser; otherwise, we'll need to dig more.

fixed by #5725

@piosz Yes, that is the PR that fixes this issue.


Add ability to add additional stores to the shader manager

At first I was considering using HashSet, however IResourceStore isn't implementing it's own hash code, so the same store can't be recognised as already being added. Comparing strings provided by GetavailableResources() would be heavier, so Dictionary with a name string was my choice.
Not sure if I should use ConcurrentDictionary instead though.

I got some serious dejavu reading through this PR because I was working on a similar branch here and everything down to the title and first 5 words of this PR was exactly the same as I was about to post.
That aside, what prevented me from posting it is the issue of isolation. Because ShaderManager has a dual role of caching IShaderParts and IShaders, there will be problems if, say, two rulesets define the lookup flashlight/texture, and either the two rulesets are played in sequence (there needs to be some cache busting logic) or the two rulesets are present simultaneously such as in multiplayer (this method cannot handle that).
I'm continuing to work on this issue, but I don't think this change is a good path forward as it is.

@smoogipoo I'll leave it up to you then since I'm not sure I have anything valuable to propose here.


Document how to use a custom image

Fixes #160

How does this look, @choldgraf?

How does this look, @choldgraf?

One other thought - I think we should define the process by which these images generally get onto the hub. E.g., do we tell the hub admins that they should open a PR to this repository that points the user image to their hub image? Do they tell the hub engineer about the location of the image and then the engineer opens the PR?
cc also @zaneselvans who I think would be interested in this workflow and might have comments himself!

One other thought - I think we should define the process by which these images generally get onto the hub. E.g., do we tell the hub admins that they should open a PR to this repository that points the user image to their hub image? Do they tell the hub engineer about the location of the image and then the engineer opens the PR?
cc also @zaneselvans who I think would be interested in this workflow and might have comments himself!

I'm just gonna merge this in because it's a clear improvement over what we've already got. Let's iterate from there!

I'm just gonna merge this in because it's a clear improvement over what we've already got. Let's iterate from there!

Sorry I've been a bit absent. We finally got a draft of the grant sent off and I have space for other things now. So if I understand correctly, we can create our own container image based on one of the ones you've listed, like something appropriate from the stack of curated Jupyter images, add our own layer to the image with our required packages installed, and then push it to some container registry, and then specify in the hubs.yaml file what registry, container, and tag should be pulled, and that's the image that will show up on our hub.  And if we screw something up in the image then we need to go fix it ourselves 😄
How would one best go about testing potential new images before deploying them to the hub for everyone to use? Is it usually enough to just try and run a notebook server locally using the image? Or is there some way to deploy it only for some users and not others? Or have a testing hub setup that runs alongside the production one?

Sorry I've been a bit absent. We finally got a draft of the grant sent off and I have space for other things now. So if I understand correctly, we can create our own container image based on one of the ones you've listed, like something appropriate from the stack of curated Jupyter images, add our own layer to the image with our required packages installed, and then push it to some container registry, and then specify in the hubs.yaml file what registry, container, and tag should be pulled, and that's the image that will show up on our hub.  And if we screw something up in the image then we need to go fix it ourselves 😄
How would one best go about testing potential new images before deploying them to the hub for everyone to use? Is it usually enough to just try and run a notebook server locally using the image? Or is there some way to deploy it only for some users and not others? Or have a testing hub setup that runs alongside the production one?

And the repositories that control all these configurations are administered by 2i2c, with users/clients making PRs to implement changes?

And the repositories that control all these configurations are administered by 2i2c, with users/clients making PRs to implement changes?

No worries @zaneselvans -

we can create our own container image based on one of the ones you've listed

You don't need to base your image based on those images, though doing so might make your life a bit easier (particularly, using repo2docker to generate the image). You just need to make sure the constraints listed in https://2i2c.org/pilot-hubs/custom-image.html#image-requirements are met

if we screw something up in the image then we need to go fix it ourselves

We can provider pointers about what kinda stuff needs to be in the image, but yeah we probably don't have time to curate everybody's custom Docker image. We're thinking of this like an "advanced use case". In the future we probably want easier ways for people to extend the environment.

How would one best go about testing potential new images before deploying them to the hub for everyone to use?

That is a good question - normally what we do is set up a staging hub alongside the production hub. That said, this would definitely be added complexity for the infrastructure and it's not set up to do this yet. In the short term, I think the method you describe is probably reasonable, though you wouldn't be able to test stuff like scaling with kubernetes etc. Maybe start off trying that and then see how it goes from there?
@yuvipanda what are your thoughts on recommendations for how users can "test out" their images before deploying them?

No worries @zaneselvans -

we can create our own container image based on one of the ones you've listed

You don't need to base your image based on those images, though doing so might make your life a bit easier (particularly, using repo2docker to generate the image). You just need to make sure the constraints listed in https://2i2c.org/pilot-hubs/custom-image.html#image-requirements are met

if we screw something up in the image then we need to go fix it ourselves

We can provider pointers about what kinda stuff needs to be in the image, but yeah we probably don't have time to curate everybody's custom Docker image. We're thinking of this like an "advanced use case". In the future we probably want easier ways for people to extend the environment.

How would one best go about testing potential new images before deploying them to the hub for everyone to use?

That is a good question - normally what we do is set up a staging hub alongside the production hub. That said, this would definitely be added complexity for the infrastructure and it's not set up to do this yet. In the short term, I think the method you describe is probably reasonable, though you wouldn't be able to test stuff like scaling with kubernetes etc. Maybe start off trying that and then see how it goes from there?
@yuvipanda what are your thoughts on recommendations for how users can "test out" their images before deploying them?

repo2docker definitely sounds like a good way to go for something like our (hopefully growing) collection of tutorial notebooks. It does seem like it might be a little funny to have a repo that mostly exists to specify a Docker container. Is that common? Our plan right now is to try and use exactly the same Docker container for the JupyterHub as we use for local day-to-day work, and to archive it alongside the data releases for use by future users that want to download a completely self-contained environment. But maybe setting up an environment.yml in our https://github.com/catalyst-cooperative/pudl-tutorials repo would be a good way to start defining the environment.
I imagine it'll also include the Intake data catalog conda packages once we create them.  I kind of want to experiment with that soon.  I've been wondering what costs would end up being associated with just having Hub users use Intake to pull data for local use -- like would there be egress fees to get it to the Hub from our cloud storage? Would every hub user necessarily end up with their own duplicated local file cache?

repo2docker definitely sounds like a good way to go for something like our (hopefully growing) collection of tutorial notebooks. It does seem like it might be a little funny to have a repo that mostly exists to specify a Docker container. Is that common? Our plan right now is to try and use exactly the same Docker container for the JupyterHub as we use for local day-to-day work, and to archive it alongside the data releases for use by future users that want to download a completely self-contained environment. But maybe setting up an environment.yml in our https://github.com/catalyst-cooperative/pudl-tutorials repo would be a good way to start defining the environment.
I imagine it'll also include the Intake data catalog conda packages once we create them.  I kind of want to experiment with that soon.  I've been wondering what costs would end up being associated with just having Hub users use Intake to pull data for local use -- like would there be egress fees to get it to the Hub from our cloud storage? Would every hub user necessarily end up with their own duplicated local file cache?

It does seem like it might be a little funny to have a repo that mostly exists to specify a Docker container. Is that common?

Well the reason to use repo2docker is because it is what Binder uses, so basically the repository you'd have would be ~ a Binder repository, for which yes there are many out there just to specify an environment 👍
The main benefit of this is just that environment.yml, requirements.txt, etc tend to be much more human-readable than Dockerfiles, so easier to maintain for folks who aren't Docker experts

like would there be egress fees to get it to the Hub from our cloud storage? Would every hub user necessarily end up with their own duplicated local file cache?

I bet it depends a lot on where hte data is stored relative to where the hub runs. Usually data transfer fees are much, much smaller if the data doesn't need to leave the cloud. If the data was (relatively) small, then it shouldn't be a big deal to effectively have copies on user drives, but definitely something we cna experiment with moving forward

It does seem like it might be a little funny to have a repo that mostly exists to specify a Docker container. Is that common?

Well the reason to use repo2docker is because it is what Binder uses, so basically the repository you'd have would be ~ a Binder repository, for which yes there are many out there just to specify an environment 👍
The main benefit of this is just that environment.yml, requirements.txt, etc tend to be much more human-readable than Dockerfiles, so easier to maintain for folks who aren't Docker experts

like would there be egress fees to get it to the Hub from our cloud storage? Would every hub user necessarily end up with their own duplicated local file cache?

I bet it depends a lot on where hte data is stored relative to where the hub runs. Usually data transfer fees are much, much smaller if the data doesn't need to leave the cloud. If the data was (relatively) small, then it shouldn't be a big deal to effectively have copies on user drives, but definitely something we cna experiment with moving forward


WIP: Refactor block queue

:clipboard: Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Change 1
Change 2
...

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.

Whoops, forgot to give an update here. This was put on hold to focus on more stuff. Might get back to it later.

Master probably drifted so much away from this. Might want to close?


[bug]: NavigationMenu content does not show right undernith of a NavigationMenuItem

Describe the bug
NavigationMenu content does not show right undernith of a NavigationMenuItem.  It just sticks to left side.
Screencast from 2024-12-20 01-39-29.webm
Affected component/components
NavigationMenu
How to reproduce
This is the component:
"use client";

import * as React from "react";
import Link from "next/link";
import { cn } from "@/lib/utils";
import {
  NavigationMenu,
  NavigationMenuItem,
  NavigationMenuList,
  NavigationMenuContent,
  NavigationMenuLink,
  NavigationMenuTrigger,
} from "@/components/shadcn-ui/navigation-menu";
import { usePathname } from "next/navigation";
import { Separator } from "@/components/shadcn-ui/separator";

interface Brand {
  brandId: string;
  categoryId: string;
  brand: {
    id: string;
    name: string;
  };
}

interface ProductSubcategory {
  id: string;
  name: string;
  categoryId?: string;
}

interface Category {
  id: string;
  name: string;
  productSubcategory: ProductSubcategory[];
  brands: Brand[];
}

export default function NavbarMenu({ categories }: { categories: Category[] }) {
  const router = usePathname();

  const shouldHide = router.includes("/dashboard");

  if (shouldHide) {
    return null;
  }

  return (

        <NavigationMenu className="max-w-screen-2xl">
          <NavigationMenuList className="flex flex-wrap gap-1">
            {categories?.map((category) => (
              <NavigationMenuItem key={category.id} className="">
                <NavigationMenuTrigger className="">
                  {category.name}
                </NavigationMenuTrigger>
                <NavigationMenuContent className="">

                      <NavigationMenuLink asChild>
                        <Link
                          className="flex h-full w-full select-none flex-col justify-end rounded-md bg-gradient-to-b from-muted/50 to-muted p-6 no-underline outline-none focus:shadow-md"
                          href={`/search?categoryId=${category.id}`}
                        >

                            {category.name}

                            Explore all {category.name} products

                        </Link>
                      </NavigationMenuLink>

                    <SubcategoryList category={category} />

                </NavigationMenuContent>
              </NavigationMenuItem>
            ))}
          </NavigationMenuList>
        </NavigationMenu>

      <Separator />

  );
}

const SubcategoryList = ({ category }: { category: Category }) => {
  return (

        {category.productSubcategory.map((subcategory) => (
          <Link
            key={subcategory.id}
            href={`/search?categoryId=${category.id}&subcategoryId=${subcategory.id}`}
          >
            <ListItem title={subcategory.name} />
          </Link>
        ))}

      {category.brands.length > 0 && (

          {category.brands.map((brandItem) => (
            <Link
              key={brandItem.brand.id}
              href={`/search?categoryId=${brandItem.categoryId}&brandId=${brandItem.brand.id}`}
            >
              <ListItem title={brandItem.brand.name} />
            </Link>
          ))}

      )}

  );
};

const ListItem = React.forwardRef<
  React.ElementRef<"a">,
  React.ComponentPropsWithoutRef<"a">
>(({ className, title, children, ...props }, ref) => {
  return (

      <NavigationMenuLink asChild>

{title}

            {children}

      </NavigationMenuLink>

  );
});
ListItem.displayName = "ListItem";

Codesandbox/StackBlitz link
No response
Logs
No response
System Info
Firefox, Chrome, Brave

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

`"use client";
import * as React from "react";
import Link from "next/link";
import { cn } from "@/lib/utils";
import {
NavigationMenu,
NavigationMenuItem,
NavigationMenuList,
NavigationMenuContent,
NavigationMenuLink,
NavigationMenuTrigger,
} from "@/components/shadcn-ui/navigation-menu";
import { usePathname } from "next/navigation";
import { Separator } from "@/components/shadcn-ui/separator";
interface Brand {
brandId: string;
categoryId: string;
brand: {
id: string;
name: string;
};
}
interface ProductSubcategory {
id: string;
name: string;
categoryId?: string;
}
interface Category {
id: string;
name: string;
productSubcategory: ProductSubcategory[];
brands: Brand[];
}
export default function NavbarMenu({ categories }: { categories: Category[] }) {
const router = usePathname();
const shouldHide = router.includes("/dashboard");
if (shouldHide) {
return null;
}
return (

{categories?.map((category) => (

{category.name}

<Link
className="flex h-full w-full select-none flex-col justify-end rounded-md bg-gradient-to-b from-muted/50 to-muted p-6 no-underline outline-none focus:shadow-md"
href={/search?categoryId=${category.id}}
>

{category.name}

Explore all {category.name} products

))}

);
}
const SubcategoryList = ({ category }: { category: Category }) => {
return (

{category.productSubcategory.map((subcategory) => (
<Link
key={subcategory.id}
href={/search?categoryId=${category.id}&subcategoryId=${subcategory.id}}
>

))}

{category.brands.length > 0 && (

{category.brands.map((brandItem) => (
<Link
key={brandItem.brand.id}
href={/search?categoryId=${brandItem.categoryId}&brandId=${brandItem.brand.id}}
>

))}

)}

);
};
const ListItem = React.forwardRef<
React.ElementRef<"a">,
React.ComponentPropsWithoutRef<"a">

(({ className, title, children, ...props }, ref) => {
return (

<span
ref={ref}
className={cn(
"block select-none space-y-1 rounded-md p-3 leading-none no-underline outline-none transition-colors hover:bg-accent hover:text-accent-foreground focus:bg-accent focus:text-accent-foreground",
className
)}
{...props}

{title}

        {children}

  </NavigationMenuLink>

);
});
ListItem.displayName = "ListItem";`
Actually The max-w-screen-2xl class on the NavigationMenu was constraining the width and affecting the natural positioning behavior of the menu components.
and
The NavigationMenuList (the container for menu items) didn't have proper centering - adding justify-center ensures the items are centered within the navigation bar rather than sticking to the left.

Actually The max-w-screen-2xl class on the NavigationMenu was constraining the width and affecting the natural positioning behavior of the menu components. and The NavigationMenuList (the container for menu items) didn't have proper centering - adding justify-center ensures the items are centered within the navigation bar rather than sticking to the left. here is the file with the fixed code . issue.txt

I have checked with your code . Still not working. I think the issue is in this navigation-menu component of shadcn. Specifically in here they set left-0 but it should be dynamic.
const NavigationMenuViewport = React.forwardRef<
  React.ElementRef<typeof NavigationMenuPrimitive.Viewport>,
  React.ComponentPropsWithoutRef<typeof NavigationMenuPrimitive.Viewport>
>(({ className, ...props }, ref) => (

    <NavigationMenuPrimitive.Viewport
      className={cn(
        "origin-top-center relative mt-1.5 h-[var(--radix-navigation-menu-viewport-height)] w-full overflow-hidden rounded-md border bg-popover text-popover-foreground shadow data-[state=open]:animate-in data-[state=closed]:animate-out data-[state=closed]:zoom-out-95 data-[state=open]:zoom-in-90 md:w-[var(--radix-navigation-menu-viewport-width)]",
        className
      )}
      ref={ref}
      {...props}
    />

));
NavigationMenuViewport.displayName =
  NavigationMenuPrimitive.Viewport.displayName;

@shadcn Could you please have a look at it?

sorry for missing out , heres the solution to your problem and i have verified it
The  NavigationMenuContent was Stuck to the left due to the following reasons :

Default Positioning: The NavigationMenuContent component was  using absolute positioning by default, with a left: 0 property. This caused it to align to the left edge of its nearest positioned ancestor (which was probably the entire navigation bar).
Lack of Relative Positioning: The parent NavigationMenuItem wasn't set to position: relative, which meant the absolutely positioned NavigationMenuContent couldn't position itself relative to its immediate parent (the category item).
Width Issues: The NavigationMenuContent probably had a fixed width or was expanding to the full width of its container, which made it appear to start from the left side of the screen.
Z-index Stacking: There might have been z-index issues causing the subcategory menu to appear behind other elements or not stack properly above the main navigation items.

To fix this, I made the following key changes:

Removed absolute positioning from the NavigationMenuContent.
Allowed the NavigationMenu component to handle the positioning of its children naturally.
Adjusted the width of the NavigationMenuContent to be consistent for each category, preventing it from expanding too wide.
Simplified the overall structure to ensure each subcategory menu appears directly below its respective category trigger.

navigationmenu.txt

Also you can close the Issue if your problem is solved kindly let me know

got you , tried a lot of times and still got the same issue think its linked with some other parameter

@kdipto1 solution for you here is to remove: md:w-[var(--radix-navigation-menu-viewport-width)] from navigation-menu.tsx then container will grow for the full width of your navbar.
And add: w-full absolute w-full left-0 top-full flex justify-center for component NavigationMenuViewport
Docs
Or implement custom logic.


Only log errors for webpack module bundles

Current behavior
I need to setup webpack module bundling in an existing .NET MVC project which currently uses old MVC javascript bundling. Both bundling methods still need to exist next to each other. For the new projects inside this solution, I thus use module bundling via WebPack. I reuse the existing tsconfig but overwrite some properties with ts-loader.
I work in Visual Studio 2019
Expected behavior
I would like to see only compilation errors in TypeScript files that are related to my webpack entry files. Currently I see all errors in the Typescript files of the project, even if they're not part of the dependency tree starting from my entry files.
Because tsconfig uses a lot of "includes" that I cannot change or overwrite, due to folder structure.
Steps to reproduce the issue
This is my setup for ts-loader
// Load all TypeScript through the "ts-loader"
            {
                test: /\.ts?$/,
                use: [
                    {
                        loader: "babel-loader",
                        options: {
                            "presets": [
                                [
                                    "@babel/preset-env",
                                    {
                                        "targets": {
                                            "esmodules": true
                                        }
                                    }
                                ]
                            ]
                        }
                    },
                    {
                        loader: "ts-loader",
                        options: {
                            transpileOnly: true, // Disable type checker - we will use it in ForkTsCheckerWebpackPlugin,
                            compilerOptions: {
                                "target": "es6", // Modern JavaScript
                                "sourceMap": false, // Webpack creates this
                            }
                        }
                    }
                ]
            }

And my setup for the Fork TS
new ForkTsCheckerWebpackPlugin({
            typescript: {
                diagnosticOptions: {
                    semantic: true,
                    syntactic: true,
                },
            },
            issue: {
                scope: 'webpack',
            },
        })

tsconfig (I didn't touch this to don't break existing projects inside the solution)
{
  "compilerOptions": {
    "sourceMap": true,
    "target": "es5",
    "lib": [ "es2015", "es2015.iterable", "dom" ]
  },
  "compileOnSave": true,
  "include": [
    "Scripts/**/*",
    "Modules/**/*",
  ],
  "exclude": [
    "bin/**/*.*",
    "obj/**/*.*",
    "node_modules/**/*.*",
    "wwwroot/**/*.*",
  ]
}

I have one entry file (webpack-entry.ts) inside the "Modules" folder that contains an error, just to test Fork TS. However, I also see errors unrelated to the entry file or it's imports.
Environment

fork-ts-checker-webpack-plugin: 6.0.1
typescript: 4.0.5,
webpack: 5.4.0
os: Windows

Hi 👋  Thanks for the report!
We don't have plan to support this. In version 6 issue.scope was removed.
If you want that behaviour, you can overwrite include and exclude in the plugin options (typescript.configOverwrite).
We have to add files outside default webpack's dependency tree to reload compilation on types-only files change.

I'm closing this issue for the maintenance reasons - let me know if you still have an issue - I will reopen then


[Feature] Add Follow Along Cursor

Description
I want to add this minimalist follow along cursor that emphasizes the important contents on the page.
Screenshots
https://github.com/user-attachments/assets/8de116ae-854f-47cf-b39c-f14401118442
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Don't open too many issues at once, max 2 can be opened @Praneeth-2602

Don't open too many issues at once, max 2 can be opened, maintain the decorum of open-source @Praneeth-2602


Ensure samtools is installed for tests

One of the tests was not actually testing anything because samtools was not installed and the test failed silently. This PR 1) installs samtools and 2) adds a test that checks whether samtools is installed so that this does not happen again.
(Background: set -e in a bash script should make subsequent commands fail, but this does not apply to commands within <( ... ).)

This is a bugfix that should be uncontroversial, so merging now.


mne.beamformer.make_lcmv crashes when given a Label

mne.beamformer.make_lcmv works without any label chosen but crashes when a Label instance is chosen with the label= argument.
Please help! Thank you :slight_smile:
OS details:
MNE version: 1.3.0
operating system: Ubuntu 20.04
Minimally reproducible example:
import matplotlib.pyplot as plt
import mne
from mne.datasets import sample, fetch_fsaverage
from mne.beamformer import make_lcmv, apply_lcmv

data_path = sample.data_path()
subjects_dir = data_path / "subjects"
meg_path = data_path / "MEG" / "sample"
raw_fname = meg_path / "sample_audvis_filt-0-40_raw.fif"

# Read the raw data
raw = mne.io.read_raw_fif(raw_fname)
raw.info["bads"] = ["MEG 2443"]  # bad MEG channel

# Set up the epoching
event_id = 1  # those are the trials with left-ear auditory stimuli
tmin, tmax = -0.2, 0.5
events = mne.find_events(raw)

# pick relevant channels
raw.pick(["meg", "eog"])  # pick channels of interest

# Create epochs
proj = False  # already applied
epochs = mne.Epochs(
    raw,
    events,
    event_id,
    tmin,
    tmax,
    baseline=(None, 0),
    preload=True,
    proj=proj,
    reject=dict(grad=4000e-13, mag=4e-12, eog=150e-6),
)

# for speed purposes, cut to a window of interest
evoked = epochs.average().crop(0.05, 0.15)

# Visualize averaged sensor space data
evoked.plot_joint()

del raw  # save memory

data_cov = mne.compute_covariance(epochs, tmin=0.01, tmax=0.25, method="empirical")
noise_cov = mne.compute_covariance(epochs, tmin=tmin, tmax=0, method="empirical")
data_cov.plot(epochs.info)
del epochs

fwd_fname = meg_path / "sample_audvis-meg-vol-7-fwd.fif"
forward = mne.read_forward_solution(fwd_fname)

# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
roi_names = [# Left
             'rostralanteriorcingulate-lh', # Left Rostral ACC
             'caudalanteriorcingulate-lh', # Left Caudal ACC
             'postcentral-lh', # Left S1,
             'insula-lh', 'superiorfrontal-lh', # Left Insula, Left DL-PFC,
             'medialorbitofrontal-lh', # Left Medial-PFC
             # Right
             'rostralanteriorcingulate-rh', # Right Rostral ACC
             'caudalanteriorcingulate-rh', # Right Caudal ACC
             'postcentral-rh', # , Right S1
             'insula-rh', 'superiorfrontal-rh', # Right Insula, Right DL-PFC
             'medialorbitofrontal-rh'] # Right Medial-PFC

subject="sample"
selected_labels = [mne.read_labels_from_annot(subject, regexp=roi, subjects_dir=subjects_dir)[0] for roi in roi_names]
print(selected_labels)

filters = make_lcmv(
    evoked.info,
    forward,
    data_cov,
    reg=0.05,
    noise_cov=noise_cov,
    label=selected_labels[0], # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    pick_ori="max-power",
    weight_norm="unit-noise-gain",
    rank=None,
)
# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I haven't tested the code but it looks okay, so if there is an error then we do probably have some bug. Hopefully someone can take a look soon!

@wmvanvliet or @britta-wstnr do you have time to look?

Hey - sorry this week is a sea of deadlines for me, but I will put it on my agenda for next week (unless @wmvanvliet beats me to it!) 📆

Managed to check this out - note that you are using a volume forward model. The code runs fine for me with a surface model (sample_audvis-meg-oct-6-fwd.fif).
We might want to throw a better error message though, WDYT @larsoner ? right now it crashes with TypeError: cannot unpack non-iterable Exception object.

Sounds like we need to fix the exception handling (that unpacking error suggests we're doing something wrong) and indeed add an error message if a label is requested for a volume source space

extract_label_time_course can work with volume atlases, so maybe you can calculate LCMV for the whole brain and then extract that way


[$500] Web – Search panel opens with delay

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.15-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR https://github.com/Expensify/App/pull/33399
Action Performed:

Go to staging.new.expensify.com
Click SearchPage

Expected Result:
Search page opens smoothly
Actual Result:
Search panel opens with delay
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] Windows: Chrome
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/cc2253ac-17dd-4596-b465-d82d8d08a2ca
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~019ade6495b88cc576
Upwork Job ID:<PHONE_NUMBER>753763840
Last Price Increase: 2023-12-21

Seems like a dupe of (or related to) these:
https://github.com/Expensify/App/issues/33326
https://github.com/Expensify/App/issues/33291

@mountiny do you agree we don't need this additional issue open?

I agree that this is a dupe, closing

Agreed


Fixing datamodel diagram and adding legacy ids

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.33%. Comparing base (5cc862a) to head (6806d4d).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #140   +/-   ##
=========================================
  Coverage     90.33%   90.33%
  Complexity      745      745
=========================================
  Files           137      137
  Lines          2153     2153
  Branches        147      147
=========================================
  Hits           1945     1945
  Misses          129      129
  Partials         79       79

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Document env vars for log level

Log, LOG_LEVEL to specify a log level, or else TRACE/DEBUG=1 (or really anything).

Make a note about: setting log level to higher then info, will disable logging of requests.


when create Index dynamically, It'll not sync the generated DefaultObjectRepository instance

ObjectRepository repo = Nitrite.getRepository(clazz);
repo.createIndex(RESOURCE_ID, IndexOptions.indexOptions(IndexType.Unique));
repo.update(entity) then I get an Exception: throw new NotIdentifiableException(OBJ_REMOVE_FAILED_AS_NO_ID_FOUND);
//Hao Liu.

As far as I understand from the error message, you have not marked any field with @Id annotation in your entity class. Normally not every object needs @Id annotation but, if you do a operation like update(entity) or remove(entity) then you must add it. The id field will be used as a filter to identity the object from the repository. The other option is to use the overloaded method update(ObjectFilter filter, T update) where you need to provide a filter to identify the object.
Your code repo.createIndex(RESOURCE_ID, IndexOptions.indexOptions(IndexType.Unique)); does not mark an id field as required by Nitrite, it just creates an index.
Moreover, your example code here is not complete, the error message you mentioned OBJ_REMOVE_FAILED_AS_NO_ID_FOUND would only come from a remove(entity) operation not from update(entity) operation. If adding @Id annotation does not solve your problem, then I suggest you to add a complete reproducible code along with the entity class here, so that I can reproduce your error.

I know that, however, the dynamically creating index of an entity is surported by the createIndex api, I think when users invoke this API, it should have the same effect of add an @Id annotation exeplicitly.

You can create as many index as you like, but those indices are not id. It is a special type of index which can only be created by using the @Id annotation. It's a design decision not to create id dynamically, otherwise it will create more problems than it will solve.

As I understand you create Index for id field if it's present in an entity by default. Then why don't you provide a default @Id filed?

I did not quite understand you, what do you mean by default id field?
To clarify, internally, nitrite converts every object to a Document and store it in a MVMap. Now Document has its own _id key which is an auto generated long field and can not be set by user and also can not be accessed by object.
The field marked with @Id annotation is just a field used as a default filter to search an object, if that is not mentioned, user need to explicitly provide search filter. This design is to keep things simple.


Add code coverage reporting

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@aead62b). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #1   +/-   ##
=======================================
  Coverage        ?   88.66%
=======================================
  Files           ?        4
  Lines           ?      150
  Branches        ?        0
=======================================
  Hits            ?      133
  Misses          ?       17
  Partials        ?        0

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

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


Login

Created loginForm component under Auth. This is the sign in page - Lgin form Amin App - Sprint  UI.
It is just the UI without the routing and connecting to the backend apis.

https://app.codacy.com/gh/ALCOpenSource/Mentor-Management-System-Team-3/pullRequest?prid=11521551
Kindly check the errors in the above url from codacy. Kindly resolve the issues. Thank you.

https://app.codacy.com/gh/ALCOpenSource/Mentor-Management-System-Team-3/pullRequest?prid=11521551
Kindly check the errors in the above url from codacy. Kindly resolve the issues. Thank you.

Sure


python312Packages.iocsearcher: init at 2.3-unstable-2024-03-04

Description of changes
Library and command line tool for extracting indicators of compromise (IOCs)
https://github.com/malicialab/iocsearcher
Related to https://github.com/NixOS/nixpkgs/issues/81418

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 294322 run on x86_64-linux 1

12 packages built:

iocsearcher (python311Packages.iocsearcher)
iocsearcher.dist (python311Packages.iocsearcher.dist)
python311Packages.cashaddress
python311Packages.cashaddress.dist
python311Packages.readabilipy
python311Packages.readabilipy.dist
python312Packages.cashaddress
python312Packages.cashaddress.dist
python312Packages.iocsearcher
python312Packages.iocsearcher.dist
python312Packages.readabilipy
python312Packages.readabilipy.dist


Skip blank lines and comments

It is valid to have blank lines and comments in a CODEOWNERS file - see here - but these are currently not handled.
A blank line added or removed (so in the diff which is filtered) results in the tool crashing, e.g.
Traceback (most recent call last):
  File ".../venv/bin/codeowners-diff", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File ".../venv/lib/python3.12/site-packages/codeowners_diff.py", line 148, in main
    affected_paths = find_affected_paths(base_code_owners_src, head_code_owners_src)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../venv/lib/python3.12/site-packages/codeowners_diff.py", line 91, in find_affected_paths
    return frozenset(
           ^^^^^^^^^^
  File ".../venv/lib/python3.12/site-packages/codeowners_diff.py", line 92, in <genexpr>
    line.split()[1]
    ~~~~~~~~~~~~^^^
IndexError: list index out of range

I suspect a comment is treated as though the initial # is a path to be globbed.

Thanks!

...and release this.

I've got another fix incoming...


can not open integrated terminal

VSCode Version: Code 1.12.2 (19222cdc84ce72202478ba1cec5cb557b71163de, 2017-05-10T13:20:36.315Z)
OS Version: Windows_NT ia32 6.1.7600
Extensions:

Extension
Author
Version

markdown-toc
AlanWalk
1.5.1

EditorConfig
EditorConfig
0.9.3

tslint
eg2
0.15.0

vscode-npm-script
eg2
0.1.9

code-spell-checker
streetsidesoftware
1.1.0

I always get
"The terminal process command C:\WINDOWS\system32\cmd.exe failed to launch (exit code: 1)"
Steps to Reproduce:

Click View-> Integrated terminal or press CTRL + `

What version of Windows are you on? Also can you check that cmd.exe actually exists in that location?

Hi @Tyriar , I'm using windows 10 (Microsoft Windows 10 Pro Version	10.0.15063 Build 15063).
cmd exists in the location and I can start it using run dialog and pasting the path.
Is there any log or similar I can attach?

@kirilpopov other than looking at the devtools console (Help > Toggle Developer Tools) there isn't much logging.
Are you running VS Code in compatibility mode? https://code.visualstudio.com/docs/editor/integrated-terminal#_integrated-terminal-exited-with-code-1-on-windows-10

Thanks, @Tyriar  - it was the comparability mode 🥇


Bump cargo to 0.32.0

It's that time of every-6-weeks!

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

@bors r+

:pushpin: Commit aab0a3385932c8f5453c4fcd69e23c82bbc1c921 has been approved by Mark-Simulacrum

:hourglass: Testing commit aab0a3385932c8f5453c4fcd69e23c82bbc1c921 with merge 2c86b7f033f7a2ac2149b40e73533897bb2a45f9...

:sunny: Test successful - status-appveyor, status-travis
Approved by: Mark-Simulacrum
Pushing 2c86b7f033f7a2ac2149b40e73533897bb2a45f9 to master...


Install issue when VueRouter is already used on Vue

Version
1.0.0-beta.11
Reproduction link
https://codesandbox.io/s/p7x5mqkx2q
Steps to reproduce
This likely applies to other libraries, but when VueRouter is already installed on Vue (i.e Vue.use(VueRouter)) and then subsequently used with localVue, it errs with
Error: [vue-router] not installed. Make sure to call `Vue.use(VueRouter)` before creating root instance.

What is expected?
No error.
What is actually happening?
Error: [vue-router] not installed. Make sure to call `Vue.use(VueRouter)` before creating root instance.

Adding
VueRouter.install.installed = true

after declaring a localVue instance fixes the issue.

As another reference, this is happening when testing with webpack (and a shall-remain-unnamed other old framework), likely due to the fact that the package is initializing the main app with VueRouter installed, etc.

due to the fact that the package is initializing the main app with VueRouter installed, etc.

Well that doesn't sound like something that should be happening in a unit test.

That's not a very classy response to a verified bug of which I spent an hour isolating and "formatting" for your issue bot. There should not be an error in using createLocalVue when Vue.use is called in the same file.

Thanks for the bug report.
We could definitely improve how we handle multiple installs. I'll look into what we should do.
We actually have some code meant to address the issue with vue-router specifically—https://github.com/vuejs/vue-test-utils/blob/dev/src/create-local-vue.js#L35. I'll look into why it's not working and possible solutions.

I'm sorry that my answer what a bit short and snappy, I apologize.
My reply was not meant as an answer or rejection of your issue, but merely as an observation of a bad pattern in general. You are loading a file that can have, and in this instance does have a global side effect on your unit tests. You are starting your whole app within your unit tests, which is not a good idea.
The error message you are seeing is created by vue-router abs plus have to be solved there, if required. Judging that I leave to the maintainer of this repo.

Thanks for looking into it. It's definitely a bad pattern, and one that we're still dealing with due to our transition off Angular.
I've been playing around with the code you referenced, @eddyerburgh, and have yet to find a clean solution.  What's strange is that VueRouter even seems to try to verify that Vue is the same Vue that the router was previously installed to...
I'll try to do some more digging as well.

Here's the culprit in core vuejs:
https://github.com/vuejs/vue/blob/049f3171a9d2e97f62c209a4b78a71ec9dae810f/src/core/global-api/use.js#L8
This commit fixes the issue for me, although I really dislike these things being so dependent on Vue's internals:
https://github.com/kellym/vue-test-utils/commit/961912c925601f28dd0e16e54046d271be20d837#diff-4dcb7576e72c067fba6def9222025466R35
Interestingly enough, the router seems to work fine on localVue and doesn't err if it's declared via Vue.use(VueRouter) and not called at all via localVue.use(VueRouter). Since I don't have any experience with VueRouter < 2.7, I'm not sure the implications of only .useing it one way or the other. (example below)
Vue.use(VueRouter); // comment out this line or the one commented below and it works fine
const localVue = createLocalVue();
// localVue.use(VueRouter);
const router = new VueRouter();
const wrapper = shallow(Component, { localVue, router });

Great find @kellym 🙂. Can you make a PR please?

Sure can, I'll try to submit one tomorrow.


Change the appearance of the GUI #1

changes have been done #10 @its-abhishek can I pull request

@TharunK41
You have submitted a PR for an issue that you were not assigned to. Hence, rejecting this PR :(


chore(deps): update terraform terraform-ibm-modules/landing-zone/ibm to v5.19.1

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/landing-zone/ibm (source)
module
minor
5.17.2 -> 5.19.1

Release Notes

terraform-ibm-modules/terraform-ibm-landing-zone (terraform-ibm-modules/landing-zone/ibm)
v5.19.1
Compare Source
Bug Fixes

deps: update terraform external to latest for the landing zone das (#718) (82a9e79)

v5.19.0
Compare Source
Features

added workload_cluster_id and management_cluster_id outputs (#713) (cae6de7)

v5.18.0
Compare Source
Features

added cluster addon support to the OCP DA and module. It can be configured using the cluster_addons and manage_all_cluster_addons variables (#733) (c7d443d)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 4.6.0 :tada:
The release is available on:

GitHub release
v4.6.0

Your semantic-release bot :package::rocket:


Don't force TextDe/Encoder

Currently the generated JS shim calls TextDe/Encoder, even if it's not required by the user.
This forces users to provide a polyfill even when not needed.
Even if just a stub is provided as a polyfill, like done in the wasm-audio-worklet example, it would still require the class TextDe/Encoder to be defined, which prevents support detection by downstream users.
This adjust calls to TextDe/Encoder to do nothing if it's not available.
I don't think this has any use-case outside audio worklets.
This doesn't prevent users from using an actual polyfill if desired.
Cc @lukaslihotzki.
Fixes #2367.

So I agree that TextDe/Encoder isn't needed outside of audio worklets, but your diff here removed the code from audio worklets where I do need it. Was that intentional? What is the best way to get this polyfilled inside of an Audio worklet?
https://github.com/rustwasm/wasm-bindgen/commit/78421dc53ccbe9dc4be437cd8b09961cb8159ddc#diff-07cf5528c3f9b4e22f2489de3616bd3ec5adbfeea002b3cad8d7f9d9cd5c68b0

It was intentional indeed, as its not required anymore to get audio worklets to run.
Using the usual Worklet.addModule() beforehand should perfectly suffice to inject any polyfill.
In general though I would recommend against using it in audio worklets, as any kind of memory allocation inside the audio worklet can cause stuttering among other issues, which is why the API was removed there to begin with. See https://github.com/WebAudio/web-audio-api/issues/2499#issuecomment-2002470074 for more information.


Default Up direction for move_and_slide not working in 2d top-down.

Godot version
3.5.3.stable.official [6c814135b]
System information
Windows 10 - Godot v3.5.3.stable.official
Issue description
Description:
While updating an old project that is a 2d top-down view from Godot 3.3.4 to the latest 3.x version, which is currently 3.5.3, I encountered a change in physics behaviour. In the previous version (3.3.4), I had two kinematic bodies - one moved by an animation player, and the second moved by player input using the _physics_process and the move_and_slide method.
In Godot 3.3.4, when these two objects collided, they exhibited some friction, but the object moved by player input continued in the same direction. However, in Godot 3.5.3, when a collision occurs, movement stops from player input. 👇

I updated the movement script so it calculates the  up_direction manually since the default value Vector2(0, 0) was not working as supposed it fixed the issue of snapping but the movement is completely different and seems off

this is my code to move the player:
func _physics_process(delta):
	if is_movable():
		movement_direction_vector = controller.output
		check_if_reached_destination()
		var speed_boost = 1.0 + (player.speed_boost/100.0)
		var velocity = movement_direction_vector * MOVEMENT_SPEED * speed_boost
		move_and_slide(velocity, up_direction)

to calculate up direction:
func _physics_process(delta):
	if is_movable():
		movement_direction_vector = controller.output
		check_if_reached_destination()
		var speed_boost = 1.0 + (player.speed_boost/100.0)
		var velocity = movement_direction_vector * MOVEMENT_SPEED * speed_boost

		var last_collision = get_last_slide_collision()
		if last_collision:
			$CollisionMarker.global_position = last_collision.position
			var up_direction_vector = last_collision.position.direction_to(global_position)
			if abs(up_direction_vector.x) < 0.3:
				up_direction_vector.x = 0
			else:
				up_direction_vector.x = 1 * sign(up_direction_vector.x)

			if abs(up_direction_vector.y) < 0.3:
				up_direction_vector.y = 0
			else:
				up_direction_vector.y = 1 * sign(up_direction_vector.y)
			up_direction = Vector2(up_direction_vector.x, 0).normalized() + Vector2(0, up_direction_vector.y).normalized()
			up_direction = up_direction * UP_DIRECTION_MULTIPLIER
			print(up_direction)
		if debug_text:
			get_node(debug_text).set_text(str(up_direction))

		move_and_slide(velocity, up_direction)

Steps to Reproduce:
Create a project in Godot 3.5.3.
Set up two kinematic bodies, one animated and one controlled by player input.
Allow them to collide.
Expected Behavior:
In collisions, the object moved by player input should continue in the same direction with some friction, similar to Godot 3.3.4 behaviour.
Actual Behavior:
In Godot 3.5.3, when collisions occur, the object moved by player input comes to a complete stop.
Steps to reproduce
Create a project in Godot 3.5.3.
Set up two kinematic bodies, one animated and one controlled by player input.
Allow them to collide.
Minimal reproduction project
Check code from description

Just tried this in Godot 4.1.3 and it has the same issue


Part 4: Create a new enum WeightUnit ; #187 - subtask.

This subtask is for the enhancement #187 .
create a new enum WeightUnit which can be used throughout your app to manage weight unit preferences, ensuring consistency and type safety. For instance, when you load the preference from the settings, you can convert the stored string value to a WeightUnit enum value, and vice versa.
Location: src/main/java/de/dennisguse/opentracks/settings
After making the necessary changes ,merge it with the branch [187-update-default-units-in-settings_Group_8_C2]

The above changes are committed and pushed to the mentioned branch.
Commit Link


Update about-digital-talent.md

Updated the page with content. Content has been fitted with syntax vs. html.

The BCDevExchange link also needs to be updated as it currently 404s.

@sidmclaughlin changes completed.


chcp_beforeInstall event for iOS

I've implemented and tested this for iOS. Event is triggered correctly, and I can use it for showing the splash screen as desired in #100.
For Android, maybe the easiest way to fix this is to trigger the event before the InstallationWorker runs?

Thanks!
As I said before - Android is implemented in a very similar way, as iOS. So yes, probably just need to dispatch the event either in UpdatesInstaller or InstallationWorker.

I've added my attempt of an Android implementation. This works well for my use case and doesn't seem to interfere with anything else, but please check it before merging :)
Since I don't know if the EventBus is thread safe, I added the event trigger outside of the InstallationWorker thread, right before the worker is executed. Feel free to move it wherever you see it fits.

Awesome, thanks! Seems to be fine. I will merge it in branch dev/v1.3.0, since it's a new feature.

Merged in branch dev/v1.3.0 with minor bugfix.


style(Calendar): highlight weekends

FX-2885
Description
BASE updated design of Calendar. We need to highlight weekends. Also, I found out that we were having some discrepancies between BASE and Picasso so also fixed these small issues.
How to test

Compare the storybook example with BASE design
Check new screenshots in Happo

Screenshots

Before.
After.

Development checks

[x] Add changeset according to guidelines (if needed)
Read CONTRIBUTING.md and Component API principles
[x] Make sure that additions and changes on design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
Annotate all props in component with documentation
Create examples for component
Ensure that deployed demo has expected results and good examples
Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[ ] Self reviewed
Covered with tests

Breaking change

codemod is created and showcased in the changeset
test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-anvil ping reviewers


[tests] add pytest for babs-check-setup

Currently added these tests for babs-check-setup: only when babs-init fails (as successful babs-init is tested in test_babs_init):

babs-init fails, by default BABS project gets removed --> babs-check-setup error: cannot find BABS project
wrong container dataset path in babs-init, also failed BABS project kept (--keep-if-failed)
wrong input dataset path in babs-init, also failed BABS project kept (--keep-if-failed)


do files ever expire and get deleted?

I am looking for a site where there is "never expire" and files are NOT DELETED.
Is there an expire of files?
Thankyou.

they don't.

Oh great thankyou very much !!
Exactly what I was hoping for!
Would be helpful if you stated no expire or deletion on the page
https://maxfile.ro/
under
Max upload size is 50MiB!
Thankyou.

Pomf is not related to maxfile. We don't know what they do, they're using the pomf source but aren't affilated with pomf.

Then what is your pomf url and I will check it out because there is no expire or deletion.
Thankyou

Pomf.se was the original "Pomf", it got shut down ~3 weeks ago due to money issues.

Pomf itself is gone, maxfile runs the Pomf software

So confusing. so Pomf itself is gone, maxfile runs the Pomf software
but no support or contact for maxfile info if files get expired or deleted?

Precisely.

@gotquestions as said before, Maxfile and others are not associated with Pomf.se (me), how others chose to modify the code is not something I can control.

I doubt maxfile will delete or expire files though, since it runs this software

Yes I understand nokonoko thankyou.
Yes I doubt it too NuckChorris but need to be sure. Thanks for adding input NuckChorris and avail.
Maybe ShareX will know because they are the ones that led me to the site.

ShareX is not affiliated in ANY WAY to any upload service. They just
use APIs of common ones and put them inside ShareX, but pretty much
nothing else. Do not ask them, they'll probably tell you to go ask
directly the owner of maxfile.
Il 05/07/2015 00:30, gotquestions ha scritto:

Yes I understand nokonoko thankyou.
Yes I doubt it too NuckChorris but need to be sure. Thanks for adding
input NuckChorris and avail.
Maybe ShareX will know because they are the ones that led me to the site.
—
Reply to this email directly or view it on GitHub
https://github.com/nokonoko/Pomf/issues/37#issuecomment-118560618.

No file expiration on maxfile.
I own it

Oh wow exactly what I need. NO FILE EXPIRATION on maxfile thankyou very much alin1337 !
Would be helpful to state that info somewhere under Max upload size is 50MiB! to be certain.
And I guess I have to trust that you alin1337 are actually the owner of the maxfile site as there is no contact link on there to prove that.
Thankyou for response !


Special characters in AWS_SECRET_ACCESS_KEY lead to "request signature does not match"  error

What is the problem?
I was using this as an environment variable:
AWS_SECRET_ACCESS_KEY=...9ZpA0...p...Oagz/gCn/5DM+IqB+XOoI6p....
(This is obfuscated by replacing some characters with ...)
Do you see the + and / in that?
It let to this error:
request signature we calculated does not match the signature you provided
EASY FIX:
When I generated a new secret key with just letters and numbers, it worked fine.
so --
Clearly there is some encoding issue.
Note -- this secret key with + and / symbols worked without issue in Python, JS, Ruby .....
Version
aws-config v0.2.0, aws-sdk-sqs v0.2.0
Platform
ubuntu 18
AWS Services
No response
Description
No response
Logs
Error { code: "SignatureDoesNotMatch", message: "The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.

we've definitely tested keys with special characters. Is it possible that you're accidentally omitting the session token?

it would also be helpful if you could share the source of the secret key to aid in reproducing the issue

I don't want to share the secret key because it is, uh, "secret".
Actually we don't use session token and never have in other languages.
I am going to close this issue now, if someone else comes here, and finds the same thing, they can reopen, but if not, and nobody else reports this issue, let's assume I did something else wrong on my end. Thanks.

Apologies, I wasn't asking for your secret key but rather source (eg. STS, downloaded via the console, IMDS, etc.)

Oh, it's from an environment variable. I can print it out like this and it looks fine.
let aws_secret_key = env::var("AWS_SECRET_ACCESS_KEY").expect("AWS_SECRET_ACCESS_KEY not found in env");
println!("aws_secret_key: {:#?}", aws_secret_key);


Does not compile on rustc 1.18.0-nightly (50c186419 2017-04-06)

   Compiling aster v0.41.0 (file:///home/anthony/git/aster)
error[E0560]: struct `syntax::ast::Attribute` has no field named `value`
  --> src/attr.rs:59:13
   |
59 |             value: item,
   |             ^^^^^^ field does not exist - did you mean `path`?

error[E0308]: mismatched types
   --> src/mac.rs:110:18
    |
110 |             tts: self.tokens,
    |                  ^^^^^^^^^^^ expected struct `syntax::tokenstream::ThinTokenStream`, found struct `std::vec::Vec`
    |
    = note: expected type `syntax::tokenstream::ThinTokenStream`
               found type `std::vec::Vec<syntax::tokenstream::TokenTree>`
    = help: here are some functions which might fulfill your needs:
            - .remove(...)
            - .swap_remove(...)

error: no method named `bt_push` found for type `syntax::ext::base::ExtCtxt<'_>` in the current scope
   --> src/mac.rs:141:8
    |
141 |     cx.bt_push(info);
    |        ^^^^^^^

error[E0063]: missing field `span` in initializer of `syntax::ast::PathSegment`
   --> src/path.rs:303:30
    |
303 |         self.callback.invoke(ast::PathSegment {
    |                              ^^^^^^^^^^^^^^^^ missing `span`

error[E0063]: missing field `span` in initializer of `syntax::ast::PathSegment`
   --> src/path.rs:324:30
    |
324 |         self.callback.invoke(ast::PathSegment {
    |                              ^^^^^^^^^^^^^^^^ missing `span`

error: aborting due to 5 previous errors

error: Could not compile `aster`.

To learn more, run the command again with --verbose.

The syntex / aster / quasi stack is not being maintained at the moment - see https://github.com/serde-rs/syntex/issues/114. Please use your own forked version, or switch to a different library.


Inline error removal is not discoverable

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
In C++, when Zed finds an error, clicking the error will put it into an inline format. If you then fix the bug, the inline error remains and cannot be removed (as far I could manage).

(there's another inline error in the second image behind the pop-up, which is my prior attempt at recreating the bug)
Expected behavior
Either fixing the error would cause the inline error to dissapear or there would be a clear close button to dismiss it.
Environment
Zed 0.60.4 – /Applications/Zed.app
macOS 12.6
architecture arm64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue
Zed.log

Use the escape key to remove it!
And yeah, this is the second time we've gotten this bug report, we should make this more discoverable somehow. cc: @iamnbutler

I've been curious to know if more people use the inline errors or the errors in the modal windows.  We currently have 3 different ways to view errors - the aforementioned ways and then project diagnostics.  Is there utility in having both a modal error and inline error?

FWIW, I think this could live behind a setting key. I personally would love for these to disappear once resolved and not require a long stretch to esc.

Use the escape key to remove it!
And yeah, this is the second time we've gotten this bug report, we should make this more discoverable somehow. cc: @iamnbutler

Yeah IMO as others are saying this experience seems broken. It should go away when you have resolved the error. It feels broken. Is there an argument for keeping it the way it is?

Is there an argument for keeping it the way it is?

It does cause a bit of visual jumping around which might feel unpleasant, especially with regards to scroll position or some such. That said, I don't think the current experience is much better. Probably good to test out how it feels in person, I do like the inline errors....

I love the inline errors ! I just think having it user configurable would be best.
persist delay instant

I regularly ran into this and finally decided to see if it was reported. Yeah, I would never have guessed that Esc would remove it. And +1 to removing diagnostic messages which no longer apply i.e. were fixed.

@JosephTLyons 👋 I think I've seen the diagnostics label applied to other diagnostics-related issues. Should we apply that here too? 💭

@JosephTLyons 👋 I think I've seen the diagnostics label applied to other diagnostics-related issues. Should we apply that here too? 💭

Thanks @izuzak, I added the label.  Also, yeah, it is an issue that this is not discoverable.  We need to figure out how to surface a way to dismiss these, and possibly auto-remove them when they are no longer valid.


Fix sample application contents and remove Asgardeo logo

Purpose

Change content of sample applications
Resolves issue1, issue2, etc.

Approach

Following changes were done

Remove OIDC heading
Landing page description
Change to signature section label
Remove logo

Please close this in favor of #14


Uninstall plugins

What is the dein way to remove an unwanted plugin?

Remove the dein#add() line

call dein#recache_runtimepath()

call map(dein#check_clean(), "delete(v:val, 'rf')")

Thank you.

I don't understand your problem.
dein#check_clean() just removes the invalid plugins.

 However the Shougo directory was empty. Note my histfile  contained no dodgy deletes.
What does the map and the delete var do?

dein#check_clean() just returns the unneeded plugins path.
So, it can be removed by call map(dein#check_clean(), "delete(v:val, 'rf')").


Revert "Revert "[frontend] Remove Complex Regex for MLIR Parsing (#4924)""

Closes #2653
This reverts commit ecc9bd4abbdd15666c05f2ed22b9a3d2816691b5.
The issue looks like:
loc("/tmp/pytest-of-runner/pytest-0/popen-gw0/test_convert2d_dst_layout8_int21/test_convert2d.ttgir":4:30): error: #"triton_intel_gpu"<"dpas<{repeatCount=8, systolicDepth=8, executionSize = 8, opsPerChan = 1, threadsPerWarp = 32, warpsPerCTA=[4, 1], repCluster=[1, 1]}>"> : 'none' attribute created with unregistered dialect. If this is intended, please call allowUnregisteredDialects() on the MLIRContext, or use -allow-unregistered-dialect with the MLIR opt tool used

Can this change be upstreamed?

I think there is a chance.  I brought it to a form more similar to what I am trying to upstream.
@etiotto @whitneywhtsang could we merge it?

@anmyachev what is the upstream PR for this changes ?


Disable WebJobs on Function apps

There is little reason to use them in a Function app, and they add difficulties in term of metering usage.

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


fix link

[Client API grid context](clientapi-grid-context.md

Thanks for creating the PR to fix this issue. This issue is resolved internally. So closing the PR without merging it.