[CDropdown] Not closed after click on CDropdownItem

I have a dropdown on my Header component where the user can select a language:
<c-dropdown toggler-text="Language">
  <c-dropdown-item :to="switchLocalePath('nl')">Dutch</c-dropdown-item>
  <c-dropdown-item :to="switchLocalePath('en')">English</c-dropdown-item>
</c-dropdown>

The switchLocalePath function is from nuxt-i18n and returns a string, which is in this case the route with a different language. On click, the user is direct to another page, but the dropdown stays in place, opened. Below are the events emitted; the first one is from opening the dropdown and the second is after clicking on the dropdown item.

Generated HTML:

    <button type="button" aria-expanded="true" aria-haspopup="true" class="btn dropdown-toggle">Language</button>

        Dutch
        English

"@coreui/coreui": "3.0.0",
"@coreui/vue": "3.0.5",

The documentation mentions the usage of router link props. If i change :to to :href the dropdown closes, but then the page is fully refreshed (as is expected).

Thank you for the report! The issue is fixed in 3.0.6 version.


Import from TeslaFi

It would be nice to have an automated import from TeslaFi (which I hope to migrate from). I think it can export all the data, but not sure on the format.
(This is something I may try to contribute once I’ve set up Teslamate, just creating this to track it or see if it is on your radar).

I have seen this request a few times and happy to take a crack at it and write a tool. The one thing though - I don't use TeslaFi - is there somewhere one can read up on its schema used and is there a export feature? Need to see what's the data structure is like.
Somewhere one of you can point me to or share this?
Cheers.

TeslaFi allows export of data as a csv by month.   Attached is a clip of an export.
Let me know if you need more/different.
TeslaFi82017 edit.zip

Thanks @tucopup ; let me try and make sense of this, and see how to map it to the schema of TeslaMate.

I started to look at this and wanted to create a documentation of the existing schema, so then to understand how to map TeslaFi's to this. I took a stab at this here. @adriankumpf , does this look directionally correct?

This is my most important issue to migrate off of TeslaFi. I don't want to lose all my historical data.
Speaking of which, one thing that I really like for this historical data is the lifetime map and calendar view (which shows the map of drives for the month displayed)

Yes, this would be a great feature!

I started to look at this and wanted to create a documentation of the existing schema, so then to understand how to map TeslaFi's to this. I took a stab at this here. @adriankumpf , does this look directionally correct?

Looks good to me, @bahree!
I have never used TeslaFi and therefore have no access to exported data. The CSV data from @tucopup seems to be quite complete though.
There are currently no plans to support an automated import from TeslaFi. Contributions are of course welcome though. So if anyone wants to contribute, that would be great!

salivates in anticipation

Huge thanks for this, and especially for including sample CSV files in test fixtures. I was able to export my data from a different logger I used before TeslaMate (https://github.com/lephisto/tesla-apiscraper), write a script to convert it to the TeslaFi CSV format, and import it all into TeslaMate. It took a half day of debugging, but it worked!
I will clean up the conversion script, and push step-by-step instructions to TeslaMate docs shortly.

Huge thanks for this, and especially for including sample CSV files in test fixtures. I was able to export my data from a different logger I used before TeslaMate (https://github.com/lephisto/tesla-apiscraper), write a script to convert it to the TeslaFi CSV format, and import it all into TeslaMate. It took a half day of debugging, but it worked!

How did you import it? I created the import/ folder, and added the entry in the data dir in the yml file, restarted, and I don't see the import screen.

Huge thanks for this, and especially for including sample CSV files in test fixtures. I was able to export my data from a different logger I used before TeslaMate (https://github.com/lephisto/tesla-apiscraper), write a script to convert it to the TeslaFi CSV format, and import it all into TeslaMate. It took a half day of debugging, but it worked!

How did you import it? I created the import/ folder, and added the entry in the data dir in the yml file, restarted, and I don't see the import screen.

ya same issue here... no import screen. Just shows the regular teslamate screen each time.

I had the same issue trying to get it to import when launching TeslaMate from source code locally (basically dev mode) - it wouldn't show the import screen, no matter how I set IMPORT_DIR and where I put the files.
Using the current docker-compose.yml to pull up a TeslaMate instance and placing the files into the "import" directory right next to it worked on first attempt.
I think it's important what the files are called - sample files in test fixtures and my output files from conversion follow the format TeslaFi<month><year>.csv, e.g. TeslaFi52019.csv (note the 5 without a leading zero). It seems that TeslaMate at least parses the filename to display the month in the import screen, even though I believe it's not important for the actual import process - but it might have to follow the format to be recognized correctly.
Also make sure you updated to v1.16 of course.

I had the same issue trying to get it to import when launching TeslaMate from source code locally (basically dev mode) - it wouldn't show the import screen, no matter how I set IMPORT_DIR and where I put the files.
Using the current docker-compose.yml to pull up a TeslaMate instance and placing the files into the "import" directory right next to it worked on first attempt.
I think it's important what the files are called - sample files in test fixtures and my output files from conversion follow the format TeslaFi<month><year>.csv, e.g. TeslaFi52019.csv (note the 5 without a leading zero). It seems that TeslaMate at least parses the filename to display the month in the import screen, even though I believe it's not important for the actual import process - but it might have to follow the format to be recognized correctly.
Also make sure you updated to v1.16 of course.

awesome - that worked.
My problem was understanding this piece of the docker-compose file
volumes:       - ./import:/opt/app/import
I thought the files needed to go in /opt/app/import. Really what I needed to do was leave this alone, and when docker created my import folder next to my yml file, just add my csv files there.
Thanks!

My problem was understanding this piece of the docker-compose file
volumes: - ./import:/opt/app/import
I thought the files needed to go in /opt/app/import. Really what I needed to do was leave this alone, and when docker created my import folder next to my yml file, just add my csv files there.

Still doesn't work for me.
My teslamate/ folder is located at /home/ec2-user/teslamate.
docker-compose.yml contains:
volumes:       - teslamate-db:/var/lib/postgresql/data       - ./import:/opt/app/import
I ran:
docker-compose down docker-compose pull docker-compose up -d
Then after it started up there was a /home/ec2-user/teslamate/import/ folder (owned by root).
I then did a sudo cp to copy the csv files over. It now contains:
$ ls import TeslaFi102019.csv  TeslaFi32019.csv  TeslaFi62019.csv  TeslaFi92019.csv TeslaFi112019.csv  TeslaFi42019.csv  TeslaFi72019.csv TeslaFi122019.csv  TeslaFi52019.csv  TeslaFi82019.csv
I then restarted teslamate again:
docker-compose down docker-compose pull docker-compose up -d
Teslamate and graphana interfaces look normal, it doesn't do any importing.

Ditto - following directions - unable to get any "import" page to pop up.  Using default directory location next to docker-compose.yml.   Has TeslaFi files with correct names.   I did ensure my docker compose file was up to date, most notably updating to postgres 12 w/backup-restore.    After restart standard Teslamate dashboard only, no import screen.
If I remove the import directory, I do get the following error, so it is seeking out the directory at startup.

admin@DiskStation:~$ sudo docker-compose up
Creating network "admin_default" with the default driver
Creating admin_teslamate_1 ... error
Creating admin_database_1  ...
Creating admin_grafana_1   ...
Creating admin_database_1  ... done
Creating admin_grafana_1   ... done
Creating admin_mosquitto_1 ... done
ERROR: for teslamate  Cannot start service teslamate: Bind mount failed: '/volume1/homes/admin/import' does not exists
ERROR: Encountered errors while bringing up the project.

When the import directory exists, it comes up without error, but navigating to the Teslmate UI home screen does not bring up any import screen:

admin@DiskStation:~$ sudo docker-compose up
admin_mosquitto_1 is up-to-date
Starting admin_teslamate_1 ...
admin_database_1 is up-to-date
Starting admin_teslamate_1 ... done
Attaching to admin_mosquitto_1, admin_database_1, admin_grafana_1, admin_teslamate_1
mosquitto_1  | WARNING: no logs are available with the 'db' log driver
database_1   | WARNING: no logs are available with the 'db' log driver
grafana_1    | WARNING: no logs are available with the 'db' log driver
teslamate_1  | WARNING: no logs are available with the 'db' log driver

Ditto - following directions - unable to get any "import" page to pop up. Using default directory location next to docker-compose.yml. Has TeslaFi files with correct names. I did ensure my docker compose file was up to date, most notably updating to postgres 12 w/backup-restore. After restart standard Teslamate dashboard only, no import screen.
If I remove the import directory, I do get the following error, so it is seeking out the directory at startup.

admin@DiskStation:~$ sudo docker-compose up
Creating network "admin_default" with the default driver
Creating admin_teslamate_1 ... error
Creating admin_database_1  ...
Creating admin_grafana_1   ...
Creating admin_database_1  ... done
Creating admin_grafana_1   ... done
Creating admin_mosquitto_1 ... done
ERROR: for teslamate  Cannot start service teslamate: Bind mount failed: '/volume1/homes/admin/import' does not exists
ERROR: Encountered errors while bringing up the project.

When the import directory exists, it comes up without error, but navigating to the Teslmate UI home screen does not bring up any import screen:

admin@DiskStation:~$ sudo docker-compose up
admin_mosquitto_1 is up-to-date
Starting admin_teslamate_1 ...
admin_database_1 is up-to-date
Starting admin_teslamate_1 ... done
Attaching to admin_mosquitto_1, admin_database_1, admin_grafana_1, admin_teslamate_1
mosquitto_1  | WARNING: no logs are available with the 'db' log driver
database_1   | WARNING: no logs are available with the 'db' log driver
grafana_1    | WARNING: no logs are available with the 'db' log driver
teslamate_1  | WARNING: no logs are available with the 'db' log driver

Did you copy the docker-compose file exactly as is without editing the volume path?

Did you copy the docker-compose file exactly as is without editing the volume path?

Yes

One thing to keep in mind: it is not enough to just create the folder, the CSV files must already be placed in it before restarting.
If you are unsure where to create the folder, try using an absolute path instead of ./import.
@dani190, on Synology the actual Docker logs can be found somewhere in the Docker UI afaik.

Huge thanks for this, and especially for including sample CSV files in test fixtures. I was able to export my data from a different logger I used before TeslaMate (https://github.com/lephisto/tesla-apiscraper), write a script to convert it to the TeslaFi CSV format, and import it all into TeslaMate. It took a half day of debugging, but it worked!
I will clean up the conversion script, and push step-by-step instructions to TeslaMate docs shortly.

That's awesome! Looking forward to the PR.

@adriankumpf: I had almost 2 years of TeslaFi data to import and I had issues importing my data. There were 2 months (07/2018 and 11/2018) which were throwing errors while importing. Removing these 2 files from the import directory helped. Would you be interested in taking a look at the data? I can send you all my files.
Also, it looks like the import is a one time process? I tried to import one month at a time (import -> restart -> import...) and only the first-month data gets imported and the rest do not show up although I see a checkmark for the other months. In my import process, I had to do multiple DB wipes and restart the import process to determine which files were causing the import to fail and that is how I determined it was 07/2018 and 11/2018 files.

@adriankumpf: I had almost 2 years of TeslaFi data to import and I had issues importing my data. There were 2 months (07/2018 and 11/2018) which were throwing errors while importing. Removing these 2 files from the import directory helped. Would you be interested in taking a look at the data? I can send you all my files.
Also, it looks like the import is a one time process? I tried to import one month at a time (import -> restart -> import...) and only the first-month data gets imported and the rest do not show up although I see a checkmark for the other months. In my import process, I had to do multiple DB wipes and restart the import process to determine which files were causing the import to fail and that is how I determined it was 07/2018 and 11/2018 files.

Had this exact same problem. Mine was 11/2018 and 12/2018. Also noticed that the import process was a one time thing as I tried to do 2019/2020 and then 2018 separately.

I imported 3 cars data, one at a time.  I'm using Synology/Docker.  There were two minor issues that occured.  Otherwise everything went as expected.
First, the import would not start until I did chmod 777 on the csv files (permission complaint in the logs).
Second, the third car import aborted quickly; the logs contained the name of the second car.  I assumed I mixed up csv files, but it turns out that in the first months csv for car #3, the first 40 lines referenced car #2.  So I re-exported that month from Teslafi; the file was identical.  So I omitted that month (actually only 1 day with one long drive) and everything went fine.   Not a Teslamate problem, rather TeslaFi/Tesla.
This is really great!

I tried full path and chmod 777 on the import and csv files, still nothing happens. What url is supposed to have the new import screen?

It opened when I went to [IP address]:4000, but my history says that it was [IP address]:4000/import

hmmm, I tried that.  Gives me an error.
Internal Server Error

@adriankumpf: I had almost 2 years of TeslaFi data to import and I had issues importing my data. There were 2 months (07/2018 and 11/2018) which were throwing errors while importing. Removing these 2 files from the import directory helped. Would you be interested in taking a look at the data? I can send you all my files.

Had this exact same problem. Mine was 11/2018 and 12/2018. Also noticed that the import process was a one time thing as I tried to do 2019/2020 and then 2018 separately.

Yeah, you can send me an email with the relevant files or open a new issue.

@adriankumpf: I had almost 2 years of TeslaFi data to import and I had issues importing my data. There were 2 months (07/2018 and 11/2018) which were throwing errors while importing. Removing these 2 files from the import directory helped. Would you be interested in taking a look at the data? I can send you all my files.

Had this exact same problem. Mine was 11/2018 and 12/2018. Also noticed that the import process was a one time thing as I tried to do 2019/2020 and then 2018 separately.

Yeah, you can send me an email with the relevant files or open a new issue.

I have sent you my Nov 2018 file which fails to import.

my issue was a permissions issue, too.  chmod 777 on the import dir and files fixed it.   Thanks for the tips!

I tried to import TeslaFi files from Sep '19 up to Sep '20. I put the files in place and restarted TeslaMate. After that I get the Import page and I can see all my files. But after I pushed the Import button I got a red exclamation mark after each file and a error message. Anyone who can clarify what happened and what I can do to solve the problem?
I also tried to import only the file for Sep 2020 but when pushed the Import button nothing at all happens.
{{:function_clause, [ {CSV.Decoding.Preprocessing.Lines, :starts_sequence?, [ <<229, 100, 229, 114, 101, 110, 44, 78, 111, 110, 101, 44, 78, 111, 110, 101, 44, 44, 53, 89, 74, 51, 69, 55, 69, 65, 57, 75, 70, 51, 55, 48, 56, 53, 57, 44, 78, 111, 110, 101, 44, 52, ...>>, "l", false, 44, <<50, 48, 49, 57, 45, 48, 57, 45, 49, 48, 32, 49, 49, 58, 53, 52, 58, 53, 52, 34, 44, 84, 114, 117, 101, 44, 44, 49, 53, 55, 50, 51, 50, 49, 50, 50, 48, 44, ...>> ], []}, {CSV.Decoding.Preprocessing.Lines, :start_sequence, 3, [file: 'lib/csv/decoding/preprocessing/lines.ex', line: 85]}, {Stream, :do_transform_user, 6, [file: 'lib/stream.ex', line: 902]}, {Enumerable.Stream, :do_each, 4, [file: 'lib/stream.ex', line: 1609]}, {Stream, :do_transform, 5, [file: 'lib/stream.ex', line: 880]}, {Enumerable.Stream, :do_each, 4, [file: 'lib/stream.ex', line: 1609]}, {Stream, :do_transform, 5, [file: 'lib/stream.ex', line: 880]}, {Enumerable.Stream, :do_each, 4, [file: 'lib/stream.ex', line: 1609]} ]}, {GenServer, :call, [:api_370859, :get_vehicle, :infinity]}}

Hello,
I'm trying to import 1 month of Teslafi datas in my Teslamate. The .csv file is detected, i'm starting the update and when it's finish after a few secondes (5 ?) is restart teslamate service.
Nothing is imported in teslamate, no charge, no drives...
What could be wrong ?
Thanks !


INIT FAILURE

Is this normal?  i changed the urls for spain and nothing happends, can u help me?

I will give it a look and replay!
By a first look I attach two notes:

It is necessary to do some debug inside the "web_scraper" function for understand in which line there is the problem.
one possibility is to update the HTML labels of the Vinted site.

I think is trying donwload the image of article
am-bot-main/Webscaper-and-Telegram-bot-main/import_telebot.py
Recived message:camisa
thread 'main' panicked at 'Downloaded file cannot be uncompressed (xml extension)', src\files.rs:46:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
thread 'main' panicked at 'Downloaded file cannot be uncompressed (xml extension)', src\files.rs:46:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
Error
But alwais dop this :

Hi,
I was not able to replicate your issue.
I need more information, can you add your Error message? and the section regarding the issue?
Note: You have to update the '''attrs''' of the following section according to the vinted site:
 #scraping the boxes
        for box in page.findAll('div', attrs={"class" : "new-item-box__container"}):

            #scraping the name the prize and the link for on a single box
            advertisement = []

            #CATEGORY
            tmp = box.find('div', attrs={'new-item-box__description'})
            category = tmp.find('h4', attrs={'web_ui__Text__text web_ui__Text__caption web_ui__Text__left'})
            print(tmp.text)
            print(category.text)
            categories.append(category.text)
            advertisement.append(category.text)
            #print(category.text)
            #print("OK category")

            #PRICE
            price = box.find('div', attrs={'title-content'})
            print(price)
            price_raw = price.text
            price_clean = price_raw.replace('\xa0', '')
            prices.append(price_clean)
            advertisement.append(price_clean)
            #print("OK price")

            #LINK
            tmp = box.find('div', attrs={'class' : 'u-position-relative u-min-height-none u-flex-auto'})
            print(tmp)
            link = tmp.find('a')
            print(link)
            links.append(link.get('href'))
            advertisement.append(link.get('href'))
            #SUBCATEGORY

            #IMMAGE and PRODUCT
            tmp = box.find('div', attrs={'web_ui__Image__image web_ui__Image__cover web_ui__Image__portrait web_ui__Image__scaled web_ui__Image__ratio'})
            image_link  = tmp.find('img')
            products.append(image_link.get('alt'))
            #image = io.imread(image_link.get('src'))
            #images.append(image)
            #print(image.get('alt'))
            #print(image.get('src'))
            #advertisement.append(image_link.get('alt'))
            #advertisement.append(image) #Wrong
            #product_data.append(advertisement) # contanins all the data grupped


Audio is muffled and distorted when playtesting a game built for Windows, doesn't happen on any other platform as far as I'm aware.

So, I'm using Stencyl, a game engine that is partially made with OpenFL. I'm reporting this bug here because the admins of the game engine's site recommended I go here, because this is apparently a bug with OpenFL, and not Stencyl.
I can't upload .ogg files here for reference on what I'm talking about, but whenever I upload audio into Stencyl, it sounds fine when I  play it in the actual engine, but for some reason whenever I playtest my game on Windows, all of the audio is weirdly bass-boosted, distorted, and kinda-mono if that makes sense. I made sure that it's not that the audio I'm importing is low quality, as when going into the actual assets of the game, the audio files are all perfectly fine and HQ, it's just whenever I play the actual build of my project when the audio turns bad.
I've exhausted every conceivable way to fix this bug myself, but the admins who run the Stencyl website and update the engine told me that it's not anything they can fix because sound is managed by OpenFL.
Here's a video of what the audio sounds like in-game. The actual audio is supposed to sound really crisp.
https://user-images.githubusercontent.com/104954320/166853584-8a58c54d-6851-4b05-9dfc-2362470f2ed1.mp4
This bug only happens when running a project as a Windows build (like a .exe file,) not on HTML, Linux, or mobile.

Can you share an audio file sample? Is this prevalent in other sound playback for windows target?

Seems to be the same issue https://github.com/FunkinCrew/Funkin/pull/3318 tries to fix.

Do you have a specific audio sample I can try that is noticeably worse on windows?

I guess you can use this one, there's also a mp3 version if you want to test it on HTML5
The PR I linked makes use of an alsoft.ini file to modify OpenAL's default settings on Windows to remove the muffling. You can try it for yourself by simply placing it in the same directory as the executable.
alsoft.ini's contents

[general]
 sample-type=float32
 stereo-mode=speakers
 stereo-encoding=panpot
 hrtf=false
 cf_level=0
 resampler=fast_bsinc24
 front-stablizer=false
 output-limiter=false
 volume-adjust=0
 [decoder]
 hq-mode=false
 distance-comp=false
 nfc=false

Here's also a comparison of that same audio file, first part uses the alsoft.ini file, second one does not.
https://github.com/user-attachments/assets/59da11bf-a99e-4c97-a3a8-c37546b36fce


eval_set only retries "cancelled" or "errored" logs

Inspect only retries "cancelled" or "errored" logs. This is a problem if you want to retry a run which was not shut down gracefully (most saliently, by the OOM killer in the OS).

We have a work item that we'll be addressing in the short term to make retry handling more customisable. I think we can handle this well in that context. One note is that "started" logs which you have here can also be cruft from runs gone complete bad (e.g. that error on every sample) so re-running them is not a no-brainer (you could end up in an infinite retry loop).

We have a work item that we'll be addressing in the short term to make retry handling more customisable. I think we can handle this well in that context. One note is that "started" logs which you have here can also be cruft from runs gone complete bad (e.g. that error on every sample) so re-running them is not a no-brainer (you could end up in an infinite retry loop).

I would have thought that inspect would only mark an EvalLog as "started" if it hasn't been cancelled or seen an error. Surely if every sample errors the log would have succeeded?

I think you are correct that the case I identified is not really about samples failing but about the whole eval failing due to a hard crash. Sometimes this would OOM and sometimes it could be something else (which we wouldn't want to keep retrying). I think there is a good resolution to be had here but I don't want to just slam in retrying "started" without thinking carefully about what could happen. There is another discussion about this w/ more details that I'll try to dig up and post a link to here.

I think you are correct that the case I identified is not really about samples failing but about the whole eval failing due to a hard crash. Sometimes this would OOM and sometimes it could be something else (which we wouldn't want to keep retrying). I think there is a good resolution to be had here but I don't want to just slam in retrying "started" without thinking carefully about what could happen. There is another discussion about this w/ more details that I'll try to dig up and post a link to here.

I'm happy for a setting. The situations I use it in is when I know that inspect has been killed by the OS, so theres an eval log which never finished (is still "started"). I'm then happy to restart it.

Here's the discussion from Slack along w/ a related change we made:
J.J.
Looking at the code, I think that could indeed occur in the case of a crash! I will code around that case
https://github.com/UKGovernmentBEIS/inspect_ai/commit/f1c8cbab0fa84c253e84f4f86a52bd113e52a410
Gabriel Mukobi (U.S. AISI)
I got this when there were some runs that hard failed such that logs with the "started" state were not properly removed. Removing those logs fixed it, but as a bandaid you could add a check for len(id_logs) and continue if it's empty
J.J.
Yup, I just added that band aid to continue w/ len(id_logs) == 0, thx!
Gabriel Mukobi (U.S. AISI)
The band-aid may do more harm than good though, since IIUC those "started" log files will prevent eval-set from rerunning those failed runs. It would be nice to have some way of distinguishing started logs that are still going from started logs that are zombies because e.g. a machine crashed. Not sure what would be best, though, maybe some health-check thing and then cleaning "started" logs with last check times older than some threshold?
J.J.
Interesting. In theory though that code only runs in between eval calls, so if the task is still running it is from some other process. In other words, at that point in the code they should all be zombies b/c we are outside of eval() which is where they would be running.
Gabriel Mukobi (U.S. AISI)
Ah, so you can just clean up all "started" logs if eval-set is called again, since users should not call eval-set while the same eval-set is running? In that case, maybe you could just remove the line a few lines up from this error line that filters out "started" tasks from pruning.
J.J.
We are actually expressly trying to ignore the "started" files (we don't want them counted as the most recent eval). We are probably "leaking" them on purpose as a post-flight black box for crashes? (I don't exactly recall, but I don't want to just start changing stuff in there w/o thinking hard about it!)

So it sounds like we are purposely ignoring "started" so that there is some record of the crash to examine post-facto. If we believe that this is unlikely to be useful, then I could see just treating "started" the same as "error" or "cancelled" -- I just recall when creating the feature thinking hard about this and going the other way (I easily could have just not been thinking carefully enough). I'd be game for an immediate change but I'd love it if we could think it through sufficiently so we don't inadvertently break something. Maybe a realtime discussion of this sometime tomorrow just as a sanity check?

It's a good point that we might want to have some evidence of the crash post-facto. I think that in many cases this is a desired behaviour (in particular if there was a run-ending crash). But I think probably needs to be squared w/ the case where it didn't exit gracefully.


[Sprint 8] more validation bug fixes and enhancements

 [Bug] Add validation CSS for individual inputs in sub-groups

Codecov Report

Merging #9 (bb27a6e) into main (5267b40) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   97.16%   97.17%
=======================================
  Files          21       21
  Lines         353      354    +1
  Branches       28       28
=======================================
+ Hits          343      344    +1
  Misses          3        3
  Partials        7        7

Impacted Files
Coverage Δ

.../app/components/builder/editor/editor.component.ts
100.00% <100.00%> (ø)


:sparkles: feat: change all default size as middle & update FieldSet doc

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

Comparison is base (ac27441) 80.96% compared to head (92d12aa) 80.97%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #116      +/-   ##
==========================================
+ Coverage   80.96%   80.97%   +0.01%
==========================================
  Files         415      416       +1
  Lines       25569    25590      +21
  Branches     1156     1159       +3
==========================================
+ Hits        20701    20722      +21
  Misses       4868     4868

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


Add unit tests for Borough service and controller

Test create, show, update in borough.service with a mock borough and with an invalid boroughId
Test create, show, update in borough.controller with mock request bodies

The service and controller were written by Lin Xiao but should be similar to tour!
See #25 for resources

Closed by #42


Error when blt_add_code_checks calls blt_add_yapf_target

Having this issue in LiDO where when I call blt_add_code_checks I get the following error:
CMake Error at cmake/blt/cmake/SetupCodeChecks.cmake:873 (message):
  blt_add_yapf_target requires a SRC_FILES parameter
Call Stack (most recent call first):
  cmake/blt/cmake/SetupCodeChecks.cmake:246 (blt_add_yapf_target)
  CMakeLists.txt:187 (blt_add_code_checks)

The SRC_FILES variable is set to _py_sources (retrieved from blt_split_source_list_by_language, see https://github.com/LLNL/blt/blob/develop/cmake/SetupCodeChecks.cmake#L156).
I guess when blt_split_source_list_by_language is called, Python_LIST is empty, which means _py_sources is empty, which means SRC_FILES is "" when it gets down to blt_add_yapf_target.
When I commented out the fatal error I was able to make by LiDO build without issues. Maybe this check is not required?

I see two solutions:

Have the user required to not provide a YAPF config file if you don't provide Python files to add code checks for (this seems less than robust).

Check on each of these if blocks that you are actually providing source files to run checks for:
https://github.com/LLNL/blt/blob/92450b0d4e4ccb534b9f69b6214ab31633cdd9d1/cmake/SetupCodeChecks.cmake#L238-L255

I would lean towards the second option.


Weird error while getting token from redirect

Came across this error when I try to call getTokenFromRedirect()
        try {
            $token = Facebook::getTokenFromRedirect();

            if (!$token) {
                return false;
            }
        } catch (SammyK\FacebookQueryBuilder\FacebookQueryBuilderException $e) {
            $error = [
                'FQB' => $e->getMessage(),
                'FB_SDK' => $e->getPrevious()->getMessage(),
            ];
            dd($error);
        }

        return $token;

I'm using "sammyk/laravel-facebook-sdk": "~1.1" with Laravel 4.2.
What could be the possible reason for this?
Thanks for your help!

I believe this is related to this issue in the main SDK: https://github.com/facebook/facebook-php-sdk-v4/issues/391
I'll have to do some digging to see where this started popping up all of a sudden.

On localhost it works fine but on server facebook gives this error even when I'm using the same app for both localhost and server.

I think I found the issue. It's due to the way the response is handled in Graph v2.3. Did you recently update to Graph v2.3 or do a composer update to pull in the latest PHP SDK 4.0?
I'm working on a patch. :)

Yeah I did the composer update today.
Thanks for patching it up quickly. :smile:

No problem! Here's the full explanation of what is happening. Once the PR gets merged & tagged, you can do another composer update and it should work again. :)

@SammyK Thank you so much :)


[Feature] Support ESLint v9

Reference: https://eslint.org/blog/2024/04/eslint-v9.0.0-released/

This might be handy for you as I had stumbled upon your config:

Also this comment is subject to change.

no-new-symbol deprecated and replace by no-new-native-nonconstructor

Related issues: https://github.com/import-js/eslint-plugin-import/issues/2948, https://github.com/eslint-community/eslint-plugin-promise/issues/449, https://github.com/sindresorhus/eslint-plugin-unicorn/pull/2250, https://github.com/typescript-eslint/typescript-eslint/issues/8211

Yesterday, I started migrating from v8.5.6 to v9.2.0 in another project, and it was a burden because of how much the Eslint's server, I guess, is no synced with the VSCode extension's version. I had to install the pre-release version, and yet I ran onto issues where .eslintrc files couldn't be found because Eslint has switched to flat configs: eslint.config.js, and this is where I realized that this wouldn't be possible, at least for for now, because a lot of plugins that currently use do not support the latest version of Eslint.
I think we just have to wait for merge PRs.


Implement Email Integration to process Nihms deposit emails

The design for email integration to process nihms deposit emails was proposed and agreed to in this issue: https://github.com/eclipse-pass/main/issues/826#issuecomment-1854774871

Adding link to Mark's analysis doc with Plan of action at the end https://docs.google.com/document/d/1JAf22f_mOrAG1-JZlEXcbTz7FbywYUmJy-16uxi3OFQ/edit#heading=h.nphpoi4ro4ru


PR: Fix issues with installer discovered from 6.0.0b2

Description of Changes

Patch recipe conda_build_config.yaml on CI in order to replicate the build string hash on conda-forge.
Use recipe_clobber.yaml and recipe_append.yaml mechanisms to patch meta.yaml instead of find/replace.
Include label/spyder_dev in the url for Spyder in the conda-lock file, if non-stable distribution
Fix an issue where the shortcut was not found after macOS update, preventing post-update launching of Spyder.

Issue(s) Resolved

Fixes #22201

Change our release workflow order to PyPi -> conda-forge -> Github release.

This option makes sense to me :+1:

I also agree with @dalthviz. But we'd still be able to test the installers manually before tagging a stable release, as we do now, right @mrclary?

I also agree with @dalthviz. But we'd still be able to test the installers manually before tagging a stable release, as we do now, right @mrclary?

We'd still be able to manually test. Here is what I'd propose:

Manually trigger installer workflow (workflow dispatch pre=true).
Manually test installers. Note that the conda-lock file will not be valid since it will not rely on a Spyder conda package from conda-forge.
Create release tag (but not a GH release).
Publish to PyPi.
Publish to conda-forge.
Create Github release (using existing tag). This triggers the installer workflow for release.

I would also change our update manager to only check for updates from GH. Then all user types will be alerted to available updates after all assets are guaranteed to be available.

Manually test installers. Note that the conda-lock file will not be valid since it will not rely on a Spyder conda package from conda-forge.

Ok, I think that's a good compromise: we should be able to test the installers before a release but not the update process with them.

I'll submit a follow-up PR:

Change our installer workflow to use the conda-forge Spyder package on releases only. Nightly, PR, and workflow-dispatch triggers will still build Spyder locally.
Discontinue patching the conda-lock file.
Change the update manager plugin to only check GH for releases.


Issue: Unable to use "Cmd+." as a Custom Shortcut Key on Macos

Description
I am running High Sierra on Mac and for some reason I cannot access the Settings menu in AO.  I have changed the darwin.json configuration to another option but it still will not pop up by using either the menu directly or via keyboard shortcut.
Error Message (if any)
No error message found, just doesn't react/open.
Relevant Links (if any)
NA
Environment
Tell us which operating system you are using, as well as which version of Ao.
Run the following script to get your OS info quickly.
OS Type: 	Darwin
OS Platform:	darwin
OS Release: 	17.4.0
Architecture: 	x64

Additional Information
NA

Would you mind sharing the contents of your ~/.ao.json file?

Unfortunately the Cmd+. shortcut key is reserved for the Edit Shortcut Keys option, which is hardcoded and not available for modification in the ~/.ao.json file, thus it conflicts with your custom "settings": "Cmd+." option. The next release will address this issue by making the Edit Shortcut Keys option editable, in order to prevent any similar future issues. For the time being you can try using a different shortcut key to toggle your Settings, the default "Cmd+." could be an option. Other than that everything seems perfect, thank you for taking the time to report it : )

@klauscfhq Well, now I am having another issue - not sure what is going on.  I removed my ~/.ao.json and now it won't load.  The application loads, but not the web app.  I also removed the application and re-installed and still the same issue.  I'll keep messing with this, unless you know of way to remove the application completely?
Thanks,

Also, I just downloaded 5.2.0 and installed it as well - still having the same issue.  Something is sticking around for some reason.

You can try uninstalling and then deleting the ~/Library/Application Support/Ao directory. After that clean installing from scratch should bring everything back to normal : )

@klauscfhq Thanks for the help again!  I did that and re-installed but I am still unable to access the settings in the menu either by shortcut or via the menu.  Here is an example (side note, I also did this with 5.2.0 and it is not working on there as well):

@klauscfhq Here's a better one I think:

Yep, now it makes sense. It looks like that Ao is loading a different version of the Microsoft Todo interface, probably an updated or latest one. That is the reason for not toggling the Settings menu, as well as the console errors, since the in-use by Ao class names are not present there. The Cmd+, shortcut actually toggles the native Settings menu of the original/traditional Microsoft Todo interface. Here is a quick look of it on Windows, same goes for Linux;

It could be that the Microsoft Todo app is under a gradual updating process and your account belongs to a circle of users that were given access to it first or it could just be a a Macos thing, but I tend to think more of the first one as the cause. I will have a better look into it and come up with a way to address it. Thank you a lot for bringing it up 👍
For the record, you can probably still access the settings menu by click the cogwheel icon at the top bar.

@klauscfhq Thanks for the explanation!  Just wanted you to be aware.
Also, I'm going to suggest another item in a #12

New 6.0.0 release, supporting the updated Microsoft To-Do interface, is now out. Full changelog & binaries are available on the GitHub Releases page.


Typo in the readme

"Koa is a middleware framework that can take 3 different kinds of functions as middleware:"
It should say 2 instead of 3, since it only lists common and async functions, not generators.

Btw, how about switch the list to match sequences of examples? Or switch examples.
Now the first one of the list is "Common function", while the first example is "async functions". Maybe "async function" without "s".

@slikts sometimes it's easier to make a PR by editing in GitHub than by opening a new issue :)

@chinesedfan that sounds good

@slikts to be fair, due to koa-convert the paragraph is accurate - for now.

I think this one is closed as https://github.com/koajs/koa/commit/87036857e6b79cfd564d7bf2352ef7abb922b48d landed?


Clean CS config, upgrade Doctrine CS to v7

Dropping PHP 7.1 is prerequisite for this https://github.com/webonyx/graphql-php/pull/470
This includes:

CS config cleanup
upgrade to Doctrine CS v7

I guess we can close this PR since we had another one focused on the clean up?

@vladar I rebased so now it contains only CS config cleanup + slevomat CS upgrade as there are some bugs fixed.

Ok cool, then I guess it will stay here until we decide to drop PHP7.1 support %)

Tru tru

Coverage decreased (-0.04%) to 86.264% when pulling e8a62ab1700b4ee13da4871f2785d3093fcf8876 on simPod:phpcs-config-simplify into 4f3430990824ff410fe548102cb85f0c46442704 on webonyx:master.


Subsequent filing into a non-indexed case

Need to make sure someone can add a motion, etc. to a case that isn't in the case management system. It's like an initial filing but there are a few other datapoints needed.

@BryceStevenWilley I think you're fastest on this one. We'll need to ask for the docket number and send back a different call to the proxy server, right? If you don't have time to complete, point me to the right place in the code and I'll do my best to move it forward

Taking a look at the Tyler docs on this.  It looks like the EFM will respond with error code -11 if the search returned no results and the court doesn't allow non-indexed filing, while it will return 136 if the case wasn't found but the court does allow non-indexed filings.
It also looks like the court lookup will reliably specify if the court allows non-indexed filing, so we don't really need to look at this error code.
Very few real courts have non-indexed cases. Here is the list for testing purposes:
          name
------------------------
 System
 File & Serve
 Kankakee County
 McLean County
 St. Clair County
 ARDC Clerk's Office
 zzz - REA-KNOX  2
 zzz - Caliber
 z - Standards 3 Test 1
 z - Standards 3 Test 2
 zzz - Henderson County
 zz - AOIC Testing
 z - Test
(13 rows)

We do still need case type and subtype for validation when filing into a non-indexed case.

@BryceStevenWilley bring me in on the DA side if necessary--I started but didn't get too far here: https://github.com/SuffolkLITLab/docassemble-EFSPIntegration/tree/35-file-into-non-indexed-case

This should be in now, most of the work was in #142, probably still a bit more polish on the DA side needed though.


Telegram bot stops sending notification after the first 5 items

Telegram bot stops sending notification after the first 5 items. From the console Log it seems searching items but the bot doesn't receive the items.

@orzynico It should still send and receive new items in theory. Can you provide me your telegram.js file. I can assist you better on https://discord.gg/WatbRXcj if you need assistance making it work.

I've just writed on the channel. Thank youuuu


Nexus-IQ security scans failing

Our nexus-iq security scans are failing with:
java.io.FileNotFoundException: The specified user settings file does not exist: /home/vsts/work/1/s/.m2/settings.xml

This was caused by ad6da42989723bf0d30e0741f3fea70d3f89f9f8 which I approved as we're using github actions. however this nexus-iq build is still running on azure pipelines (so we hadn't noticed the failure) and does need this file.
cc: @lpalashevski

See current build pipelines at https://dev.azure.com/ODPi/Egeria/_build

^ @cmgrote note a few of the builds in your connectors are failing too for nexus/sonar
We may also want to raise an issue to move these scans to github actions, or agree to replace them with another approach.


Support Cloud Formation templates & create cost estimates

Add support for Cloud Formation Templates. This is for users who are not using Terraform (or not only using terraform).
https://aws.amazon.com/cloudformation/

This is a duplicate of https://github.com/infracost/infracost/issues/190

This is a duplicate of https://github.com/infracost/infracost/issues/190


Add .17.60 recipes.

.17.60 has changed a few recipes . Can you update the calculator for them? More info: https://old.reddit.com/r/factorio/comments/cjsmu8/version_01760/

Would be nice to have the old recipes too though. The oil change is a bit controversial and some people are staying in 17.59 for now. If only to finish ongoing games without large redesigns

I have created a pull request that updates the recipes to 0.17.60.
@SteveS8 I would argue that the official calculator should not have datasets containing information from outdated experimental releases. You can always use the offline version of the calculator (https://github.com/KirkMcDonald/factorio-tools) to host a local calculator from an old game version if you want to keep using that.

I am getting my tooling into a state where I can dump the current version, and plan on pushing a 0.17.60 dataset once that is working. I believe the only barrier right now is the image-scaling thing. I have yet to receive a PR from @FoxLBA with a fix for this (cf. #172), so I'll probably hack up something of my own in the meantime.
I probably won't make a 0.17.59 dataset. If the devs decide to revert their changes then so be it, but I plan on tracking the game in its current state.

Ok. I will made PR with dadaset end then for scaling fix.

I have pushed KirkMcDonald/factorio-tools@8c66310f5e024dc5772787682acfd62e66bc0a20, which hacks in a solution for these mipmapped icons.

Done in b2d92eabedb786fadca71906f79808033bfa4a48.


CreateOrUpdate  Snapshot REST API - No mention of how to specify that the disk is a managed disk

The REST API documentation for creating disk snapshots can be found at https://docs.microsoft.com/en-us/rest/api/compute/snapshots/createorupdate.  It makes no mention of how to specify that the disk is a managed disk.

@erickson-doug Can you take a look and see if it can be updated

Hi Team,
Any update on this?
Regards,
Amit Bhatia

@erickson-doug can you help address this?

@erickson-doug Any update?

Sent email to @erickson-doug to follow up

@neilpeterson should be the first contact? Neil, can you connect folks with the VM devs, or the writer who currently owns VMs?

@iainfoulds any thoughts on whom to contact here?

On the compute side, @singhkays, and on the storage side, @ramankumarlive, should be able to provide assistance. I think this would fall under updates required within the Compute API ref.

@Powerhelmsman - can we re-assign this issue? I am not the right person to handle.
Thanks

@neilpeterson Reassigned to @singhkays and @ramankumarlive

@meetamitbhatia Your issue is transferred to vsts-rest-api team. They will help you there. I will close as transferred. If you have other question related to this issue, we can reopen it and continue discussion.

@meetamitbhatia I do not believe you have to specify the disk you are creating the snapshot of is a managed disk.  I tested this with my own REST call on a managed disk without specifying it was a managed disk, and it worked fine.


How can resolve "ChunkLoadError: Loading chunk" with your plugin?

My case I have an react app using CRACO without your craco-module-federation plugin, so my craco.config file looks like:
craco.config
const ModuleFederationPlugin = require("webpack/lib/container/ModuleFederationPlugin");
const deps = require("./package.json").dependencies;

module.exports = {
  devServer: {
    port: 5004
  },
  webpack: {
    plugins: [
      new ModuleFederationPlugin({
        name: "reactappcraco",
        filename: "remoteEntry.js",
        exposes: {
          "./web-components": "./src/index.js",
        },
        shared: {
          ...deps,
          react: {
            singleton: true,
            requiredVersion: deps.react,
          },
          "react-dom": {
            singleton: true,
            requiredVersion: deps["react-dom"],
          },
        },
      })
    ],
  }
}

But, when execute the app in the browser console shows:

However, when I use your plugin this error does not show, I can see that you are using in your plugin the overrideWebpackConfig function, I would like to know why don't show you the ChunkError?.
maybe could be for this

sorry this is not an issue, it is like a question.. ty.. :)

@danimauro16 , I had the same problem. Define webpackConfig.output.publicPath = 'auto'; in your remote app.
See an example:
remote app
https://github.com/fiuzagr/acme-repo/blob/cf213e6216b0f330c9a840904e43e3642827b461/sites/home-site/craco.config.js#L7
host app
https://github.com/fiuzagr/acme-repo/blob/cf213e6216b0f330c9a840904e43e3642827b461/sites/root-site/craco.config.js#L11


Add support for multiple architectures

@robbert229 Can you please merge this?

I completely missed the notifications for this one until now. merging


Migrate to official Cypress Angular schematic

This the same as this issue in the iteration template, which was accomplished in this commit.
To do this I did:

ng add @cypress/schematics
npm uninstall @nrwl/cypress @nrwl/workspace
Changed @nrwl/cypress:cypress to @cypress/schematic:cypress in angular.json

This was done somewhere in the past.


Update README.md

From the official discord developer server. (Source: Discord) You should add this to README.md.
Some people may not find the issue to why they dont get the badge after 24hrs.

Don't think it is needed..


optimized code,all override methods must be added @override

What is the purpose of the change
all override methods must be added @override
Brief changelog
all override methods be added @override
Verifying this change
Not
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[x] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[x] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

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

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

@XavierChengZW hi, thanks for your contribution.
Please resolve conflicts with the latest master branch.

close for long time no response
Please feel free to reopen it


/health reports 0.0.0 for api versions

Using Bee-factory images that uses Bee docker images I am getting:
$ curl http://localhost:1635/health
{"status":"ok","version":"1.4.1-238867f1","apiVersion":"0.0.0","debugApiVersion":"0.0.0"}

I get the same on a direct download of the 1.4.1 release for Linux AMD64.
{
  "status": "ok",
  "version": "1.4.1-238867f1",
  "apiVersion": "0.0.0",
  "debugApiVersion": "0.0.0"
}

The versions are set in the build process so I'm guessing that the binary you're running wasn't built by make binary.

My Linux AMD64 version was directly downloaded from github's releases, so how it was built is up there somewhere.


Fix required-features using renamed dependencies.

The dep_name/feat_name syntax in required-features should use the "name in toml" for dep_name, not the actual package name.  Otherwise, it is impossible to actually enable the feature (because the --features flag expects a "name in toml").

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

@bors: r+

:pushpin: Commit cafec11467cc4758c0b3ce3751865d2334ab360e has been approved by alexcrichton

:hourglass: Testing commit cafec11467cc4758c0b3ce3751865d2334ab360e with merge ad7015086a75a19f7fabc6bcc72b1fbbcf053d5e...

:broken_heart: Test failed - checks-azure

CI failure was #7865.
@bors retry

:hourglass: Testing commit cafec11467cc4758c0b3ce3751865d2334ab360e with merge 06834dcaf2d53175ccf4801a6b6212b5fb56a519...

:sunny: Test successful - checks-azure
Approved by: alexcrichton
Pushing 06834dcaf2d53175ccf4801a6b6212b5fb56a519 to master...


Why do color settings disappear from Fonts and Color dialog?

does VS14 solution still compile?
rename it to VS15?
build it on CI and publish as a distinct package?

I confirm that the bug no longer appears on VS 2015 CTP 5. Closing.


feat: Added user login endpoint SAP-25

Setup login endpoint with JWT and basic endpoint authentication using passport.
DRAFT: Pending successful integration testing once actual user data exists in the database.

Looking really good. To abstract our architecture a bit more, I was wondering if it's possible to put database and external application interfaces in a Services directory. While interfaces to our application can stay as a controller in a Controllers directory. With this, multiple controllers can interact with other applications through services rather than using another controller.

Why do we need a data-access directory? From what I understood after reading the changes is that data-access and service serve the same purpose, rendering one of them redundant. We could just keep the Services instead where that directory can immediately execute data access and data manipulation.

Why do we need a data-access directory? From what I understood after reading the changes is that data-access and service serve the same purpose, rendering one of them redundant. We could just keep the Services instead where that directory can immediately execute data access and data manipulation.
What I was expecting from the structures was after calling and making a request to a given Route. That will call a method made in a Controller and a Controller can interact with our server our external applications. Something like the following:
Route -> Controller -> Services

I think I see what you mean.
But a few things:
Routes are rolled into controllers thanks to decorators (or annotations, if you're familiar with that syntax). The data access layer is responsible to the actual interfacing with the database and configuration of the model.
The service is what the endpoints call to access specified pieces with specific parameters.
Another way of thinking about it is a separation of database access from business logic.
Here's roughly what a few things I was basing this architecture on:
https://stackoverflow.com/a/66441894/4358021
https://merlino.agency/blog/clean-architecture-in-express-js-applications
Let me know if this makes sense. Or it this is an over-engineered approach.


Added support for 2nd Generation HUE bridges

Hue
Status
Bug Fix / Feature enhancement to support 2nd Generation Phillips HUE bridges
Description
The Python-Hue library doesn't support the new authentication method used in the 2nd Generation Hue Bridge.  Easy work-around is to manually generate the API Key via the HUE Bridge WebGUI. Once configured in ST2, the library will use this key (if valid) and will not try to use 1st Generation authentication method.  The manual method will also work with 1st Generation.
Checklist (tick everything that applies)

[ ] Metadata: pack.yaml, icon, structure (required for new packs)
[X] Version bump (required for changed packs)
[ ] Code linting (required, can be done after the PR checks)
[ ] Tests (not required but really recommended)

Nice work, thanks!

Do we also need to update requirements.txt or not (I assume changes depend on the new functionality in a client library)?
Edit: It looks like we don't pin to a specific version right now, would be a good idea to do it in any case.

The Phillips-Hue library has not been updated to support 2nd Gen Bridge Authentication, but it does support overriding of the client_identifier (aka. username) in the class. If the client_identifier is valid, then the 1st Generation method of authentication is never tried, thus allowing this method to work for both generations without a library modification.

Ah, OK, thanks for the clarification and a heads up.
Works for me and looks good then!

Merged, thanks.


Report public object properties as exports in list-exports.

Currently levitate reports exports of packages on its top level only. We'd like to report the public object properties of those exports when possible.
Example:
@grafana/data exports DataSourcePlugin  which is a class that has several public methods such as setConfigEditor or setQueryEditor and many more.
Levitate should report those object properties.

Closed by https://github.com/grafana/levitate/pull/187


⚠ DDoS-Relay US-W-sfo3-01 has degraded performance

In 3775bb9, DDoS-Relay US-W-sfo3-01 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 137 ms

Resolved: DDoS-Relay US-W-sfo3-01 performance has improved in 7bee4c9 after 18 minutes.


LoadingButton doesn't exist on the CDN version

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I try to use the  component just like all the other components. But since it doesn't exist the app just crashes.
I tried to console.log it and it is undefined.
Expected behavior 🤔
It should let me use it just like every other component and the way it is specified in the docs.
Steps to reproduce 🕹
Steps:

Setup react via CDN, without Nodejs
Import MUI
Decompose the variable from the CDN:  const { LoadingButton } = MaterialUI;
Try to use the component or log it on the console

Context 🔦
I am trying to use the LoadingButton component, using MUI via CDN
Your environment 🌎
I am running React and MUI via CDN

As you can see the LoadingButton is undefined while Paper is an object

Hi. Thanks for the report. Can you create a codesandbox that directly shows the issue? You can fork this template: https://codesandbox.io/s/mui-issue-latest-s2dsx

I've found out it doesn't work because LoadingButton is part of the MUI lab, so it doesn't come on the CDN.
Is there any way to get the components that are only available on the lab via CDN?
Thanks for the help

As you can find in https://mui.com/getting-started/installation/#cdn ,

You can start using MUI with minimal Front-end infrastructure, which is great for prototyping.

Two Universal Module Definition (UMD) files are provided:
one for development: https://unpkg.com/<EMAIL_ADDRESS>one for production: https://unpkg.com/<EMAIL_ADDRESS>I am afraid you can only access @mui/material via CDN.


Integration Test - Release - 2018/09/06 03:00:37

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest1 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


Hardcoded Base URI and API Key in Service Provider

Hi, just started getting 403 errors on the package when searching. After some digging I noticed that the base uri and api key are hardcoded! Not sure whether this has always been the case or it the hard coded api key was deleted or companies house updated their security but needs to be updated to use config please.
https://github.com/GhazanfarMir/laravel-companies-house/blob/ac9ddbc4b095bd5fbad258e1b8ae683c0541bcd9/src/CompaniesHouseServiceProvider.php#L25

See https://github.com/GhazanfarMir/laravel-companies-house/pull/31#issuecomment-608398940

Resolved by merging #31


KAFKA-8785: fix request timeout by waiting for brokers up at the begining

We initializing adminClient, we'll first fetch the metadata of the brokers. Usually, we expected the brokers are already up (and metadata are updated in server side). So that we can choose 1 node to connect to in the following request. But if we only fetch "partial" metadata of the brokers, and after the "partial" brokers shutdown, the adminClient will not work anymore due to no nodes to connect to.
So, the reason why this test is flaky is because we have race condition at the beginning of the test, when brokers are staring up, and the adminClient is requesting for brokers metadata. Once the adminClient only got broker2/broker3, the test will fail, because in these tests, broker2 and broker3 will be shutdown to test leader election.
Fix this issue by explicitly waiting for all brokers up and metadata updated, before creating adminClient.
java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. Call: describeTopics
	at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999)
	at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:165)
	at kafka.utils.TestUtils$.$anonfun$waitForBrokersOutOfIsr$1(TestUtils.scala:1897)
	at kafka.utils.TestUtils$.waitForBrokersOutOfIsr(TestUtils.scala:992)
	at kafka.admin.LeaderElectionCommandTest10.testPathToJsonFile(LeaderElectionCommandTest10.scala:155)

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@hachikuji  @dajac , please take a look. Thanks.

Run twice and have no failed tests from LeaderElectionCommandTest
    Build / JDK 11 and Scala 2.13 / kafka.api.PlaintextAdminIntegrationTest.testReplicaCanFetchFromLogStartOffsetAfterDeleteRecords()
    Build / JDK 11 and Scala 2.13 / kafka.api.PlaintextAdminIntegrationTest.testReplicaCanFetchFromLogStartOffsetAfterDeleteRecords()
    Build / JDK 8 and Scala 2.12 / org.apache.kafka.connect.mirror.integration.IdentityReplicationIntegrationTest.testReplication()
    Build / JDK 8 and Scala 2.12 / kafka.api.PlaintextAdminIntegrationTest.testReplicaCanFetchFromLogStartOffsetAfterDeleteRecords()
    Build / JDK 8 and Scala 2.12 / kafka.api.PlaintextAdminIntegrationTest.testReplicaCanFetchFromLogStartOffsetAfterDeleteRecords()

    Build / ARM / kafka.server.ReplicaManagerTest.[1] usesTopicIds=true
    Build / JDK 17 and Scala 2.13 / kafka.api.PlaintextAdminIntegrationTest.testInvalidAlterPartitionReassignments()

@showuon Thanks for the PR. I left a suggestion. Overall, I wonder if the real issue is in the admin client. If we have all the brokers in the bootstrap list, it should be able to recover if there are no nodes. However, it seems that it does not try to re-resolve the bootstrap list in this case.
We could perhaps apply the suggestion that I've made to fix the flaky tests and file a jira if there is a real limitation in the admin client. What do you think?

@dajac , thanks for the comment.

We could perhaps apply the suggestion that I've made to fix the flaky tests

Sure. I'll update the PR later.

file a jira if there is a real limitation in the admin client. What do you think?

Agree!
Thank you.

@dajac , it doesn't work to put the admin client creating after cluster.waitForReadyBrokers(), because the waitForReadyBrokers only wait for all brokers registered and unfenced (ref: here), but the metadata cache in broker might have not updated the cluster metadata. I think we need to explicitly wait for all brokers up via describeCluster and then create adminClient for testing.
WDYT?

@dajac , KAFKA-13653 is created for the improvement to proactively discover alive brokers from bootstrap server lists when all nodes are down. Thanks.

it doesn't work to put the admin client creating after cluster.waitForReadyBrokers(), because the waitForReadyBrokers only wait for all brokers registered and unfenced (ref: here), but the metadata cache in broker might have not updated the cluster metadata. I think we need to explicitly wait for all brokers up via describeCluster and then create adminClient for testing.

Hmm, I wonder if this is right. I checked the QuorumController logic and unfencing implies that the broker has caught up to the current end of the log. At least it implies that the offset reported in the heartbeat request is up to date. From what I can tell, there might still be a race between the time that this offset gets updated in BrokerMetadataListener and the time that the latest entries have been published to BrokerMetadataPublisher. Is that delay enough to explain the issue?

@hachikuji , let me check it and let you know.

@hachikuji , I finally got time to investigate it. Short answer to your question: Yes, you're right!

From what I can tell, there might still be a race between the time that this offset gets updated in BrokerMetadataListener and the time that the latest entries have been published to BrokerMetadataPublisher. Is that delay enough to explain the issue?

Yes, when broker unfenced, it means it has caught up to the current end of the log. So basically, the broker is ready. But the BrokerMetadataPublisher is in another thread, which will have race condition with the main thread (in test). That is, even when waitForReadyBrokers passed, all the broker images might still be out-of-date.
Fix it now by waiting the metadata cache up-to-date in waitForReadyBrokers. Thank you.

Also updated the PR title and description. Thanks.

@showuon Thanks for the update. What do you think about modifying the heartbeating logic so that we do not advertise an offset to the controller until it has been published?

What do you think about modifying the heartbeating logic so that we do not advertise an offset to the controller until it has been published?

@hachikuji , thanks for your suggestion. But sorry, I'm not very familiar with kraft. As far as I can see, we'll wait until the broker has caught up with the latest metadata from the controller quorum (i.e. initialCatchUpFuture) before we unfenced the broker. Then we send out the unfenced heartbeat to controller, controller check wantFence and high offset to see if this broker can be unfenced. Next, it'll commit the unfenced metadata, and wait for the broker to read the update, and let the listener to publish the update to the metadata cache. That's what my understand (correct me if I'm wrong).
So, if we don't advertise the offset to controller, the controller won't unfence the broker becaue metadata is not caught up, and no metadata commit happen, and the broker listener won't publish the unfenced info. I don't know how we can achieve it. Could you help explain to me?
Thank you.
Another thing is that do you think we could take this temporary solution (i.e. waiting the metadata cache up-to-date in waitForReadyBrokers) to fix the tests first, and we can work on the better solution you suggested in another PR if it takes time. WDYT?

if we don't advertise the offset to controller,

@showuon, Here, Jason means we postpone advertising offset after the publisher has finished publishing, which means MetadataCache has been updated.
We can achieve it in a simpler way here:

Add a method/field in MetadataPublisher, def highestMetadataOffset long
every time we call BrokerMetadataPublisher.publish(), we set the highestMetadataOffset to the newest offset, maybe we should add a parameter logEndOffset to BrokerMetadataPublisher.publish()
Change the code lifecycleManager.start(() => metadataListener.highestMetadataOffset ) to lifecycleManager.start(() => metadataPublisher.highestMetadataOffset in BrokerServer.

PTAL.

@dengziming , cool! Thanks for the info. Are you interested in submitting another PR to address it? That would be helpful and make v3.2.0 release sooner!

@showuon Thank you, I will have a try.

@showuon @dengziming @hachikuji @dajac What is the status of this PR? This PR would resolve a blocker for the 3.2.0 release. Would be great if we could merge this PR as soon as possible?

Rebase to the latest trunk and the failed tests are unrelated:
    Build / JDK 8 and Scala 2.12 / kafka.admin.TopicCommandIntegrationTest.testDescribeAtMinIsrPartitions(String).quorum=zk
    Build / JDK 8 and Scala 2.12 / kafka.admin.TopicCommandIntegrationTest.testAlterAssignment(String).quorum=kraft
    Build / JDK 8 and Scala 2.12 / kafka.server.KRaftClusterTest.testIncrementalAlterConfigs()
    Build / JDK 8 and Scala 2.12 / kafka.server.KRaftClusterTest.testSetLog4jConfigurations()
    Build / JDK 8 and Scala 2.12 / kafka.server.KRaftClusterTest.testLegacyAlterConfigs()
    Build / JDK 8 and Scala 2.12 / kafka.server.KRaftClusterTest.testCreateClusterAndPerformReassignment()
    Build / JDK 17 and Scala 2.13 / kafka.admin.TopicCommandIntegrationTest.testAlterAssignment(String).quorum=kraft
    Build / JDK 11 and Scala 2.13 / kafka.admin.TopicCommandIntegrationTest.testAlterAssignment(String).quorum=kraft
    Build / JDK 11 and Scala 2.13 / kafka.admin.TopicCommandIntegrationTest.testAlterAssignment(String).quorum=kraft


_389-ds-base: <IP_ADDRESS> -> 2.0.5

Motivation for this change
Closes #100098
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126641 at c7809bce run on x86_64-linux 1

1 package built successfully:

_389-ds-base

2 suggestions:

warning: build-tools-in-build-inputs
rsync is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/servers/ldap/389/default.nix:57:3:
   |
57 |   buildInputs = [
   |   ^

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/servers/ldap/389/default.nix:155:3:
    |
155 |   meta = with lib; {
    |   ^

Builds successfully, nixos x86_64. Can't really test it any more than that.


cpp-redis: init at 4.3.1

Description of changes
Adds cpp redis library required for ceph 19.x
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

I don't understand the formatting error.
pkgs/by-name/cp/cpp-redis/package.nix: not formatted
Some new/changed Nix files are not properly formatted
Please go to the Nixpkgs root directory, run `nix-shell`, then:
nixfmt 'pkgs/by-name/cp/cpp-redis/package.nix'
If you're having trouble, please ping @NixOS/nix-formatting

nix-shell && nixfmt is exactly what I did. Shows 0 diff after running this again.


Extend the validity of the GPG signing key

Our signing key expires on 2016-07-15. Somebody has to extend it, before this date.

Uh oh, that didn't work out as expected.

Ok, I've extended the keys validity to 2017-07-15, so next year. I've put the key pair on Bintray and uploaded it to tarent PGP server and the SKS key server pools. The updated key is currently propagating through the internet and should be available on each key server within the next hours. Can somebody confirm this and then close the issue please? /cc @wallner

Thanks!


2.3.4 to 2.4.2，Vue works wrong

Version
2.4.2
Reproduction link
https://github.com/vuejs/vue
Steps to reproduce
import vueComp from '../ad-generator.vue';
var Ad = Vue.extend(vueComp);
var ad = new Ad({
el: document.createElement('div'),
data: data
});
What is expected?
work properly，the data will prop into the component instance "ad"
What is actually happening?
the props data in instance is undefined

when i run npm i，the vue upgrade into 2.4.2 , this problem happens.

Hello, your issue has been closed because it does not conform to our issue requirements. Please use the Issue Helper to create an issue - thank you!
Specific reason: The provided reproduction link is not a reproduction, it's the vue repository.


Changes to publish the VS Code extension into marketplace

Purpose

Make changes for the initial publishing of the Ballerina Integrator VS Code extension into VS Code marketplace.

resolves #352

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Should ThreadInterruptedException be rethrown?

The extension method ExceptionHelper.MustBeRethrown rethrows the out-of-band exceptions StackOverflowException, ThreadAbortException and OutOfMemoryException for good reason: they can be thrown from nearly any method call and will result in terminating the thread anyway.
ThreadInterruptedException is similar but not quite the same. It can be thrown anytime the thread enters a WaitSleepJoin state. It does not necessarily result in terminating the thread, but semantically, it should.
The problem lies when I want to be able to interrupt a worker thread this way when that worker thread is inside a call to NLog and some target puts the thread in a wait state. The code in the worker thread doesn't receive the ThreadInterruptedException because NLog doesn't rethrow it.
NLog itself doesn't seem to put the thread into a WaitSleepJoin sate, but it appears that the System.Console class uses such waits to perform thread synchronization, so the problem can arise if a Console logger is configured. Similar synchronization might be in place for the File target, but I haven't checked on that.
NLog's default behavior of swallowing exceptions during logging is very useful when the writing thread simply fails to write the log entry to the configured target, but because ThreadInterruptedException is generally caused by an external thread, it seems like NLog should not swallow it.

related: https://stackoverflow.com/questions/3313575/how-to-properly-handle-threadinterruptedexception

I can't fully understand it either, but it seems like it could be a good idea to rethrow the exception. But has anybody had issue with this?

Closing this because of inactivity.


Stanza retries forever when log entry is too big for Google Cloud Logging

Describe the bug
I see this occasionally while using the vcenter plugin. The error repeats over and over in the log.
{"level":"warn","timestamp":"2021-02-26T18:24:54.777-0500","message":"Failed flushing chunk. Waiting before retry","error":"rpc error: code = InvalidArgument desc = Log entry with size 256.4K exceeds maximum size of 256.0K","wait_time":21.213547168}

If I stop stanza, delete stanza.db, and restart stanza, the error does not show up for a while. Indicating that only a few log entries are too large. Google Cloud Logging console shows plenty of log activity.
To Reproduce
Steps to reproduce the behavior:

Use syslog input
Use Google Cloud output
Send a very large message to stanza ( I am working on an easy way to do this )

Expected behavior
Stanza should handle messages that are too large for Google Output, either by breaking them up or dropping them and logging a warning or error.

Possibly unrelated, and requires its own issue. I created a large single line file, and sent it to stanza's tcp listening port. I seem to have crashed stanza in a way that prevents me from stopping and starting. I rebooted the VM only to find it hanging during shutdown:

I filed an issue related to systemd https://github.com/observIQ/stanza/issues/258.


chore: bdd-gh-1586825136 to 0.0.1

chore: Promote bdd-gh-1586825136 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Instead of failing or panicking, skip tests

Based on the fact that an API key is required, automated tests done via TravisCI and such fail without it, and in some instances lead to a panic and recovery. Instead, perhaps this is a better alternative to tests that just cannot possibly pass. Skipping may not be a lot better than a failure, but at least as many as possible runnable tests actually run.

I'll be releasing a new version that has a refactored set of tests. I'll take the feedback from this PR and make sure to accommodate your request.


Docker flow: Forward stdin

In order to interpret .tcl scripts using ./bazel-bin/Top_variant_floorplan_docker open_floorplan < script.tcl', docker_shellmust passstdintomake`. If there are less ill-advised ways to achieve this, any help would be appreciated.
@oharboe

@lpawelcz @eszpotanski Thoughts?


New version: eTeks.SweetHome3D version 7.3

Pull request has been created with komac v2.2.1 :rocket:

Resolves #148397

Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/issues/142854

@Exorcism0666 Hi, this failed my sandbox testing once the update was detected.


Please add est. duration or end times for the different presentations

@piejanssens - thanks for the suggestion.  We have started adding duration to the session information.


[Service Bus] Fix browser test failures - New logging tests

Fixes the following browser test failures.

Do we know what commit of ours caused the test failure?

Do we know what commit of ours caused the test failure?

The tests were newly added at https://github.com/Azure/azure-sdk-for-js/pull/11058

do we always need this fix for browser tests when we use assert from chai?

Yes.. from what I've seen!


Based on CornerNet, detects each object as a triplet, rather than a pair, of keypoints, CenterNet has made great progress. Do you have a test comparison between CenterNet and CornerNet-Lite? Thank you！

Based on CornerNet, detects each object as a triplet, rather than a pair, of keypoints, CenterNet has made great progress. Do you have a test comparison between CenterNet and CornerNet-Lite? Thank you！
https://github.com/Duankaiwen/CenterNet
CenterNet: Keypoint Triplets for Object Detection  CenterNet：用于对象检测的关键点三元组
CenterNet is an one-stage detector which gets trained from scratch. On the MS-COCO dataset, CenterNet achieves an AP of 47.0%, which surpasses all known one-stage detectors, and even gets very close to the top-performance two-stage detectors.
Description of their paper: “We build our framework upon a representative one-stage keypoint-based detector named CornerNet. Our approach, named CenterNet, detects each object as a triplet, rather than a pair, of keypoints, which improves both precision and recall. Accordingly, we design two customized modules named cascade corner pooling and center pooling, which play the roles of enriching information collected by both top-left and bottom-right corners and providing more recognizable information at the central regions, respectively.”

我觉得你这是个奇怪的问题，A 论文先发出来，B论文后发出来，B中已经做了详细的对比，你还问A的作者你对比B了吗？

我觉得你这是个奇怪的问题，A 论文先发出来，B论文后发出来，B中已经做了详细的对比，你还问A的作者你对比B了吗？

Firstly, because the two papers are almost overlapping in time, and they are issued simultaneously, the difference is one day, and CenterNet was submitted on April 17 (v1), the latest revision is April 19, 2019(v3).  CornerNet-Lite(Submitted on 18 Apr 201)
CenterNet: Keypoint Triplets for Object Detection
Kaiwen Duan, Song Bai, Lingxi Xie, Honggang Qi, Qingming Huang, Qi Tian
(Submitted on 17 Apr 2019 (v1), last revised 19 Apr 2019 (this version, v3))
CornerNet-Lite: Efficient Keypoint Based Object Detection
Hei Law, Yun Teng, Olga Russakovsky, Jia Deng
(Submitted on 18 Apr 2019)
Secondly, they are based on the original author CornerNet. The core is CornerNet. The original author didn't know this information. I told them the information.
Can't we?
Thirdly, you said that detailed comparison has been made in B. Would you please check the original paper carefully? That's just a comparison with the old version of CornerNet, ok? Is there a comparison between the new CornerNet Lite?
Fourthly, in the spirit of research, if CornerNet-Lite and CornerNet-Lite+CenterNet were compared, would there be any difference?
Thank you!
第一，因为这两篇论文的时间几乎是重叠的，同时发的，相差1天，而且CenterNet是4月17日提交（v1），最新修订于2019年4月19日。CornerNet-Lite4月18日提交
CenterNet：用于对象检测的关键点三元组
Kaiwen Duan, Song Bai, Lingxi Xie, Honggang Qi, Qingming Huang, Qi Tian
（2019年4月17日提交（v1），最新修订于2019年4月19日（本版本，v3））
CornerNet-Lite：基于关键点的高效对象检测
Hei Law，Yun Teng，Olga Russakovsky，Jia Deng
（于2019年4月18日提交）
第二，CenterNet和CornerNet-Lite都是基于原始作者CornerNet分别改进而来的。核心都是CornerNet，原始作者可能不知道这个信息，我告知一下不可以吗？
第三，你说B中已经做了详细的对比，麻烦您仔细核对原始论文，那只是对比CornerNet的老版本，ok？新的CornerNet-Lite有对比吗？
第四，本着研究的精神，如果CornerNet-Lite与CornerNet-Lite+CenterNet对比会不会有差异呢？
谢谢！

@QQ2737499951 谢谢你的分析，我没有留意到你提到的细节信息，抱歉我的回答
还有一个建议给你，既然都开源了，也可以下载到作者的模型，可以自己分析下啊

谢谢！正在验证，还没有结果

@xiaozhuka  想请问您个问题，作者给出的ConnerNet-lite的安装教程，需要利用conda创建一个python3.7的虚拟环境，那么在conda_packagelist.txt中需要安装的包，是都安装在虚拟环境中，还是有一部分安装到系统里？因为我现在其他的虚拟环境中在跑faster，我担心安装这些包时会对已有虚拟环境中安装的包有影响


pollen css components

this looks nice.
Any there any html components using pollen css ?
I know of https://www.franken-ui.dev . If there was something like this for pollen it would make development faster.

You can check https://www.pollen.style. There are no components.
You can swap with tailwindcss and use any components you want.


Static bioinformatics packages: samtools, megahit, prodigal, and bwa

None of these changes should have any effect on standard builds, but they enable static building

Built on platform(s)

[x] x86_64-linux

for pkg in megahit samtools bwa ; do
  nix-build . -A pkgsCross.musl64.pkgsStatic.${pkg}
done

Result of nixpkgs-review pr 171469 run on aarch64-darwin 1

5 packages built:

angsd
bcftools
htslib
nimPackages.hts-nim
samtools

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

1 package marked as broken and skipped:

truvari

4 packages failed to build:

octopus-caller
python310Packages.cnvkit
python39Packages.cnvkit
tebreak

17 packages built:

angsd
bcftools
bwa
deeptools
delly
htslib
megahit
mosdepth
nimPackages.hts-nim
platypus
python310Packages.HTSeq
python310Packages.bwapy
python310Packages.pysam
python39Packages.HTSeq
python39Packages.bwapy
python39Packages.pysam
samtools

@siraben: At least tebreak and octopus-caller build on my side (cnvkit is still running: it seems to be building openjdk from scratch). octopus-caller did need a lot of time and memory, so I wonder if maybe it timed out for you.
Unless I am missing something, non-static builds should not be affected at all.

Non-static is working for me on x86_64-linux:
1 package marked as broken and skipped:
truvari

2 packages failed to build:
python310Packages.cnvkit python39Packages.cnvkit

19 packages built:
angsd bcftools bwa deeptools delly htslib megahit mosdepth nimPackages.hts-nim octopus-caller platypus python310Packages.HTSeq python310Packages.bwapy python310Packages.pysam python39Packages.HTSeq python39Packages.bwapy python39Packages.pysam samtools tebreak

CNVKit failure is unrelated.
Static builds for prodigal, megahit, samtools, and BWA all working for me on x86_64-linux.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/is-it-possible-to-achieve-static-linking-with-musl-openmp/19253/1


complement(fn) reports wrong arity

var whereNeq = R.complement(R.whereEq);
whereNeq.length; // => 0

A side effect of this is that such a function doesn't play well with ``cond```.

This was inadvertently fixed in #1408.


Suggestion: Craftable Recipes only appear when recipe is unlocked.

I think that this would be a good feature to have for a more immersive experience

Closing this in place of #102 which has more of a description for the same idea.