documentation for Date doesn't list the parameters for the constructor

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details
I wanted to find out about the parameters for the Date constructor. The obvious place to look was here:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date#Constructor
but it doesn't even mention passing parameters. Just underneath in a different section it says "The value of Date.length is 7. This is the number of arguments handled by the constructor", but even the examples at the bottom only go up to a mxmimum of 6.
Specifically I wanted to find out what would happen if I passed in null or undefined. By experiment, the answer seems to be that passing in null is the same as passing in no parameters, but passing undefined throws an error)

The parameters of the Date() constructor are talked about in a lot more detail on the actual constructor page:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/Date
Does that give you the information you need? Always happy to add more details if you think something is missing.

Ah sorry, I think I was confused by the fact that the constructor's own page isn't listed in the left-hand navigator so I didn't originally find it.
so my main feedback is that it would be useful to include constructors in the navigator alongside the methods. This is what Microsoft do (e.g. https://docs.microsoft.com/en-us/dotnet/api/system.web.httpcontext), but I appreciate that's probably just the style of the MDN documentation so it would be a huge effort to update it all.
In terms of the actual constructor page, I don't see any problems. The fact that it links directly to the ECMAScript spec means it's perfect for pedants like me to find out what would happen if you pass in things like null or undefined.

Ah, I think it should be included in the sidebar. We'll have to look into that.
Glad we were able to help you in the end. I'll close this for now.


AssemblyLoadContext failing to load Microsoft.AspNetCore.Components

Here's a link to the code to reproduce the issue:  https://github.com/bryanenroute/assemblyloadcontext-issue
I can load a plugin (IModule) that resides in a basic .NET Core console application assembly, but fails to load a plugin/module that resides in an ASP.NET Core application assembly.
When the ASP.NET Core module goes through assembly resolution, I get LoaderExceptions:
"Could not load file or assembly 'Microsoft.AspNetCore.Components, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified."
Can you assist?

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

ID: 06023407-704f-0ace-e89a-eedd9f95a007
Version Independent ID: f25a6e1a-cb10-867b-0522-a377bf9d016b
Content: Create a .NET Core application with plugins - .NET Core
Content Source: docs/core/tutorials/creating-app-with-plugin-support.md
Product: dotnet-core
GitHub Login: @jkoritzinsky
Microsoft Alias: jekoritz

Thanks for your feedback @bryanenroute. @jkoritzinsky is this similar to issue #15156?

I think this one is different. This failure is because the ASP.NET Core plugin depends on the Microsoft.AspNetCore.App framework, but the core library only depends on the Microsoft.NETCore.App framework. Since the core library only has a framework reference to the Microsoft.NETCore.App framework, the host doesn't look for other frameworks when loading any assemblies.
cc: @vitek-karas we should open an issue for this in core-setup or transfer this issue there (I don't have the permissions to do so).


unexpected validation error when providing examples

Using OAS3
I am trying to add examples for good and bad requests (with the thought of eventually trying to use these to generate automated tests against my implementation). However, adding a proper example value generates a validation error with openapi-enforcer.
  /auth/login:
    post:
      summary: Login user
      operationId: login
      x-controller: auth
      x-operation: login
      tags:
        - Auth
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                username:
                  type: string
                password:
                  type: string
              required:
                - username
                - password
            examples:
              200:
                value: { "username": "testuser", "password": "testuser" }

Error: One or more errors exist in the OpenApi definition
  at: paths > /auth/login > post > requestBody > content > application/json > examples > 200 > value
    Properties not allowed: password, username
    at OpenApiEnforcerMiddleware.promise.Enforcer.then.result ([...]/openapi-enforcer-middleware/index.js:73:28)

I am following the 2nd syntax example provided here: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#example-object

Thanks the the bug report. This is fixed in version 1.2.5.


[npm] Upgrades 'inline-style-prefixer' to 3.0.8

Mentioned in this comment by @mbrookes in #9299.
This brings the legacy branch current with the inline-style-prefixer library.

Thanks, @mbrookes! 🎉


Multiple images viewer

Awesome lib!
It would be even more awesome if you could make it possible to view multiple images in a scroll view.
e.g.
images = [self getAllImages]; // array of images
[EXPhotoViewer showImagesFor:images];
then the original imageview stays at its old place but the other pretty effects still work (zooming, pull-back etc.) and you can view the images by just sliding left and right.
Very appreciate for all your great work!

Any news on this?

It is been 3 years since then. Any news? :D


[BUG] Update the preview in the readme

Has this bug been raised before?

[X] I have checked "open" AND "closed" issues and this is not a duplicate

Where did you find this bug?
GitHub
Description
The preview image is from the old design. We need to update it
Steps to Reproduce
If you know the steps, follow the below format and provide steps to reproduce
For example:

Go to Github page.

Screenshots

Do you want to work on this issue?
No
If "yes" to above, please explain how you would technically implement this
No response

Thank you 👍

Can you assign me this issue. I would like to take a screenshot from the current design of the website and integrate it to the README file.


Getting 400 - Header Content-Length has invalid value on uploadPhoto

I have a function which uploads the photo and returns the media.code from docs.
const upload_photo = async (client, path, caption, post) => {
  const { media } = await client.uploadPhoto({ photo: path, caption: caption, post: post});
  return media.code;
};

When I try to upload it from this function, I get this error message:
UnhandledPromiseRejectionWarning: StatusCodeError: 400 - "{\"debug_info\":{\"retriable\":false,\"type\":\"ParameterValidationError\",\"message\":\"Header Content-Length has invalid value\"}}"
Uploading my images from a path like this: ./path/to/my/image.jpg
Tried to changing caption length, didnt work. Whats wrong? Thank you.

I got The same issue, have you fixed that? maybe?

Sorry for late response,
I solved it with converting the image by buffer and uploading it as a buffer (which i got it in #206).


Fixes typo

Fixes typo when flashing an alert that "Something went wrong.".

Thanks for your contribution @alvincrespo!


Dependencies of flatpak applications aren't removed when uninstalling

When uninstalling a flathub application the dependencies are currently not being uninstalled, even if they aren't needed any other application.

This is really easy to fix (2 lines), but it is currently it would conflict with https://github.com/gamer-os/steam-buddy/pull/12. I'll make a pull request after that one is merged.

I did some research. This isn't as easy as I was expecting. The --unused option doesn't work when uninstalling a specific application. I'll close this one, since it shouldn't be a major issue anyway.


BUG: EOS locked by system contract - many voters' staked property <voters.staked> is less than total staked CPU/NET of the voter account, and leads to "stake for voting cannot be negative" assert when the voter account trying to unstake EOS.

Take an EOS account huangpanlong (who has 18.3154 EOS sadly locked) as an example:

cleos -u https://mainnet.eos.dfuse.io get table eosio eosio voters -L huangpanlong -l 1, will see in the voter table, huangpanlong has 40032.8596 EOS staked.

{
  "rows": [{
      "owner": "huangpanlong",
      "proxy": "aboringgame1",
      "producers": [],
      "staked": 400328596,
      "last_vote_weight": "442764385327593.43750000000000000",
      "proxied_vote_weight": "0.00000000000000000",
      "is_proxy": 0,
      "flags1": 0,
      "reserved2": 0,
      "reserved3": "0.0000 EOS"
    }
  ],
  "more": true
}

cleos -u https://mainnet.eos.dfuse.io get table eosio huangpanlong delband, will see in the deband table, huangpanlong actually staked 2.5000+ 40048.6750 = 40048.675 EOS:

{
  "rows": [{
      "from": "huangpanlong",
      "to": "huangpanlong",
      "net_weight": "2.5000 EOS",
      "cpu_weight": "40048.6750 EOS"
    }
  ],
  "more": false
}

cleos -u https://mainnet.eos.dfuse.io get table eosio eosio rexbal -L huangpanlong -l 1, will see in the rexbal table, huangpanlong has no rex staked.

{
  "rows": [{
      "version": 0,
      "owner": "huangpanlong",
      "vote_stake": "0.0000 EOS",
      "rex_balance": "0.0000 REX",
      "matured_rex": 0,
      "rex_maturities": []
    }
  ],
  "more": true
}

As all we know the stake formula, voters.staked ≈ delband.net_weight + delband.cpu_weight + rexbal.vote_stake (rexbal.vote_stake constantly updated via the action updaterex), which means  voters.staked >= delband.net_weight + delband.cpu_weight.
But for huangpanlong, the voters.staked: 40032.8596 EOS less than delband net&cpu weight: 40048.675 EOS, so there will be a 18.3154 EOS locked by voting system contract when huangpanlong trying to unstake CPU&NET more than 40032.8596 EOS.

Error
{
	"code": 500,
	"message": "Internal Service Error",
	"error": {
		"code": 3050003,
		"name": "eosio_assert_message_exception",
		"what": "eosio_assert_message assertion failure",
		"details": [{
			"message": "assertion failure with message: stake for voting cannot be negative",
			"file": "wasm_interface.cpp",
			"line_number": 964,
			"method": "eosio_assert"
		}, {
			"message": "pending console output: ",
			"file": "apply_context.cpp",
			"line_number": 113,
			"method": "exec_one"
		}]
	}
}

the assert code in system contract:
   void system_contract::update_voting_power( const name& voter, const asset& total_update )
   {
      auto voter_itr = _voters.find( voter.value );
      if( voter_itr == _voters.end() ) {
         voter_itr = _voters.emplace( voter, [&]( auto& v ) {
            v.owner  = voter;
            v.staked = total_update.amount;
         });
      } else {
         _voters.modify( voter_itr, same_payer, [&]( auto& v ) {
            v.staked += total_update.amount;
         });
      }
      check( 0 <= voter_itr->staked, "stake for voting cannot be negative" ); // HERE: the assertion
      if( voter == "b1"_n ) {
         validate_b1_vesting( voter_itr->staked );
      }
      if( voter_itr->producers.size() || voter_itr->proxy ) {
         update_votes( voter, voter_itr->proxy, voter_itr->producers, false );
      }
   }

As I inspected, the BUG happened a lot on those accounts who bought and sold rex, maybe they forgot to run updaterex action, but I also checked the code, rexbal.vote_stake also updated in buying and selling rex, so I failed to root cause the BUG by myself.
Please take the bug as high priority, I have found more than 600+ accounts has their EOS locked by system voting contract, and because I ignored the their rexbal staked, so there must be more EOS locked accounts than I searched, the attatchment is the list, Thanks!
voter-stake-error-accounts.txt

@shawnbow Did you also check the delband table for all other accounts that may have also staked on behalf of huangpanlong? "cleos -u https://mainnet.eos.dfuse.io get table eosio  delband" finds all of the accounts with a "from" equal to "", like if you do "cleos -u https://mainnet.eos.dfuse.io get table eosio eosio delband"

Sorry, this wouldn't account for any difference here, it would account for a difference on the other ("from") account (if there was one) that was staking on the "to" accounts behalf.

@brianjohnson5972
I wrote a typescript script with eosjs to check more accounts that have the problem, and I did check the delband table for all accounts that may have been staked on behalf of those accounts.
For example, this account: haztonrqhege:
root@ss:/opt# cleos -u https://mainnet.eos.dfuse.io get table eosio eosio voters -L haztonrqhege -l 1
{
  "rows": [{
      "owner": "haztonrqhege",
      "proxy": "proxy4nation",
      "producers": [],
      "staked": 1056150,  // 105.6150 EOS
      "last_vote_weight": "1282345165450.74853515625000000",
      "proxied_vote_weight": "0.00000000000000000",
      "is_proxy": 0,
      "flags1": 0,
      "reserved2": 0,
      "reserved3": "0.0000 EOS"
    }
  ],
  "more": true,
  "next_key": "7619978758482991264"
}
root@ss:/opt# cleos -u https://mainnet.eos.dfuse.io get table eosio haztonrqhege delband
{
  "rows": [{
      "from": "haztonrqhege",
      "to": "haztonrqhege",
      "net_weight": "0.2000 EOS",
      "cpu_weight": "114.2747 EOS" // cpu+net: 114.4747 EOS
    }
  ],
  "more": false,
  "next_key": ""
}

haztonrqhege has 114.4747 EOS staked on himself, but only has 105.6150 EOS voter-staked, which means when he tries to unstake more than 105.6150 EOS, he will get the "stake for voting cannot be negative" assert and 8.8597 EOS permanently locked sadly.
My script is located at: https://github.com/shawnbow/eosio-helper/blob/master/scripts/check_voter.ts, you can git clone https://github.com/shawnbow/eosio-helper/, and run ts-node ./scripts/check_voter.ts to get part of locked accounts.
Attached is some of those poor accounts, you can see an account has 90+ EOS locked, it's so terrible for him.
eos-stake-locked-accounts.txt

@brianjohnson5972
I could provide a fix for the issue as:
   void system_contract::update_voting_power( const name& voter, const asset& total_update )
   {
      auto voter_itr = _voters.find( voter.value );
      if( voter_itr == _voters.end() ) {
         voter_itr = _voters.emplace( voter, [&]( auto& v ) {
            v.owner  = voter;
            v.staked = total_update.amount;
         });
      } else {
         _voters.modify( voter_itr, same_payer, [&]( auto& v ) {
            v.staked += total_update.amount;
+            if (v.staked < 0) {
+              v.staked = 0;
+            }
         });
      }

      check( 0 <= voter_itr->staked, "stake for voting cannot be negative" );

      if( voter == "b1"_n ) {
         validate_b1_vesting( voter_itr->staked );
      }

      if( voter_itr->producers.size() || voter_itr->proxy ) {
         update_votes( voter, voter_itr->proxy, voter_itr->producers, false );
      }
   }

But I don't know whether it's the best solution, just for your reference.

I'm one of them. Account gy2danbvgyge. I get stake for voting cannot be negative when I try to unstake 0.259 eos. I know this is a very low value, but I wanted to let you know

@cic8ino , many accounts have much more than your locked EOS, but seems developers of EOSIO don't have time to fix the serious bug.

My understanding is that the rex sell order may not happen immediately.  Could you check the rexqueue table to see if there are any orders that haven't been processed or that are closed?

@TimothyBanks, I've checked rexqueue table, there is no order for those locked EOS accounts.

I am currently investigating the issue.


feat(frontend): Add Typing Indicator for Agent Response using Tailwind CSS

PR Summary
feat(frontend): Implement Animated Typing Indicator for Agent Responses
PR Description
Problem Statement and Solution
This PR addresses the need for visual feedback during agent response generation, enhancing user experience in the chat interface. It implements an animated three-dot typing indicator that appears when the agent is processing user input and generating a response.
Resolves: Issue #1787 - Display a loading indicator in the chat interface when waiting for a response from OpenDevin
Key Implementation Details

New Component: Introduced a TypingIndicator component (frontend/src/components/chat/TypingIndicator.tsx).
Styling: Utilized Tailwind CSS for efficient, inline styling of the typing indicator.
Integration: Updated ChatInterface.tsx to incorporate the TypingIndicator component, triggered when AgentState is RUNNING.

Design Decisions

Tailwind CSS: Chosen for its utility-first approach, allowing for rapid styling and easy maintenance directly within the component file.
Conditional Rendering: The typing indicator is displayed only when the agent is actively processing, ensuring a clean interface at other times.
Accessibility: Ensured the animation is subtle to avoid distracting users while still providing clear visual feedback.

https://github.com/OpenDevin/OpenDevin/assets/95778421/756c1f3a-8420-4c8d-b909-5a48898c9b21

Very nice. But you are mixing module css styles with TailwindCSS; try creating the animations with TailwindCSS instead, maybe with keyframes

Hmm you're asking a lot from an old man here 🤣
I'll look into it now 👍

phew... had to fix a self-made error but should be good to go now 😔

LGTM. Thanks!


[11.0] ISPN-12492 Server option to load property file

https://issues.redhat.com/browse/ISPN-12492

integrated! thanks @tristantarrant !


LSP not working?

I am able to install this extension within the app. I am able to use the tasks provided by the extension. But anything to do with syntax doesn't seem to work. No inline hints, No LSP errors.

Helps if you have the language server installed :/
nimble install nimlangserver

Not working to me as well. I have nimlangserver installed and correctly added to the path.

> nimlangserver --version
1.6.0

I've changed the zed_extension_api from 0.06 to 0.1.0 inside Cargo.toml and I`ve found no error after that.


After running download, there's nothing in the DB

This is what I tried:
$ yt-fts download --number-of-jobs 5 "https://www.youtube.com/channel/UCaxar6TBM-94_ezoS00fLkA"

This channel has something like 8.8k videos (quite a lot) so it took a good half hour to run. After running it, I run yt-fts list and no new channel is added.
As a sanity check, I then tried it against my own personal youtube channel (which has like, 20 videos, 3 of which had generated subs) and it worked fine and added the subtitles to the DB.
So something must be weird about this channel. As a sample of the log output:
I get tons of these, I figure this just means a video doesn't have subtitles:
WARNING: [youtube] vsJVEOLjRcM: nsig extraction failed: You may experience throttling for some formats
         n = mEPEUHKmGeMrduZp ; player = https://www.youtube.com/s/player/d60b0ef9/player_ias.vflset/en_US/base.js

I also get some of these (much less common):
ERROR: Did not get any data blocks
ERROR: Unable to download video subtitles for 'en': ERROR: Did not get any data blocks

And of course I get tons of these which I'm pretty sure are successful downloads:
[download] 100% of  112.96KiB in 00:00:00 at 1.27MiB/s -> NbuMCyvPJA8.en.vtt

But at the end, it just ended on a download, with no other output. I tried running the download twice, just in case I somehow did something wrong the first time, but nope it still didn't save the output the second time either.
I went through the DB with sqlite3 ~/.config/yt-fts/subtitles.db and none of the tables had any data at all except the config table with a couple default rows I guess. But channels and subtitles were empty.
All that said, I ended up using https://videomentions.com/search to find what I was looking for in a channel. But it would still be neat to get it working so I could do local searches in the future on this channel.

@francislavoie thanks for reporting this. Do you mind sharing the version you are on? you can find that by running yt-fts --version. I made recent changes to how the subtitles are parsed and that might be the culprit. Thanks.

I just installed it yesterday with pip so I assume the latest. Afk at the moment but will circle back ASAP

$ yt-fts --version
yt_fts version: 0.1.54

I'm having the same issue. I tried the README example with @3blue1brown and it worked, but then I tried with @godago and the captions weren't added to the database. I got some warnings like
WARNING: [youtube] uPjO5o6vgE8: nsig extraction failed: You may experience throttling for some formats
         Install PhantomJS to workaround the issue. Please download it from https://phantomjs.org/download.html
         n = AeShK02qVZmCyONL ; player = https://www.youtube.com/s/player/d60b0ef9/player_ias.vflset/en_US/base.js

and some python errors like
ERROR: Did not get any data blocks
ERROR: Unable to download video subtitles for 'en': ERROR: Did not get any data blocks
Traceback (most recent call last):
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 4331, in _write_subtitles
    self.dl(sub_filename, sub_copy, subtitle=True)
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 3180, in dl
    return fd.download(name, new_info, subtitle)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_dlp/downloader/common.py", line 466, in download
    ret = self.real_download(filename, info_dict)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_dlp/downloader/http.py", line 370, in real_download
    return download()
           ^^^^^^^^^^
  File "path/to/site-packages/yt_dlp/downloader/http.py", line 336, in download
    self.report_error('Did not get any data blocks')
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 1073, in report_error
    self.trouble(f'{self._format_err("ERROR:", self.Styles.ERROR)} {message}', *args, **kwargs)
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 1012, in trouble
    raise DownloadError(message, exc_info)
yt_dlp.utils.DownloadError: ERROR: Did not get any data blocks

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "path/to/venv/bin/yt-fts", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "path/to/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "path/to/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_fts/yt_fts.py", line 88, in download
    dl_status = download_channel(channel_id, channel_name, language, number_of_jobs, s)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_fts/download.py", line 272, in download_channel
    download_vtts(number_of_jobs, list_of_videos_urls, language, tmp_dir)
  File "path/to/site-packages/yt_fts/download.py", line 146, in download_vtts
    futures[i].result()
  File "path/to/lib/python3.12/concurrent/futures/_base.py", line 456, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "path/to/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "path/to/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_fts/download.py", line 168, in get_vtt
    ydl.download([video_url])
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 3583, in download
    self.__download_wrapper(self.extract_info)(
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 3558, in wrapper
    res = func(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 1595, in extract_info
    return self.__extract_info(url, self.get_info_extractor(key), download, extra_info, process)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 1606, in wrapper
    return func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 1762, in __extract_info
    return self.process_ie_result(ie_result, download, extra_info)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 1821, in process_ie_result
    ie_result = self.process_video_result(ie_result, download=download)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 2993, in process_video_result
    self.process_info(new_info)
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 3247, in process_info
    sub_files = self._write_subtitles(info_dict, temp_filename)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 4338, in _write_subtitles
    self.report_error(msg)
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 1073, in report_error
    self.trouble(f'{self._format_err("ERROR:", self.Styles.ERROR)} {message}', *args, **kwargs)
  File "path/to/site-packages/yt_dlp/YoutubeDL.py", line 1012, in trouble
    raise DownloadError(message, exc_info)
yt_dlp.utils.DownloadError: ERROR: Unable to download video subtitles for 'en': ERROR: Did not get any data blocks

apparently, yt_dlp is not finding subtitles in English for some of the videos.

The nsig extraction failed error was caused by this bug in the yt-dlp package, fixed by bumping the yt-dlp version to 2024.7.16. This is not what causes the program to skip vtt parsing although fixing it results in much more successful transcript downloads.
The problem is with the ERROR: Did not get any data blocks traceback from get_vtt which occurs unpredictably. This might be caused by a new rate-limiting method from YouTube as I was only able to trigger it after re-downloading the @godago channel a couple of times from the same IP. For some reason (probably related to multithreading) the program will continue to download the channel transcripts after this error occurs but then fail to insert the transcripts into the database.
I added a hotfix by wrapping the call to ydl.download([video_url]) in a try/except.

def get_vtt(tmp_dir, video_url, language):  # download

    try:
        ydl_opts = {
            'outtmpl': f'{tmp_dir}/%(id)s',
            'writeinfojson': True,
            'writeautomaticsub': True,
            'subtitlesformat': 'vtt',
            'skip_download': True,
            'subtitleslangs': [language, '-live_chat'],
            'quiet': True,
            'progress_hooks': [quiet_progress_hook]
        }

        with yt_dlp.YoutubeDL(ydl_opts) as ydl:
            ydl.download([video_url])

    except Exception as e:
        console.print(f"Failed to get: {video_url}\n{e}")

Ideally, we want a retry method or to avoid the rate limit altogether which could be possible with user agent randomization.

This should be resolved in v0.1.55.  I did not test on the given channel but did test on https://www.youtube.com/@GothamChess which has ~2k videos. Feel free to ping me if you still experience the error and I will reopen the issue. Thanks again for reporting this.

Thanks, running it now :hourglass:

I'm seeing stuff like this occasionally
ERROR: Did not get any data blocks
ERROR: Unable to download video subtitles for 'en': ERROR: Did not get any data blocks
[download]   15.00KiB at  151.07KiB/s (00:00:00)Failed to get: https://www.youtube.com/watch?v=zk96P3uTTdw
[1m[0;31mERROR:[1m[0m Unable to download video subtitles for 'en': [1m[0;31mERROR:[1m[0m Did not get any data blocks

WARNING: [youtube] Webpage contains broken formats (poToken experiment detected). Ignoring initial player response
WARNING: [youtube] API returned broken formats (poToken experiment detected). Retrying (1/3)...

It seems to run slower overall, maybe because of the retries? I suppose that would be expected.
Took about 2-2.5 hours to finish. That might be as expected :man_shrugging: but it did save properly this time!

A slower download would be expected because I think yt-dlp skips the video when nsig extraction failed is printed. The ERROR: Did not get any data blocks seems to be caused by rate limiting but it doesn't mean the video doesn't have a transcript. You can use the update command to add any videos missed by the first attempt
yt-fts update --number-of-jobs 8 --channel 1


Output from STDOUT is sometimes incomplete

In vistrails, connect a Queue to a PythonSource with the following contents:
print queue._call("printf 'ABCAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABBBBBBBBBBBBBCCCCCCCCCCCCCCCCCCCCCCCC%.0s\n' {1..40} | tail -n 40", True)[1]

When executed, sometimes not all output is printed. It seems like the collection of output from tail is interrupted for some reason.

Yes, I see the problem in the code, will fix shortly. _call() should never actually return enough data to trigger this though, output is always written to files...


TS2307 error when importing dependencies to TypeScript files

Which Category is your question related to?
Using TypeScript for Amplify functions (for a REST API).
Amplify CLI Version
4.23.1
What AWS Services are you utilizing?
Only one REST API with one lambda function.
Provide additional details e.g. code snippets
I am trying to migrate my existing Amplify REST API to TypeScript. Following the https://docs.amplify.aws/cli/function/build-options guide, I restructured my code directory and added a script to transpile my code prior pushing it to AWS. However, when executing the script (or using amplify push), I get TS2307 errors like the following one:
ts/app.ts:3:44 - error TS2307: Cannot find module 'aws-serverless-express' or its corresponding type declarations.
3 import awsServerlessExpressMiddleware from 'aws-serverless-express'

It seems like my external dependencies, which are installed in the function's package.json can not be resolved when using TypeScript.
Here is how me directory structure looks like:
amplify/backend/function/test
|- src
   |- node_modules
   |- event.json
   |- package-lock.json
   |- package.json <-- here the imported dependencies are installed
|- lib
   |- app.ts <-- here I'm trying to access the dependencies
   |- index.ts
|- tsconfig.json

I guess it is because the lib directory is outside the src directory where the package.json lives? That would mean Amplify's build options manual does not work when using any dependencies.
How can this be resolved?
Interesting side note:
It seems like only some of the dependencies can't be resolved: There are no issues with importing express and body-parser.
Thanks in advance.

@flogy yes, that's the root cause I think you are right. We'll check the above guide with external dependencies if there are some errors.
As a workaround I can share in one project here is how I used TS with external and shared dependencies:

in root package.json I had this entry:

"amplify:<functionName>": "cd amplify/backend/function/<functionName>/src && yarn && yarn build",

in the function's package.json I handled the local build of the package:

"build": "yarn clean && touch package.json && tsc && cp ./lib/* . && rimraf lib tsconfig.tsbuildinfo",
"clean": "rimraf tsconfig.tsbuildinfo lib ./index.d* ./index.js*"

here is my function structure:
.
├── function-parameters.json
├── <functionName>-cloudformation-template.json
└── src
    ├── node_modules
    ├── package.json
    ├── src
    │   └── index.ts
    ├── tsconfig.json
    └── yarn.lock

tsconfig.json
{
  "compilerOptions": {
    "target": "ES6",
    "rootDir": "src",
    "outDir": "lib",
  },
  "references": [
  ],
  "exclude": [
    "**/lib/**/*"
  ]
}

Let me know if this helps to resolve your problem.

@flogy yes, that's the root cause I think you are right. We'll check the above guide with external dependencies if there are some errors.
As a workaround I can share in one project here is how I used TS with external and shared dependencies:

in root package.json I had this entry:

"amplify:<functionName>": "cd amplify/backend/function/<functionName>/src && yarn && yarn build",

in the function's package.json I handled the local build of the package:

"build": "yarn clean && touch package.json && tsc && cp ./lib/* . && rimraf lib tsconfig.tsbuildinfo",
"clean": "rimraf tsconfig.tsbuildinfo lib ./index.d* ./index.js*"

here is my function structure:
.
├── function-parameters.json
├── <functionName>-cloudformation-template.json
└── src
    ├── node_modules
    ├── package.json
    ├── src
    │   └── index.ts
    ├── tsconfig.json
    └── yarn.lock

tsconfig.json
{
  "compilerOptions": {
    "target": "ES6",
    "rootDir": "src",
    "outDir": "lib",
  },
  "references": [
  ],
  "exclude": [
    "**/lib/**/*"
  ]
}

Let me know if this helps to resolve your problem.

Hi @attilah
Thank you very much for your workaround. I was not able to get it to run though, but it inspired me to build another workaround:
<functionName>
├── function-parameters.json
├── .gitignore <-- to ignore the generated contents of the `src` directory
├── src <-- empty, but needs to exist to make `amplify push` work
└── ts
        ├── node_modules
        ├── src <-- containing my `index.ts` and other TypeScript source files
        ├── event.json
        ├── package-lock.json
        ├── package.json
        └──  tsconfig.json

.gitignore
/src/*

tsconfig.json
{
  "compilerOptions": {
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "lib": ["dom", "esnext"],
    "module": "CommonJS",
    "moduleResolution": "node",
    "skipLibCheck": true,
    "resolveJsonModule": true,
    "outDir": "../src",
    "baseUrl": "./",
    "rootDir": "./src",
    "paths": {
      "src": ["./src"]
    }
  }
}

function package.json
"scripts": {
    "build": "npm run clean && tsc && copyfiles -e '**/*.ts' -e 'tsconfig.json' '**/**' ../src",
    "clean": "rimraf ../src/*"
  },

project package.json
"scripts": {
    "amplify:<functionName>": "cd amplify/backend/function/<functionName>/ts && npm install && npm run build && cd -"
  },

This resolved my problem.
It would still be awesome though if an easier solution for external dependencies could be documented in the Amplify CLI docs.
Thanks for your nice support!

Hi @attilah
Thank you very much for your workaround. I was not able to get it to run though, but it inspired me to build another workaround:
<functionName>
├── function-parameters.json
├── .gitignore <-- to ignore the generated contents of the `src` directory
├── src <-- empty, but needs to exist to make `amplify push` work
└── ts
        ├── node_modules
        ├── src <-- containing my `index.ts` and other TypeScript source files
        ├── event.json
        ├── package-lock.json
        ├── package.json
        └──  tsconfig.json

.gitignore
/src/*

tsconfig.json
{
  "compilerOptions": {
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "lib": ["dom", "esnext"],
    "module": "CommonJS",
    "moduleResolution": "node",
    "skipLibCheck": true,
    "resolveJsonModule": true,
    "outDir": "../src",
    "baseUrl": "./",
    "rootDir": "./src",
    "paths": {
      "src": ["./src"]
    }
  }
}

function package.json
"scripts": {
    "build": "npm run clean && tsc && copyfiles -e '**/*.ts' -e 'tsconfig.json' '**/**' ../src",
    "clean": "rimraf ../src/*"
  },

project package.json
"scripts": {
    "amplify:<functionName>": "cd amplify/backend/function/<functionName>/ts && npm install && npm run build && cd -"
  },

This resolved my problem.
It would still be awesome though if an easier solution for external dependencies could be documented in the Amplify CLI docs.
Thanks for your nice support!


Automating Emails with SMTP For Secret Santa project

[X] My project tutorial topic has already been aproved by the Codédex team
[X] My project tutorial file renders properly in mdx
[X] The content written is my own, and not plagiarized from other sources
[X] All code written is commented or documented thoroughly
[X] I have already completed a self-review of the project tutorial
[X] I will comply with changes from the Codédex team about my project tutorial

Hey @Bobliuuu!
Fantastic work with the project tutorial. Can we update all the images to use the <RoundedImage /> component? Here's a project tutorial for your reference. We'll also need to update the CONTRIBUTING.md file to explain the use of this component for images.


[13.0] ISPN-13465 Update server config examples in YAML and JSON

Backport for https://issues.redhat.com/browse/ISPN-13465

Merged


Test for #195  Postback action writes to the chat window

Adding tests for imBack and postBack buttons.. Notice that postBack
button test currently will fail because we are expecting no echo: for
postBack, but there is a bug postBack will return echo:

@photodesignch,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

linked to #195


Transfer a large amount of data will crash the docker daemon

When I attach the container stdout and transfer a large amount of data, docker daemon crashed ,and I get error log of docker daemon.
INFO[0378] POST /v1.19/containers/create
ERRO[0378] Couldn't run auplink before unmount: fork/exec /sbin/auplink: cannot allocate memory
ERRO[0378] Couldn't run auplink before unmount: fork/exec /sbin/auplink: cannot allocate memory
DEBU[0378] Calling POST /containers/{name:.*}/attach
INFO[0378] POST /v1.19/containers/743fd2471a0be51700b0fbc0e5cea53cb2840da5b0e91d12452743f052840ac4/attach?stderr=1&stdin=1&stdout=1&stream=1
DEBU[0378] attach: stdin: begin
DEBU[0378] attach: stdout: begin
DEBU[0378] attach: stderr: begin
DEBU[0378] Calling POST /containers/{name:.*}/start
INFO[0378] POST /v1.19/containers/743fd2471a0be51700b0fbc0e5cea53cb2840da5b0e91d12452743f052840ac4/start
ERRO[0378] leaving endpoint failed: a container has already joined the endpoint
ERRO[0378] Couldn't run auplink before unmount: fork/exec /sbin/auplink: cannot allocate memory
ERRO[0378] Handler for POST /containers/{name:.*}/start returned error: Cannot start container 743fd2471a0be51700b0fbc0e5cea53cb2840da5b0e91d12452743f052840ac4: namespace creation reexec command failed: fork/exec /usr/bin/docker: cannot allocate memory
ERRO[0378] HTTP Error                                    err=Cannot start container 743fd2471a0be51700b0fbc0e5cea53cb2840da5b0e91d12452743f052840ac4: namespace creation reexec command failed: fork/exec /usr/bin/docker: cannot allocate memory statusCode=500
DEBU[0378] Closing buffered stdin pipe
DEBU[0378] attach: stdin: end

You can run these test cmds:
docker run -i --log-driver=none ubuntu dd if=/dev/zero of=/proc/self/fd/1 bs=1M count=1000

docker run -i --log-driver=none ubuntu yes hellwflwejfwefklefjkejfkejfkejfigjrijgrijgijfejfejfjejfefjefjeijfiejfiejfiejfijeifjeifjeijfiejfiej >> hello.txt

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

We suspect docker daemon is leaking memory somewhere copying stdout to hijack connection.

According to your error message, you just run out of memory.

@hqhq I have 4G memory (3G for free), but dd just generate 1G data ,why run out of memory ?

@hqhq
The problem we are describing is that  there seems to be memory bloating issue in docker daemon when executing commands that outputs huge amounts of data, (Even without enabling logging)  This is a issue for us because we are trying to replace a command SSH with docker exec.

Yes, I see the problem, I'm investigating now.

Just see this issue, the reason is that https://github.com/docker/docker/blob/master/pkg/ioutils/readers.go#L76 the buf is a variable-sized buffer, so https://github.com/docker/docker/blob/master/pkg/ioutils/readers.go#L187 will keep on writing to this buf until the memory run out.

including @unclejack in this conversation as he's currently working on some memory related issues
ping @unclejack ^^

In normal the buf will not keep on growing because some process will read from the buf and clear the buf, but at this scenario docker run -i --log-driver=none ubuntu yes hellwflwejfwefklefjkejfkejfkejfigjrijgrijgijfejfejfjejfefjefjeijfiejfiejfiejfijeifjeifjeijfiejfiej >> hello.txt the data will write to buf first and then write to the disk, but the speed write to disk is much slower than the container write to the buf, so the buf keep on growing until the memory run out.

@thaJeztah Thanks for the ping!
@coolljt0725 Yes, this is a known problem right now. The fix will be quite complicated and it needs to be done after the other major problems with memory usage are fixed. I've got to try out some ideas and propose a fix which doesn't impact performance in any way.
That unbounded and endless buffer growth has been fixed for non-degenerate cases (long running containers which write 0.1-100 KB/s to stdout/stderr).
This scenario with a flood is the last issue which needs to be fixed as far as I know.

An interesting observation is that if we enable pty, docker will not crash .
docker run -it --log-driver=none ubuntu yes hellwflwejfwefklefjkejfkejfkejfigjrijgrijgijfejfejfjejfefjefjeijfiejfiejfiejfijeifjeifjeijfiejfiej >> hello.txt
My guess is that PTY have some sort of flow control, is that the case ?

@unclejack  Another thing is that the memory is not immediately released upon docker run -i --log-driver=none ubuntu dd if=/dev/zero of=/proc/self/fd/1 bs=1M count=1000 finishes,  Which cause next run to use up memory, (is it because of we rely on golang GC?)

@thefallentree Memory isn't released immediately because of Go's GC.

@unclejack  which is a problem for us, as we are expecting to launch/destroy many commands which output quite a bit of content to stdout/stderr.  With current implementation, it is likely we need to triple the memory usage (1 in process before writing out, 1 in docker daemon , 1 in client reading) , which is ... a lot.

@unclejack  on a side note, we are currently executing these commands through SSH,  switching to docker exec make it easier to specify resource constraints on these commands (and better balancing etc), but apparently it is causing all these issues.
Can you also comment on the PTY thingy?

@thefallentree I'm going to look into this and comment afterwards on that. Please keep in mind I'll have to work on this before being able to provide a fix.

@unclejack could you take this bug?

Chiming in as I've just been hitting this while applying the following pretty useful pattern:
docker run --log-driver=none --rm <build-image> bash -xec '
  (git clone some/repo && make)>&2
  tar c build/
' | tar xv

i.e., run a tarball-producing command in an ephemeral container, using standard output to route that to a matching tar on the client side.
I'm mentioning that in case a reasonable use-case was needed to justify "flooding" stdout.
Seen from my window, blocking the contained process's writes to stdout seems perfectly reasonable and consistent with what would happen if I replaced docker run … bash above with a ssh … bash equivalent. In fact, I can see only three alternatives for dealing with a reader that reads slower than the container can generate data:

buffer it with no limit (current solution, which quickly leads to out-of-memory errors)
buffer within a reasonable limit, then block (basically what UNIX pipes do)
buffer within a reasonable limit, then drop data

Based on my experience, I would favor capping the daemon's transfer buffer to a reasonable value (a couple megabytes at most, particularly if this is to be multiplied by the number of active clients) and blocking stdout/stderr once that fills up ; and yet @unclejack , in https://github.com/docker/docker/issues/9139#issuecomment-87323320 you mentioned that "Some applications don't handle [getting blocked on stdout or stderr] properly and they crash." I find this surprising (any file descriptor can be expected to block at least some of the time!) but I guess this means Docker would need some kind of flag to support both scenarios: an app that is OK with blocking and wants to spit out lots of data, vs one that absolutely must not be slowed down. Right?

#16190 will help improve this.

Thanks @unclejack for the pointer. I'll go ahead and build #16190 to see if it improves my workloads. I'm still a bit puzzled that you would resist capping the buffer, given that the alternative is crashing the daemon (or making it so big that it can't fork anymore, which is pretty much the same for practical purposes). But I'll defer to your experience on the matter.
Do you have examples in mind of applications that would behave badly given a blocked stdout/stderr, as you alluded to in https://github.com/docker/docker/issues/9139#issuecomment-87323320? I'd like to help: would testing those with various alternative buffering strategies be useful?

@jonathanperret I'm not opposed to it in general, just opposed to making too many changes at once. The goal is to see if #16190 is 100% OK and take it from there as far as I'm concerned.

Understood, sounds like a good plan. Thanks for the clarification.

Fixed in #17877
Feel free to try master builds!


Didn't know you had to move the wormc binary as well.


New Hubot Slack app

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/fabric8-quickstarts-master-pullreq/599/
Test PASSed.


Support dataflow unit and configurable page title

Support dataflow curriculum unit [#167254016]{304}
Support unit authoring of browser page title [#167150604]{294}

Right, for now this is the simplest Dataflow curriculum that I believe will work. Later we can remove additional constraints (like sections) as appropriate.


Improve loading and allow accent change/removal

inspired by Add null accent, to allow accents to be removed #385
call airline#parts#define_accent('mode', 'red')
call airline#parts#define_accent('mode', '')
can be directly in .vimrc or called via autocmd vimEnter *

is there anything particular about your changes to the initialization that is required for the null accenting to work?  i'm a little hesitant to merge changes in this area because any time there are changes here it inevitably breaks the plugin in some weird way for someone.

in #385 you wrote

this is a simple PR, but i wanted to use it as a catalyst for fixing how the initialization of airline works. specifically, this falls into the area where if you place your config change outside an VimEnter autocmd, it works, or if you place the config inside the VimEnter, it doesn't work, or vice versa. i'd like to come up with a consistent way for configuring these things that is less order dependent....

So I made it work for that usecase ie you can add it in your .vimrc in VimEnter or outside.
Without that it feels too 'buggy'

does this fix a bug?


Rollback on failed GPU deployments doesn't work

Description
I tried to deploy a FullVM with a GPU option enabled and deployment failed due to network issue as seen in the logs, then I tried to re-deploy but failed cause there's another deployment was the same name (Failed previous deployment).

After refreshing.

This issue is duplicate according to https://github.com/threefoldtech/tfgrid-sdk-ts/issues/695

should be fixed in #751

Verified in https://github.com/threefoldtech/tfgrid-sdk-ts/issues/695#issuecomment-1632290538


Add Proxmox installation guide

fixes #3324
@cercatrova21 PR ready to merge?

@rootzoll yes ready to merge

Hi, how would the raspiblitz VM handle a shutdown signal from the proxmox VE (in case of low laptop/UPS battery power for example)? The desired behavior would be that it would trigger blitz.shutdown.sh to run, but I don't know if this is the case currently.
Maybe a solution could be to run blitz.shutdown.sh with systemd right before shutdown of the raspiblitz VM? ()?


error compiling interface that inherits both a member and the member's refinement

With https://github.com/ceylon/ceylon-sdk/commit/3915b5acd70a4fe0be96ebbc537d188a396b6909, the following:
import ceylon.collection {
    MapMutator
}

interface MyMap<out Key, out Item>
        satisfies Map<Key, Item>
        given Key satisfies Object {
    // inherits "Map<Key,Item> Map<Key, Item> clone()"
}

interface MyMapMutator<in Key, in Item>
        satisfies MapMutator<Key,Item> & MyMap<Object,Object>
        given Key satisfies Object {
   // inherits "MapMutator<Key,Item> MapMutator<Key, Item> clone()"

   // workaround is:
   //shared actual formal MyMapMutator<Key, Item> clone();
}

results in:
$ ceylon compile
source/simple/run.ceylon:5: error: $clone() in MyMapMutator clashes with $clone() in MapMutator
interface MyMap<out Key, out Item>
^
  return type Map<? extends Object,? extends Object> is not compatible with MapMutator<? super Key#2,? super Item#2>
  where Key#1,Item#1,Key#2,Item#2 are type-variables:
    Key#1 extends Object declared in interface MapMutator
    Item#1 extends Object declared in interface MapMutator
    Key#2 extends Object declared in interface MyMapMutator
    Item#2 extends Object declared in interface MyMapMutator
1 error
warning: manifest attribute provided by compiler: ignoring value from 'Bundle-Version' for module 'simple'
Note: Created module simple/1.0.0
ceylon compile: There was 1 error

Note: the example does compile if MyMapMutator instead satisfies MyMap<Object, Anything>, but using Object for the Item type arg is intentional.

This bug is caused(*) by:

TypeDeclaration.getMember() not always returning the best refinement (furthest from Anything), and
The backend apparently relying on getMember() to determine covariant returns of supertypes

Regarding item 1, in this case, getMember() "skips over" MapMutator.clone(), since, per the logic of getMember(), MapMutator<K,I> is not a subtype of all possible Map<K,I>s, but only Map<Object, I>s, so it is not considered a subtype at all, and its members aren't considered valid refinement's of Map's members.
A second example of this is:
interface I<out T> {
    shared formal T | Integer item;
}

interface J satisfies I<Float> {
    shared actual default Float item => 1.0;
}

interface K<T> satisfies I<T> & J {}

// GetItem() in simplebug.K clashes with getItem() in simplebug.J
// return type java.lang.Object is not compatible with ceylon.language.Float

where K.getMember(item) will return I.item, "skipping over" J.item which refines the return type.
And a third example, more closely resembling the original:
interface E1<out T> {
    shared default E1<T> clone() => this;
}

interface E2 satisfies E1<Object> {
    shared actual E2 clone() => this;
}

interface E3<T> satisfies E1<T> & E2 {
}
// $clone() in simplebug.E3 clashes with $clone() in simplebug.E2
// return type simplebug.E1<? extends T> is not compatible with simplebug.E2

and finally, a simplified version of the original test case:
interface MyMapMutator<in Key, in Item>
        satisfies MapMutator<Key,Item> & Map<Object,Object>
        given Key satisfies Object {

    // $clone() in simplebug.MyMapMutator clashes with $clone() in ceylon.collection.MapMutator
    // return type ceylon.language.Map<? extends java.lang.Object,? extends java.lang.Object> is not compatible with ceylon.collection.MapMutator<? super Key,? super Item>
}

(*) I confirmed this by using an experimental implementation of getMember() that disregards type parameters (thereby always considering, e.g., MapMutator to be a subtype of Map), and all test cases compiled without error.


What is client id

Hi @tmyroadctfig ,
Please clarify to me, What is client id and how can I get it.

I just used a random GUID in the code I'm using this library from. Here is how they do it over in the original library:
https://github.com/picklepete/pyicloud/blob/ced8e83a40764438b9f0de7f441b932411aaac97/pyicloud/base.py#L123

Thanks @tmyroadctfig


1.5.4 mac update asks admin password

Updating from 1.5.3 to 1.5.4 asks for the administrator password.
This should not be required when AsciiDocFX is installed in a non-privileged directory.
Neither 1.5.2 installation nor 1.5.3 update asked for it.

Hi @mildis, installer needs to remove old installation directory, i got many feedback there is a duplication problem, so i requested to get root privilege for the installer.

The duplication issue (1.5.2. to 1.5.3) appeared on the update because 3 jars from the old version stay concurrently in the new version.
However, it happened even when the application was inside an unprivileged directory.
It looks more like an updater logic issue than a permission issue.
Even after giving the admin password, I get a warning about AsciidocFX-1.5.3.jar and AsciidocFX-1.5.4.jar being duplicated in the app bundle.
From 1.5.2 to 1.5.3, the issue was about asciidocfx, plantuml and terminalfx jars.

Thank you @mildis, this issue bored me too much however it is related to the installer. Does AsciidocFX want admin password on startup or is it only for installation time?

For my first installation (1.5.2), I installed it in an unprivileged directory. It asks no password.
When upgrading from 1.5.2 to 1.5.3, it asked no password but I ended with duplicated jars.
When upgrading from 1.5.3 to 1.5.4, it asks for a password when running the installer-updater process : it does not ask for a password when starting.

I got back asking password right now, it is available in v1.5.5

The directory layout has changed so update from 1.5.4 to 1.5.5 did not show up.
Had to install 1.5.5 by hand.
I’ll see when 1.5.6 will be out.


Navigation gestures should ignore Stylus and Apple Pencil

In iOS it is standard for the UI to ignore Apple Pencil input in navigation gestures, like swiping back, or in some cases (drawable canvases) scrolling.
I assume this would be potentially dependent on #38135

Hi @kerberjg
I'm inclined to see you issue more specific to the gestures and navigation aspect
and more generic towards all types of stylus.
Thank you
(I'm aware that the plural of Stylus is "styli", but it might be confusing)
https://github.com/flutter/flutter/issues/42846

I can investigate if this is how the native apps behave, since I do not have such certainty at the moment. I will get back with some test results within the next few days


Add previews and deploys to Sakha transliterator app

Initially GitHub Pages only, but then PyPI, etc. alongside maybe mobile apps

We'll concentrate our efforts on another starting point for our NLP library, so closing this one.


Getting error message with "cannot import name 'DATA_RESTORE_STATE' "

Installed pyscript manually by copying manually into custom_component from git branch main. Getting following error from basic validation of configuration.yaml
Component error: pyscript - cannot import name 'DATA_RESTORE_STATE' from 'homeassistant.helpers.restore_state' (/usr/src/homeassistant/homeassistant/helpers/restore_state.py)
likely linked to https://github.com/custom-components/pyscript/commit/716ffd7f88a0f69cf395a3a62678758775115861
as when I check out an older version it works fine.

What version of HA are you running?

Same problem with HA 2022.6.7.

Ok, thanks for reporting the failing version.  Seems like that commit broke backward compatibility.  Any chance you can upgrade to a more recent HA version?

just got the same: Home Assistant 2023.5.4

Thx... done.

Simona
Il giorno mar 10 ott 2023 alle ore 18:29 Craig Barratt <
@.***> ha scritto:

A workaround would be to run the prior version of pyscript if you have an
older verison of HA.
—
Reply to this email directly, view it on GitHub
https://github.com/custom-components/pyscript/issues/483#issuecomment-1755798724,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ5PBXLXWA6IVYKX4KBCMUTX6VZXNAVCNFSM6AAAAAA2B6ADW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJVG44TQNZSGQ
.
You are receiving this because you commented.Message ID:
@.***>


Create WBUT.txt

pls check

@rajiv3269 I am sorry, it is still not correct. The file path shall be lib/domains/in/ac/wbut.txt, not the content. The content of the file (i.e. a signle line in the file) shall be
West Bengal University of Technology
Thank you!

@rajiv3269 I am sorry, this request remains unanswered for a while. I close it without merging. If you still wish to submit this domain to the repository, please submit a request with the file lib/domains/in/ac/wbut.txt, which contains one line:
West Bengal University of Technology
Thank you!


OpenAttestationDidSignedDocumentStatus verifier throws Cannot read property 'blockTag' of undefined

Thanks for all the work on open-attestation! As the title reads, the OpenAttestationDidSignedDocumentStatus verifier throws an 'Cannot read property 'blockTag' of undefined' error on signed documents. The documents passed in have no issue being verified on https://dev.tradetrust.io/ or https://dev.opencerts.io/.
Below is a reproducible example:
const {
  verificationBuilder,
  openAttestationDidSignedDocumentStatus,
} = require('@govtechsg/oa-verify');
const {
  wrapDocument,
  signDocument,
  SUPPORTED_SIGNING_ALGORITHM,
} = require('@govtechsg/open-attestation');

const verify = verificationBuilder([openAttestationDidSignedDocumentStatus], {
  network: 'ropsten',
});

const main = async () => {
  const document = {
    issuers: [
      {
        id: /*REPLACE THIS*/,
        name: 'Demo Issuer',
        revocation: {
          type: 'NONE',
        },
        identityProof: {
          type: 'DNS-DID',
          location: /*REPLACE THIS*/,
          key: /*REPLACE THIS*/,
        },
      },
    ],
  };

  const wrappedDocument = wrapDocument(document);
  const signedDocument = await signDocument(
    wrappedDocument,
    SUPPORTED_SIGNING_ALGORITHM.Secp256k1VerificationKey2018,
    {
      public: /*REPLACE THIS*/,
      private:
        /*REPLACE THIS*/,
    }
  );
  const fragments = await verify(signedDocument);
  console.log(fragments);
};

main();

Results in:
[
  {
    name: 'OpenAttestationDidSignedDocumentStatus',
    type: 'DOCUMENT_STATUS',
    data: TypeError: Cannot read property 'blockTag' of undefined
        at S.resolve (/Users/kierian/Desktop/oa-verify-test/node_modules/ethr-did-resolver/lib/index.umd.js:1:11817)
        at /Users/kierian/Desktop/oa-verify-test/node_modules/did-resolver/lib/resolver.js:1:2147
        at r.t [as cache] (/Users/kierian/Desktop/oa-verify-test/node_modules/did-resolver/lib/resolver.js:1:568)
        at /Users/kierian/Desktop/oa-verify-test/node_modules/did-resolver/lib/resolver.js:1:2121
        at r.resolve (/Users/kierian/Desktop/oa-verify-test/node_modules/did-resolver/lib/resolver.js:1:2259)
        at /Users/kierian/Desktop/oa-verify-test/node_modules/@govtechsg/oa-verify/dist/cjs/did/resolver.js:84:58
        at step (/Users/kierian/Desktop/oa-verify-test/node_modules/@govtechsg/oa-verify/dist/cjs/did/resolver.js:44:23)
        at Object.next (/Users/kierian/Desktop/oa-verify-test/node_modules/@govtechsg/oa-verify/dist/cjs/did/resolver.js:25:53)
        at /Users/kierian/Desktop/oa-verify-test/node_modules/@govtechsg/oa-verify/dist/cjs/did/resolver.js:19:71
        at new Promise (<anonymous>),
    reason: {
      message: "Cannot read property 'blockTag' of undefined",
      code: 1,
      codeString: 'UNEXPECTED_ERROR'
    },
    status: 'ERROR'
  }
]

package.json:
{
  "name": "oa-verify-test",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "@govtechsg/oa-verify": "^7.4.1",
    "@govtechsg/open-attestation": "^5.2.2"
  }
}

Codesandbox:
https://codesandbox.io/s/jovial-gould-8h8eg?file=/index.js

Hi there, thanks for pointing out this issue.
After some amount of investigation, we discovered that one of our dependencies ethr-did-resolver has a breaking interface change between 3.0.3 and 3.1.0.
currently we allow minor versions for this particular dependency, but I have just pushed up a fix to pin the dependency to 3.0.3.
once that is up, the error should go away.


Documentation for AzCLI to acknowledge Incomplete Data Factory Functionality

Considering #18536's request for az datafactory dataflow commands is in a backlog and is not currently supported... Can there be an explicit call out in the documentation that:
a.) Notes that there is not 100% supported feature parity across AzCLI and its Powershell counterpart, or
b.) At a minimum calls out that dataflow commands are not supported (yet/currently)? And point to the Powershell documentation?

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

ID: da110bf9-e979-a0fd-65b0-55ac6cae2077
Version Independent ID: d2a9d97c-07f7-108c-06cd-8913c89bd041
Content: az datafactory
Content Source: latest/docs-ref-autogen/datafactory.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

route to CXP team

https://github.com/MicrosoftDocs/azure-docs-cli/pull/3303 @yonzhan - The documentation has been updated :D Still will work on getting the data flow functionality working.


Spawn ego-vehicles and other vehicles randomly

Hi, I am running a multi-agent project on highway-v0. Say that I have 5 controlled ego-vehicles, then they all spawn in a cluster at the beginning of the road. I would like them to spawn randomly, with a probability that other vehicles(not controlled) spawn in between them. Is this possible? Thanks, Mikael.

Hi @Mikael-OLS,
That should not be too difficult to modify.
I think that at the moment, I spawn every new vehicle at the front of the current traffic. I start with the N controlled vehicles, and then proceed to the M other vehicles.
It suffices to change the order and insert M/N other vehicles after each controlled vehicle.


Running ./whitelist.sh locks pi-hole server hard locks computer

I am running Pi-Hole on a Ubuntu Server 18-04.02 LTS server with 2 Gig of ram, 60 gigs hard drive, 2 logical hard drives in VMWARE ESX-i 6.5. When I attempt to run the whitelist script. It will attempt  rebuild the gravity list and the computer will completely lock up.   I am unable to get to it using console or ssh. I have to hard reboot the unit in order to gain access again.

Do you have large lists on pi-hole?
If you run pihole -g on the server will it lock up.

I have a stock install of Pi-hole on a ubuntu virtual machine. I wasn't running any custom white lists or black lists. I have noticed the that instance of pihole was crashing with pihole -up and pihole -g. I have reinstalled the operating system and made sure it was patched correctly. I was getting the same issue on 18-04 of ubuntu. I have reinstalled with 16-04 ubuntu and it seems to be working correctly. I think there is an issue with the way 18-04 is running causing it to lock u

@naota2k3 @naota2k3 thanks for the input. I also have pi-hole installed on 16.04 in an AWS instance. Anyways I will check the 18.04.


Dynamic determination of queue

Would be great if we could specify a queue based on resources (like mem_mb, gpu, ...).

@johanneskoester We have not addressed this — yet.  Meanwhile, I see the slurm-gustave-roussy integrated into the catalogue. This is a bit unfortunate because it is a one-cluster only solution, and we loose maintainability or feature completeness, if we further support the proliferation of cluster plugins for one batch system. On the other hand, though, we strive to provide a convenient UI. One without the need to write complex profiles for every cluster.
An idea presumably similar to yours has been discussed (see #106). I elaborated, that this is nice to have, but difficult to implement because every cluster is different and SLURM allows coding additional plugins, which in turn allow having similar features addressed by different user syntax. If you've got time, either next week or (better) after my holidays.


" Always on Top" feature  , please!

Hello
please add this feature : " always on top"

What's always on top?

Ui?!
Always on top of other windows?!


Update baseboxes to latest Jammy 22.04.3 / Focal 22.04.6 .iso images (published as v23.1021.1)

Update baseboxes to latest Jammy / Focal .iso images and add support for building with VirtualBox 7.x / VMware Fusion 13.x support:

Update to latest Jammy Jellyfish 22.04.3
Update to latest Focal Fossa 20.04.6
Set VirtualBox --nat-localhostreachable1==on (for compatibility with VirtualBox 7.x)
Set VMware ethernet virtualDev to "e1000" by default (for compatibility with VMware Fusion 13.x)

All the boxes (22.04, 20.04, 18.04) have been rebuilt and published for vmware|virtualbox|parallels providers here:

https://app.vagrantup.com/tknerr/boxes/ubuntu2204-desktop/versions/23.1021.1
https://app.vagrantup.com/tknerr/boxes/ubuntu2004-desktop/versions/23.1021.1
https://app.vagrantup.com/tknerr/boxes/ubuntu1804-desktop/versions/23.1021.1

Note: the boxes were built with the following tools versions:

Hypervisors:

VMWare Fusion Pro 13.0.2
VirtualBox 7.0.12 with ExtensionPack 7.0.12
Parallels Desktop 19.1.0

Tools:

Packer 1.9.4, with the following plugins:

packer plugins install github.com/hashicorp/vmware v1.0.10
packer plugins install github.com/hashicorp/virtualbox v1.0.5
packer plugins install github.com/Parallels/parallels v1.1.5

Vagrant 2.4.0, with the following plugins:

vagrant plugin install vagrant-vmware-desktop 3.0.3
vagrant plugin install vagrant-parallels 2.4.1

Vagrant VMware Utility 1.0.22

Merging, as the boxes have been published already. Further PRs to follow.
/fyi @fasmat


Email input placeholder text doesn't translated

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to the about page https://matters.news/about
Scroll down to the bottom

Expected behavior
should be translated correctly
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Close it since fixed.


Fixed point arithmetic and Data.Fixed

Describe the feature you'd like
Haskell has long enjoyed convenient fixed point arithmetic with Data.Fixed.
However, we cannot use Data.Fixed cannot use parametric precision at the moment, since the type with kinded argument is not supported.
Describe alternatives you've considered
Alternatives considered are:

request support for kinded argument
template haskell derivation of alternative Data.Fixed for each resolution
manually implement each case

Describe the approach you would take to implement this
Since fixed point arithmetic comes in many financial applications, I would like suggestions on the best way to tackle this problem in the long run.
Additional context / screenshots

Ledger.Ada datatype is best example of how each such type needs to be implemented manually.

Yeah, it's annoying that Data.Fixed is poly-kinded. That won't be supported any time soon. Manually implementing the N versions might be the simplest solution.

Closing as a duplicate of #4537.


Unify onnx and JIT resize implementations

This PR unifies the two separate implementations of resize used by ONNX and JIT.
Unfortunately a workaround is necessary related to how we handle the scale_factor because:

The interpolate method needs it to be a float.
ONNX needs it to be a tensor so that the variable is in the computation graph.
JIT complains about its type if ONNX passes a tensor.

To resolve the problem we introduce a conditional fake cast to fool JIT and stop it from complaining about the ONNX branch.

Hi @datumbox
I found that this modification will cause an exception, the Pytorch "true" division is not numerically equal to the numpy, and I file an issue in https://github.com/pytorch/pytorch/issues/58234 .
scale_factor is caught from master
https://github.com/pytorch/vision/blob/0fd0f503a14ccf3f51d291c2f89721a7bc36c7b8/torchvision/models/detection/transform.py#L42
vs
scale_factor is caught from 0.9.0
https://github.com/pytorch/vision/blob/8fb5838ca916fd4ace080dae0357e7c307037bef/torchvision/models/detection/transform.py#L40-L42
This will cause numerically error between the exported ONNX model and the pytorch.
Besides, this phenomenon will weakly affect the mAP of the previous object detection model. I recompute the mAP of retinanet_resnet50_fpn as following (As a reference, the previous result is 0.364 in #2784)
IoU metric: bbox
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.363
 Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=100 ] = 0.557
 Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=100 ] = 0.382
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.193
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.400
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.490
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=  1 ] = 0.314
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 10 ] = 0.500
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.540
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.340
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.581
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.696

Validated with:
train.py --dataset coco --model retinanet_resnet50_fpn --pretrained --test-only

@zhiqwang Thanks for the heads up! Those two should be the same, so it's great that you already filed an issue on PyTorch code.
Concerning the perceived decrease in accuracy, the specific metric is know to be a bit flimsy and fluctuate. Here is a newer benchmark on master from what you posted https://github.com/pytorch/vision/pull/2954 . Hopefully once the ticket is resolved, the mAP will return to its expected value.
Let me know if there is anything else you recommend doing in the meantime.

Hi @datumbox
As mentioned in https://github.com/pytorch/pytorch/issues/58234#issuecomment-841090846 , it is because that the data type have changed after this modification.

This is a little confusing and it's happening because PyTorch's default datatype is float32 while NumPy's is float64.

I've done locally that it will perform previous behavior if we change the data type to torch.float64 in the im_shape. Do you think it is necessary to open a follow-up PR about this problem?
diff --git a/torchvision/models/detection/transform.py b/torchvision/models/detection/transform.py
index 55cfb483..a8525b41 100644
--- a/torchvision/models/detection/transform.py
+++ b/torchvision/models/detection/transform.py
@@ -27,9 +27,9 @@ def _resize_image_and_masks(image: Tensor, self_min_size: float, self_max_size:
                             target: Optional[Dict[str, Tensor]],
                             fixed_size: Optional[Tuple[int, int]]) -> Tuple[Tensor, Optional[Dict[str, Tensor]]]:
     if torchvision._is_tracing():
-        im_shape = _get_shape_onnx(image)
+        im_shape = _get_shape_onnx(image).to(torch.float32)
     else:
-        im_shape = torch.tensor(image.shape[-2:])
+        im_shape = torch.tensor(image.shape[-2:], dtype=torch.float64)

     size: Optional[List[int]] = None
     scale_factor: Optional[float] = None
@@ -37,8 +37,8 @@ def _resize_image_and_masks(image: Tensor, self_min_size: float, self_max_size:
     if fixed_size is not None:
         size = [fixed_size[1], fixed_size[0]]
     else:
-        min_size = torch.min(im_shape).to(dtype=torch.float32)
-        max_size = torch.max(im_shape).to(dtype=torch.float32)
+        min_size = torch.min(im_shape)
+        max_size = torch.max(im_shape)
         scale = torch.min(self_min_size / min_size, self_max_size / max_size)

@zhiqwang Thanks for the top notch investigation as always.
Your proposed changes look great to me and since they fix the problem, it would be great if you could send a PR.

@zhiqwang Just following up on this. We would like to bring your proposed fix prior to the upcoming PyTorch release. I was wondering if you are still interested sending the PR since you pretty much have it ready to go as far as I understand. Else let me know if I can give you a hand.

@zhiqwang Sorry for the back-to-back pings. Let me know if you are interested in sending the PR. We would like to have this patched as soon as possible so if you are not available I'm happy to take your fix and merge it.
I would prefer if you do it instead because 1) you should get credit for finding and fixing the issue and 2) it would be great to have your confirmation that the problem is resolved after we merge.
Let me know, thanks! :)


Add MsgCreateValidator 5% check before production

we commented this out for testnet.
remember to uncomment out the relevant tests as well

done


Include POI data in metadata

Include POI data in metadata. Fixes issue #54.

Hi, before I approve this, can you post a video that contains POI data? I want to make sure the code captures it properly, and none of the few I just tried seem to have it.


Question: Why does Bundler still support Ruby 1.8.7?

Ruby 1.8.7 is end of life since almost 5 years now.
I am wondering, why does Bundler still support it?
Would it be enough to tell Ruby 1.8.7 users to use an old version of Bundler known to still support Ruby 1.8.7?
From an external point of view, it seems to create a lot of extra efforts for maintenance and making the codebase harder to read and understand.

Bundler conforms to semantic versioning, which means we need to release a major version (e.g. 2.0) to drop compatibility with Ruby 1.8.7. As you can maybe imagine, it has been a complex process to ship breaking changes in Bundler without also breaking every existing Ruby project—but we're getting close. The master branch is currently Bundler 2.0, and we're pushing towards a prerelease.
While the master branch of this repo does not currently support Ruby 1.8.7, any commits that we backport to Bundler 1.x do need to support Ruby 1.8. After we release the Bundler 2.0 final, we plan to reduce support for the 1.x series to security issues only. At that point, we also plan to stop supporting Ruby 1.8 on the master branch. If you want to help, definitely check out the Bundler 2.0 milestone.

Thank you for the quick answer, that makes sense.


Adding support for NSCopying protocol.

What it says on the box. Making RouteObject conform to NSCopying. Needed for mapbox/mapbox-navigation-ios#806.
/cc @1ec5 @bsudekum

Would it be possible to avoid all this boilerplate code by adopting Codable now that we're on an Xcode 9 stack already?

I agree @frederoni, but wouldn't it be better to do that refactor in one tech-debt chore, rather than piecemeal? There are 8 classes that use NSSecureCoding, and two that use NSCopying, so it seems like there's enough of a payload to justify a chore here.


Patch signing issue with Nami wallet

In CIP30, an address is defined as being either hex-encoded or bech32 encoded (reference). However, Nami only allows hex-encoding
This is problematic because Paima always uses bech32 encoding for signing data (ref).
Solution
Two options:

Move to hex encoding addresses when using signData for all wallets, and test that all wallets support that one properly (and hope no wallet only supports bech32)
Add a special case where for Nami only we pass in hex-encoding

Neither is great, but we have to pick one. I tested bech32 with Flint and Eternl and they both worked.

Fixed in #250


Autocomplete throws error

Autocomplete has been failing with this error for me:
Uncaught (in promise) Error: Request workspace/executeCommand failed with message: Cannot read property 'version' of undefined
    at new ResponseError (/Users/monoidmusician/.atom/packages/ide-purescript/node_modules/vscode-jsonrpc/lib/messages.js:46)
    at handleResponse (/Users/monoidmusician/.atom/packages/ide-purescript/node_modules/vscode-jsonrpc/lib/main.js:430)
    at processMessageQueue (/Users/monoidmusician/.atom/packages/ide-purescript/node_modules/vscode-jsonrpc/lib/main.js:258)
    at Immediate.<anonymous> (/Users/monoidmusician/.atom/packages/ide-purescript/node_modules/vscode-jsonrpc/lib/main.js:242)
    at runCallback (timers.js:651)
    at tryOnImmediate (timers.js:624)
    at processImmediate [as _immediateCallback] (timers.js:596)

with atom-ide-ui 0.7.2, PS 0.11.7, and this package at 0.21.0

Yeah I haven't run into issues with this again, it seems to be working well!

I run into this every once in a while too, and I haven't found any pattern as to why it happens. Currently waiting for it to pass again...


Install instructions need to be updated to account for packaging changes

Describe the issue
Follow up to https://github.com/elyra-ai/elyra/pull/2043. If a user follows the installation instructions, the deployment won't work for kfp configured with tekton
To Reproduce
Steps to reproduce the behavior:

Install elyra following the instructions in repo readme/install guide
Try kfp/tekton

Screenshots or log output
If applicable, add screenshots or log output to help explain your problem.
Log Output

Paste the log output here.

Expected behavior
A clear and concise description of what you expected to happen.
Deployment information
Describe what you've deployed and how:

Elyra version: [e.g. 1.5.3]
Installation source: [e.g. PyPI, conda, from source, official container image, custom container image]
Deployment type: [e.g. local installation, Docker, Kubernetes, Kubeflow [notebook server] , Open Data Hub]
Operating system: [e.g. macos, linux]

think this is a duplicate of #2133. please reopen if not.


New BrewPi-Script Daemon, Eliminate Circus, and Refactor Backups

This PR introduces a number of substantial changes from the previous release of Fermentrack.
Major Changes
BrewPi-Script Manager Rewrite
Since the early days of Fermentrack, Circus has been used to launch & manage individual instances of brewpi-script for each individual BrewPi Device. Unfortunately, Circus imposes a number of upstream dependencies that make keeping Fermentrack up-to-date an extremely onerous task. This PR replaces Circus with a custom BrewPi-Script management daemon.
Backup/Restore Refactor
The original implementation of backup/restore relied on an internal Django management command to read the database and write out database object descriptions to a JSON file. Although this works in theory, in practice this means that the backup is fairly dumb given that it is not aware of the nuance of Fermentrack's object relationships.
This PR replaces the use of the internal Django management command with new logic that generates a "smart" backup, which includes a Fermentrack-generated (rather than database-driven) representation of Fermentrack objects in JSON.
Changes from the previous logic when using newly-generated backups

Backup/restore no longer requires a fresh installation of Fermentrack for restoration to work
Backup/restore will no longer restore user accounts
Restoring controllers will no longer restart logging if they were logging when the backup was generated
Restoring controllers will no longer trigger a temperature profile to be applied if one was applied when the backup was generated

UUIDs
As part of the backup/restore refactoring, I have added UUIDs to every object that is likely to be exported. These UUIDs allow Fermentrack to recognize when an object in a backup file already exists in the Fermentrack database, and will update that object (rather than attempting to install a second instance).
Full Changelog (so far)
Added

BrewPi-Script instances are now controlled via a custom process manager
Officially added arm64v8 to supported platforms
Added support for new versions of the BrewPi Firmware for certain ESP-based BrewPi Controllers
Added support for extended settings on new BrewPi Firmware for certain ESP-based BrewPi Controllers
Added board types for ESP32, ESP32-C3, and ESP32-S2
Added examples for HTTPS support (Thanks @HuggableShark)
Added UUIDs to most exportable objects to allow for easier import/export

Changed

Removed Circus support in favor of managing processes via Supervisord
Removed libzmq requirement
Removed environment tests for Tilt hydrometers (Obviated via Docker)
Switch to use latest LTS version of Django
Update to Python 3.9
Changed most references to ESP8266 to reference ESP32 as appropriate
Rewrote backup & restore functions to no longer rely on Django management code
Changed restoration of legacy backups to explicitly utilize the staging folder

After install of this my tilt reconnected but the brewpi Arduino isn't connected.
Traceback (most recent call last):   File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main     return _run_code(code, main_globals, None,   File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code     exec(code, run_globals)   File "/app/brewpi-script/brewpi.py", line 31, in <module>     from scriptlibs.brewpiScriptConfig import BrewPiScriptConfig ModuleNotFoundError: No module named 'scriptlibs'

You switched to the testing (or docker-dev) images?

I used the update within the app. I will update via docker and report back.


Fixes bug w/ view controller dismissal on button click

If handler contains code to present another view controller, the presentViewController method within the handler does not execute properly.

I'll take a look at this in a little bit. Thanks.


Why does javascript similar to my code exist in memory?

Compiled this:
var x = "xxx";
y = x;
z = y;
console.log(x + y + z);

Loaded into windbg and ran the following commands:
g
s -a 0 L?80000000/2 "xxx"

Saw something interesting at 0068d713, so dumped it.
d 0068d713-15 L50

Why does javascript similar to my code exist in memory?

Hi,
As we wanted to launch fastly a boostraped version, the actual version embed a JS engine for Linux/Windows,
We are finishing a new release of the core compiler and will update it soon,
stay tuned on Slack : http://api.nectarjs.com:3000/
More info here<EMAIL_ADDRESS>

My mistake.  I though this was meant to compile javascript to machine code, and I wanted to see the optimizations.

No, it's not a mistake, it will compile to machine code
for testing purpose, we have replaced the compiler by an engine, but we will replace soon the engine by compiled machine code

I compiled your fibonacci algorithm example:
function fibonacci(n)
{
if (n < 2)  return n;
return fibonacci(n - 2) + fibonacci(n - 1);
}
console.log(fibonacci(30));

It looks like this in memory:

The important bit is:
function t(n){return n<2?n:t(n-2)+t(n-1)}console.log(t(30))}

This looks like uglifyjs output.  The rest looks like garbage code.  When I run the fibonacci example code through an obfuscator, I get this:
!function(a,b){function c(b,d){var e,f;if("."!=b[0]&&"/"!=b[0])return a(b);if(d=d||"root",e=c.resolve(b),!e&&/\.json$/i.test(b))return a("./"+c.basename(b));if(f=c.cache[e],!f)try{return a(b)}catch(g){throw Error('failed to require "'+b+'"
from '+d+"\n"+g.message+"\n"+g.stack)}return f.exports||(f.exports={},f.call(f.exports,f,f.exports,c.relative(e))),f.exports}c.cache={},c.basename=a("path").basename,c.resolve=function(b){var d,e,f,g;if("."!=b[0])return a.resolve(b);for(d="
/"===b.slice(-1)?b:b+"/",e=[b,b+".js",d+"index.js",b+".json",d+"index.json"],f=0;g=e[f];f++)if(c.cache[g])return g},c.register=function(a,b){c.cache[a]=b},c.relative=function(a){function b(b){var d,e,f,g,h;if("."!=b[0])return c(b);for(d=a.s
plit("/"),e=b.split("/"),d.pop(),f=0,g=e.length;g>f;f+=1)h=e[f],".."==h?d.pop():"."!=h&&d.push(h);return c(d.join("/"),a)}return b.resolve=c.resolve,b.cache=c.cache,b},c.register("./orig.js",function(){function d(a){return 2>a?a:d(a-2)+d(a-
1)}console.log(d(30))}),b.exports=c("./orig.js")}(require,module);

Similar to what I'm seeing in memory, but some differences in approach.  Maybe I'm using a different obfuscator, or different options.
I only have time to look at this on my lunch break, so unfortunately I won't have an opportunity any time soon to answer these on my own.

Is any portion of your compiler involved in creating the output executables at this stage at all?  Or, are the executables just our code, an embedded runtime, and layers of obfuscation?
Which engine, as you put it, are you embedding?  Is it your own?  Part of the compiler?
Can we have access to files produced by the version of the core compiler you are working on now so we can start to get an idea of its nature?

Answered a couple of my questions myself.
console.log(Duktape.version)

Outputs 20299.
Maybe I missed it (I didn't look very hard), but I have not seen Duktape (https://github.com/svaarala/duktape) in your documentation or articles.  Until Duktape is replaced by your compiler, this seems like important information to have for anyone trying to understand behavior of their code, or even assess NectarJS as an option for projects.

Yes,
we have uptaded NectarJS with the core compiler today, no more Duktape or JS engines, doc's coming soon

Just tried it.  Executable still contains obfuscated javascript and Duktape.


Create pwned.go

golang version

Looks good! Could you add some kind of comment / acknowledgment at the top of your go file to credit the github repo you reference?

updated !!