Regarding terminal

Type: Feature Request
I am not able to open wsl terminal in vscode. Some days back I used to open wsl terminal in vscode itself, but not now. I have tried to figure it out but not able to solve it. Please give me instructions to open wsl terminal into vscode.
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.19045
Modes:

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


get_historical_klines limit does not work

Hi, first of all thanks for the great package. I'm trying to fetch a fixed number of candles at different timeframes, i set a start date and a limit of say 1000. But it always gets me data up to the present time, for instance, today april 3rd,
ticker = 'BTCUSDT'
interval=Client.KLINE_INTERVAL_4HOUR
client = Client()
data = client.get_historical_klines(ticker, interval, start_str='1 Jan, 2022', limit=1000)
returns 2746 candles.
I could somewhat fix the issue by changing the code of client.py, line 999 from:
if len(temp_data) < limit:
to
if len(temp_data) == limit:
Now i can set a limit up to 1000 and have exactly that number of candles returned, but limit=1001 in the above will return again 2746 candles.
Any idea how to fix client.py so as to have the expected behavior when setting a limit. I suppose my pseudofix will not hold water in the long run. Thank you very much.

duplicate #1250
I have a fix there. But cannot spare time to submit a sound patch or pull request.

Thank you very much. I think i searched to avoid potential duplicate. Sorry i did not do that well enough.


[python] simplify handling of fixed length char arrays [behavior change]

Sorry - code formatting issue


fix the order of segments at the same level

Please answer these questions before submitting pull request
for the #3844

Does this sort work?

We have multiple implementation of storage. If you order at database side, you need to change all. H2 and Mysql.

@wu-sheng
Does this mean that I need to make the same changes on H2 and MySQL?

Does this mean that I need to make the same changes on H2 and MySQL?

Yes, if you have checked this change makes the UI right, can you confirm?

Why close?


Reduce duplicate code in ServiceBean and ReferenceBean

I find that there are much duplicate code in the method afterPropertiesSet of ServiceBean and ReferenceBean. Can we move them to their common super class ?

feel free to submit a PR to address this, I will review.

feel free to submit a PR to address this, I will review.

OK

#4709

The configuration has been refactored.


ci: remove tests from schedule

Signed-off-by: Long Dai<EMAIL_ADDRESS>Description
It is unnecessary for tests run as schedule since it would be tests when pull request.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

Running e2e tests on a schedule helps us gather data about test flakiness over time. If there aren't may outstanding PRs, we may miss failures that are 1 in 10 or more.

Outstanding PRs mean not merged, they do no harm on project, if a PR merged, which means e2e pass, so I am confused about why we would miss failures.


Check if image file is broken on upload

When uploading an image form should check for file integrity, this is not happening.
Image gallery raises 500 trying to access to corrupted files and it show absolutely nothing if this happens, it should, at least, raise proper error message to the user.
On Wagtail v1.0b2

Related bug: https://github.com/torchbox/wagtail/issues/1326
Only the header contents of an image get validated on upload at the moment. In order to validate the entire image, we would have to load the whole thing and catch any IOErrors that get thrown.
This is something that would probably be best to implement in Willow (https://github.com/torchbox/Willow)

Also related: #1262

I had this problem also with the version 1.9.5

This problem still occurs in wagtail 1.5.3 and 1.6.2.
Is there any way to fix this issue?

@dpratter @salsotto there may be a better place to put this, but I added these lines to my settings/base.py as a quick fix and it appears to fix the issue (for truncated files at least, not sure about other types of corrupt image files).
from PIL import ImageFile
ImageFile.LOAD_TRUNCATED_IMAGES = True

Haven't tested this in my staging/production environments, but will report back if anything goes wrong


Confd failing to read etcd key that definitely exists

I have a confd template that throws the key does not exist error but the key does exist.
APP_DEBUG={{getv "/myapp/APP_DEBUG"}}

The .toml config file is just a basic src and dest:
[template]
src = ".env.tmpl"
dest = "/opt/myapp/.env"

I can access the key using etcdctl with no problems:
root@6928f66b3d73:/opt/myapp# etcdctl -endpoints http://etcd.mysite.net:4001 get /company/config/dev/myapp/APP_DEBUG
true

Confd tells me the key doesn't exist?
root@6928f66b3d73:/opt/myapp# confd -onetime -node http://etcd.mysite.net:4001 -prefix /company/config/dev -log-level debug
2017-01-17T12:20:16Z 6928f66b3d73 confd[49]: INFO Backend set to etcd
2017-01-17T12:20:16Z 6928f66b3d73 confd[49]: INFO Starting confd
2017-01-17T12:20:16Z 6928f66b3d73 confd[49]: INFO Backend nodes set to http://etcd.mysite.net:4001
2017-01-17T12:20:16Z 6928f66b3d73 confd[49]: DEBUG Loading template resources from confdir /etc/confd
2017-01-17T12:20:16Z 6928f66b3d73 confd[49]: DEBUG Loading template resource from /etc/confd/conf.d/myapp.toml
2017-01-17T12:20:16Z 6928f66b3d73 confd[49]: DEBUG Retrieving keys from store
2017-01-17T12:20:16Z 6928f66b3d73 confd[49]: DEBUG Key prefix set to /company/config/dev
2017-01-17T12:20:16Z 6928f66b3d73 confd[49]: DEBUG Using source template /etc/confd/templates/.env.tmpl
2017-01-17T12:20:16Z 6928f66b3d73 confd[49]: DEBUG Compiling source template /etc/confd/templates/.env.tmpl
2017-01-17T12:20:16Z 6928f66b3d73 confd[49]: ERROR template: .env.tmpl:1:12: executing ".env.tmpl" at <getv "/myapp/APP_DEBUG...>: error calling getv: key does not exist

Confd version:
root@6928f66b3d73:/opt/myapp# confd -version
confd 0.11.0

My bad! This was caused by a missing section in the .toml file:
keys = [
  "/myapp"
]

Works as expected now!


⚠ SpeakUpConference.com has degraded performance

In 19383ce, SpeakUpConference.com (https://www.speakupconference.com) experienced degraded performance:

HTTP code: 200
Response time: 9016 ms

Resolved: SpeakUpConference.com performance has improved in 1a395f7 after 19 minutes.


Enable flaw creation from NVD collector in BZ

This PR enables the creation of flaws from NVD collector in BZ.
Also, it fixes the following:

NVD collector created references that may be invalid and could not be stored in FlawReference
BZ code ignored the SOURCE reference and failed to write a new flaw

Closes OSIDB-2201

@osoukup Yes, I tested it. You can check the BZ stage; new flaws look like CVE-2023-7244 placeholder only, see description. I just updated their title to sth more clean. Please check.

@osoukup Yes, I tested it. You can check the BZ stage; new flaws look like CVE-2023-7244 placeholder only, see description. I just updated title in code to sth more clean. Please check.

There should be then some integration test to ensure that we do not break the functionality in the future.

@osoukup I updated the whole PR to fix the known issues and nothing else. The rest will be handled in the future.


Adding more recommended text editors to the TMPE wiki

Describe your idea
I came across alot of good text editors that maintains plain text UTF-8 format.
These 2 are some that I
Notepad++
and Jext  https://sourceforge.net/projects/jext/
https://web.archive.org/web/20100113234025/http://www.jext.org/

Hi, thanks for the suggestions. I've added Notepad++ and a few others.
Jext is obviously abandonware, so I've not added that.


feat(eventing): disable eventing for release 2.3

Since eventing feature is pushed for next release, disabling this feature for 2.3 release.
cc @avishnu

Let's maybe remove this from 2.3?

bors merge


Fixed goroutine leak, made tests deterministic

This is based on howbazaar's changes with 4a6f656c's comments here: https://github.com/natefinch/lumberjack/pull/100/files
I changed a few things, too.

Is this based on https://github.com/natefinch/lumberjack/pull/100 ?

Is this based on natefinch#100 ?

Yep.  Added that to the description, but you were too fast for me.

@TimKingtonFC this good to land?

Yes, but I haven't figured out how to run the linux tests.


RegExp example

in .htmllint:
{
  "class-style": "/[a-z]+/g"
}

in terminal:
[htmllint error in filePath.html ] TypeError: Cannot read property 'test' of undefined

please tell me where I go wrong?

The docs state you can set An arbitrary Javascript RegExp object, but I'm not sure how else you would format this as json in the .htmllintrc file if the format mentioned by @nicothin does not work?

@nicothin Update: this issue seems to have been worked on since the 0.6.0 tag release. Although another version has not yet been tagged (as of 3rd Feb 2017). If you are installing htmllint via NPM or using via htmllint-cli, then you will not be able to pass a regular expression in `.htmllintrc' until a new version is tagged (and htmllint-cli updated also).

@mickeyhead7 i have "htmllint-cli": "0.0.6" via NPM

@nicothin Yep, 0.6.0 has a fault in lib/knife/get_format_test.js that can't accept a RegExp from the class-stylestring in your.htmllintrc` file. This has been removed/fixed/updated in the latest commit, but... that hasn't been tagged for release yet, so NPM and the CLI doesn't pull this in.
I'm having the same issue and haven't managed to test the latest version yet, so I am stuck as well :)

I was aware of the JSON issue, but hadn't taken the time to figure out how RegExps should be specified by strings. Turns out it's pretty simple to just use Javascript's syntax (/, stuff, /, some combination of gim). I've excluded the u and y options because I'm pretty sure they aren't useful. g isn't either, but a lot of people use it for every regular expression, as this post shows.
I have some things I want to sort out before releasing 1.0.0, but I'll try to get it on npm this weekend.


chore: use encrypted tokens for api keys

TEST

Instead of saving the plain access tokens in the .travis.yml the tokens are now encrypted.

Closing & and leaving the tokens are they are for now.
The Travis JWT addon is only allowing the tokens to be used from trusted addons and therefore wouldn't help us encrypting the tokens.

https://github.com/travis-ci/travis-ci/issues/7223


Query with column_formats set on FixedString columns should convert to pandas.StringDtype

Describe the bug
When a table has FixedString type columns, query_df method can use read formats parameter to convert it to string in the returned dataframe. However, unlike other returned String columns which are converted to Pandas StringDType, FixedString columns are converted to object dtype. This makes the returned string columns have inconsistent types and behaviors.
Reference: https://pandas.pydata.org/docs/user_guide/text.html
Steps to reproduce

Create a test table:

CREATE TABLE test_string
(
    `id` UInt32,
    `name` String,
    `sex` FixedString(1),
    `city` String
)
ENGINE = Memory

Insert test values

INSERT INTO test_string VALUES (1, 'Jacob', 'M', 'Chicago'), (2, 'Annie', 'F', 'Los Angeles');

Query from client and check dtypes:

df = client.query_df("SELECT * FROM test_string", column_formats={"sex": 'string'})

In [8]: df.info()
<class 'pandas.core.frame.DataFrame'>
RangeIndex: 2 entries, 0 to 1
Data columns (total 4 columns):
 #   Column  Non-Null Count  Dtype
---  ------  --------------  -----
 0   id      2 non-null      uint32
 1   name    2 non-null      string
 2   sex     2 non-null      object
 3   city    2 non-null      string
dtypes: object(1), string(2), uint32(1)
memory usage: 188.0+ bytes

In [10]: df.name.dtype
Out[10]: string[python]

In [11]: df.sex.dtype
Out[11]: dtype('O')

In [12]: df.city.dtype
Out[12]: string[python]

Expected behaviour
As shown above, the returned String columns name and city have Pandas StringDType type, while the FixedString column sex is converted to object dtype. It's expected the sex column is also converted to Pandas StringDType.
Configuration
Environment

clickhouse-connect version: 0.7.11
Python version: 3.12.3
Operating system: Linux 6.8.11-1-MANJARO

ClickHouse server

ClickHouse Server version: 24.4 official docker image

Have you tried setting the read format for the column to string?  https://clickhouse.com/docs/en/integrations/python#read-formats
I'm not sure that will work without a code change but it's worth testing.

Have you tried setting the read format for the column to string?

The simple example in the description uses read formats with column_formats={"sex": 'string'} parameter. If you mean to set it globally like
from clickhouse_connect.datatypes.format import set_read_format

set_read_format('FixedString', 'string')

# client = get_client()
df = client.query_df("select * from test_string")

this gives the same object type for the FixedString column.

Ah, I missed that, the column level should be good enough.  I'll try to push a fix in the new day or two.

I actually can't reproduce this.  What Pandas version are you using?

This should be fixed in 0.7.12 if you want to validate.  I did manage to recreate the issue (I think), although pandas was reporting weird data types in my tests.


Add a Newtype instance to StatusCode

Makes it easier for users of the library to access the underlying
statuscode with unwrap.

Thanks!


feat(sink): do compact per barrier with the sink pk in the sink executor

This issue propose to always do compaction in the sink executor for those sink with the key/primary key. because

We have added this behavior when the  https://github.com/risingwavelabs/risingwave/pull/12458. To make the behavior consistent.
some of users felt weird when RW sink unnecessary intermediate result. https://github.com/risingwavelabs/risingwave/issues/13025

cons
After that, the freshness will be bound on the barrier interval. user need to config the barrier interval to achieve better freshness.
FORCE APPEND ONLY SINK
thanks @xiangjinwu  https://github.com/risingwavelabs/risingwave/issues/9443#issuecomment-1758910077. The primary key defined on MQ is actually the partition key. MQ can maintain the order of events with the same key.
for the normal append only sink, RW will never retract the records and records can be reordered anyway based on the SQL semantics. But we have a "force append only" semantic widely used to convert a retractable stream to append only stream by only maintaining the insert operation. Under this definition. The order of events in the specified key matters.
So the common per barrier compact will also be done on the force append only sink.

The motivations didn't fully convince me.

some of users felt weird when RW sink unnecessary intermediate result.

For these cases, I think

If the intermediate results come from RisingWave, we should try to eliminate this in executors.
If the intermediate results come from user's upstream, it's okay to output them.

"Compact per barrier" was proposed to solve the "sink key & stream key mismatch" problem. Here it sounds like an abuse of it.

If the intermediate results come from RisingWave, we should try to eliminate this in executors.

Some efficient computation of the executors results that such as projectSet

Is it possible to do the compaction on the fly during project and projectset? I imagine that only the adjacent items with the same key need to be checked and compacted. Will the overhead be significant?

Is it possible to do the compaction on the fly during project and projectset? I imagine that only the adjacent items with the same key need to be checked and compacted. Will the overhead be significant?

Yes, we can do that in some place to optimize https://github.com/risingwavelabs/risingwave/issues/13409
But the question here is that we have in some cases, it is difficult to maintain the update delete and update insert be adjacent.
e.g. 1: update join key/ over window partition key, the old value and new value could be shuffled into different partitions.
e.g. 2: vectorized expand/projectset. https://github.com/risingwavelabs/risingwave/issues/4894#issuecomment-1228521280

If the intermediate results come from RisingWave, we should try to eliminate this in executors.

Some efficient computation of the executors results that such as projectSet

Due to our previous discussion, in my mind, we finally decided to choose the Option 2 from these 2 options below:

Completely remove UpdateDelete & UpdateInsert and never rely on them any more
Keep UpdateDelete & UpdateInsert and rely on them to identify Update as much as possible, although it's not 100% guaranteed but in the best effort way

Today I am just trying to follow the option 2.
While for these exceptions you mentioned:

e.g. 1: update join key/ over window partition key, the old value and new value could be shuffled into different partitions.
e.g. 2: vectorized expand/projectset. https://github.com/risingwavelabs/risingwave/issues/4894#issuecomment-1228521280

1 is inevitable. 2 is a trade-off for us.

I understand that you want to solve an issue completely. The problem is, IMO, the proposed solution isn't free, and the price seems to be even higher than the benefit.


Custom endpoint in Azure IoT is restricted to 10 max

We have a need to add more than 10 custom endpoint in message routing for IoT hub. Can anyone help me in getting to the right contact to get this done ? There is a linked issue as well for this : https://github.com/MicrosoftDocs/azure-docs/issues/32624 .

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

ID: ec6fc6a5-9bf6-889e-075d-b5b009e67d1f
Version Independent ID: f3d6fa56-a494-fec8-50e3-f8682c90ac42
Content: Understand Azure IoT Hub quotas and throttling
Content Source: articles/iot-hub/iot-hub-devguide-quotas-throttling.md
Service: iot-hub
GitHub Login: @robinsh
Microsoft Alias: robinsh

Thanks for the Comment. We are actively investigating and will get back to you soon.

@ash2017 Could you please look into this issue?

@nehsin please investigate.

@nehsin Assigning this issue to you so that you can close once there has been any progress.

Hello Guys, Never heard back from you on this.  Can you make an exception for my subscriptions to allow more than 10 custom endpoints on IOT hub? This is a must requirement for our project so let me know whom to contact to get is done? Thanks.

To make this request, put in a support ticket.
From: amitabh-github<EMAIL_ADDRESS>Sent: Wednesday, August 12, 2020 10:04 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Robin Shahan<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Custom endpoint in Azure IoT is restricted to 10 max (#59846)
Hello Guys, Never heard back from you on this. Can you make an exception for my subscriptions to allow more than 10 custom endpoints on IOT hub? This is a must requirement for our project so let me know whom to contact to get is done? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F59846%23issuecomment-672996819&data=02|01|Robin.Shahan%40microsoft.com|819635f1bc97403e6b3d08d83ee1a4a6|72f988bf86f141af91ab2d7cd011db47|1|0|637328486131376812&sdata=Crm0ggqzimQh24lfqmoM%2FjN7fOS7WHUcRnNpAJEvWGo%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADK7Q2BPX46YUADJF73BPJDSALDOHANCNFSM4PKSTNBQ&data=02|01|Robin.Shahan%40microsoft.com|819635f1bc97403e6b3d08d83ee1a4a6|72f988bf86f141af91ab2d7cd011db47|1|0|637328486131386806&sdata=UQc0VkVDzuRKVsQl4RvKeSXpJ4BCARU6QI9zCOBb2JI%3D&reserved=0.

Hey @amitabh-github - Can you provide details on your project, subscription details and why you need to extend that beyond 10 endpoints?

Hello, We have opened a support incident for this request. The subscription details are provided in the Incident request. Kindly check Support request number<PHONE_NUMBER>0096.

#reassign v-gpettibone

Amitabh-github opened a support issue to get more than 10 endpoints in Sep 2020. This is not a documentation issue. Closing the issue.

#please-close


Integrate calendar on site (PoC with iCal)

Final Update: December 8, 2023
Calendar is a potential Project Portal feature we have been exploring. Specifically, trying to implement the fullcalendar library as seen here https://fullcalendar.io/docs/icalendar.
Tested with 2 approaches

iCalendar plugin

<FullCalendar
  plugins={[dayGridPlugin, iCalendarPlugin]}
  initialView="dayGridMonth"
  events={
    {
      url: '{path_to_ics_file}',
      format: 'ics'
    }
  }
/>

Google calendar through google API

 <FullCalendar
  plugins={[dayGridPlugin, googleCalendarPlugin]}
  initialView="dayGridMonth"
  eventSources={
    {
      googleCalendarApiKey: '{generated_api_key}',
      googleCalendarId: '{google_email}'
    }
  }
/>

The iCalendar approach does not work, for some unresolved reason. The Google calendar approach works but obviously restricts the compatibility of email types for a potential calendar feature.
Either way, this approach using the FullCalendar library represents only a basic feature of displaying calendar events based on a specified calendar source. It wouldn't provide us the power to manipulate these calendar events obtained from an external source.
If we want to be able to implement stretch goals of showing specific events from the calendar on Project Detail pages or include calendar updates in the "New updates" digest, a more complex calendar system, perhaps one built in-house will be required.

Display the events from a publicly shared iCalendar/.ics calendar
Allow users access to that calendar
Stretch goal: Show specific events from the calendar in the Project Detail page
Stretch goal: Include calendar updates in the “New updates” digest

https://fullcalendar.io/docs/icalendar

trying out FullCalendar package, seems to be the most popular/recommended library for calendar
Tried with iCalendar plugin provided by fullcalendar packag, all you need is to provide the ".ics" link for the package.
Attempted with my google calendar .ics path, also tried finding .ics link for Apple iCal but cannot find.
Could not get it to work with google calendar .ics path, tried making my calendar public, also tried "secret" .ics url provided by google as well.

https://fullcalendar.io/docs/google-calendar

trying this next, implementing google calendar through google api
assumption that google calendar will be the most popular source of iCalendar anyways, could be an alternative

May need to write own ical parser, there are many examples online, but it seems like the logic is easy enough to make our own, and make sure it does what we need it to. Ex. https://github.com/jens-maus/node-ical

We need to trigger the curl to get data from the .ics file and have it formatted in a way that makes it easy for us to query for potential "project detail" details.
Calendar data will be separate from cms data.
It will have to be formatted into a file, maybe json like the rest of our data, in order for our email-service to query these files and detect calendar updates for potential "New Updates" feature
we will need some way of standardizing how we link these calendar events to the actual projects. Such as using the slug. Hard to enforce, and. could be a weak point in this implementation as we will be relying on user-generated slug to make the relationship between calendar event and project.
we can feed the .ics file in its own format to the FullCalendar prop.

 <FullCalendar
          plugins={[dayGridPlugin, googleCalendarPlugin]}
          initialView="dayGridMonth"
          eventSources={
            {
              googleCalendarApiKey: 'AIzaSyDb89J-XhloI5FEnjuoPoCorCYMPSxZc00',
              googleCalendarId<EMAIL_ADDRESS>            }
          }
        />

Google calendar "sync token" https://developers.google.com/calendar/api/guides/sync
Could be interesting, method to efficiently keep local calendar data up-to-date with changes happening on remote google calendar.
First, it does initial full sync, to make sure local calendar matches everything on the remote server. You collect all info from the server and store.. perhaps in json files?
After collecting data, you get special token from server (sync token)
If you want to find out what's new or has changed since last sync, send sync token to server, and it sends you all the new and changed stuff since last sync.

https://developers.google.com/calendar/api/guides/push
has built-in push notification system as well to send notifications when changes are made to the calendar

@thepolicylab-projectportals/renci
Here is an in-progress feature that we simply did research on. Passing on to you all!


Presence bug - Raspberry Pi

Hello @neuoy ,
I made a OneWire Slave with your Code and added some code for measurements. It worked very well over a long time(i think endless) with a Arduino as OneWire Master.
In my Project is a RaspberryPi as OneWire Master and that works too (Why not?).  With the original OneWire Slaves, that does not happen. Without my code added to your "OneWireArduinoSlave" the Problem is the same. Only with a RaspberryPi as Master!
I tried to trigger the error, but I did not succeed. When the RaspberryPi only scans the bus for slaves, it worked without Problems for days (I tested it for ~30 hours).
When the raspberry sent the slave a request (measure, read, write), enters the bug spontaneously. Sometimes after one request and sometimes after 100 requests. When i restart the slave it's working again for some time.
The bug looks like a Presence fail, because the Master pulled down the bus and release them after 480µS - 850µS. After the rising edge and 30-35µS the Slave pulled down the Bus and hold them for 296µS low. Then the magic begin:

If there was no requests on the Bus, the Slave release the Bus aufter 296µS. All ok.
If there was a request () on the Bus previously, the Slave pulled down the bus to show presence and after 296µS the Bus is still low, because the slave hold them low infinitely long. After a Hardware Reset at the Slave, it´s working again until next Presence fail.

My first Idea was the long reset pulse from master, but with various reset pulses from an arduino it worked too. The ArduinoSlave does not freeze when the bug appear, because my extra code run continues without problems when the fail happened.
Write me if I can do something for you to find the Issue (measurements, code changes... I think i can do every measurements what you want)! I will add later a picture of the bug.
greeting goial

Hi goial,
Thanks for your bug report.
Since you say your code is still running, this means the arduino did not crash or enter an infinite loop. The only thing I can imagine is that it is stuck doing nothing, with no timer or pin interrupt registered. How this can happen is unclear to me though. Since it's difficult to trace the sequence of events due to timing constraints (logging to the serial port is too slow), and even harder since the bug seems difficult to reproduce, I don't really know what the next move can be.
I don't have a RaspberryPi at hand to try to reproduce the issue. But I do have two arduinos (or is it "two arduini" ?) so I could try to reproduce the issue by tweaking a master library to have a longer reset (if I understand correctly you are suspecting that's the difference that make it fail with a Pi). But I really can't make any promise as to when that would be (like, maybe tonight, maybe in two years...).
Also, after reading my code again, I think I should make some charts about the various interrupt and timer sequences because currently it's hard to follow... Maybe the bug would be easier to find by reviewing the code carefully, than by trying to reproduce it, I don't know.
FYI, I'm using a DS9490R master adapter here (almost the cost of a RaspberryPi! but I bought it before the Pi even existed). And I never observed my arduino stuck pulling low, even after almost one year of continuous service (it's managing my boiler installation for house heating). Though, now you mention it, I did have to unplug/replug my master adapter on two occasions, for unknown reasons, maybe that was the same issue, hard to say. If that happens again I'll check the bus state before resetting it all.
Oh and one last thought : can you modify the Pi master library to change the reset duration? That could work around the issue for you, and also confirm the bug is triggered by a particular reset duration...

Hi goial,
Commit https://github.com/neuoy/OneWireArduinoSlave/commit/a108089f02cabd236a53bbbccb96b730fe0f7b50 might fix your issue.
I'm closing this issue now, but if you have the opportunity to test again (with the fix), and see that it doesn't work, let me know so I reopen the issue.


Consider describing advantages over pylint support in python extension

I'm currently using pylint with the python extension and am wondering if I should switch to this extension. What benefits does it give? Is it performance?

Direct benefits are:

It's much faster (as long as you don't specify the path to Pylint, else it's the same)
Pylint is included (so you don't have to install it)
You have more control of the severity of error codes

Indirectly:

We can update this w/o updating the entire Python extension
It's easier to contribute to since nearly all the code for this extension is written in Python

FYI we will be removing Pylint support in the Python extension once we are happy with this extension.


WIP: more specific userland names for node clusters

Trello: Update clusterNode names to better indicate contents
This looks to improve the labelling  for userland information in clusterNodes - we can extract better information from the AggregateNode Frames when the initial label is too generic - and pass that up to the ClusterNode.
From the example in the above Trello Issue:
Before:

After:

Some other generic labelling may be more valuable in places where the type is displayed (e.g. nextTick - here is an example where the more specific information may or may not be of value. Should we refine these rules?

I think this is great!

argh -  failing tests. of course - will look at that.  - meanwhile - here are some of my notes from my investigations here:

I have some of my own code which I’m using as example code for clinic bubbleprof - where I’m trying to get more meaningful names to display on the cluster nodes layout.
I’m seeing a lot of generic, js-native or nodejs-native labels - where I would expect to see my own userland named functions.
digging deeper…

I have identified blocks of code such as this module - where the aggregate node can only be identified as module.exports:
This makes sense - but it would be better to expose this in the bubbleprof interface so I can improve naming in my modules as  a function

module.exports = function (fastify, opts, next) {
  fastify.get(‘/‘, (req, reply) => {
    reply.send({ hello: ‘world’ })
  })

  // register routes
  fastify.register(require(‘./api’), { prefix: ‘/api’ })
  next()
}

in another example - I do have a named function - but it’s ignored in the naming of the cluster - and  being identified by its type - in this case a promise

  async getDocumentList (query) {
    const collection = await db.collection(DOCUMENTS_COLLECTION_NAME)
    const result = await collection.find(query).toArray()
    return result
  }

and here I have defined as function as the handler - but not named it - so the clusterNode just uses this handler name - without any context.

  fastify.route({
    method: 'GET',
    url: '/',
    handler: async function (req, reply) {
      try {
        const docs = await fastify.docsDb.getDocumentList({})
        return reply.send(docs)
      } catch (error) {
        return reply.send(error)
      }
    }
  })

Most profiles I've looked at so far give really good results 👍 Will continue testing.
One small issue: Windows-style paths. From 11332.clinic-bubbleprof in node-clinic-samples for example:

If you're using the system path separator for this bare in mind that it's possible to collect the data in one environment and run the analysis generating the HTML in another (e.g.  --collect-only on Windows, --visualize-only on posix).


Laravel 9.x Shift

This pull request includes the changes for upgrading to Laravel 9.x. Feel free to commit any additional changes to the shift-93136 branch.
Before merging, you need to:

Checkout the shift-93136 branch
Review all pull request comments for additional changes
Run composer update (if the scripts fail, add --no-scripts)
Clear any config, route, or view cache
Thoroughly test your application (no tests?, no CI?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

:information_source: Laravel 9 moved the resources/lang folder to the top level of the project. While Shift moved and replaced references to this folder, you may have additional references to this folder which need to be updated.

:warning: Laravel 9 transitioned from SwiftMailer to Symfony Mailer. While this transition should be relatively seamless and Shift automates any tedious changes, some changes may not reliably be automated.
Dependencies
Some mail providers may require an additional dependency. For example, if you are using Mailgun, then you will need to install the symfony/mailgun-mailer package:
composer require symfony/mailgun-mailer symfony/http-client

Updated Return Types
The send, html, raw, and plain methods now return an instance of Illuminate\Mail\SentMessage.
Proxied Illuminate\Mail\Message Methods
Shift detected that you may be using calling some methods on Illuminate\Mail\Message that were being proxied to the underlying Swift_Message class. These are now being proxied to the Symfony\Component\Mime\Email class instead, which has different method names and signatures.
Failed Recipients
It is no longer possible to retrieve a list of failed recipients after sending a message. Instead, a Symfony\Component\Mailer\Exception\TransportExceptionInterface exception will be thrown if a message fails to send. Instead of relying on retrieving invalid email addresses after sending a message, it is recommend that you validate email addresses before sending the message instead.
For more details on what has changed you may review the Symfony Mailer section of the Upgrade Guide.

:x: Shift could not upgrade the following files since they differed from the default Laravel version. You will need to compare these files against the default Laravel 9 versions and merge any changes:

[ ] public/index.php

:information_source: Laravel 8 removed the public/web.config file. The presence of this file creates a potential security risk for projects not using Microsoft IIS as their web server.
Shift removed your file since it did not appear to be modified from the default version. If you are using Microsoft IIS as your web server, you may undo this commit by running git revert be1ee0f5.

:warning: The FILESYSTEM_DRIVER environment variable was renamed to FILESYSTEM_DISK in Laravel 9. Shift attempted to automate this change, but you should review any additional environment configuration and rename this variable.

:warning: Shift upgraded your configuration files by defaulting them and merging your true customizations. These include values which are not changeable through core ENV variables.
You should review this commit for additional customizations or opportunities to use new ENV variables. If you have a lot of customizations, you may undo this commit with git revert d005efe8 and make the config file changes manually.

:warning: The token driver for API authentication is no longer available. This driver was not very robust and was removed from the documentation. Laravel now recommends using Sanctum.
If you were using the token driver, you may re-add it within your auth.php configuration file then migrate to Sanctum at your convenience.

:information_source: The FILESYSTEM_CLOUD environment variable was removed in a later release of Laravel 8. While you may still use the cloud disk, you are encouraged to configure your own disks.
Shift found references to the FILESYSTEM_CLOUD variable in the following files:

[ ] ./config/filesystems.php

:information_source: Shift updated your dependencies for Laravel 9. While many of the popular packages are reviewed, you may have to update additional packages in order for your application to be compatible with Laravel 9. Watch dealing with dependencies for tips on handling any Composer issues.
The following dependencies were updated by a major version and may have their own changes. You may check their changelog for any additional upgrade steps.

[ ] spatie/laravel-medialibrary
[ ] spatie/laravel-permission

:warning: Shift upgraded your NPM dependencies and scripts for Laravel Mix 6. You will need to run npm install locally to ensure your dependencies are up-to-date and compatible.
If you encounter any issues, be sure you have the latest LTS or stable version of Node installed. If the problem persists, review the Update to Mix 6 docs for any additional steps.

:x: Shift detected Vue components within your resources folder. Laravel Mix 6 extracted Vue support into its own feature flag.
You should update your webpack.mix.js and append the new mix.vue() call when building any Vue components. For example:
mix.js('resources/js/app.js', 'public/js').vue();

:information_source: Laravel 9 adopted anonymous migrations. Shift automated this change to align with modern Laravel conventions and avoid naming migrations.

:information_source: All of the underlying Symfony components used by Laravel have been upgraded to Symfony 6. If you are directly interacting with any Symfony component, you should review the Symfony change log for additional changes.

:information_source: Laravel 9 now uses Vite to build frontend assets. While you may continue to use Laravel Mix, it is no longer the default. If you wish to modernize your application to use Vite, you may run the Vite Converter for free.


Cheat ready

how can i notification cheat ready this is old ready message but doesnt works anymore pls help
interfaces.gameUI->messageBox("title", "Osiris ready");

Under " Hooks::Hooks(HMODULE cheatModule) : module{ cheatModule } " paste this
" interfaces->gameUI->messageBox("title", "Osiris ready");   "

Class gameui doesnt includes messageBox

#1506

https://hizliresim.com/7SMEAG   plss help me I can not

@toprak1224 maybe too late answer but u forgot ending your command.


[Bug]: Playwright chain of locators  insert double ">"

Version
Latest
Steps to reproduce
When I used sequence of Locators specified as css selectors, it was generated with double
“Greater than” signs >> instead of single >
For the following code
var rowLocator = Page.Locator(“table.booking-table tbody:nth-child(3) tr:nth-child(1)”);
var cellLocator = rowLocator.Locator($"td.{columnClass}");

The generated locator was “table.booking-table tbody:nth-child(3) tr:nth-child(1) >> td.booking-time-to-travel”, which doesn’t work.
I had to concatenate selectors as strings instead of  call chain of locators.
Expected behavior
Single > should be generated, e.g. “table.booking-table tbody:nth-child(3) tr:nth-child(1) > td.booking-time-to-travel” that does work
Actual behavior
The generated locator was “table.booking-table tbody:nth-child(3) tr:nth-child(1) >> td.booking-time-to-travel”,
Additional context
No response
Environment
- Operating System: [Windows]
- Browser: [All, Chromium, Firefox, WebKit]
- .NET Version (TFM): [net8.0]
- Other info: .Net Playwright

How do you use the generated locator - do you call String() on it?
The >>  is the nesting operator when interacting with e.g. Locators and you click etc. It's part of the Playwright Selector syste.
They are not compatible with e.g. document.querySelectorAll in the browser - since they contain many more features which the web does not support out of the box.

Thanks @mxschmitt , you are right. I've confirmed that chain of locators is working.
I probably had some other error in selector, but in debugger it was shown with ">>" which made me think that it is a reason of mismatch.
Both following tests  work the same way:
using Microsoft.Playwright.MSTest;
namespace PlayWright.Tests;
[TestClass]
public class ChainedLocator : PageTest
{
[TestMethod]
public async Task SearchCellInRow2Locators()
{
await Page.GotoAsync("https://www.w3schools.com/html/html_tables.asp");
int rowNumber=3;
int cellNumber = 3;
var rowLocator = Page.Locator($"table.ws-table-all tbody tr:nth-child({rowNumber+1})");
var cellLocator = rowLocator.Locator($"td:nth-child({cellNumber})");
var text=await cellLocator.TextContentAsync();
Assert.IsTrue(text== "Austria");
}
[TestMethod]
public async Task SearchCellInRowSingleLocator()
{
await Page.GotoAsync("https://www.w3schools.com/html/html_tables.asp");
int rowNumber = 3;
int cellNumber = 3;
var cellLocator = Page.Locator($"table.ws-table-all tbody tr:nth-child({rowNumber+1}) td:nth-child({cellNumber})");
var text = await cellLocator.TextContentAsync();
Assert.IsTrue(text == "Austria");
}
}


Golang Intergartion with ytt

I am trying to generate data/values dynamically using golang
Current Code :
dvs := []string{"x=hello", "y=world"}
templatingOptions := yttcmd.NewOptions()

	input, err := templatesAsInput(tpl...)
	if err != nil {
		return "", err
	}

	templatingOptions.DataValuesFlags.KVsFromYAML = dvs

Is there is way where I can pass a data values directly via structure or map in golang ?
If there is any, pls share the code snippet.

@balu-ce apologies for the delay; we intend to answer more quickly, but have had a lot on our plate, recently.
check this out: https://github.com/carvel-dev/ytt/blob/develop/examples/integrating-with-ytt/apis.md


Adding support for ES6 modules with non-JS extensions:

existing:
import "./MyJsFile" -> MyJsFile.js

and now:
import "./MyJsxFile.jsx" -> MyJsFile.jsx

@ChadKillingsworth might want to glance at this.

This change is

I'm fine with this concept - but I'd like to keep all the module types in sync. We'll need to do the same thing for common js.

Actually - now that I say that. We can do this temporarily, but it will be superseded when I implement the Node module resolution algorithm.

Can't wait!

I've rebased this PR and will squash the commits if you're happy with the revised implementation, following @MatrixFrog's conflicting edit https://github.com/google/closure-compiler/commit/3d03f42df9fcff0ee9f1e7d481b1c98c1fe830c2.
This is a small stop-gap to allow us to use ".jsx" files with ES6 modules. I can look at using ".js" extension for jsx files although it would hurt my own build process, and ideally CompilerOptions would include more control over implicit and explicit extensions, but meanwhile this fix shouldn't harm any existing ES6 module use with Closure Compiler.

Wait, what? How would this work? We don't support the JSX syntax so we wouldn't even be able to parse the files.

@MatrixFrog I've preprocessed them using Babel's JSX conversion. Ideally I'd build this conversion in Java but adapting the CC parser to support JSX is way beyond me. It's just a pure JSX conversion, with none of the other transpilation enabled.

Does Babel not output files with the .js extension?

Ideally I'd build this conversion in Java but adapting the CC parser to support JSX

Actually, it's good that you're not working on this :) There is a strict policy at Google about introducing new language extensions, and we don't have any plan to support JSX at the moment.

In my sources I have a mix of js and jsx files. This is common practice. I use an IDE like webstorm, and browserify+babel to process require() and .jsx files. It's normal to have js and jsx files together, and to omit the .js extension (or to keep it) but to always have the .jsx extension when require'ing a module. The same goes for ES6 modules.
So yes I could theoretically output the jsx files as js (or rename them in-stream) before processing them but then my module references would need to also refer to modules without extensions, and my IDE would lose track of them. Also you couldn't have two files both called the same name .js and .jsx (not that you'd probably want that). I don't fancy transforming the module references on the fly.
(In fact I do something more obscure in that I use Closure Compiler from Java and have my own Java pre+post processing + AST caching going on, including invoking the Babel process to do the JSX alone, thereby allowing me to patch the JSX conversion to reinstate type casts it loses - https://github.com/google/closure-compiler/issues/1782... but I try to minimise the custom steps.)
My aim is to use a standardised approach which works with babel/browserify toolstack but optionally can slot into a Closure Compiler toolstack. So I don't want to use a module naming convention that would only work with Closure Compiler. ES6 modules, my current successful experiment with Closure Compiler, allows this to work seamlessly (albeit with this PR for .jsx support within the module name/filename).
In summary this tiny PR is trying to make common patterns of CJS/ES6 module names (implicit .js + explicit .jsx) work the same way in Closure Compiler.

In my sources I have a mix of js and jsx files. This is common practice.

Having the jsx files alongside the js files is common practice, sure. With you so far.

It's normal to [...] have the .jsx extension when require'ing a module.

This is where I start to be more confused. I doubt that browsers will ever support import * from 'something.jsx', so I'm worried that we'll end up with a syntax that works in Closure but doesn't actually work when you just load the JS directly in the browser. We want to make sure that our users are writing code that will run unmodified in the browser (which is part of the reason we don't support JSX/TypeScript/etc -- we are a JavaScript compiler so we only want to accept valid spec-compliant JavaScript)
Anyway maybe I'm misunderstanding things, and if this small change will make things a lot easier for certain workflows, we can consider merging it. But my reluctance is because it seems like we're diverging from JS here and starting to accept "code that is mostly JS but with a few minor things that aren't quite JS" and I want to be very careful that we don't go very far down that road.

While I'd love it if JSX support was possible, I completely am not asking for this and understand the project goals (though TS syntax seems partly supported in contrary to that... I'm waiting for unification of flow and TS in some future ES standard but guess it is very far away).
Here's an example talking about the same problem in the webpack toolchain:
http://stackoverflow.com/a/34678598
They suggest either an explicit extension (could be something other than js or jsx and not necessarily indicative of a language extension) in the module ref.
Or by configuring "resolve" extensions in the tool config.
The latter is clearly more favourable as a generic solution in CC but it's not a 2 line PR whereas the former brings support for a common workflow out of the box very cheaply. Making it easier to interop between toolchains and migrate to CC.

@supersteves A subset of TypeScript syntax was added for three reasons:

The Angular team experimented with AtScript and added the initial TypeScript syntax support, but then they switched to just using TypeScript.
We were hoping that some future standard (whether it be in ECMAScript itself) would allow optional TypeScript-style colon typing in JavaScript that runs in the browsers, but that has not happened yet.
Even without browser support, being able to use the existing large collection of TypeScript .d.ts type definition files as externs files would be nice. They are less verbose and people already wrote a bunch of them.

3 is already supported by using ``--language_in=ECMASCRIPT6_TYPED`, but we currently we don't have a separate language mode for externs so users would be able to pass in a subset of TypeScript in actual code.
JSX is even less likely to be supported in the browsers because it's React specific, but if this PR is small and it greatly facilitates some workflow, I'm fine with it. Some documentation would be required though.

Interesting history of TS syntax support - thanks. I'd love to see that TS standardised day come for its brevity but am not holding on. But I never thought of TS support as potentially opening up a new route to getting better externs E.g. for React. Something I'll experiment with.
Docs in code, or wiki/elsewhere?

@supersteves The unit tests and integration tests might be the best docs at the moment:
https://github.com/google/closure-compiler/blob/bfaf7180678604011a06580e695dca7c3bddf9e2/test/com/google/javascript/jscomp/Es6TypedToEs6ConverterTest.java
and
https://github.com/google/closure-compiler/blob/871694f79e8bf45c2706b9fdf247909f367703bf/test/com/google/javascript/jscomp/Es6TypedIntegrationTest.java
If you try it on a random .d.ts file, you will likely get some errors / warnings due to things currently not supported in Closure. Last time we tried, about 200 files from https://github.com/DefinitelyTyped/DefinitelyTyped got converted without error / warning.
I will continue working on this feature. There are also improvements coming up in Closure's type system, such as bounded generics, that will allow us to support a large subset of TypeScript definition files.

I think it's pretty reasonable if you are using the existing .d.ts library
to transpile the an externs definition for that library.  For libraries
that we don't maintain externs for, this is much better than starting from
scratch, and if you need to edit a few lines of the .d.ts file for it to
work, it still provides a benefit.
On Fri, May 20, 2016 at 2:26 PM, Michael Zhou<EMAIL_ADDRESS>wrote:

@supersteves https://github.com/supersteves The unit tests and
integration tests might be the best docs at the moment:
https://github.com/google/closure-compiler/blob/bfaf7180678604011a06580e695dca7c3bddf9e2/test/com/google/javascript/jscomp/Es6TypedToEs6ConverterTest.java
and
https://github.com/google/closure-compiler/blob/871694f79e8bf45c2706b9fdf247909f367703bf/test/com/google/javascript/jscomp/Es6TypedIntegrationTest.java
If you try it on a random .d.ts file, you will likely get some errors /
warnings due to things currently not supported in Closure. Last time we
tried, about 200 files from
https://github.com/DefinitelyTyped/DefinitelyTyped got converted without
error / warning.
I will continue working on this feature. There are also improvements
coming up in Closure's type system, such as bounded generics, that will
allow us to support a large subset of TypeScript definition files.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/google/closure-compiler/pull/1774#issuecomment-220722563

Thanks for the info, I'll play with that.
My "Docs in code, or wiki/elsewhere?" referred to @Dominator008's:

Some documentation would be required though.

i.e. what's needed for this PR.

reminder note to update https://github.com/google/closure-compiler/wiki/JS-Modules with info on resolving file extensions after whatever comes out of this PR

Whether we use this exact PR or not, I do plan on enabling this functionality. It's specifically part of the Node module resolution algorithm. Node/CommonJS module loading uses this functionality to support importing JSON files.

Gets my vote!

Per discussion on https://github.com/google/closure-compiler/issues/1897 I'll bring this in but without the jsx support (just js, at least for now).

I.e. just making the .js extension optional.
Separately I propose adding a CompilerOptions member to list the set of known extensions, thereby allowing users to specify .jsx and other extensions...?
I considered skipping adding .js if any .* was found, but it would conflict with filenames containing dots in the name part.

I don't want to get ahead of the browsers here. It seems likely browsers are only going to support .js but we'll keep an eye on it.

@MatrixFrog It's not that I propose explicit support for .jsx. I just want to be able to tell the compiler "Don't add a .js" if it already has a whitelisted extension (default ".js", configurable as ".,js,.jsx").

You can send a separate PR for that but I'm not sure I would be in favor of it. We are generally trying to make the compiler less configurable, not more.

@supersteves Did you ever get around to handing in a PR or making this work? We have a mixed codebase with .js and .es6 extensions and I run into the same import problem.

@joscha No, I'd be happy to submit a proper configurable "known extensions option" PR, but the last response didn't fill me with confidence it would be accepted. We have our own fork with a bunch of minor changes including a low-grade version of this. Supporting explicit .es6 extensions (hard-coded) would be a 1 line fix if you were to fork it yourself: https://github.com/visokio/closure-compiler/commit/ec8a81ac1aeadbbc74e06c2c191920e6e71bb5d2

It's covered by #2130

Closed by #2130 - requires use the --module_resolution flag to be either BROWSER or NODE.


Fixes two omissions in the ExtensionServiceCreator

Overview

ExtensionServiceCreator ignores namespace supplied by user, always takes default instead
ExtensionServiceCreator creates inspector even when "Generate Inspector" is unselected

Changes

ExtensionServiceCreator now uses NameSpace in stead of DefaultExtensionNamespace while creating the files. This also required adaption of the template files as those now have a missing "using" on top now they are no long in Microsoft.MixedReality.Toolkit.Extensions;
Added simple "if(UsesInspector)" around creation of inspector. This was read from the UI and clearly intended to use for this, but was not checked

@Railboy, can you take a look as well?

Thanks for fixing this! Change lgtm, would like to get @Railboy's eyes because he wrote this.

Changed base to stabilization branch so that this makes it into the next release.

/azp run stabilization_pr

Glad to be of service. I had run into this limitation for quite some number of times, and I am glad I could lend a helping hand


Add Concurrency Limiter

Description
This enables limiting concurrency. It is a naive approach which
will reject requests as soon as they exceed the maximum number
of in-flight requests.
Motivation and Context

[X] I have raised an issue to propose this change (https://github.com/openfaas-incubator/of-watchdog/issues/52)

How Has This Been Tested?
There are tests in the code that test for all of the obvious possible variants. The code is written in such a way that testing is easy.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I've read the CONTRIBUTION guide
[X] I have signed-off my commits with git commit -s
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

Hi @sargun thanks for raising this.
Are there any differences from the original PR?
Alex

One of the comments/questions I left on the issue was:
Given that this is required in the watchdog, what is an appropriate way to handle the code in both places? A shared package or duplicated code figured out later?

Some changes:

Broke out the concurrency-limiter into its own code. This will allow us to use this code in the legacy handler. I do not see a way to vendor / gomod code in the repo, but I'm willing to hand-vendor, use go mod, copy the directory, or govendor.
Renamed concurrency_limit to max_inflight
Normalized usage between http.Handler, and http.HandlerFunc

In this part of the PR unit testing and manual e2e validation is normally mentioned.

How Has This Been Tested?

I'm guessing that you've been using a HTTP-template of your own or from the template store and that's how the original PR got raised here instead of on the classic watchdog. Which templates have you tested with, in a Docker image, deployed to an OpenFaaS cluster and in http mode?

Thanks for adding your review @LucasRoesler
@sargun this looks close to being merged, at which point I will cut a binary release for you.
Once ready there will also be a quick rebase needed with origin/master. Please avoid doing a merge commit into your branch. I usually do this with git pull origin master --rebase then fix up any conflicts if I see any.

@alexellis PTAL

Thank you @sargun - please let us know on Slack if there's anything else that we can do to help enable your use-case.
@LucasRoesler thanks for the review :+1:
Here's the release which contains this change:
https://github.com/openfaas-incubator/of-watchdog/releases/tag/0.5.1
A binary is added by the CI process a few minutes after cutting the release.
Follow-up actions
@sargun are you able to run with these follow-up items?

This should be documented at openfaas/docs -> docs.openfas.com under the watchdog design/architecture page
All templates using the of-watchdog in openfaas/templates and openfaas-incubator/* should be updated to pull in 0.5.1 in their Dockerfile
This work should be back-ported to the Classic Watchdog and then released

@LucasRoesler do you see anything else that we need to do?
A short / brief blog post may be a good follow-up on openfaas.com - I guess we would want to promote this with the use of an IngressController that does automatic retries when it gets a non 2xx code such as Heptio Contour?
Alex

Got it.

@LucasRoesler / @alexellis One quick thing. To complete the backport, does it make sense to move this into the classic watchdog, and then we vendor the classic watchdog? I noticed you just introduced the first use of vendoring.
P.S.
Any reason why you didn't use go modules. From my understanding, that's the Golang "Standard" now.

Hey @sargun,
Thanks for the PR! :100:
The 2 watchdogs are different enough I don't think it makes sense to vendor one into the other. This would likely cause confusion in the future. (in my opinion)
In reference to your question of using go modules, we plan on sticking with dep for the foreseeable future due to the amount of effort involved. You can read a little more about it in the freshly updated contribution guide


Allow to pass callbackUrl when signAndSendTransactions with Near Wallet connected

Is your feature request related to a problem? Please describe.
My application needs additional process after transactions was successful. Using wallet.near.testnet will redirect to other page rather than stay in, so I need a way to customize the callback url like near-api-js package.
Describe the solution you'd like
Add code to receive parameter callbackUrl and pass to the return function in this file
https://github.com/near/wallet-selector/blob/19af6005890a026a478ab0d093fc6856d8183874/packages/near-wallet/src/lib/near-wallet.ts#L188

Hey @phucloc8697, thanks for opening this issue!
My initial thoughts on a solution is similar to how we've tackled walletUrl by defining a value during setup:
// Init
setupNearWallet({ callbackUrl: "..." });

// Usage (e.g. click handler)
await selector.signAndSendTransactions({ ... });

Would this solve the issue you're having?

@lewis-sqa  Sadly it's not. I need to use different callbackUrl  based on transactions used in signAndSendTransactions. Ideally, I can pass callbackUrl as a parameter to signAndSendTransactions, or is there a way to update callbackUrl after the setupNearWallet ?

Hey @phucloc8697, I've opened a couple of PRs (main -> v3.x & dev -> v4.x) to address this requirement. As you mentioned above, you'll have the ability to pass a callbackUrl for signAndSendTransaction and signAndSendTransactions.
Let me know what your thoughts are on the solution(s) 🙂

@lewis-sqa  The solutions work perfectly for my case. Looking forward to getting this PR on new version soon 👍

Hi @phucloc8697,
You can now find the changes from #292 in our latest release, 3.1.0 👍


Mir is not moving in a straight line. (mir+ur5)

Hi. I am currently struggling with this issue and I have no idea why mir is not moving in a straight line. Do you know what could be the possible cause of error? Thank you!

Are you sure that the path is curving? Or is the start simply offset by a bit? It's a bit hard to tell by the video.
In my experiments, there is a slight offset at the start. This is caused by small perturbations in the simulation while the robot is at rest. However, the path is not significantly curved. Are any warnings printed to the terminal when you start your Gazebo simulation?

Also, I've plotted the data via plotjuggler, and the path also looks to be straight:


Implement pytest

What? and Why?

What does this pull request change/fix? Why was it necessary?

Implement pytest this should improve test output and coverage.
Checklist

[x] CHANGELOG.md updated? (if required)

 sdx-store - implement py.test

Codecov Report

Merging #79 into master will decrease coverage by 4.56%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #79      +/-   ##
==========================================
- Coverage   92.41%   87.85%   -4.57%
==========================================
  Files           5        1       -4
  Lines         343      214     -129
==========================================
- Hits          317      188     -129
  Misses         26       26

Impacted Files
Coverage Δ

tests/test_data.py

tests/__init__.py

settings.py

tests/test_store.py

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 407fb76...6cad8ec. Read the comment docs.


make caching work for source-less functions, e.g. strings, lambdify exprs.

I am evaluating a big sympy generated expression to solve and ODE. I have been able to accelerate it by applying numba.jit to the lambdified expression. However, as the the compilation of the expression takes a long time I wanted to cache the jitted function. Unfortunately, this step returns an error.
A minimal working example is:
from sympy import symbols, lambdify, sqrt
import numpy as np
from numba import jit

x, y = symbols('x y')

expr = sqrt(x**2 + y**2)

fun = lambdify((x, y), expr, modules='numpy', dummify=False)

fun_jit = jit(fun, nopython=True)  # works
# fun_jit = jit(fun, nopython=True, cache=True)  # does not work

N = 10000
x, y = np.linspace(0, 100, N), np.linspace(0, 100,  N)

print('lambdify')
fun(x, y)
print('jitted lambdify')
fun_jit(x, y)

The error returned is:
Traceback (most recent call last):
  File "C:\Users\xxx\user_programs\miniconda3\envs\py36_64\lib\site-packages\IPython\core\interactiveshell.py", line 3296, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-15-0a062e456430>", line 1, in <module>
    fun_jit = jit(fun, nopython=True, cache=True)
  File "C:\Users\xxx\user_programs\miniconda3\envs\py36_64\lib\site-packages\numba\decorators.py", line 161, in jit
    return wrapper(pyfunc)
  File "C:\Users\xxx\user_programs\miniconda3\envs\py36_64\lib\site-packages\numba\decorators.py", line 179, in wrapper
    disp.enable_caching()
  File "C:\Users\xxx\user_programs\miniconda3\envs\py36_64\lib\site-packages\numba\dispatcher.py", line 571, in enable_caching
    self._cache = FunctionCache(self.py_func)
  File "C:\Users\xxx\user_programs\miniconda3\envs\py36_64\lib\site-packages\numba\caching.py", line 614, in __init__
    self._impl = self._impl_class(py_func)
  File "C:\Users\xxx\user_programs\miniconda3\envs\py36_64\lib\site-packages\numba\caching.py", line 349, in __init__
    "for file %r" % (qualname, source_path))
RuntimeError: cannot cache function '_lambdifygenerated': no locator available for file '<lambdifygenerated-6>'

I already opened an issue in sympy https://github.com/sympy/sympy/issues/18432 and as suggested by @oscarbenjamin , this might be related to the fact that sympy is not generating a source file for the lambdified expression.
Do you think that there is any possible modification to get this working in numba?

I'm having a very similar issue - I have tens of thousands of blocks of code that are decorated by numba and loaded with exec.
So far I came up with this:
import hashlib
import pickle

import numba.core.caching

def exec_with_numba_cache(source: str) -> dict:
    source_stamp = hashlib.sha1(source.encode("utf-8")).hexdigest()
    globals_ = {"_exec_source_stamp": source_stamp}
    code = compile(source, filename=f"<{source_stamp}>", mode="exec", dont_inherit=True)
    exec(code, globals_)
    del globals_["_exec_source_stamp"]
    return globals_

class _ExecCacheLocator(numba.core.caching._CacheLocator):
    def __init__(self, source_stamp: str, disambiguator: str):
        self.source_stamp = source_stamp
        self.disambiguator = disambiguator

    def get_cache_path(self):
        return "/my/exec/cache"

    def get_source_stamp(self):
        return self.source_stamp

    def get_disambiguator(self):
        return self.disambiguator

    @classmethod
    def from_function(cls, py_func, py_file):
        try:
            source_stamp = py_func.__globals__["_exec_source_stamp"]
        except KeyError:
            return None

        # Emulate the behaviour of IPython to avoid this code path:
        # https://github.com/numba/numba/blob/ccdf61381cc543afda76a80ef4c51e613472e1f7/numba/core/funcdesc.py#L152-L157  # noqa: E501
        py_func.__module__ = "__main__"

        # Create a unique hash of the function, in case of multiple functions with the
        # same name are in the same source code. It will be appended to the file names.
        co = {
            attr: getattr(py_func.__code__, attr)
            for attr in dir(py_func.__code__)
            if attr.startswith("co_") and attr != "co_filename"
        }
        disambiguator = hashlib.sha1(pickle.dumps(co)).hexdigest()[:10]
        return cls(source_stamp, disambiguator)

numba.core.caching._CacheImpl._locator_classes.append(_ExecCacheLocator)

It works great in unit tests, but as soon as I reach production scale the trouble starts.
I am seeing that numba is incorrectly returning functions that are identical in all but a constant; e.g. if I run in quick succession exec_with_numba_cache on these two source codes:
import numba

@numba.guvectorize(["f8,f8[:]", "()->()", cache=True)
def f(x, out):
    out[0] = x + 1

and
import numba

@numba.guvectorize(["f8,f8[:]", "()->()", cache=True)
def f(x, out):
    out[0] = x + 2

I will randomly get both times the code for the second function, or both times the code for the first.
Note how the two functions have identical f.__code__.co_code, but different f.__code__.co_constants.
My Locator is effective in keeping the two apart since it is generating the file name as the hash of the whole exec'ed source, and in fact I am getting two separate sets of files in the cache.
something else outside of the locator is caching stuff in memory, and it's incorrectly using just f.__code__.co_code as a cache key.
I have now spent almost a week trying to debug this with no results; could anybody point me to where this in-memory caching is happening so that I can, at the very least, wipe it clean before each call to my exec wrapper?

@crusaderky first of all, thank you for using an contributing to Numba. I am sorry, that you have been spending so much time debugging without any results.  Hopefully someone from our development community will be able to give you some pointers soon! cc @stuartarchibald @sklam

@stuartarchibald @sklam any feedback please?

@crusaderky thanks for asking about this. I am sorry for the delay in processing your request, the Numba team is currently in the burndown phase for the first release candidate of the next release. We expect to release 0.51.0RC1 on the 5th of Aug or shortly thereafter. We kindly thank you in advance for your patience.

I have finally pinpointed what triggers the collision and produced a POC.

IF I use my function exec_with_numba_cache above (cannot reproduce with regular python files or ipython)
AND I decorate functions in my source code with guvectorize (cannot reproduce with jit and vectorize)
AND I compile a function and obtain a cache hit, with the cache files having been generated by a different process
AND I then compile, in the same process, a different function, which is identical in all except co_constants to the one from point 3, and obtain a cache miss
THEN the output of the compilation at point 4 will be the output of point 3. The cache files for point 4 will likewise contain the ELF blob for point 3. After an interpreter restart, the issue will persist.

If compilations are either all cache hits or all cache misses, the problem does not surface.
POC
import argparse
import hashlib
import pickle
from textwrap import dedent

import numba.core.caching

def exec_with_numba_cache(source: str) -> dict:
    source_stamp = hashlib.sha1(source.encode("utf-8")).hexdigest()
    globals_ = {"_exec_source_stamp": source_stamp}
    fname = f"<{source_stamp}>"
    code = compile(source, filename=fname, mode="exec", dont_inherit=True)
    exec(code, globals_)
    del globals_["_exec_source_stamp"]
    return globals_

class _ExecCacheLocator(numba.core.caching._CacheLocator):
    def __init__(self, source_stamp: str, disambiguator: str):
        self.source_stamp = source_stamp
        self.disambiguator = disambiguator

    def get_cache_path(self):
        return "mycache"

    def get_source_stamp(self):
        return self.source_stamp

    def get_disambiguator(self):
        return self.disambiguator

    @classmethod
    def from_function(cls, py_func, py_file):
        try:
            source_stamp = py_func.__globals__["_exec_source_stamp"]
        except KeyError:
            return None

        # Emulate the behaviour of IPython to avoid this code path:
        # https://github.com/numba/numba/blob/ccdf61381cc543afda76a80ef4c51e613472e1f7/numba/core/funcdesc.py#L152-L157  # noqa: E501
        py_func.__module__ = "__main__"

        # Create a unique hash of the function, in case of multiple functions with the
        # same name are in the same source code. It will be appended to the file names.
        co = {
            attr: getattr(py_func.__code__, attr)
            for attr in dir(py_func.__code__)
            if attr.startswith("co_") and attr != "co_filename"
        }
        disambiguator = hashlib.sha1(pickle.dumps(co)).hexdigest()[:10]
        return cls(source_stamp, disambiguator)

numba.core.caching._CacheImpl._locator_classes.append(_ExecCacheLocator)

def main():
    parser = argparse.ArgumentParser()
    parser.add_argument("i", nargs="+", type=float)
    args = parser.parse_args()

    for i in args.i:
        print(i)
        source = dedent(
            """
            import numba

            @numba.guvectorize(
                ["f8,f8[:]"], "()->()", cache=True, nopython=True
            )
            def f(_, out):
                out[0] = {}
            """.format(i)
        )

        globals_ = exec_with_numba_cache(source)
        f = globals_["f"]
        out = f(1337)
        assert out == i, f"{out} != {i}"

if __name__ == "__main__":
    main()

$ rm -rf mycache
$ python cache_collision_demo.py 1 1 2
1.0
1.0
2.0
$ python cache_collision_demo.py 1 1 2 3
1.0
1.0
2.0
3.0
Traceback (most recent call last):
  File "cache_collision_demo.py", line 84, in <module>
    main()
  File "cache_collision_demo.py", line 80, in main
    assert out == i, f"{out} != {i}"
AssertionError: 1.0 != 3.0

I found a workaround!
If I trick numba into believing my exec'ed code is a regular Python file, the issue disappears.
The POC showing the issue: https://github.com/crusaderky/numba_pocs
The output: https://github.com/crusaderky/numba_pocs/runs/937237396
PR that makes the issue disappear: https://github.com/crusaderky/numba_pocs/pull/1/files

Interesting. For SymPy, we already add the source to the linecache, but we don't add a fake module to sys.modules. That doesn't seem like a good thing to do in general. It would be better if numba were fixed to not need this.


UI Issues

From 00:00 to 00:30 on video:

Add highlight mark on some line of code,
Add/remove some code BEFORE highlighted line
Higlighted line and dot auto duplicates and moves to incorrect line

From 00:30 on video: Left click on any point on vertical scrollbar must move the code window on that point. But If your mouse pointer aims on scrollbars highliter line the carret does not moves. It is simply to get stacked scrollbar if there are many highlights in one place.
https://github.com/user-attachments/assets/69e775cd-ee66-4cc7-9bff-c2b71a4f10a5

The issue with clicking on the scrollbar is an easy fix.
The other issues will take more thought.
I'm fine with the highlighted area changing as text is added or removed earlier in the file (on the basis that a position in a file is being highlighted, not a specific piece of text), it's the duplication of highlighting indicators that is more of a concern.

I'm fine with the highlighted area changing as text is added or removed earlier in the file (on the basis that a position in a file is being highlighted, not a specific piece of text), it's the duplication of highlighting indicators that is more of a concern.

I would like to use this extension to highlight function names for easy and quick navigation through the code. And if I add a lot of code above the highlighted line, the context can be lost and it is not immediately clear which function was highlighted earlier.


investigate why mdnsresponder has enourmous ttl with no response

default	11:13:11.532148 -0700	mDNSResponder	378    105621 -U-    - Addr     0 srv3.default.my-domain.test. Addr

fix in https://github.com/cppforlife/kwt/commit/fb70471dad3632cd7164e611f432aa3525b25fb9


TraceLoggingEnhancer, MonitoredResourceUtil public methods reverted to 1.0.0 surface.

public constructor for TraceLoggingEnhancer
MonitoredResourceUtil : createResourceEnhancers => getResourceEhancers

LGTM after tests pass

Coverage decreased (-0.01%) to 80.882% when pulling 3ba981bc6ccb87daab229b4688f5ca37c59b99f9 on jabubake:ja_logging_method_rename into 5d502490a9e9677c105441941f1d471bdde8a916 on GoogleCloudPlatform:master.

Coverage decreased (-0.01%) to 80.882% when pulling 3ba981bc6ccb87daab229b4688f5ca37c59b99f9 on jabubake:ja_logging_method_rename into 5d502490a9e9677c105441941f1d471bdde8a916 on GoogleCloudPlatform:master.


Defeat + AGO Bleeding = Stuck

Describe the bug
AGO bleeding doesn't play well with Defeat surrender. I was rolling with a full Riverwood party (Faendal, Gorr, and Hjorlmir (sp)) and cleaning up the watchtower near Bleak Falls. Decided to surrender for kicks but the aggressor had an arrow in his back. He died before the SL animation could start and I was stuck standing. Resetting Defeat would probably solve this but I didn't want to risk it.
To Reproduce
Steps to reproduce the behavior:

Surrender to an enemy with an arrow in his back (good luck)

Expected behavior
Ideally Defeat would recognize bleeding and end its sequence but thats unlikely. Disable bleeding might work.
Screenshots
N/A

Maybe fixed in the next update. I changed the AGO Bleeding effect to stop at 30% HP instead of 10%.


Clangd Can't Find STD Library Headers After Installing Boost

Please describe the problem.
I'm additionally using the VSCode clangd plugin with Remote Explorer.  I use CMake to with CMAKE_EXPORT_COMPILE_COMMANDS flag set to 1.  Code completion, highlighting, signatures, ... all work as expected before installing Boost.  After installing boost, clangd does not parse standard header files.  It always reports "<std header>" not found.
If you can, provide a minimal chunk of code that shows the problem (either inline, or attach it if larger).
sudo apt install libboost-all-dev
Logs
Log when trying to #include std::array header
I[19:12:00.350] <-- textDocument/definition(112) V[19:12:00.350] ASTWorker running Definitions on version 1557 of <path_to_application_code> ... V[19:12:00.350] No heuristic index definition for array I[19:12:00.350] --> reply:textDocument/definition(112) 0 ms V[19:12:00.350] >>> {   "id": 112,   "jsonrpc": "2.0",   "result": [] }
System information
Output of clangd --version:
clangd version 14.0.3 (https://github.com/llvm/llvm-project 1f9140064dfbfb0bbda8e51306ea51080b2f7aac)
Features: linux+grpc
Platform: x86_64-unknown-linux-gnu
Editor/LSP plugin:
VSCode
clangd plugin
Operating system:
Description:    Ubuntu 20.04.3 LTS
Release:        20.04
Codename:       focal

Sounds very strange, but there isn't a lot of info to go on here.
Could you post a complete log of a clangd editing session that involves opening a file that shows an unresolved include diagnostic?

hi @jcmfisker as @HighCommander4 pointed out it's really hard to follow up on such issues in the absence of logs (sometimes even with logs). feel free to re-open once you can attach some logs.


Ghost claims

We have a problem with "ghost claims" (claims that don't exist but prevent to create a new claim or expand an existing one).
The two red marked blocks in the first screen are such ghost claims. All blocks on the right side of the leaves are part of a real claim. But if you want to expant that claim it will be blocked ("Your selection would overlap another claim - No claims found in world", see second screen).
If I shift-rightklick with a stick to show all existing claims it says that there are two claims, but only one of them (the unbuggy one) is listed.

I'm running on GP 1.12.2-<IP_ADDRESS>3 and SF 1.12.2-2705-7.1.0-BETA-3406

Please zip your griefprevention folder and provide the location in world where this issue happens.

Okay, I've found the solution:
There was an old subdivision claim of a claim which no more exist (It was stored in /world/ClaimData/subdivision and not in /world/ClaimData/basic/subdivision). So the subclaim still exists but the parent claim is deleted. It won't be shown in the list because it's only a children claim but you are not able to delete it because the original one doesn't exist (I hope you can understand what I mean :D)

It wasn't enough, it's still buggy :( The both affected blocks are at x2070/z3038 and x2071/z3038.
Here's a link to the griefprevention-folder:
griefprevention.zip


WIP: add expiry to state observing/modifying functions in actor-storage.capnp

Dumb question: where are the expiration timestamps going to come from?

Haha that's what I've been spending the past week trying to figure out. Will dm you about it.


added an upper bound to the php version constraint

versions constraints without a upper bound is bad-practice

this build fails because travis seems to be unable to do a git checkout. I guess its a temporary problem... will retry later.

Thanks @staabm!


RUB-19 Generate class files in core gem and allow translation to happen per file

@rtdp Please revierw.


Remove direct use of os.environ; leverage click.

This completes cleaning up configuration by using a few more click
Context features.

I'm going to plow ahead here with this and #16 to see if releasing works and iterate the Rube Goldberg.


releases seem off 🤔

Why is it the case that 2.7.0 was released three weeks ago, but 2.6.3 is the latest, most recent release?
cc @mrousavy

yea, I made a mistake. 2.6.3 is latest.


Add nvim-cmp highlights + minor improvements

Fix: #71
I think using Fg4 for Popupmenu selection color is better because CmpItemAbbrMatch is already blue.
Also I find really annoying bold yellow for LspReference*, wouldn't it better to softly highlight them as I've done in the commit?

thanks @xeluxee


update APC extension link

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
https://github.com/yiisoft/yii2/issues/19049

👍🏻


Support mixed precision training

It adds loss scale factor for removing invalid data while training.
The factor is dynamically calculated while gradient clipping step, And it initially disabled until
loss scale proeprty is set.
fc/pooling/conv2d/softmax layers are modified for loss scale and mixed tensor type.
Signed-off-by: Jiho Chu<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2455. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2455-202402021547410.65952706336975-af2e8829e8e0ac70333370e438e9b7b37bc604f2/.

:octocat: cibot: @jihochu, nntrainer/layers/pooling2d_layer.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2455-202402021637130.47981810569763-5ce56ff64b70e29561125de65169bff8ee06a41d/.

:octocat: cibot: @jihochu, nntrainer/layers/pooling2d_layer.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jihochu, nntrainer/layers/pooling2d_layer.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jihochu, nntrainer/layers/pooling2d_layer.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2455-202402021651530.78149199485779-49a1f68583e1320967a59ee591050fead566528b/.

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2455-202402051749140.35963010787964-9a6a8b8869043cf1202f0271050f078eaffd0bb1/.

nntrainer/graph/network_graph.cpp:16:10 [clang-diagnostic-error]: nntrainer/graph/network_graph.cpp#L16
'node_exporter.h' file not found

@DonghakPark , please check cpp-linter 's behavior. It's not differ from clang which we are using with TAOS.

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2455-202402051915550.65697598457336-1808a25f14ff73a075672e238c68fba47628b0d5/.

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2455-202403061129400.95467805862427-20dce009fbaeb77274c3554dbad9eb6eb1978760/.

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2455-202403071044020.67149591445923-20dce009fbaeb77274c3554dbad9eb6eb1978760/.

:octocat: cibot: @jihochu, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2455-202403071447080.89027905464172-4ecb30625452a8255d2e33c6b3a05bcd08a06a91/.

:octocat: cibot: @jihochu, nntrainer/layers/loss/mse_loss_layer.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jihochu, nntrainer/layers/loss/mse_loss_layer.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jihochu, nntrainer/layers/loss/mse_loss_layer.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jihochu, nntrainer/layers/loss/mse_loss_layer.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

Recommentation:
Keep a PR with every related commits as a test basis and mark it "Do Not Merge" or "Draft PR"
Make a number of independent smaller PRs ("sub-PR of this PR") so that reviewers can actually read and understand, removing them from the "full PR", whenever they are merged.

closed by  #2663


Fix email overflow for long emails

If the email has more than 20 chars, it overflows in the Tiki app. The example app has more space and works fine.
Acceptance criteria:
1 - The whole email should appear, no matter how long it is.

add ellipsis

In the example app

In Tiki app


Delete key not working

In micro my delete key is not working. I'm on elementary os, xterm and using the latest version of micro now. Maybe something is buggy with elementary os, see issue #34

Also occurs on Kubuntu 15, probably just not implemented.

Delete key (Entf in Germany) Backspace is working well. If it's not implemented it's ok, but would be great of course.


Add indexing for SIREN number

In accordance with #10 , it would be good to have indexing on SIREN for quicker searches.

After checking the code, there is already an indexing on SIREN numbers.


feat(evento): allow to publish with consumer context

:tada: This PR is included in version 1.0.0-alpha.2 :tada:
The release is available on:

GitHub release
v1.0.0-alpha.2

Your semantic-release bot :package::rocket:


Added another submit element selector

For reference see docs for xhtml and html5.

I will not find time to finish this in the near future, sorry for bothering.


[MRG] scale_source_space(): add support for vol source spaces

Resurrecting #1205...

I think it added about a second on my Mac mini.

@larsoner merge if you're happy too

@christianbrodbeck I don't get nan when doing this:
np.linalg.norm(np.array([-0.0005, -0.0005,  0.0005], dtype=np.float32))

So I am a bit confused by that commit message. But we can merge in any case.

It might be the specific version/platform/distribution combination? I figured using scipy's norm wouldn't hurt.
In [2]: import numpy as np

In [3]: np.__version__
Out[3]: '1.11.3'

In [4]: np.linalg.norm(np.array([-0.0005, -0.0005,  0.0005], dtype=np.float32))
//anaconda/envs/mayavi45/lib/python2.7/site-packages/numpy/linalg/linalg.py:2130: RuntimeWarning: invalid value encountered in sqrt
  ret = sqrt(sqnorm)
Out[4]: nan


CAMEL-20804 - mark classes as deprecated  in camel-api o.a.c.cloud

package
camel-cloud component was deprecated in 4.7.0, these packages need also to be deprecated
Description

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

I'd probably use @Deprecated(since = "4.7.0") if they should have been deprecated in the last version, but I'm fine with either way.

I had this dilemna effectively. I feel like it is slightly better with the real moment it is marked as deprecated in the code base.


Fetch plugin not working

I have two pipelines .
Push artifact working fine but when my dependent pipeline trying to fetch the artifact from s3 bucket .
Giving me this error:-
[cd.go.artifact.s3] Retrieving file xyz/abc/env.sh from S3 bucket xvz-us-west-1.
[cd.go.artifact.s3] Failed pull source file: com.amazonaws.services.s3.model.AmazonS3Exception: The specified key does not exist. (Service: Amazon S3; Status Code: 404; Error Code: NoSuchKey; Request ID: B99807E787B09977; S3 Extended Request ID: VwF4gBCo8v1vf7ITQ+4njuvq6+dWyY5sX5yKZ5X4umDmWSur3vrkznU2j86R7G3MvvaTbuNNl1o=), S3 Extended Request ID: VwF4gBCo8v1vf7ITQ+4njuvq6+dWyY5sX5yKZ5X4umDmWSur3vrkznU2j86R7G3MvvaTbuNNl1o=
The plugin sent a response that could not be understood by Go. Plugin returned with code '500' and the following response: 'Failed pull source file: com.amazonaws.services.s3.model.AmazonS3Exception: The specified key does not exist. (Service: Amazon S3; Status Code: 404; Error Code: NoSuchKey; Request ID: B99807E787B09977; S3 Extended Request ID: VwF4gBCo8v1vf7ITQ+4njuvq6+dWyY5sX5yKZ5X4umDmWSur3vrkznU2j86R7G3MvvaTbuNNl1o=), S3 Extended Request ID: VwF4gBCo8v1vf7ITQ+4njuvq6+dWyY5sX5yKZ5X4umDmWSur3vrkznU2j86R7G3MvvaTbuNNl1o='
And the user which is integrated with gocd server has full s3 access.

@Diogomrol hey can you help in this issue.

@shivani-hotstar can you post the following information so that we can reproduce the bug in tests?

Paths of files that are on disk during the fetch.
The configuration of the upload part
What was uploaded to AWS S3.
The configuration of fetch part.

Acc to json file should be fetch from
{"s3extid":{"IsFile":true,"Destination":"xyz","Source":"terraform/env.sh"}}

2 configuration of the upload part:-
artifacts:
- build:
source: terraform/env.sh
- external:
id: s3extid
store_id: s3bucket
configuration:
options:
Destination: 'xyz'
Source: terraform/env.sh

I have one bucket abc which  has xyz folder and under this folder i have my env.sh file which i want to fetch .

fetch part configuration:-
tasks:
- fetch:
options:
SubPath: xyz
Destination: ''
artifact_id: s3extid
pipeline: "123-dub"
stage: terraform-deploy
job: deploy
artifact_origin: external
run_if: passed

2.0.0/s3-artifact-plugin-2.0.0-42.jar .

@tomzo @Diogomrol hey any findings?

@shivani-hotstar thank you for submitting details. I didn't have time to debug this yet as I am a quite busy. I think your use case will suffice to fix it, I'll try to have a look at at, by the end of this week.

@shivani-hotstar me and @sradnev have tried to reproduce the problems you are having using the details you provided. You can review the test cases we have added in https://github.com/Diogomrol/gocd-s3-artifact-plugin/commit/59a81d3ef51a22b3248f4ff593662121d880bffa
The tests are passing, including an e2e cases which both publish and fetch artifacts.
The 3 things that we noticed:
1:
In your upload definition, the build is not really necessary, since if you want to use external plugin for storage, you should need only 1 method for artifacts upload.
      artifacts:
                  - build:
                      source: terraform/env.sh
                  - external:
                      id: s3extid
                      store_id: s3bucket
                      configuration:
                        options:
                          Destination: 'xyz'
                          Source: terraform/env.sh

2:

I have one bucket abc which has xyz folder and under this folder i have my env.sh file which i want to fetch .

This seems inaccurate. With above configuration, the file that is being created on AWS is xyz/terraform/env.sh.
3:
The SubPath is redundant and ignored in this case. You don't need to specify a subpath when artifact is just a single file.
fetch part configuration:

         tasks:
                  - fetch:
                      options:
                        SubPath: xyz
                        Destination: ''
                      artifact_id: s3extid
                      pipeline: "123-dub"
                      stage: terraform-deploy
                      job: deploy
                      artifact_origin: external
                      run_if: passed

Thankyou so much @tomzo @sradnev for the help .
it is working with s3_bucket_name/.
Can we also create sub folders in S3_bucket and post and fetch from those sub_paths for eg s3_bucket_name/folder_name/


Can't open port inside app

Hello
I'm trying to run a web server inside an app in Aind, the webserver responds correctly inside the anbox but not from the Aind docker shell or outside of the docker. The port is not in LISTEN mode inside the docker. Should I configure something to enable this?

https://github.com/aind-containers/aind/issues/44