[Mixcloud] Add support for channels/playlists

[me@pc /tmp]$ youtube-dl --version
2015.03.18
[me@pc /tmp]$ youtube-dl -x --audio-format "mp3" --restrict-filenames -o "%(title)s.%(ext)s" --verbose https://www.mixcloud.com/LeFtOoO/uploads/
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-x', '--audio-format', 'mp3', '--restrict-filenames', '-o', '%(title)s.%(ext)s', '--verbose', 'https://www.mixcloud.com/LeFtOoO/uploads/']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.03.18
[debug] Python version 2.7.6 - Linux-3.16.0-33-generic-x86_64-with-Ubuntu-14.04-trusty
[debug] exe versions: avconv 1.2.6-7, avprobe 1.2.6-7, ffmpeg 1.2.6-7, ffprobe 1.2.6-7
[debug] Proxy map: {}
[mixcloud] LeFtOoO-uploads: Downloading webpage
[mixcloud] LeFtOoO-uploads: Checking URL 21/30 ...
ERROR: Unable to extract title; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 654, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 275, in extract
    return self._real_extract(url)
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/mixcloud.py", line 89, in _real_extract
    PREFIX + r'm-title="([^"]+)"', webpage, 'title')
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 557, in _html_search_regex
    res = self._search_regex(pattern, string, name, default, fatal, flags, group)
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 547, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract title; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

[me@pc /tmp]$

duplicate of #5272 ?

Is there any update for this? The 11.24.2015 build does not work for mixcloud...
All attempts through "Unable to extract title" errors
Thank you =)

Thanks to @Phaeilo Mixcloud playlists and user pages will be supported in the next version.


issues with es6 template strings

Imagine a function like this...
function masterRunner(){
  var conv = new showdown.Converter()
  return conv.makeHtml(`
    ## markdown doc
    you can use markdown for card documentation
    - foo
    - bar
  `)
}

this is the output

## markdown doc
you can use markdown for card documentation
- foo
- bar

It means i always have to untab my markdown.
I understand why but it seams ungood.

I see your point. However, I can't think of any sane way showdown core can ignore tabs smartly without breaking the tab code blocks.
Do you have any suggestions?
An extension, for your specific case, might do the trick.
Or even some kind of pre parser function

To fix your specific issue, however, you have several options:
Move es6 template strings to a new line
You can fix the issue by moving the es6 opening mark to a new line that respects your indentation:
function masterRunner() {
  var conv = new showdown.Converter()
  return conv.makeHtml(
    `## markdown doc
     you can use markdown for card documentation
      - foo
      - bar`);
}

Use a wrapper function
you can also use a wrapper function, although I think is really an overkill and potentially breaks tab code blocks:
function masterRunner(){
  var conv = new showdown.Converter()
  return conv.makeHtml(t(`
    ## markdown doc
    you can use markdown for card documentation
    - foo
    - bar
  `));
}

function t(txt) {
  return txt.replace(/^\s+/gm, '');
}

Make the above t function a lang extension
This would remove the need to pre-parse the text but, again, I think is an overkill.

Hey thanks for the response.
So If i use option 1 (Move es6 template strings to a new line)
This is what i get. The first line is converted and nothing else.

markdown doc

  you can use markdown for card documentation
  - foo
  - bar

the alternative is
function masterRunner() {
  var conv = new showdown.Converter()
  return conv.makeHtml(`
## markdown doc
you can use markdown for card documentation
- foo
- bar
  `);
}

Which is also not super great. (this is what im currently doing)
Using something like option 2 up above would work but would need some major testing to make sure you don't remove white space from unintended lines.
My proposal is that showdown could let you pass an argument that would try to intelligently fix your es6 string.
Is that crazy?

My proposal is that showdown could let you pass an argument that would try to intelligently fix your es6 string.

Yeah, but how would we accomplish that? Right trimming would not work as it would remove important right whitespaces.
Passing the indentation level would be kind of useless since it would tighly couple the text with the code style, which is crazy!!
The only way I can think of is guessing by the the "indentation" level of the first line of the text, but that would also break under some circumstances such as:

first line of text not indented but the rest is
a list or a code block as first element in a string
etc...

Check 261f127 and see if it fixes your problem,
Its on it's own branch since I would like further testing before introducing this feature on core.
This type of "smart" indentation fixing is problematic and I don't think we can create a system that reliably can identify indented text.

@jhicken  Have you had time to check and test 261f127 ?

I have not.  Sorry been super busy.  I'll try and get to it tonight.  Ps thanks for working on this.


feat(request-id): introduce Request ID

Description
Docs for https://github.com/Kong/kong/pull/11624 where the Request ID is introduced.
Few minor changes to the log serializer as well to make mapping between IDs easier.
Testing instructions
Preview link:
Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

thanks for the review @lena-larionova.

I think someone accidentally removed deploy previews for release/gateway-3.5 🤔 And the smoke tests rely on the preview. I've enabled them now, but they won't kick off until something is pushed to the PR.
Let me run locally and see if I get the same issue.

It's a submodule issue. Fixing it separately; your PR causes no errors 😄


using userBind cause error on setFilter

Not sure if it's a bug or not having proper configuration, I tried to change le-scan-test.js to use bluetoothHciSocket.bindUser() and when run it I get [Error: File descriptor in bad state]. It's happens when code sets in bluetoothHciSocket.setFilter. BTW beside that error,  looks like scanning works
this the change:
diff --git a/examples/le-scan-test.js b/examples/le-scan-test.js
index e573c53..8912a5d 100644
--- a/examples/le-scan-test.js
+++ b/examples/le-scan-test.js
@@ -120,7 +120,7 @@ function setScanEnable(enabled, duplicates) {
   bluetoothHciSocket.write(cmd);
 }

-bluetoothHciSocket.bindRaw();
+bluetoothHciSocket.bindUser();
 setFilter();
 bluetoothHciSocket.start();

and this is the output
sudo hciconfig hci0 down
sudo node le-scan-test.js
[Error: File descriptor in bad state]
data: 040e04010c200c
data: 040e04010b2000
LE Scan Parameters Set
data: 040e04010c2000
LE Scan Enable Set
data: 043e1702010000efe1d4c2153c0b02010607ff4c0010020b00c7
LE Advertising Report
	ADV_IND
	PUBLIC
	3c:15:c2:d4:e1:ef
	02010607ff4c0010020b00
	-57
data: 043e0c02010400efe1d4c2153c00c6
LE Advertising Report
	SCAN_RSP
	PUBLIC
	3c:15:c2:d4:e1:ef

	-58
data: 043e2b02010000ca09cc6ebb141f02011e1bff7500420401404f14bb6ecc09ca16bb6e5109c908000000000000ae

@slashmili please see: https://github.com/sandeepmistry/node-bluetooth-hci-socket#user-channel
For user channel the adapter must be powered down before starting the Node.js app as per the documentation.

@sandeepmistry as I mentioned in the output I already powered down the device
sudo hciconfig hci0 down
sudo node le-scan-test.js
...

@slashmili apologies for missing this.
I believe setFilter is only applicable for bindRaw and not bindUser mode, as you are still getting an the events.
Could you please submit a PR to read me to document this?

Sure!
Does it mean that in noble/hci.js, there should be a checking to only call setSocketFilter if HCI_CHANNEL_RAW is set?
The reason I'm interested to these details is, I'm porting this library to Erlang and planning to use it in Nerves

Does it mean that in noble/hci.js, there should be a checking to only call setSocketFilter if HCI_CHANNEL_RAW is set?

Yes, I agree. It currently ignores the error event of "File descriptor in bad state" - but it would be clearer to not call setSocketFilter as you suggested. Do you have time to submit a PR for this as well?

Of course! I'll do this this week

@slashmili any progress on the PR?

@sandeepmistry no sorry I'm still pretty busy moving 🚚

Just for the record I found this explanation

Using this new facility does not require any external library or special
ioctl or socket filters. Just create the socket and bind it. After that
the file descriptor is ready to speak H:4 protocol.

http://www.spinics.net/lists/linux-bluetooth/msg37345.html


Feature Request - nested tags

We would like to group some of our tags into a "Tag Group".
This would be used in the nav-bar section to collapse/expand groups of tags inside a single header.
See here for an example:
https://redocly.com/docs/api-reference-docs/specification-extensions/x-tag-groups/

+1 for focused mode


capture source callsign from packets, expose in log and api

The source callsign is not logged nor is it exposed in the api for the lastheard list. The client id is exposed, but in a multi-user system (such as a repeater), you can not assume that the client id is the same as the source callsign. Modification of the packet and lastheard code is required.
I've made working code changes for all packet types, but I've only been able to complete testing for YSF. I believe this code will require a change in the length used for the memcpy in lastheard.c based on the mode. The memcpy currently is using the max callsign length constant, but that would not be correct for all modes. Will this cause a problem on the modes that are shorter than YSF? I'm not sure.
My branch is here and can be used for testing of other modes:
https://github.com/MichaelDBrown/srf-ip-conn-srv/tree/source_callsign
I'm using this in production for the Central Illinois Fusion Network and have had no problems, with both the logs and the dashboard now showing source callsign information:

Please create a pull request.
--
Norbert Varga
http://www.nonoo.hu/
On Fri, Feb 9, 2018 at 5:28 AM, Michael Brown<EMAIL_ADDRESS>wrote:

The source callsign is not logged nor is it exposed in the api for the
lastheard list. The client id is exposed, but in a multi-user system (such
as a repeater), you can not assume that the client id is the same as the
source callsign. Modification of the packet and lastheard code is required.
I've made working code changes for all packet types, but I've only been
able to complete testing for YSF. I believe this code will require a
change in the length used for the memcpy in lastheard.c based on the mode.
The memcpy currently is using the max callsign length constant, but that
would not be correct for all modes. Will this cause a problem on the modes
that are shorter than YSF? I'm not sure.
My branch is here and can be used for testing of other modes:
https://github.com/MichaelDBrown/srf-ip-conn-srv/tree/source_callsign
I'm using this in production for the Central Illinois Fusion Network and
have had no problems, with both the logs and the dashboard now showing
source callsign information:
[image: image]
https://user-images.githubusercontent.com/10491209/36011701-ba29598a-0d1e-11e8-9f3a-0c77f0cb4e48.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sharkrf/srf-ip-conn-srv/issues/10, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYEHaoC-yxNgIVjhqLgIYl9yMfkaK54ks5tS8lfgaJpZM4R_Zv7
.

Done, but I still need assistance with testing modes other than YSF. Thanks!

On Feb 9, 2018, at 1:45 AM, Norbert Varga<EMAIL_ADDRESS>wrote:
Please create a pull request.
--
Norbert Varga
http://www.nonoo.hu/
On Fri, Feb 9, 2018 at 5:28 AM, Michael Brown<EMAIL_ADDRESS>wrote:

The source callsign is not logged nor is it exposed in the api for the
lastheard list. The client id is exposed, but in a multi-user system (such
as a repeater), you can not assume that the client id is the same as the
source callsign. Modification of the packet and lastheard code is required.
I've made working code changes for all packet types, but I've only been
able to complete testing for YSF. I believe this code will require a
change in the length used for the memcpy in lastheard.c based on the mode.
The memcpy currently is using the max callsign length constant, but that
would not be correct for all modes. Will this cause a problem on the modes
that are shorter than YSF? I'm not sure.
My branch is here and can be used for testing of other modes:
https://github.com/MichaelDBrown/srf-ip-conn-srv/tree/source_callsign
I'm using this in production for the Central Illinois Fusion Network and
have had no problems, with both the logs and the dashboard now showing
source callsign information:
[image: image]
https://user-images.githubusercontent.com/10491209/36011701-ba29598a-0d1e-11e8-9f3a-0c77f0cb4e48.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sharkrf/srf-ip-conn-srv/issues/10, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYEHaoC-yxNgIVjhqLgIYl9yMfkaK54ks5tS8lfgaJpZM4R_Zv7
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Question: :dev branch container gives permission denied errors on migration script (in /app) even after new install

Hi there,
I've been using ArchiveBox for quite a while, previously I was using the :latest branch, which works fine for most things, except that SingleFile doesn't work because of the missing link to /usr/bin/chromium-browser
I see there's a fix in the dockerfile, so when I switch to the dev docker release the link is correct however I cannot start the server due to permission errors, this happens regardless of PUID, PGID host permissions (777 for debugging) of the data folder, the issue appears to be for some reason the /app/ folder has the wrong permissions
Initial logs
Attaching to archivebox-archivebox-1
archivebox-archivebox-1  | Change in ownership detected, please be patient while we chown existing files
archivebox-archivebox-1  | This could take some time...
archivebox-archivebox-1  | chown: changing ownership of '/data/index.sqlite3': Permission denied
archivebox-archivebox-1  | chown: changing ownership of '/data/archive': Permission denied
archivebox-archivebox-1  | chown: changing ownership of '/data/logs/errors.log': Permission denied
archivebox-archivebox-1  | chown: changing ownership of '/data/logs': Permission denied
archivebox-archivebox-1  | chown: changing ownership of '/data/sources': Permission denied
archivebox-archivebox-1  | chown: changing ownership of '/data/ArchiveBox.conf': Permission denied
archivebox-archivebox-1  | chown: changing ownership of '/data': Permission denied
archivebox-archivebox-1  | chown: changing ownership of '/data': Permission denied
archivebox-archivebox-1  | [i] [2022-07-24 12:00:30] ArchiveBox v0.6.3: archivebox server --quick-init <IP_ADDRESS>:8000
archivebox-archivebox-1  |     > /data
archivebox-archivebox-1  |
archivebox-archivebox-1  | [^] Verifying and updating existing ArchiveBox collection to v0.6.3...
archivebox-archivebox-1  | ----------------------------------------------------------------------
archivebox-archivebox-1  |
archivebox-archivebox-1  | [*] Verifying archive folder structure...
archivebox-archivebox-1  |     + ./archive, ./sources, ./logs...
archivebox-archivebox-1  |     + ./ArchiveBox.conf...
archivebox-archivebox-1  |
archivebox-archivebox-1  | [*] Verifying main SQL index and running any migrations needed...
archivebox-archivebox-1  | Traceback (most recent call last):
archivebox-archivebox-1  |   File "/usr/local/bin/archivebox", line 33, in <module>
archivebox-archivebox-1  |     sys.exit(load_entry_point('archivebox', 'console_scripts', 'archivebox')())
archivebox-archivebox-1  |   File "/app/archivebox/cli/__init__.py", line 140, in main
archivebox-archivebox-1  |     run_subcommand(
archivebox-archivebox-1  |   File "/app/archivebox/cli/__init__.py", line 80, in run_subcommand
archivebox-archivebox-1  |     module.main(args=subcommand_args, stdin=stdin, pwd=pwd)    # type: ignore
archivebox-archivebox-1  |   File "/app/archivebox/cli/archivebox_server.py", line 64, in main
archivebox-archivebox-1  |     server(
archivebox-archivebox-1  |   File "/app/archivebox/util.py", line 114, in typechecked_function
archivebox-archivebox-1  |     return func(*args, **kwargs)
archivebox-archivebox-1  |   File "/app/archivebox/main.py", line 1280, in server
archivebox-archivebox-1  |     run_subcommand('init', subcommand_args=['--quick'], stdin=None, pwd=out_dir)
archivebox-archivebox-1  |   File "/app/archivebox/cli/__init__.py", line 80, in run_subcommand
archivebox-archivebox-1  |     module.main(args=subcommand_args, stdin=stdin, pwd=pwd)    # type: ignore
archivebox-archivebox-1  |   File "/app/archivebox/cli/archivebox_init.py", line 43, in main
archivebox-archivebox-1  |     init(
archivebox-archivebox-1  |   File "/app/archivebox/util.py", line 114, in typechecked_function
archivebox-archivebox-1  |     return func(*args, **kwargs)
archivebox-archivebox-1  |   File "/app/archivebox/main.py", line 344, in init
archivebox-archivebox-1  |     for migration_line in apply_migrations(out_dir):
archivebox-archivebox-1  |   File "/app/archivebox/util.py", line 114, in typechecked_function
archivebox-archivebox-1  |     return func(*args, **kwargs)
archivebox-archivebox-1  |   File "/app/archivebox/index/sql.py", line 143, in apply_migrations
archivebox-archivebox-1  |     call_command("makemigrations", interactive=False, stdout=null)
archivebox-archivebox-1  |   File "/usr/local/lib/python3.10/site-packages/django/core/management/__init__.py", line 168, in call_command
archivebox-archivebox-1  |     return command.execute(*args, **defaults)
archivebox-archivebox-1  |   File "/usr/local/lib/python3.10/site-packages/django/core/management/base.py", line 371, in execute
archivebox-archivebox-1  |     output = self.handle(*args, **options)
archivebox-archivebox-1  |   File "/usr/local/lib/python3.10/site-packages/django/core/management/base.py", line 85, in wrapped
archivebox-archivebox-1  |     res = handle_func(*args, **kwargs)
archivebox-archivebox-1  |   File "/usr/local/lib/python3.10/site-packages/django/core/management/commands/makemigrations.py", line 182, in handle
archivebox-archivebox-1  |     self.write_migration_files(changes)
archivebox-archivebox-1  |   File "/usr/local/lib/python3.10/site-packages/django/core/management/commands/makemigrations.py", line 220, in write_migration_files
archivebox-archivebox-1  |     with open(writer.path, "w", encoding='utf-8') as fh:
archivebox-archivebox-1  | PermissionError: [Errno 13] Permission denied: '/app/archivebox/core/migrations/0021_auto_20220724_1200.py'

This happens even if I set up a brand new directory with the :dev branch to create a new database and do setup/init.
If I create the container and spawn a shell to poke around it appears /app has permissions root:root which should be fine, but I guess ArchiveBox writes out the migration files to the /app directory, what's interesting is that this happens even on a totally fresh install.
Here are the permissions:
$ id
uid=999(archivebox) gid=999(archivebox) groups=999(archivebox),29(audio),44(video)
$ ls -lahS /
total 84K
drwxr-xr-x   1 root       root       4.0K Jul 24 11:59 .
drwxr-xr-x   1 root       root       4.0K Jul 24 11:59 ..
drwxr-xr-x   1 root       root       4.0K Jun  9 08:09 app
drwxr-xr-x   1 root       root       4.0K Jun  9 00:22 bin
drwxr-xr-x   2 root       root       4.0K Mar 19 13:46 boot
drwxr-xr-x   3 archivebox archivebox 4.0K Jul 24 11:59 data
drwxr-xr-x   1 root       root       4.0K Jul 24 11:59 etc
drwxr-xr-x   1 root       root       4.0K Jun  9 00:00 home
drwxr-xr-x   1 root       root       4.0K Jun  9 00:02 lib
drwxr-xr-x   2 root       root       4.0K May 27 00:00 media
drwxr-xr-x   2 root       root       4.0K May 27 00:00 mnt
drwxr-xr-x   1 root       root       4.0K Jun  9 00:16 node
drwxr-xr-x   2 root       root       4.0K May 27 00:00 opt
drwx------   1 root       root       4.0K Jun  9 00:21 root
drwxr-xr-x   3 root       root       4.0K May 27 00:00 run
drwxr-xr-x   1 root       root       4.0K Jun  9 00:03 sbin
drwxr-xr-x   2 root       root       4.0K May 27 00:00 srv
drwxrwxrwt   1 root       root       4.0K Jun  9 00:30 tmp
drwxr-xr-x   1 root       root       4.0K May 27 00:00 usr
drwxr-xr-x   1 root       root       4.0K May 27 00:00 var
drwxr-xr-x   5 root       root       4.0K Jun  9 00:20 venv
drwxr-xr-x   5 root       root        340 Jul 24 11:59 dev
-rwxr-xr-x   1 root       root          0 Jul 24 11:59 .dockerenv
dr-xr-xr-x 135 root       root          0 Jul 24 11:59 proc
dr-xr-xr-x  12 root       root          0 Jul 24 11:59 sys

Update:
May not be a permissions issue, the file doesn't seem to exist
$ cat /app/archivebox/core/migrations/0021_auto_20220724_1159.py
cat: /app/archivebox/core/migrations/0021_auto_20220724_1159.py: No such file or directory

Not too sure what causes this, I looked at the migrations subdir and they're all on git anyways, so I'm guessing it's trying to execute a migration that doesn't exist yet? Maybe @pirate pushed a new build expecting a migration there when there isn't one yet?
Update: Yeah it's a permissions issue, giving archivebox:archivebox ownership of /app/archivebox/core/migrations works:
$ archivebox server --quick-init <IP_ADDRESS>:8000
[i] [2022-07-24 12:54:06] ArchiveBox v0.6.3: archivebox server --quick-init <IP_ADDRESS>:8000
    > /data

[^] Verifying and updating existing ArchiveBox collection to v0.6.3...
----------------------------------------------------------------------

[*] Verifying archive folder structure...
    + ./archive, ./sources, ./logs...
    + ./ArchiveBox.conf...

[*] Verifying main SQL index and running any migrations needed...
    Operations to perform:
      Apply all migrations: admin, auth, contenttypes, core, sessions
    Running migrations:
    Applying core.0021_auto_20220724_1254... OK

    √ ./index.sqlite3

[*] Checking links from indexes and archive folders (safe to Ctrl+C)...
    √ Loaded 4 links from existing main index.
    > Skipping full snapshot directory check (quick mode)

----------------------------------------------------------------------
[√] Done. Verified and updated the existing ArchiveBox collection.

    Hint: To view your archive index, run:
        archivebox server  # then visit http://<IP_ADDRESS>:8000

    To add new links, you can run:
        archivebox add < ~/some/path/to/list_of_links.txt

    For more usage and examples, run:
        archivebox help

A quick and dirty workaround to fix permissions on start:
services:
  archivebox:
    image: archivebox/archivebox:dev
    entrypoint: /bin/bash
    command: -c "chown -R archivebox:archivebox /app/archivebox/core/migrations && /app/bin/docker_entrypoint.sh server --quick-init <IP_ADDRESS>:8000"

@selim13 Can you make this a PR? I have the same issue

@agnosticlines @selim13 You can use my docker image turian/archivebox:migrations-0021 or wait for this PR to be merged: https://github.com/ArchiveBox/ArchiveBox/pull/1027 (based upon my branch https://github.com/turian/ArchiveBox/tree/feature/migrations-0021_auto_20220914_0934.py )

Yeah sorry a bug got merged into dev with one of the recent PRs a few months ago and I haven't had a chance to bisect and dig it out yet.

This should be fixed now as I merged @turian's PR with the missing migration. Comment back if you're still having issues on the latest dev release.

Hi, I found that this problem seems to still exist:
archivebox  | find: '/.config/chromium/Crash Reports/pending/': No such file or directory
archivebox  | [i] [2022-11-28 11:16:37] ArchiveBox v0.6.3: archivebox server --quick-init <IP_ADDRESS>:15200
archivebox  |     > /data
archivebox  |
archivebox  | find: '/.config/chromium/Crash Reports/pending/': No such file or directory
archivebox  | [+] Initializing a new ArchiveBox v0.6.3 collection...
archivebox  | ----------------------------------------------------------------------
archivebox  |
archivebox  | [+] Building archive folder structure...
archivebox  |     + ./archive, ./sources, ./logs...
archivebox  |     + ./ArchiveBox.conf...
archivebox  | find: '/.config/chromium/Crash Reports/pending/': No such file or directory
archivebox  |
archivebox  | [+] Building main SQL index and running initial migrations...
archivebox  | Traceback (most recent call last):
archivebox  |   File "/usr/local/bin/archivebox", line 33, in <module>
archivebox  |     sys.exit(load_entry_point('archivebox', 'console_scripts', 'archivebox')())
archivebox  |   File "/app/archivebox/cli/__init__.py", line 140, in main
archivebox  |     run_subcommand(
archivebox  |   File "/app/archivebox/cli/__init__.py", line 80, in run_subcommand
archivebox  |     module.main(args=subcommand_args, stdin=stdin, pwd=pwd)    # type: ignore
archivebox  |   File "/app/archivebox/cli/archivebox_server.py", line 64, in main
archivebox  |     server(
archivebox  |   File "/app/archivebox/util.py", line 114, in typechecked_function
archivebox  |     return func(*args, **kwargs)
archivebox  |   File "/app/archivebox/main.py", line 1280, in server
archivebox  |     run_subcommand('init', subcommand_args=['--quick'], stdin=None, pwd=out_dir)
archivebox  |   File "/app/archivebox/cli/__init__.py", line 80, in run_subcommand
archivebox  |     module.main(args=subcommand_args, stdin=stdin, pwd=pwd)    # type: ignore
archivebox  |   File "/app/archivebox/cli/archivebox_init.py", line 43, in main
archivebox  |     init(
archivebox  |   File "/app/archivebox/util.py", line 114, in typechecked_function
archivebox  |     return func(*args, **kwargs)
archivebox  |   File "/app/archivebox/main.py", line 344, in init
archivebox  |     for migration_line in apply_migrations(out_dir):
archivebox  |   File "/app/archivebox/util.py", line 114, in typechecked_function
archivebox  |     return func(*args, **kwargs)
archivebox  |   File "/app/archivebox/index/sql.py", line 143, in apply_migrations
archivebox  |     call_command("makemigrations", interactive=False, stdout=null)
archivebox  |   File "/usr/local/lib/python3.10/site-packages/django/core/management/__init__.py", line 168, in call_command
archivebox  |     return command.execute(*args, **defaults)
archivebox  |   File "/usr/local/lib/python3.10/site-packages/django/core/management/base.py", line 371, in execute
archivebox  |     output = self.handle(*args, **options)
archivebox  |   File "/usr/local/lib/python3.10/site-packages/django/core/management/base.py", line 85, in wrapped
archivebox  |     res = handle_func(*args, **kwargs)
archivebox  |   File "/usr/local/lib/python3.10/site-packages/django/core/management/commands/makemigrations.py", line 182, in handle
archivebox  |     self.write_migration_files(changes)
archivebox  |   File "/usr/local/lib/python3.10/site-packages/django/core/management/commands/makemigrations.py", line 220, in write_migration_files
archivebox  |     with open(writer.path, "w", encoding='utf-8') as fh:
archivebox  | PermissionError: [Errno 13] Permission denied: '/app/archivebox/core/migrations/0021_auto_20221128_1116.py'

root@docker:~/app/archivebox# docker images
REPOSITORY                          TAG                 IMAGE ID       CREATED         SIZE
archivebox/archivebox               dev                 b7a570c267b8   8 hours ago     1.63GB

I believe this issue should be fixed again, comment back if you're still having trouble and I can re-open it.

Hi! Looks like trouble is back with migration 0069
[*] Verifying main SQL index and running any migrations needed...
[!] Failed to create some migrations. Please open an issue and copy paste this output for help: [Errno 13] Permission denied: '/app/archivebox/core/migrations/0069_alter_archiveresult_extractor.py'

Ok yeah the issue is it's trying to create a new migration that it shouldn't be creating. Don't run the workarounds posted above (don't worry if you did it should be fine), it's an edge case for some setups that I need to fix in the code directly.

Ok yeah the issue is it's trying to create a new migration that it shouldn't be creating. Don't run the workarounds posted above (don't worry if you did it should be fine), it's an edge case for some setups that I need to fix in the code directly.

unfortunately currently my instance is stuck without being able to access my archive anymore, I was using 0.7.2 but at some moment it stopped grabbing titles for all links with just something like "title not found", or similar from logs and also it was really, really slow in most cases, so I tried to update it to latest dev 0.8.2 - now stuck with django.db.utils.IntegrityError: NOT NULL constraint failed: core_snapshot.created_by_id
Tried to downgrade back - but stuck with some different other problems each time too.. Like latest was django.db.utils.IntegrityError: NOT NULL constraint failed: core_snapshot.created
I should've create a full instance backup before trying to update.. :(
So for now I'm just hoping that this issue in first place after being resolve can resolve some other issues and I'll be able to use my archive again..

Can someone encountering this issue please share the contents of the autogenerated file:
/app/archivebox/core/migrations/0069_alter_archiveresult_extractor.py
I need it to understand what exactly Django thinks it needs to migrate.

Just bumping this to send a new notification because I edited my previous comment quite a bit ^

@Astro1247, I understand it looks scary but don't worry you shouldn't lose data, Django migrations are deterministic and atomic (meaning if they fail during some step it wont leave your db in a corrupted state). In the future you should definitely back up before installing any BETA releases but I'll help fix it for now.
I just pushed fixes for the two underlying issues you encountered (missing migration 0069 and created_by_id failure):
* [afe1307](https://github.com/ArchiveBox/ArchiveBox/commit/afe130761780f259b0841fe7dd2240cee6e02a31)

* [09553d83](https://github.com/ArchiveBox/ArchiveBox/commit/09553d83)

You should be able to pull the latest :dev and run it, and it will pick up wherever it left off, and re-run the migrations needed to bring you up to the current version.
docker compose pull
docker compose down
docker compose up

Thanks, it managed to recover (some?, it said it loaded 530 links and next row it said it ignored 530 invalid links) data and even it completely mixed all the data (date of saving is new now) at least I'm able to view this data and archivebox itself started.
All new starts are now with this warning:
WARNING: Error loading /app/node_modules/.bin/readability-extractor: Expected /app/node_modules/.bin/readability-extractor version None, got 0.0.11
- ❌ Binary /app/node_modules/.bin/postlight-parser failed to load with error: None of the configured providers [env] were able to load binary: postlight-parser

Also no new archiving tasks can be completed, no matter how much different attempts with different settings I've done, all fails into:
archivebox-1            |       > dom
archivebox-1            |         Extractor failed:
archivebox-1            |              Failed to save DOM
archivebox-1            |             [315:315:0829/175745.921310:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

So no new data can be saved, it all fails with same error, even that everything is okay, when using vnc everything seems fine too, but, its fails on archiving attempt :)
Also, all these actions that I've taken, all this updates etc were to fix failing title extracting, and.. it still fails to extract any page title XD Even with everything latest
archivebox-1            |       > title
archivebox-1            |         Extractor failed:
archivebox-1            |              Unable to detect page title
archivebox-1            |         Run to see full output:
archivebox-1            |           docker run -it -v $PWD/data:/data archivebox/archivebox /bin/bash
archivebox-1            |             cd /data/archive/1724950329.479523;
archivebox-1            |             curl --silent --location --compressed --max-time 60 --user-agent "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "https://github.com/ArchiveBox/ArchiveBox/issues/1002"


Create 'isAboveTheFold' prop in SlotInjector and use it in the PWA

Closes https://github.com/frontity/frontity/issues/69

:tada: This PR is included in version 0.12.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


DeprecationWarning: '_app_ctx_stack' is deprecated and will be removed in Flask 2.3.

When running python -m pytest -v test.py I get:
===================================================================================== warnings summary ======================================================================================
../../../../usr/lib/python3.11/site-packages/flask_sqlalchemy/__init__.py:14
../../../../usr/lib/python3.11/site-packages/flask_sqlalchemy/__init__.py:14
  /usr/lib/python3.11/site-packages/flask_sqlalchemy/__init__.py:14: DeprecationWarning: '_app_ctx_stack' is deprecated and will be removed in Flask 2.3.
    from flask import _app_ctx_stack, abort, current_app, request
...
test.py: 1146 warnings
  /usr/lib/python3.11/site-packages/flask_sqlalchemy/__init__.py:302: DeprecationWarning: '_app_ctx_stack' is deprecated and will be removed in Flask 2.3. Use 'g' to store data, or 'app_ctx' to access the current context.
    queries = _app_ctx_stack.top.sqlalchemy_queries

test.py: 21 warnings
  /usr/lib/python3.11/site-packages/flask_sqlalchemy/__init__.py:304: DeprecationWarning: '_app_ctx_stack' is deprecated and will be removed in Flask 2.3. Use 'g' to store data, or 'app_ctx' to access the current context.
    queries = _app_ctx_stack.top.sqlalchemy_queries = []

Hmm this stems from flask sqlalchemy. Not this library. Ignoring.


BOCM-51 - LPA Case officer landing

Describe your changes
WIP pull request for BOCM-51 (LPA / case officer dashboard page)
Issue ticket number and link
BOCM-51
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review
N/A (draft PR)

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Brian update

Hey @bwalsh does this look good? Did a little link cleanup at the bottom and added the linkedin profile page as a button. You now have write privileges on the repo–feel free to make any other updates here.

Thanks Alex, looks great.   Should I merge?

Sounds great. Go for it @bwalsh.


blog: add fluorine fermi image to release notes

Thanks to gnuteardrops for the image: https://monero.graphics/all/monero-gui-v-0.18-concept-design/

Nice thank you


Replace Azure.Identity AAD references

Replace Azure AD references in Markdown files with Microsoft Entra ID, per the guidance at https://learn.microsoft.com/azure/active-directory/fundamentals/how-to-rename-azure-ad.

API change check
API changes are not detected in this pull request.


migrate to new architecture

part of https://github.com/hoodiehq/hoodie/issues/458
I tried to think of all the steps to migrate this module to the new architecture:

[ ] rename GitHub repository to hoodie-log
[ ] move index.js to client/index.js. I would say we can leave the lib/ and test/ folder as they are, as this module only has  client code?
[ ] add "browser": "client/index.js" to the package.json just for convenience, so we can continue to do require('hoodie-log'), won’t harm
[ ] rename the "name" in package.json to "@hoodie/log"
[ ] find  "github.com/hoodiehq/hoodie-client-log" and replace with "github.com/hoodiehq/hoodie-log" in package.json
[ ] find  "github.com/hoodiehq/hoodie-client-log" and replace with "github.com/hoodiehq/hoodie-log" in README.md
[ ] commit changes with chore: ... and docs: ... commits. At the end add an empty commit:

chore: renamed module to @hoodie/client-log

BREAKING CHANGE:
The repository has been renamed from `hoodie-client-log` to `@hoodie/client-log` as part of https://github.com/hoodiehq/hoodie/issues/458

[ ] start a PR for review

Once merged

[ ] deprecate hoodie-client-log in the npm registry

ping @hoodiehq/maintainers could you review to see if I missed anything?
@boennemann will renaming the npm package name "just work" with semantic release"? Or do we need to do an initial release to the npm registry first? Will it continue with the version numbers or try to create 1.0.0 again? That’ll break git tags / releases on GitHub.

I am going to start working on the PR.

For a new name semantic-release will start over at 1.0.0. I'd suggest to checkout the last release that happened with the old name. Change name field to the new one. Manually add last released version number to version field. Run npm publish once locally.
(Given that the configured semantic-release user has access to publish to the new package) semantic-release will pick up the old version number an continue from there.

okay thanks I’ll take care of it


Google.com page

make clone of https://www.google.com/ page

Can I work on this issue please?

Can I work on this issue please?

sure

Please assign me, I have completed my other two issues :)

Please assign me, I have completed my other two issues :)

assigned u for this issue ✔👍


Fix flat structure for asyncErrors and submitErrors for FieldArray and Fields.

This PR fixes the rest of #3755 that was introduced in 7.2.1 where nested async errors and submit errors are flat. The other change should have been released as 8.0.0 since this is a breaking change in how asyncErrors and submitErrors are handled by redux-form.
This PR should also fix #3779
Note that this change requires errors for parent FieldArrays to be structured as foo._error when returned from the server. The tests should be clear as to what will happen.

Could they generate a release? This is affecting me.

@marlonmleite this is released as of v7.2.2.


[SPARK-46353][CORE] Refactor to improve RegisterWorker unit test coverage

What changes were proposed in this pull request?
This PR aims to improve the unit test coverage for RegisterWorker message handling.

Add handleRegisterWorker helper method which is testable easily.
Add new unit tests for three conditional branches.

Why are the changes needed?
It's easily to test and improve.
Does this PR introduce any user-facing change?
No. This is a refactoring on the main code and only additions to the test methods.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @viirya

Thank you so much, @viirya !

Hi, @viirya . Could you review once more? The following is the change from the original PR.
- handleRegisterWorker(registerWorker)
+ handleRegisterWorker(id, workerHost, workerPort, workerRef, cores, memory, workerWebUiUrl,
+        masterAddress, resources)

Thank you so much, @viirya . I'll dig more this area with more test cases.


Improvements For Linux Users

I Have Experienced that Osirs performs waaay worse on linux than on windows, but it cancels out because linux gives more fps anyway.
But Is there any way to make fast reload work on linux. Thanks

Btw fast reloading takes the same or more time than normal reloading no point.

Here you go #3398


[Snyk] Security upgrade python from 3.7 to 3.14.0a1

Snyk has created this PR to fix 2 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

samples/contrib/versioned-pipeline-ci-samples/kaggle-ci-sample/train_model/Dockerfile

We recommend upgrading to python:3.14.0a1, as this image has only 185 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-5927132
  829

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-5927132
  829

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-5927132
  829

Out-of-bounds Write SNYK-DEBIAN12-GLIBC-5927132
  829

CVE-2023-44487 SNYK-DEBIAN12-NGHTTP2-5953379
  829

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 1 commits between 57a28230fb3390fda3195efb99228bfc8d99c7f8...c37bccac19f3dc301ecb7803c1bfed926bd8baf7

UPSTREAM commit c37bcca has invalid summary fix: samples/contrib/versioned-pipeline-ci-samples/kaggle-ci-sample/train_model/Dockerfile to reduce vulnerabilities.

The Data Science Pipelines team recommends testing this using the Data Science Pipelines Operator.  Check here for more information on using the DSPO.
To use and deploy a DSP stack with these images (assuming the DSPO is deployed), first save the following YAML to a file named dspa.pr-99.yaml:
apiVersion: datasciencepipelinesapplications.opendatahub.io/v1alpha1
kind: DataSciencePipelinesApplication
metadata:
  name: pr-99
spec:
  dspVersion: v2
  apiServer:
    image: "quay.io/opendatahub/ds-pipelines-api-server:pr-99"
    argoDriverImage: "quay.io/opendatahub/ds-pipelines-driver:pr-99"
    argoLauncherImage: "quay.io/opendatahub/ds-pipelines-launcher:pr-99"
  persistenceAgent:
    image: "quay.io/opendatahub/ds-pipelines-persistenceagent:pr-99"
  scheduledWorkflow:
    image: "quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-99"
  mlmd:
    deploy: true  # Optional component
    grpc:
      image: "quay.io/opendatahub/mlmd-grpc-server:latest"
    envoy:
      image: "registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2"
  mlpipelineUI:
    deploy: true  # Optional component
    image: "quay.io/opendatahub/ds-pipelines-frontend:pr-99"
  objectStorage:
    minio:
      deploy: true
      image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance'

Then run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines.git
cd data-science-pipelines/
git fetch origin pull/99/head
git checkout -b pullrequest c37bccac19f3dc301ecb7803c1bfed926bd8baf7
oc apply -f dspa.pr-99.yaml

More instructions here on how to deploy and test a Data Science Pipelines Application.


Question: passing/retrieve additional elements other than" id" and "label"

say the sever passing me an array of objs like this.
[  {"id":"1","label":"car", "price":"xyz", "desc":"sth sth sth"},
{"id":"2","label":"bike", "price":"aa", "desc":"blah blah blah"}
]
How can I display respective price and desc info while the user selected the label from the drop down.  thanks!

You can use node.raw in scope https://stackoverflow.com/a/50461474/2303610

Yes,
Price: {{ value.price }} Description: {{ value.desc }}
 is what I want if it works.  But I am not sure I am able to get the value as an object .i.e. not be able to display {{value.price}} nor {{value.desc}}.  Does the code above   :value-format="object" do the trick?   sorry. I am new to Vuejs. I tested your code and can not make it work. @riophae . thanks!

@topegret @riophae
I think it's value-format="object" instead of :value-format="object"
<template>

    <treeselect v-model="value" :options="options" value-format="object" />

Price: {{ value.price }} Description: {{ value.desc }}

</template>

@topegret @ittus Sorry! You are right, it should be without the :.

seems this snippet won't work.the browser will 'hiccup' on '{{value.price}}' and '{{value.desc}}'. I am thinking to add a method to parse the object and then display it.
`

Price: {{ value.price }} Description: {{ value.desc }}

`

@topegret Hey! Can you give more information on your problem? Then I can better help you.

thanks @riophae and @ittus . it works now.
In this example, from outside of the treeselect tag.  using {{value.map(item=item.price}}  and {{value.map(item=item.desc}} will get only 'price'  and 'desc' displayed. That is what i want.

Yeah, you are using the multi-select mode. The example previously given is single-select mode.


Resetting Data

I needed my pity counter reset every 70-90 pulls, to do that I had to reset the entire page data (not cache)
It would be very helpful if we had options to reset without resetting the page settings i.e. the unlimited fates option, skip animation, banner stages, etc. And more importantly, thank you for making this.

Actually, I have added a button to clear gacha history for each banner. The Site settings will not be affected if you delete the data from History Page.


Explore options to publish generated app artifacts to Bintray

As a developer, I'd like to study the best approach to automatically publish generated app artifacts to Bintray, so it can then be automated to synchronize from Bintray to Maven Central.

The rest of Spring Cloud doesn't do the Bintray sync at all so why are we pursuing this?

This has been already addressed.


Support for Custom Resources & Providers

** Question : **
How can I use terraform-compliance to work with custom resources made by my custom provider. It can recognize my provider but is not able to recognize the resources and it seems to just skip them. Please let me know if this is possible, @eerkunt

It shouldn't be a problem. Is it possible to have a test.tf and plan.out.json to have a deeper dive ?

I figured out the issue. The resource name must start with the provider name because of the terraform naming convention. If the resource name starts with data, it will fail.

In _parse_resources in terraform.py if the conditions
if resource['address'].startswith('data'):
Are too lose as we should also check if the mode is data because the provider name may also start with data and this creates ambiguity between a data object and resource object. There may need to be and resource['mode'] == "data".
Please let me know what you think @eerkunt

This issue is especially true for datadog provider since the startswith is not 'data.' but 'data'

Thanks again for clarifying the real problem. I agree, we shouldn't have startswith('data') there, and I agre it should be on either checking the first offset (splitting by .) should be data or the mode property should be data.
Fixing it.

hey thanks a lot for the quick turn around time! Much appreciated

Can you please have a try with 1.1.17 ?

Assuming this is working as intended, closing the issue.
Please let us know if the issue still persists. Thanks again :tada:


Fixes an issue when dal is loaded twice

When dal is initialized multiple times, yl.functions stays set to {} and the select2 function is no longer present. This causes any future dal fields not to render and instead appear as normal HTML select fields.
This error came up when I tried using HTMX in conjunction with dal. HTMX reloads the form on the fly using ajax calls. When it pulled the new form in and tried to render it, the script tags for dal were loaded again. Thus producing this error.

Can I ask why did you choose HTMX over unpoly.js ? Just curious, I've tried both and ended with unpoly because it had more features, such as updating two separate fragments from a request...
Anyway, nice catch! Did you know we've been patching this stuff over and over again for the last years :joy:
Hopefully DAL will be proposing a web component based alternative soon

I've never tried unpoly before. I'll definitely to check it out. Thanks!
This is a great project by the way. Good work by you are everyone else who contributed. I love using this tool! Thanks for all your efforts @jpic  😄

Thank you for the kind words! Always appreciated ;)
Did you see that new documentation entry ? I hope this saves you from writing a lot of code :P

Hi, seams for me the same error when I use DAL with HTMX with def clean validation,
I got duplicated DAL select field (check GIF screen capture that shows it)
When I use DAL with HTML with validation also, everything works fine, no duplicated fields
P.S. i use HTMX as convenient way to use dynamic inline formsets

@akalikin1
I haven't encountered this exact issue myself. But I have run into a similar issue where it was duplicating the select field.
Fair warning, it's a bit of a hacky solution. I ended up with this bit of code when instantiating my form: form(auto_id=f"field_name_{random.randint(0, 999999)}")
if using a class-based view:
def get_form_kwargs(self):
kwargs = super().get_form_kwargs()
kwargs["auto_id"] = f"field_name_{random.randint(0,<PHONE_NUMBER>)}_%s"
return kwargs
The problem is that for some reason when the same ID is used on a field and you try to instantiate the field twice, autocomplete sort of freaks out. I'm not sure if this is the same issue your running into, but hopefully it will point you in the direction of a solution.
If you want to test it, just make sure the ID for the html field when it's rendered is different each time. After that, the field shouldn't duplicate.
Also, please let me know if you end up finding something better. 😄 Happy coding!

@FiooCode thanks for the answer
My exact problem is that when I use HTMX and render the field the class="select2-hidden-accessible" is not added to select field,
But in HTML everything is ok this class added to select field and the duplicated field is hidden
I don't know the reason and don't know how to fix it.
@jpic could you look at this problem please?


Markdown does not render when using --fullscreen

First, thanks for all your hard work on Dialog; simply excellent.
In a single test with Dialog 1.9.2 running on macOS 12.3 (21E5212f),  Markdown renders as expected, except when using --fullscreen; see attached.

Markdown Renders
/usr/local/bin/dialog --title 'Title Goes Here' --message "# Heading 1  \n## Heading 2  \n### Heading 3  \nText can include **bold** and _italics_\n  * point 1\n * point 2\n * point 3  \n\n[Getting Started with Dialog](https://github.com/bartreardon/Dialog/wiki)\n\n  \![Inline images are also supported](https://www.stockvault.net/data/2010/01/20/112821/preview16.jpg)"  --icon /System/Library/CoreServices/Finder.app --iconsize 128 --messagefont "size=14" --button1text "button1text" --button2text "button2text" --infobuttontext "View KB8675309 …" --infobuttonaction "https://servicenow.company.com/support?id=kb_article_view&sysparm_article=KB8675309" --timer 60

Markdown does not render when using --fullscreen
/usr/local/bin/dialog --title 'Title Goes Here' --message "# Heading 1  \n## Heading 2  \n### Heading 3  \nText can include **bold** and _italics_\n  * point 1\n * point 2\n * point 3  \n\n[Getting Started with Dialog](https://github.com/bartreardon/Dialog/wiki)\n\n  \![Inline images are also supported](https://www.stockvault.net/data/2010/01/20/112821/preview16.jpg)"  --icon /System/Library/CoreServices/Finder.app --iconsize 128 --messagefont "size=14" --button1text "button1text" --button2text "button2text" --infobuttontext "View KB8675309 …" --infobuttonaction "https://servicenow.company.com/support?id=kb_article_view&sysparm_article=KB8675309" --timer 60  --fullscreen

(Perhaps, just update the Wiki entry for Full Screen to advise users Markdown doesn't render when using --fullscreen.)

If it makes sense to have markdown in fullscreen mode then its easy enough to add it in. Im thinking of some other layout changes here in any case but its more of a basic view than the main dialog window. Its mostly modelled to give a reasonable approximation to jamfhelpers fullscreen mode.

@dan-snelson how would you feel about something like this?
Looking through my code, I did make a start on markdown for the fullscreen view but didn't finish it. (fullscreen is supposed to be a much simplified display after all)
I did place the text in a scroll view and also added a display for any timer present. I'm not sold on making the text scrollable as it's not obvious that the text here can be scrolled. To compensate for the lack of space in the fullscreen view I made the icon display at a maximum of 1/4 the screen height.
https://user-images.githubusercontent.com/3598965/155521135-534eda81-e369-4832-94e6-700f242d7bea.mov

One word: Sweetness!
LGTM, @bartreardon

fixed in 1.9.3


窗体最大化时启动growl全局通知会卡死

Describe the bug
将窗体设置为最大化时调用Global.ErrorGlobal()等带有Global的方法会出错
Steps to reproduce the bug
1、将窗体设置最大化
2、发送Growl信息通知
Expected behavior
No response
Screenshots
No response
NuGet package version
No response
IDE
No response
Framework type
No response
Windows version
No response
Additional context
No response

https://github.com/HandyOrg/HandyControl/issues/793#issuecomment-820859410

as above


Bower.json dependency resolves to Angular 1.2.28 instead of 1.3.16

I use "angular-ui-grid": "3.0.0-rc.22" in my bower.json file while I'm using "angular": "~1.3.0" (currently resolved to 1.3.16) as the base for my app.
This causes angular-ui-grid not to install, because there's conflict. Adding "resolutions" helps to fix it and reveals the true problem:
Please note that,
    angular-ui-grid#3.0.0-rc.22 depends on angular#>=1.2.16 <=1.3.x which resolved to angular#1.2.28

Maybe you'd better define dependency as "angular": ">=1.2.16 <1.4" or something like that?

Do you have any idea why the version spec that we use: >=1.2.16 <=1.3.16 doesn't work? Shouldn't that allow any version between 1.2.16 and 1.3.16? I have confirmed this with manual testing using semver.js: http://plnkr.co/edit/dHvHpgK53mtEcgI2goDQ?p=info  but for some reason it doesn't work with Bower.

Yes, I've got an idea. Bower uses it's own slightly modified version of semver, called bower-semver https://github.com/bower/semver . I tried to install and run it from node:
semver.maxSatisfying(['1.3.16', '1.2.18'], '>=1.2.16 <=1.3.16')
and the result was 1.2.18, while in common semver it results with 1.3.16.

Well that's kind of terrible, isn't it?


Quote font-families

Purpose
When trying to use certain font names (e.g., Exo 2), CSS requires them to be quoted. Note that at some point in the pipeline, even quotation explicitly added to the configuration file is stripped.
This PR changes the SCSS rules that define a font-family based on a variable to quote that variable.
Documentation
No documentation change necessary, just makes a feature work as advertised.

To the best of my understanding, this is due to Exo 2 being tokenized as "Identifier Whitespace Number", but font-families may only be a whitespace-separated list of Identifiers (or quoted strings).

Thanks for reporting the bug with font names containing a space followed by a number.
It wasn't caught earlier as the popular browsers were parsing font names containing spaces fine (such as in the Mr Robot theme) and it appears to be the number that's causing the issue.
Anyway, we shouldn't modify vendor files such as has been performed in this PR. I'll submit a commit to fix the bug.


Make compatible with original beyond framework

@noraesae Sorry, I merge it before review because I have another project that should add submodule it.
if you comments about these commit. I'll fix.


⚠ Samsung has degraded performance

In f9e4c46, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2803 ms

Resolved: Samsung performance has improved in 00bfce1.


[release-2.8] Better handling of cluster-scoped template lookups

Previously, there were some inconsistencies in how a hub template lookup for a cluster-scoped resource worked. As a result, the propagator would throw an error, and not be able to populate a real status for policies that tried to use that kind of lookup.
Now, in general, using lookup in a hub template for a cluster-scoped resource will fail with a template error that can be seen in the propagated policy. The one current exception is that a lookup of the ManagedCluster where the policy is replicated is allowed.


allow returning Observable from Spring MVC Controllers via ObservableRet...

...runValueHandler
fixes gh-231
@dsyer I'm hesitant to merge this as it is a new feature and the version is 1.0.1-BUILD-SNAPSHOT, hence the pull request.
@rstoyanchev I'd like you to take a look.

@spencergibb I tried to implement your classes on my project but seems injecting RequestMappingHandlerAdapter breaks the HateoasPageableHandlerMethodArgumentResolver#pageableResolver() making MVC method with parameter Pageable pageable throwing Failed to instantiate [org.springframework.data.domain.Pageable]: Specified class is an interface.
On your tests try to put a Pageable argument on controller method and see if it works

Superseded by 5ac5f198aae7a9c0c8d4fdccc8e63439425dda44


Keras interface and Python 3 compatability

Also adds a pretrained CIFAR-10 model

Add a comment linking to said posts?
On Tue, Dec 5, 2017 at 2:49 PM Henry Ehrenberg<EMAIL_ADDRESS>wrote:

@henryre commented on this pull request.
In experiments/cifar10/dataset.py
https://github.com/HazyResearch/tanda/pull/3#discussion_r155099682:

def load_cifar10_batch(fpath, one_hot=True, as_float=True):
with open(fpath, 'rb') as f:

   data = cPickle.load(f)

   data = cPickle.load(f, encoding='latin1')

Many stacks overflowed here. Just let it be.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/tanda/pull/3#discussion_r155099682, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABgw_WGumkIOb_HmQvXMN_gVZ2IN9CPkks5s9chrgaJpZM4Q3CYd
.


About the RL or Custom Algo (With tactile or visual pointcloud)

Hi, thank you for open source of this project, and I'm researching grasp with tactile sensors in simulation.
When I tried the second training example which shows the custom algorithm of tactile, it shows this project lack some files or directory, there is no files of custom, like /cfg/train/custom/.....
Can you updates and upload these files, thanks a lot.
And are there any materials or papers show how the tactile sensor works in this project, it will realy help if you share some.

For the custom part, you can directly copy and rename other algorithms or reinforcement learning environments for modification. The tactile simulation is based on the depth camera, and certain modifications have been made to the URDF file to make the visual model of the contact part transparent while retaining the collision model. The reason for doing this is that Isaac Gym does not support translucent materials. We've noticed that there have been some works on tactile simulation in Isaac Gym recently, and in the future, we will refer to these works to update this project.


fix(java/gazelle): Use new gazelle runfiles API to locate javaparser

This PR extends the work from @stevebarrau in #216 (still open at this time) to fix and simplify the new logic to locate the javaparser binary in runfiles, using the new Gazelle's runfiles package.

IIUC the issue is not with java_stub_template.txt but with the gazelle runner shell wrapper @ar3s3ru (see https://github.com/bazelbuild/bazel-gazelle/pull/828). I inline your changes and got a green CI run in https://github.com/bazel-contrib/rules_jvm/pull/216/commits/711b68ceb76a38cf6c58a8998e4656114fee6d7d.

Thanks for the ping @stevebarrau and linking the root issue.
I still see your PR is missing the handling of JAVA_RUNFILES environment variable. Only fixing the runfile location resolution won't make the plugin runnable (at least in my case)
Can we find a solution to get this merged?
Either your PR or mine, as long as you can include my commits so my work is part of the history, this took some effort 😅

Thank you both @illicitonion @stevebarrau 🙌🏻 Glad to see the issue fixed 🎉


Linking.sendIntent(action, extras) is insufficient.

Description
This link  (https://developer.android.com/distribute/marketing-tools/linking-to-google-play#android-app) documents the way to send an intent to Google Play.  It requires the passing of a URI (data) and setting a package.  Neither is currently supported.
The Intent documentation (https://developer.android.com/reference/android/content/Intent#intent-structure) lists the data parameter as a primary piece of information.
The sendIntent method should support both of these.
React Native Version
71.11
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 13.4
CPU: (10) arm64 Apple M1 Max
Memory: 1.27 GB / 64.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.16.0/bin/yarn
npm: 9.6.7 - ~/.nvm/versions/node/v16.16.0/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.0 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
Android SDK:
API Levels: 33
Build Tools: 30.0.3, 33.0.0
System Images: android-33 | Google APIs ARM 64 v8a, android-33 | Google Play ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: Flamingo 2022.2.1 Patch 2 Flamingo 2022.2.1 Patch 2
Xcode: 14.3/14E222b - /usr/bin/xcodebuild
Languages:
Java: 11.0.18 - /Users/dcorbin/.jenv/shims/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.11 => 0.71.11
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Try to link to a Google Play app or Developer page as documented here.  The existing API does not support it.
Snack, code example, screenshot, or link to a repository
  Linking.sendIntent('android.intent.action.VIEW', [ ])

⚠	Add or Reformat Version Info
ℹ	We could not find or parse the version number of React Native in your issue report. Please use the template, and report your version including major, minor, and patch numbers - e.g. 0.70.2

Is it not shown above as 0.71.11, 4 lines from the bottom.

I have attempt to create a patch for this, but there's clearly something I've missed on the internal workings of the project.  I can build and run rn-tester.    But after making my changes there are errors centered around the additional arguments I've added.  From what I can tell there something call Prefab that I may need to understand better, but can find little to no documentation about this.

The API is effectively not very useful due to the lack of data parameter. Could we reopen this issue?

I'm trying to figure out how to open an intent activity for the calendar service but it seems that it's impossibile with the current sendIntent function. @dcorbin, were you able to figure out how to solve the lack of parameters?

I did not.


Help needed to replace secret from user stores to Key vault

Reference
https://docs.microsoft.com/en-us/graph/tutorials/azure-functions?tutorial-step=5
Update code
Configuration is read from the user secret store, which only applies to your development machine. Before you publish to Azure, you'll need to change where you store your configuration, and update the code in Program.cs accordingly.
Can you please help how can we updated this code while publishing it in Azure Function app. Required code for Azure key vault or any other way .

This might be helpful: https://docs.microsoft.com/azure/app-service/app-service-key-vault-references.


Add padding to target coverage collection

The original BaitDepthWalker used in python recapseg (even though it is a GATK walker) adds a padding (250 bases on either side) to each target before counting the reads.  Additionally, it goes through logic to make sure reads are not double-counted.  The end result is that there is less noise in the coverage profiles, since substantially more reads are included in the estimates of copy ratio.

Note:  I am making the assumption that there are no differences in behavior in the PoN and tangent normalization in Hellbender from python.  With this assumption in place, the coverage collection is the only difference left.
If this assumption is not correct, then this issue may not necessarily need to be addressed.  And a new issue will be filed for the actual cause of the lower noise in python recapseg relative to Hellbender.

Looks like QC is improved by adding the padding (250)...

Summary updated with padding (250bp either side):

Metric
Comment
HB value
RCS value
Winner
HB passes CRSP

postQC
STAD samples  median postQC (lower is better)
0.085
0.119
HB
NA

Specificity

0.9879
0.9879
Tie
Yes

Reproducibility
RMSE (lower is better)
0.1414
0.1393
ReCapSeg possibly
Yes

Call Concordance

0.9762
0.9846
ReCapSeg
Yes

Small deletions
Purity series

Tie
Yes

Small amplifications
Purity series

Tie
Yes

Amplification Sensitivity
Purity series
see plots
see plots
Tie
Yes

Amplification Precision
Purity series
see plots
see plots
Tie
Yes

Deletion Sensitivity
Purity series
see plots
see plots
Tie
Yes

Deletion Precision
Purity series
see plots
see plots
Tie
Yes

Clinical Sensitivity
Caannot evaluate small deletions and small amplifications
see plots
see plots
Tie
Yes

https://iwww.broadinstitute.org/~lichtens/validationReport_out_pd250/recapseg_res.html


Refactor silence constants

Clean up silence constants duplicated; I chose to keep the ones declared inside the types package because it's where the silence struct is also declared.
@stuartnelson3 @brancz

@stuartnelson3 It appears that not only the State constants are duplicated, there is a few parts duplicated for pb.Silence and types.Silence. Maybe I should stay the constants duplicated as well, and only change the code that is using the hardcoded strings. Let me know if you what you prefer.


feat: expose TaskLocalFuture

This PR exposes TaskLocalFuture from tokio, which is also part of the task_local API.

published as v0.2.23


Flexible work Shop with Capacity

Hello all,
I am trying to add capacity constrain for the FJP problem. However during the implementation, I notice that the solve would get stuck when I increase the number of jobs just a little bit (say from 9 to 15).. The code I have tried and more details could be found from this link.
Could anyone give me some suggestions how to improve or change my current code to resolve this issue? Many thanks!

Can you send the code with 15 jobs ?
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mer. 18 sept. 2019 à 03:14, YooTimmy<EMAIL_ADDRESS>a écrit :

Hello all,
I am trying to add capacity constrain for the FJP problem. However during
the implementation, I notice that the solve would get stuck when I increase
the number of jobs just a little bit (say from 9 to 15).. The code I have
tried and more details could be found from this link
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/or-tools-discuss/0syUImixcFI
.
Could anyone give me some suggestions how to improve or change my current
code to resolve this issue? Many thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1584?email_source=notifications&email_token=ACUPL3K5PXAF3HBFYHHEON3QKF6G7A5CNFSM4IXXSBK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HMACRXQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3JZ4HRYH3MB6JTFXUDQKF6G7ANCNFSM4IXXSBKQ
.

Actually, let me rephrase
job_profile_1 = [[(3, 0), (2, 2)], [(2, 1)]]
job_profile_2 = [[(4, 0), (3, 2)], [(3, 1)]]
job_profile_list = [job_profile_1, job_profile_2]
The total amount of tasks to be planned on the machine
2 orders:
orders = [[(0, 3), (1, 3)], [(1, 3)]]
I understand the job profiles.
I do not understand the orders, do we create 3 copies of job 1 and 3 + 3
copies of job 2, or do we create 3 jobs that will require a capacity of 3
on the machines ?
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mer. 18 sept. 2019 à 09:38, Laurent Perron<EMAIL_ADDRESS>a écrit :

Can you send the code with 15 jobs ?
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68
53 00
Le mer. 18 sept. 2019 à 03:14, YooTimmy<EMAIL_ADDRESS>a
écrit :

Hello all,
I am trying to add capacity constrain for the FJP problem. However during
the implementation, I notice that the solve would get stuck when I increase
the number of jobs just a little bit (say from 9 to 15).. The code I have
tried and more details could be found from this link
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/or-tools-discuss/0syUImixcFI
.
Could anyone give me some suggestions how to improve or change my current
code to resolve this issue? Many thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1584?email_source=notifications&email_token=ACUPL3K5PXAF3HBFYHHEON3QKF6G7A5CNFSM4IXXSBK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HMACRXQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3JZ4HRYH3MB6JTFXUDQKF6G7ANCNFSM4IXXSBKQ
.

Hello Laurent,
Thanks for getting back. Short answer your first understanding is correct.
For Orders, it is more like simulating in real scenarios, where customer may need different jobs in each order. Let me explain the orders =  [[(0, 3), (1, 3)], [(1, 3)]]
Here there are 2 orders. First order is [(0, 3), (1, 3)], which means we create 3 copies of job 1 (0,3) and 3 copies of job 2 (1,3). Second Order is [(1,3)], which just means we need to create 3 copies of job 2. In other words, here we have a total 9 jobs that need to be planned (3 copies of job 1, and 6 copies of job 2). In this case, I can able to get a valid schedule.
When I mentioned changing 9 jobs to 15 jobs, I was just change the orders to [[(0, 5), (1, 5)], [(1, 5)]]. In this case seems the solver will stuck on my PC.

OK. So I believe that quite fast, you get the optimal solution.
Proving optimality is hard, and I am looking at redundant constraint for it.
I have not found anything yet.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mer. 18 sept. 2019 à 10:27, YooTimmy<EMAIL_ADDRESS>a écrit :

Hello Laurent,
Thanks for getting back. Short answer your first understanding is correct.
For Orders, it is more like simulating in real scenarios, where customer
may need different jobs in each order. Let me explain the orders = [[(0,
3), (1, 3)], [(1, 3)]]
Here there are 2 orders. First order is [(0, 3), (1, 3)], which means we
create 3 copies of job 1 (0,3) and 3 copies of job 2 (1,3). Second Order is
[(1,3)], which just means we need to create 3 copies of job 2. In other
words, here we have a total 9 jobs that need to be planned (3 copies of job
1, and 6 copies of job 2). In this case, I can able to get a valid schedule.
When I mentioned changing 9 jobs to 15 jobs, I was just change the orders
to [[(0, 5), (1, 5)], [(1, 5)]]. In this case seems the solver will stuck
on my PC.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1584?email_source=notifications&email_token=ACUPL3K4EQJEJPE5NBHBNYLQKHQ7VA5CNFSM4IXXSBK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD67IENI#issuecomment-532578869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3K4XEA55HMCEPHUYL3QKHQ7VANCNFSM4IXXSBKQ
.

Hello Laurent,
Thanks for the feedback.

So I believe that quite fast, you get the optimal solution.

I am not sure if I capture you correctly. For now in the case of 15 jobs, I have tried to let it run for like 10 mins, seems it is not solved by then. Maybe I should wait some more time?

If that is the case, is the reason because perhaps adding the capacity consideration to flexible job shop problem would increase the complexity significantly? I thought 15 jobs is not that much but seems not the case then.

I believe 17 is optimal. So you get it in 0.04s.
Proof is just hard.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mer. 18 sept. 2019 à 10:55, YooTimmy<EMAIL_ADDRESS>a écrit :

Hello Laurent,
Thanks for the feedback.
So I believe that quite fast, you get the optimal solution.
I am not sure if I capture you correctly. For now in the case of 15 jobs,
I have tried to let it run for like 10 mins, seems it is not solved by
then. Maybe I should wait some more time?
[image: image]
https://user-images.githubusercontent.com/32185776/65133114-b2892e00-da34-11e9-9562-5d23510dc281.png
If that is the case, is the reason because perhaps adding the capacity
consideration to flexible job shop problem would increase the complexity
significantly? I thought 15 jobs is not that much but seems not the case
then.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1584?email_source=notifications&email_token=ACUPL3KGGOMUNYSUR7JNII3QKHUHNA5CNFSM4IXXSBK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD67KYYA#issuecomment-532589664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3LEZPQQ63TKCZXJVCLQKHUHNANCNFSM4IXXSBKQ
.

Got it!
Would it be possible to let solver return the variable values when it is not able to prove it is optimal say in 60s? I guess that will be helpful as well as a potential optimal solution.

Thank you Laurent, now I understand your point.

Just add a time limit.
https://github.com/google/or-tools/blob/stable/ortools/sat/doc/solver.md#changing-the-parameters-of-the-solver
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mer. 18 sept. 2019 à 11:26, YooTimmy<EMAIL_ADDRESS>a écrit :

Thank you Laurent, now I understand your point.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1584?email_source=notifications&email_token=ACUPL3IYDLBGMOPDTWJJDFTQKHX3JA5CNFSM4IXXSBK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD67NYUY#issuecomment-532601939,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3P7MNOX5BHPJ5OK3LLQKHX3JANCNFSM4IXXSBKQ
.


require the operator-sdk v1 and yq version 4

If you have operator-sdk v1 or yq version 3 installed, it will still download newer version of tools to make it running.

/shrug

/lgtm

/pony

/pony


SESE Loops: transform loops to have single exit block in non-cloning case.

I could not break the PR further down. Hopefully the algorithm outline presented here helps.
Algorithm Outline
(Note that exiting blocks are inside the loop and exit blocks are outside the loop. Therefore, an exit edge is from an exiting block to an exit block.)
This PR takes care of transforming the loop such that the common post dominator of all exit blocks is the new exit block for the loop.  This is one of the several transformations needed to eliminate undef from SESE loops. Consider the following snippet:
while(...) {
   if (...) {
     ...
     break;
   }
}

Recall that the blocks within if do not belong to the while loop in the SIL IR. The transformation implemented in this PR has the effect of moving the blocks back into the loop.
Step 1. Transform Loop.  (See ensureSingleExitBlock)

Let nearestCommonPD be the  nearest common post-dominator block of all the exit blocks.
Move all the blocks reachable from exiting blocks to the nearestCommonPD inside the loop. (It is not always possible to move all reachable blocks without cloning some of the them.  See notes below.)
Let exitBlocks be the set of exit blocks for the loop  after the above transformation.

Step 2. Connect exiting blocks to a new latch and unify loop arguments. (See patchEdges)
(Only changes related to exit arguments are shown here.)

Let exitArgs be the union of the arguments of all exitBlocks.
for each exitArg in exitArgs, add an appropriate argument to the new header block. Let p0, p1, ..pn be the new arguments corresponding to exit arguments a0, a1, a2, ..., an.
For a exit edge br exit_i(x, y, z) -> exit_i(a2, a3, a4), change it to br new_latch(p0, p1, a2, a3, a4, ..., an)

Notes.
If a block is not dominated by the header of the loop, we cannot move it into the loop in Step 1. For such cases, we will need to clone the block before moving it into the loop. I will send out a separate PR for that purpose.

@swift-ci please test tensorflow linux

@swift-ci please test tensorflow macos

From a quick read of the code (not a deep algorithmic understanding) the patch LGTM!

I will go ahead and merge the PR.


I Ran a basic web server to test http PATCH call
type User struct {
ID   int    json:"id"
}
func main() {
http.HandleFunc("/users/", patchUserHandler)
http.ListenAndServe(":8080", nil)
}
func patchUserHandler(w http.ResponseWriter, r *http.Request) {
...
..
json.NewEncoder(w).Encode(User{})
}
What did you see happen?
NO response when run from curl or postman or go client code
curl --location --request PATCH 'http://localhost:8080/users/'
GET/POST/DELETE/PUT is working
When monitored from wireshark I can see the response in http packet
When run directly run within ubuntu VM (in microk8s) on same go version, getting response for PATCH call.
What did you expect to see?
Expecting any "response" either 200+ or 400+ http status

Related Issues and Documentation

affected/package:  #62521 (closed)
net/http: Http Server (request) is not working with enabled Proxy Protocol #64365 (closed)
net/http: server will drop tcp connections after a certain number of concurrent connections are made #61924 (closed)
net/http: Content-Length: 0 is not set for PATCH requests with empty body #40978 (closed)
net/http: Listening on localhost at port 8080 on Darwin #16676 (closed)
net/http: enhanced ServerMux routing #65231 (closed)
net/http header not being set as expected #50587 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Sounds like a problem with your client software if you can see the http response sent over the wire.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


[Bug]: Unexpected token 'export' when Jest test imports d3 (7.1.1)

Version
27.3.1
Steps to reproduce
We use Typescript, if our test file (*.spec.ts) contains the following import
import { scaleLinear } from 'd3';

Expected behavior
Test runs without problems
Actual behavior
Running the test will give the following error:
.../node_modules/d3/src/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from "d3-array";
                                                                                ^^^^^^

    SyntaxError: Unexpected token 'export'

Additional context
The issue started when updating Jest from 26.6.3 to 27.3.1.
I finally found a workaround for this. I first found this Jest issue https://github.com/facebook/jest/issues/2550 it mentioned setting up transformIgnorePatterns and adding "allowJs": true to our tsconfig.json. This did not work, what did solve it in the end was adding the following to our jest.config.js:
    moduleNameMapper: {
        'd3': '<rootDir>/node_modules/d3/dist/d3.min.js',
    },

Which makes it import from that minified file instead of node_modules/d3/src/index.js. Not sure if it is reasonable and possible for Jest to import from a module's dist folder when it cannot import from the index file? Also not sure if this is an issue with d3 or a mismatch with all the different ways in which you can express JavaScript (ESM/CommonJS/...)?
Environment
System:
    OS: Linux 5.11 Ubuntu 21.04 (Hirsute Hippo)
    CPU: (16) x64 Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz
  Binaries:
    Node: 14.16.1 - /tmp/fnm_multishells/13239_1636009783566/bin/node
    npm: 6.14.12 - /tmp/fnm_multishells/13239_1636009783566/bin/npm
  npmPackages:
    jest: 27.3.1 => 27.3.1

I had the same problem yesterday.

I'm having this problem as well with the "unified" module, which is an ESM only module. This is on Node v12 on a recent MacBook Pro<EMAIL_ADDRESS>

I have a React project created with Nx and I am using TypeScript, I have<EMAIL_ADDRESS>and I also receive the same error.

@istvandesign did the workaround I ended up with work for you?
so adding this to your jest config:
moduleNameMapper: {
    'd3': '<rootDir>/node_modules/d3/dist/d3.min.js',
},

I had to use the transformIgnorePatterns in one of my projects..
"transformIgnorePatterns": [
    "/node_modules/(?!d3|d3-array|internmap|delaunator|robust-predicates)"
],

I had to do this with multiple modules.

@istvandesign did the workaround I ended up with work for you?
so adding this to your jest config:
moduleNameMapper: {
    'd3': '<rootDir>/node_modules/d3/dist/d3.min.js',
},

mapping the d3 to the final bundle worked for me since the jest does not need to compile ESModule anymore. Thanks!

ran into this issue in a typescript project using jest@27 with a few d3-* (ESM) dependencies. No luck fiddling with #transformIgnorePatterns, but arrived at same general workaround as @maistrotoad with #moduleNameMapper:
  moduleNameMapper: {
    ...
+   "^d3-(.*)$": `d3-$1/dist/d3-$1`
  }

I'm not sure if all d3-* pkgs are similarly structured, but the ones on which my project depends are. Hopefully we won't need to revisit when we add another.

d3 should add a require condition (https://www.runpkg.com/?d3@7.3.0/package.json#32), then Jest 28 (via #9771) will support this.
beyond that, this is a usage question and not a bug, so closing this


feat(ingest/unity): Ingest notebooks and their lineage

We don't get notebook upstreams directly, instead we get tables' upstreams and downstreams which can include notebooks. Am open to suggestions on how to solve this in a cleaner way
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Merging through test failures as I think they failed due to slowness / node image not being available?


Revert " Add formatting support for fork"

Reverts ballerina-platform/ballerina-lang#15328
Reverting this PR because of the semantic error generated after refactoring implementation to stop duplicating worker nodes in the forkjoin node and in the parent block of the forkjoin node. By removing duplication it removes visibility of workers in forkjoin to outside block.

Codecov Report

Merging #15381 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master   #15381      +/-   ##
============================================
- Coverage     22.84%   22.81%   -0.03%
+ Complexity     5112     5105       -7
============================================
  Files          1352     1352
  Lines         69591    69567      -24
  Branches       9407     9396      -11
============================================
- Hits          15895    15870      -25
- Misses        51917    51923       +6
+ Partials       1779     1774       -5

Impacted Files
Coverage Δ
Complexity Δ

...ang/langserver/formatting/FormattingConstants.java
50% <ø> (ø)
1 <0> (ø)
:arrow_down:

...rg/ballerinalang/langserver/formatting/Tokens.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...lang/langserver/formatting/FormattingNodeTree.java
73.95% <0%> (-0.27%)
766 <0> (-7)

...erinalang/compiler/parser/BLangPackageBuilder.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Improve npm package names

I feel Athenz npm package's names aren't better for practices of Node.js.

Avoid redundant naming: "nodejs" in package name is redundant. npm packages are always provided for Node.js runtime.
Use hyphen instead of underscore: npm package name usually uses hyphen. e.g. eslint-, babel-.
Push all packages into one namespace: auth-core doesn't associate Athenz with the package name. Use scoped package name instead.

This changes is my proposal these issues. Please let me know if you have more idea on this.

@okuryu Thanks for the PR but have you had a chance to look at the Travis CI build failure and provide an update to fix the build issue. Thanks.

The build failure due to the @athenz/auth-core package isn't available on the npm registry yet. I just reverted the path to @athenz/auth-core to a relative path to resolve dependencies of ui in 586b77e.
The building passed now, but I think we should revert 586b77e again after the @athenz/auth-core package is published on the npm registry.


WebView-Update package to latest version

link SDK has an old version of the web view, it needs to be updated, and because of this it creates version solving failed issue

Fixed in https://github.com/leantechnologies/link-sdk-flutter/pull/15


Accommodate asynchronous pattern

Problem description
This topic is mentioned here https://github.com/camaraproject/PopulationDensityData/issues/10 but probably deserves it owns issue.
Seems that for UCs we can provide asynchronous answer that will allow us more flexibility to handle the request.
If we want to offer this capability we need slight changes.
Possible evolution

add 202 as possible answer
add callbackurl & token in the request. By valued them the consumer expect to get an asynchronous answer and this answer will be posted  to this callbackUrl

Alternative solution

add 202 as possible answer
add a requestId in the POST response & provide GET operation but this change a bit more the API

Additional context

I believe,  the first approach with the callback URL and token is more appropriate for our current API scenario. Providing the callback URL in the initial response simplifies the process for the client, eliminating the need for additional requests (first to get subscription ID and then CallbackURL) or managing subscription IDs. Additionally, since the client is only interested in receiving the processed data once, there's no need for a subscription model or ongoing updates.

Agreed that first option allows a better and more refine approach, also enabling sync use case in case callback is not included in the request, but on the other side provides a higher complexity for the developer to enable such callback endpoint.
Based on meeting discussions, #21 is including callback proposal as reference, with some modifications to be implemented, but discussion will remain opened at least until next meeting.

Agreed, we can go with first option to have callback URL.

Works for me.
Note: As we are changing the subscription model I expect some name change for the attributes. It will not change the fonction of the callback but the attributes instead of webhook should be sink. Perhaps let's wait this update before to change the yaml.

With this two validations, I'd suggest to merge this PR to follow discussion on additional specification topics.

@sachinvodafone can we merge?


Undefined symbols for architecture arm64

Hi,
My setup is

Setup
Version

React Native
0.68.2

AppCues
3.1.4

XCode
13.4.1

I'm facing an issue when building my app
Undefined symbols for architecture arm64:
  "tooltipFrame #1 (position: AppcuesKit.ContentPosition) -> __C.CGRect in AppcuesKit.TooltipWrapperView.(tooltipPosition in _55E48D59DE4D8313706070264B9F9B2C)(for: __C.CGRect) -> __C.CGRect", referenced from:
      AppcuesKit.TooltipWrapperView.(tooltipPosition in _55E48D59DE4D8313706070264B9F9B2C)(for: __C.CGRect) -> __C.CGRect in libAppcues.a(TooltipWrapperView.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I'm available for any further informations if needed

On the Android side, our native SDK (which this React Native module wraps) does require Android API 34 in the latest versions, due to the usage of Jetpack Compose 1.5. This ends up causing the latest versions of this module to also require Android API 34 in the build, and thus a compatible version of React Native. I believe the root issue on the React Native side with Android API 34 was this one. And that issue was resolved in 0.72.4 and also ported back to 0.71.13, so I would suspect that any version of 0.71.13+ would also be sufficient, but likely not back to the 0.68.2 version mentioned here, unfortunately.
On the iOS side, an older version of React Native should still work, as long as it can use the newer version of Xcode.
Attempting to use an older version of this module may help in the short term - you could try version 3.1.0 here, as that was the last version before the Android 34 requirement update. We would not recommend this long term, as it will be missing the more recent updates and fixes that have been made, but it is certainly an option to test out your build environment to start, at least.


navigate is not available in iteration

Describe the bug
Original codes :
https://github.com/leptos-rs/leptos/blob/4029de2d42f3b15368111c83e28fd4817c99c9d2/examples/router/src/lib.rs#L87-L101
bug:

    let location = use_location();
    let navigate = use_navigate();
    let contacts = create_resource(move || location.search.get(), get_contacts);
    let contacts = move || {
        contacts.get().map(|contacts| {
            // this data doesn't change frequently so we can use .map().collect() instead of a keyed <For/>
            contacts
                .into_iter()
                .map(|contact| {
                    view! {
                        //
{&contact.first_name} " " {&contact.last_name}

{&contact.first_name} " " {&contact.last_name}

                    }
                })
                .collect_view()
        })
    };

Irrelevant but important note: You should (almost) never use . You should use . This is important for accessibility.

I think you mean that this example doesn't compile, with the following error:
error[E0525]: expected a closure that implements the `Fn` trait, but this closure only implements `FnOnce`
    --> src/lib.rs:90:20
     |
90   |     let contacts = move || {
     |                    ^^^^^^^ this closure implements `FnOnce`, not `Fn`
...
99   |                             navigate("", Default::default());
     |                             -------- closure is `FnOnce` because it moves the variable `navigate` out of its environment
...
111  |                 {move || view! {
{contacts}
}}
     |                          ----------------------------
     |                          |            |
     |                          |            this tail expression is of type `[closure@lib.rs:90:20]`
     |                          the requirement to implement `Fn` derives from here
     |                          required by a bound introduced by this call
     |
     = note: required for `[closure@src/lib.rs:90:20: 90:27]` to implement `leptos::IntoView`
note: required by a bound in `leptos::HtmlElement::<El>::child`
    --> /Users/gjohnston/Documents/Projects/leptos-main/leptos/leptos_dom/src/html.rs:1061:36
     |
1061 |     pub fn child(self, child: impl IntoView) -> Self {
     |                                    ^^^^^^^^ required by this bound in `HtmlElement::<El>::child`

This is just a fairly normal Rust ownership error. use_navigate returns impl Fn(&str, NavigateOptions) without guaranteeing that that function is Clone or Copy. If you want to share it between multiple other items, you should add some kind of wrapper, like Rc or StoredValue.
The example below does exactly what your example does, but uses store_value to share navigate callback between the multiple event listeners:
    let location = use_location();
    let navigate = store_value(use_navigate());
    let contacts = create_resource(move || location.search.get(), get_contacts);
    let contacts = move || {
        contacts.get().map(move |contacts| {
            // this data doesn't change frequently so we can use .map().collect() instead of a keyed <For/>
            contacts
                .into_iter()
                .map(move |contact| {
                    view! {
                        //
{&contact.first_name} " " {&contact.last_name}

{&contact.first_name} " " {&contact.last_name}

                    }
                })
                .collect_view()
        })
    };


ml2cpp step 13 : Caret R Models

See https://github.com/antoinecarme/caret2sql
Follow the six steps described in #1

Closing


Streaming: failure to drain output stream unless .end() is called

Testing with current v0.6.0-snapshot release bits
The function below writes an output message (the current running average) when an input is negative, and re-computes a running average as long as the the inputs are positive.
With the function as written below, and the input stream on('end',...) handler disabled, the output stream is not drained, and nothing appears on the output stream after publishing a positive and a negative value to trigger the output. This is unexpected.
The function does work when the on('end') handler is uncommented, to call .end() on the output stream.
module.exports = (inputStreams, outputStreams) => {
  const ins = inputStreams.in;
  const outs  = outputStreams.out;
  console.log('new invocation');

  let avg = undefined;
  let sum = 0;
  let cnt = 0;

  ins.on('data', (x) => {

    if (x < 0) {
      if (avg) {
        let rval = outs.write(avg);
        console.log('outs.write: ', avg, rval ? '(OK)' : '(not OK)');
      }
      avg = undefined;
      sum = 0;
      cnt = 0;
      return;
    }

    if (x >= 0) {
      sum += x;
      cnt ++;
      avg = sum/cnt;
      console.log('avg updated: ', avg);
    }
  });

  ins.on("end", () => {
    // *********************************************
    // outs.end();
    // console.log('end on ins, call outs.end()');
    // *********************************************
    console.log('end on ins, NO outs.end()');
  });
  ins.on("error", (err) => {
    outs.end();
    console.log('error on ins, outs.end()', err);
  });
  outs.on("error", (err) => {
    ins.end();
    console.log('error on outs, ins.end()', err);
  });
};

module.exports.$interactionModel = 'node-streams';

TL;DR: I cannot reproduce the issue
I tried to reproduce the issue with a simpler version of the program, i.e. rid of end/error handlers:
module.exports = (inputStreams, outputStreams) => {
    const { ins } = inputStreams;
    const { outs } = outputStreams;
    let avg = undefined;
    let sum = 0;
    let cnt = 0;
    ins.on("data", x => {
        if (x < 0) {
            if (avg) {
                outs.write(avg);
                console.log("output: ", avg);
            }
            avg = undefined;
            sum = 0;
            cnt = 0;
            return;
        }
        if (x >= 0) {
            sum += x;
            cnt++;
            avg = sum / cnt;
            console.log("average updated: ", avg);
        }
    });
};
module.exports.$interactionModel = "node-streams";

I ran this with both the invoker and streaming processor running on my machine (as well as a simple main function wrapping stream-client-go to send data to remote streams).
I got the expected "average updated: " logs whenever a positive number was sent, as well as the expected "output" when I sent a negative number.

Closed due to lack of reproducibility.