fix(tracking_object_merger): fix bug and rework parameters

Description
Use param file as well as fixing a bug in param name.
Must be merged with https://github.com/autowarefoundation/autoware_launch/pull/823

Tests performed

Launch Autoware and parameters are successfully loaded.
Effects on system behavior

Now logging_file_path will be /tmp/decorative_tracker_merger.log and enable_logging will be false by default in Autoware (see https://github.com/autowarefoundation/autoware_launch/pull/823).
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@YoshiRi Would appreciate if you could briefly check this PR :pray:
This will fix a bug, which will change the default parameter of tracking_object_merger. Let me know if it is better to set the default value something else.

@YoshiRi Would you also approve https://github.com/autowarefoundation/autoware_launch/pull/823?


Updated the Alembic Standin plugin.

Hi, I have done a few changes to the Arnold DSO as we had troubles to use it in certain scenarios:

Fixed the Alembic Standin plugin so it's pulling data from the good parameter (names have changed)

Added Ogawa support to the Arnold DSO

The plugin will compute the normals if the attribute is not defined in the geometry instead of skipping the geo.

Changed the way the motion blur is done for dynamic topology, a velocity attribute is needed.

Thank you!  I will merge this but I haven't tested it.


fix: typos Mepdlum in documents and react-hooks

Fix typos Mepdlum in documents and react-hooks

thanks @ThatOneBro,
can you help with 2 failing check ? Or i can merge now ?

thanks @ThatOneBro, can you help with 2 failing check ? Or i can merge now ?

Sorry about that, just needed approval.  Should be done soon.


Filename is too short

Hello,
Thanks for the great wrapper! Works flawlessly.
Please consider making filename longer, because it is truncated too much which makes unclear what file is processed.

I tried to increase targetLength from 10 to larger number in
https://github.com/sidneys/ffmpeg-progressbar-cli/blob/master/lib/formatter.js#L36
But it didn't help
As a workaround for showing full filename I just commented out all filename length checker. And it seems to work now.
    if (fileNameLength > targetLength) {
        if (fileExtensionLength < (targetLength - 2)) {
            // Name too long: ellipse title, leave extension as-is
            // filetit….extension
            fileName = `${ellipsize(fileTitle, targetLength - fileExtensionLength, { ellipse: ellipseCharacter })}${fileExtension}`
        } else {
            // Name too long, extension too long: Ellipse title, hide extension
            // filetit…
            fileName = `${ellipsize(fileTitle, targetLength, { ellipse: ellipseCharacter })}`
        }
    } else if (fileNameLength < targetLength) {
        if (fileNameLength >= (targetLength - 1)) {
            // Name too short by less than 2 characters: pad title left
            //   filetitle.extension
            fileName = `${fileTitle}${fileExtension}`.padStart(targetLength, ' ')
        } else {
            // Name too short by more than 2 characters: Prefix ellipsed directory tree
            // …ocuments/filetitle.extension
            fileName = `${ellipseCharacter}${filePath.substr(filePath.length - targetLength + 1, filePath.length - 1)}`
        }
    } else {
        // File name has perfect length
        fileName = `${fileTitle}${fileExtension}`
    }

Same thing to me: long file names are cut, also if there is space left on screen
Screenshot: https://imgur.com/eUcOZWn


Slim Redirect Displays Headers Only

Slim Redirect method returns a 301 status code and nothing more. I will like to redirect to a login page if a user is not signed in. but I keep getting a header that looks like this :
HTTP/1.1 301 $s
Server: nginx/1.13.7
Date: Thu, 14 Dec 2017 15:56:53 GMT
Transfer-Encoding: chunked
Connection: keep-alive
: /login:
I expect that the redirect method will call '\login' route which will then display my login.html page. I  have attached a copy of my server.php file below. When I execute curl -D- localhost/login, it works. What am I doing wrong?

$slim->get('/', function(Request $req, Response $res) use ($provider): Response{
$sessionId = $req->getCookieParams()['session'] ?? ' ';
if(!$provider->hasSession($sessionId))
{
return $res->withRedirect('/login');
}

//Login Callback

$slim->get('/login', function(Request $req, Response $res): Response {
$res->getBody()->write(file_get_contents('templates/login.html'));
return $res->withHeader('Content-Type', 'text/html;charset=utf8');
});

$adapter = new \Packt\Chp6\Http\SlimAdapterServer($slim);
//Login Route
$app->route('/', $adapter, ['*']);
$app->route('/login', $adapter, ['*']);
server.php.zip

Please provide the output of curl -I http://yourserver.com/path/to/

Thank you. This is output that I get...

HTTP/1.1 301 $s
Server: nginx/1.13.7
Date: Thu, 14 Dec 2017 16:26:04 GMT
Connection: keep-alive
: /login:

That makes no sense as the status line is wrong and you're missing a header name.
How about curl -v http://yourserver.com/path/to/ ? Also show me the curl command itself.

Ahh Yes you are right when I curl -I http://localhost/login, I get this output:

HTTP/1.1 200 $s
Server: nginx/1.13.7
Date: Thu, 14 Dec 2017 16:30:31 GMT
Connection: keep-alive
: text/html;charset=utf8:

curl command is  curl -I http://localhost/login

You dont have a content type header?
In the previous one you don't have a Location header.

thank you.  Where do I set the content type header and location header...
I did curl -v http://localhost/login and I got this output:

Trying ::1...
TCP_NODELAY set
Trying <IP_ADDRESS>...
TCP_NODELAY set
Connected to localhost (<IP_ADDRESS>) port 80 (#0)

GET /login HTTP/1.1
Host: localhost
User-Agent: curl/7.54.0
Accept: /
HTTP/1.1 200 $s
Server: nginx/1.13.7
Date: Thu, 14 Dec 2017 16:45:40 GMT
Transfer-Encoding: chunked
Connection: keep-alive
: text/html;charset=utf8:

Chat Application: Login

Login

Username
class="form-control">

Password
class="form-control">

                       Log in

I'm going to guess that it's a problem somewhere in your NGINX configuration. Slim and PHP sets a default header for Content-Type.

wow, I just realized that. Let me check my Nginx config file.

I fixed the header issue. My output for curl -D- http://localhost is

HTTP/1.1 302 Found
Server: nginx/1.13.7
Date: Fri, 15 Dec 2017 05:13:37 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Location: /login

The content-type is not showing up at all. When I curl -D- http://localhost/login (file that I want to be redirected to...) I get the following output:

HTTP/1.1 200 OK
Server: nginx/1.13.7
Date: Fri, 15 Dec 2017 05:21:32 GMT
Content-Type: text/html;charset=utf8
Transfer-Encoding: chunked
Connection: keep-alive

I would have expected that redirection to work. You don't need a Content-Type header for a 302, but you do need a Location.

Perhaps it could be from my Nginx conf file. Please, can you take a look at it and see if it has any bug. According to my Nginx configuration, a request made to http://localhost/ should serve index.html, then my code logic says the user has no sessions so redirect to http://localhost/login instead.
Am I missing something? Thank you for your replies and help...
 It is working now. Thank you so much

You’re welcome.


called Option::unwrap() on a None value

Hi Prisma Team! My Prisma Client just crashed. This is the report:
Versions

Name
Version

Node
v20.8.1

OS
debian-openssl-3.0.x

Prisma Client
5.3.1

Query Engine
61e140623197a131c2a6189271ffee05a7aa9a59

Database
mysql

Logs
-specific paths for "debian" (and "ubuntu")
prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
}
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu")
prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
}
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu")
prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
}
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu")
prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
}
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu")
prisma:get-platform Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
}
prisma:get-platform Trying platform-specific paths for "debian" (and "ubuntu")
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:client:libraryEngine library starting
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:get-platform Found libssl.so file using platform-specific paths: libssl.so.3
prisma:get-platform The parsed libssl version is: 3.0.x
prisma:client:engines:resolveEnginePath enginePath /root/caribes-back/node_modules/.prisma/client/libquery_engine-debian-openssl-3.0.x.so.node
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true

Client Snippet
        let links: any[] = await this.prismaService.target_links.findMany({
            select: {
                id: true,
                source: true,
                link: true,
                site_id: true,
                site: {
                  select: {
                    name: true,
                    domain: true
                  },
                },
                created_at: true,
                source_rec: {
                  select: {
                    utm_source: true,
                    source_id: true,
                    name: true
                  },
                },
              },
            orderBy: {
              [name]: dir
            }
        });
// ERROR VANISHED WHEN I COMMENT OUT source_rec: { ...

Schema
// PLEASE ADD YOUR SCHEMA HERE IF POSSIBLE
model target_links {
  id         Int       @id @default(autoincrement())
  site_id    Int
  source     String    @db.VarChar(255)
  link       String    @db.Text
  created_at DateTime? @db.DateTime(0)

  site       sites_list @relation(fields: [site_id], references: [id])
  source_rec sources    @relation(fields: [source], references: [utm_source])
}

model sources {
  source_id     Int      @id @default(autoincrement())
  name          String?  @db.VarChar(255)
  utm_source    String?  @unique @db.VarChar(255)
  active        Boolean  @default(true)
  comment       String?  @db.Text
  created_at    DateTime @default(now()) @db.Timestamp(0)

  target_links   target_links[]
  web_list       web_list[]
  calendars_list calendars_list[]
  rates_v2       rates_v2[]
}

Prisma Engine Query
{"X":true}}}}}

Googling error message shows that issue was fixed at 4 version
https://github.com/prisma/prisma-engines/pull/2973
but I have 5th..

Hey @cosinus90,
Would you be able to provide us with a contained reproduction repository? That would help us a lot here because the issue is very likely to be about your data rather than just the schema.
Thanks 🙏


Check presence of ca cert in kubeconfig

Signed-off-by: Tamal Saha<EMAIL_ADDRESS>

xref: https://github.com/appscodelabs/issues/issues/103


Ctrl+V (vertical selection in Vim) does not work

I guess it's because it's now bound by default to do paste.
I think it's quite a pain point for anyone new to Linux development on Window: vim basic functionality does not work :(

I think MS Terminal should allow some Keybinding Profiles (like Visual Studio / ReSharper do) and hopefully it would be super-easy to change them. It may seem that satisfy everyone is impossible :(

So we've probably had this discussion 1000 times across this repo now. The basic conclusion is always the same:

It may seem that satisfy everyone is impossible

When we only had Ctrl+Shift+C/Ctrl+Shift+V as the copy/paste keybindings, users were unhappy. Now that we've added back Ctrl+C/Ctrl+V, users are still unhappy.
With the new "default" settings in 0.11, the balance we've tried to compromise on is the following:

Ctrl+Shift+C/Ctrl+Shift+V are bound in defaults.json, and users will need to actually unbind those keys to disable their functionality.

These are the keybindings we've always had for copy-paste, so breaking them seemed like a terrible idea
Nobody was really complaining about these being used for copy/paste as opposed to something else

Ctrl+C/Ctrl+V are now listed in new user's settings.json file when they create a new settings file.

If they don't like them, it's trivial to just delete them from the file.
Ctrl+Shift+C/Ctrl+Shift+V will still work if the user deletes the Ctrl+C/Ctrl+V bindings from their settings.json

I understand there're tradeoffs. I understand one can fix manually the keybindings by editing settings.json.
The point of this issue is to point out a concrete example of very common, wide-spread vim functionality that breaks. This is not just "I don't like Ctrl+V", it is a problem that almost every vim-user will encounter. Since it's wide-spread, I think, it calls for more special consideration: e.g. big letters in README about this specifically or MessageBox on first launch, or an explicit invitation to change keybindings on the first launch, or sth else.
The profile idea would allow users to change multiple keybindings at once without encountering the problems and fixing them one by one. The same motivation applies to Microsoft Visual Studio / IntelliJ etc. If my preset is e.g. "Gnome Terminal", I'm sure everything will "just work" and have correct expectations about the chosen tradeoffs.

I'm actually having issues with ctrl+shift+v behaving erratically. It's not pasting new lines apparently.

So, this would ultimately be solved by /dup #5790, which I've promoted to be "profile-specific keybindings". FWIW: I don't like binding ^V by default either, but I more don't like how literally 50% of all our users yell at us regardless of the choice we made. :smile:
All we can do is add more flexibility.


[Feature Request] Refactoring into idf library and separate blink example

We are thinking about refactoring the codebase in the following directory structure:

idf/

imports
includes
...

blink/

app.zig
build.zig
build.zon

What do you think about this structure @kassane ?
My hope is if we use this structure we could reference the idf-library directly from our build.zon midterm so we would not need to include it in our codebase directly.
I am envisioning sth like this:
    .dependencies = .{
        .idf = .{
            .url = "git+https://github.com/kassane/zig-esp-idf-sample/idf",
            .hash = "",
        },
    },

If you would agree that this structure is a good way forward I am happy to help with the refactoring (I would need your guidance with respect to the idf / cmake integration though)

The first time it was that the api shared was this:
https://github.com/georgik/esp32-lang-lab/tree/main/examples%2Fzig%2Fesp-idf-v5%2Fget-started%2Fhello_world

However, I still need to be careful with cmakelists. How would this refactoring work?
Unfortunately the current solution for this project depends on CMake!!
If the proposal makes it easier and passes the CI/CD test, I approve it without any problem.

I would need your guidance with respect to the idf/cmake integration though

Zig's integration into cmake is modularized (see https://github.com/kassane/zig-esp-idf-sample/commit/a313db9c13a9bb827791041c56cdb547cc6ed2c2) and detached from the main/CMakeLists.txt script, perhaps making it easier to include in multiple cmakelists (add_subdirectory(blink_path) projects).

Hey @kassane,
I did some initial tests of separating the two projects. My idea would be to only rely on zig build system for separation, make zig build system pull in the dependency and then provide the final build result to cmake.
Unfortunately I have some issues with the setup that I do not fully understand.
Here is my initial setup:
zig-idf base library:
https://github.com/opendata-nuernberg/zig-idf
zig-idf application sample:
https://github.com/JanBeelte/zig-esp-idf-sample
if you check out both repositories on the same directory level e.g.:
~/projects/zig-esp-idf-sample
~/projects/zig-idf
you should be able to run idf.py build from within zig-esp-idf-sample. The dependency resolution already works and the zig-idf project is compiled. During that process you can see a lot of errors from zig build system complaining that it cannot find the imports so it looks like I broke sth with respect to the build system I currently do not fully understand.
Maybe you could take a look and provide a hint?

Update, I managed to fix all the import issues, now I am facing a linking issue:
libapp_zig.a.o):(.literal+0xc0): undefined reference to `esp_log_system_timestamp'
collect2: error: ld returned 1 exit status

do you maybe have an idea how to fix that?

anything that I should change here?

Remove or replace esp_log_system_timestamp -- compare to import/log.zig in esp_log function and see esp_log_timestamp.

Ok we have a working proposal for the restructuring now.
We split the repository into two parts, a base library and some minimal samples that show how to use it.
You can find our proposal for the base library here:
https://github.com/opendata-nuernberg/zig-idf
If you want we can keep the ownership in opendata-nuernberg and invite you as an admin or you create a new repository where you have exclusive ownership.
Whatever you prefer, I would propose to remove the word "sample" from the repository name.
You can find our proposal for the samples here:
https://github.com/JanBeelte/zig-esp-idf-sample
I also added some instructions on how to build the blink example for beginners.
What I really like about this new approach that we can fully utilise the zig build system for the base library like this:
https://github.com/JanBeelte/zig-esp-idf-sample/blob/fb49237674eab08be5249aeb7fedd8c4fe178493/blink/build.zig.zon#L12
I also tried to create working versions of blink_s3SPI and mqtt_client that I found in your example folder. Unfortunately I could not make them compile, maybe you can chime in here?

If you want we can keep the ownership in opendata-nuernberg and invite you as an admin or you create a new repository where you have exclusive ownership.

No, thank you! However, PRs are accepted from this proposal up.

I also tried to create working versions of blink_s3SPI and mqtt_client that I found in your example folder. Unfortunately I could not make them compile, maybe you can chime in here?

Mqtt is incomplete [untested], I admit (based on the official example)!!!
esp32s3_blink was a RGB_led test. I tried tested it both in C++ and Zig with build.zig and my device worked, although it is still subject to problems from upstream (esp-idf). See #3

Besides those points, you're doing a great refactoring process.
Although this project was a solo experiment to sharpen my interest in it (inspired by the esp-rs team).


Redis pipeline enablement

Enabled Redis pipeline on cluster
And include redis-plus-plus change also, to avoid build dependency failure.

This PR include the dependency change also.
Will avoid build failure @przmk0

Is there a chance to fix #182  at the same time ?

Is there a chance that it also fix #182 at the same time ?

This patch is non ralated to the issue.  My patch change the code only with redis cluster, will not impact legacy redis feature.
Acturally I have verified docker-compose(single machine), but cannot reproduce issue #182 at all.

@cdelimitrou can you help to review and merge this pach please?
The issue #182 has been resolved. And not ralated to this PR.


Refactor periodic re-authentication as expire WireGuard configuration after...

The periodic re-authentication feature has been a source of UX woes, and leaked configs will still work indefinitely as long as the originating user keeps signing in.
Refactor this feature to instead "expire configurations" after a set period of time.

[ ] Move preshared_key, public_key to a new table, wireguard_keys so their lifetime is decoupled from other device details
[ ] Update marketing material to reflect new functionality
[ ] Add comment to generated WireGuard configurations noting the expired time

Caveat
This will likely be a non-issue or be further refactored into a more general key rotation feature after we have client applications.

cc @conectado

With #1329 this won't be relevant anymore.


⚠ Bofrost.fr has degraded performance

In 25f8121, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1403 ms

Resolved: Bofrost.fr performance has improved in a33cf40.


Ignore .DS_Store file

The .DS_Store file make some user's finder hang/crash. And it's also un-readable. So I just ignore the file with this name to prevent the issue: https://github.com/whomwah/qlstephen/issues/34

@tomfado Hi Tom. After forking this project I contacted @whomwah about changing the source of the homebrew-cask to my repo so that development could continue. He had the much better idea of adding me to this project. He listed you as the new maintainer so I want to talk to you before I start making changes.
If you look at my repo you can see I've merged the pull requests open on this repo into mine. It does fix some of the open issues (the .DS_Store hang being the biggest one).
I'd like to do the following:

Merge all open pull requests.
Close the issues that are fixed by them.
Ask @comawill for the travis integration. (Would you mind opening a pull request @comawill?)
Draft a 1.4.3 release
Release 1.4.3

Thoughts? Are you ok with me doing these things? Thank you.

Hi Trevor
Thank you for your effort. I have not been able to put any time into
this project, despite my initial intentions. How about you ask Duncan to
become the new maintainer? Are you interested? I am more than happy to
back down. I like the project very much though and would like it to be
well and prosper.
And even if you don't want to become a maintainer, you're more than
welcome to do what you suggested.
Best regards
Tomas Fasth
Den 2016-02-02 kl. 19:00, skrev Trevor Dorsey:

@tomfado https://github.com/tomfado Hi Tom. After forking this project
I contacted @whomwah https://github.com/whomwah about changing the
source of the homebrew-cask to my repo so that development could
continue. He had the much better idea of adding me to this project. He
listed you as the new maintainer so I want to talk to you before I start
making changes.
If you look at my repo you can see I've merged the pull requests open on
this repo into mine. It does fix some of the open issues (the .DS_Store
hang being the biggest one).
I'd like to do the following:

Merge all open pull requests.
Close the issues that are fixed by them.
Ask @comawill https://github.com/comawill for the travis
integration. (Would you mind opening a pull request @comawill
https://github.com/comawill?)
Draft a 1.4.3 release
Release 1.4.3

Thoughts? Are you ok with me doing these things? Thank you.
—
Reply to this email directly or view it on GitHub
https://github.com/whomwah/qlstephen/pull/39#issuecomment-178723052.

--
Tomas Fasth<EMAIL_ADDRESS>Debian Developer
GPG fingerprint: B9BC EDE2 9580 516A EA8C 34E7 33C1 FE3D 81D7 2FF8

Finally👏👏👏👏👏👏


Facebook Like doesn't Likes

Hi Julien, this is an amazing plugin, congratulations!
I've stumbled upon a small issue: the facebook likes are not taken into account, despite the fact that the open graph shows them
http://graph.facebook.com/?id=http://themesrobot.com
do you know what could be causing the issue?
Cheers!

Likes are now retained after adding the fb:app_id meta tag but the count is not updated.

Changing the url to +1/like/tweet from http://themesrobot.com/ to http://themesrobot.com without the trailing slash did the trick. Weird though.

Yes it's weird, i have tested a lot of URL and it's the first time i have a difference with a slash.


[ Updated Hero.jsx ] - Added an animated Number Counter for metrics on the landing page.

Issue #49 📐

I Ayushi Choudhary have worked for https://github.com/warmachine028/nike/issues/48

Guidelines 🔐
I accept the fact that I have followed the guidelines and have not copied the codes from around the internet

[x] Contribution Guidelines
[x] Code of Conduct

Issue to be closed 🛅

My pull request closes #49

Fastastic work @ayushichoudhary-19! I'll be merging it right away.

Make sure to star this repo 🌟 if you liked contributing to it.
You can also follow me for more such amazing projects and opportunities.


Update go-edge-ds and azm

Includes fixes for:

Tracing in reader.Check calls
Panic in GetGraph with certain negation and intersection permissions

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 26.361%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1230

Relevant Lines:
4666

💛  - Coveralls


Samba

Branch started here : https://github.com/kestra-io/plugin-fs/blob/feat/samba/docker-compose-ci.yml

https://github.com/kestra-io/plugin-fs/tree/feat/samba

https://github.com/kestra-io/plugin-fs/tree/feat/samba


Move fetch to extra and clean up some code

Moves fetch to extra (see #661) and cleans up some code.

i'm conflicted about fetch being in extra. here's why.
reasons for moving it to extra

we may want it in extra there because i think ssl is required and some platforms may have a problem with that.

reasons for not moving it to extra

if we get to the place we want to be, which is recognizing when plugins are needed and automagically downloading them, we'll need fetch as a regular internal command.

I definitely agree with the second part, when we need to download things automatically. So how about making it always available? Now we're not usyng async + tokio anymore, so the only crate needed is reqwest...

@fdncred are you thinking of making fetch part of the default features?

Ahh yeah, +1 on making it part of the default commands.

ya, i think default is where we want to be with fetch to allow us to auto-download things in the future.

I made it to be a default command :-)

thanks!


Saveload convenience (proc-)macros

This adds two major features:

A custom derive for IntoSerialize and FromDeserialize named #[derive(Saveload)]. It may seem odd to derive them together, but after spending significant time trying to do it the normal way (one derive per trait) it became clear that due to the requirement of "proxy" types that fill the IntoSerialize::Data and FromDeserialize::Data fields, it made sense to do it this way or you start getting into attribute hell.
A macro which automatically will create SystemData for the most common usecase of SerializeComponents and DeserializeComponents. Unlike the existing tuple auto-implementation, this generates arbitrarily large structs that you can readily plop straight into your serialization or deserialization system. It also doesn't use recursion, so it shouldn't hit any nasty macro expansion recursion limits.

I recommend reading the module comment for the Saveload derive, the doc comment for saveload_components!, and the new documentation all around for a greater overview of what this all looks like in the end. This makes using the saveload features much more pleasant and less stuttery. In the case of saveload_components! especially it lets people easily keep their Serialization and Deserialization component lists in sync which can be hugely important and has been a source of a lot of frustrating bugs for me in the past.
The current derive does have a major downside in that I couldn't figure out how to get it to work with generic structs, but due to the way specs works I don't find myself holding a Foo<T> too often anyway.

This change is

Hmm, the visibility modifiers are being a pain. If they're pub they want all components to be pub, but if they're pub(crate) or pub(super) they complain endlessly about leaking private types.

Crap, I forgot code like
impl IntoSerialize for C where C: Serialize+Clone vs impl IntoSerialize for Vec<T> where T: IntoSerialize would require specialization to resolve (and even though IDK if specialization would solve this).
Not sure how to solve this from a design standpoint, seems like there are only really two options:

Hand-implement IntoSerialize and FromDeserialize for every native type to avoid a blanket impl, and expect others to #[derive(Saveload)] for their own types.
Extend the derive to have special casing for things like Vec<T> and generate specialized code

I feel like 1 is more painful but probably ultimately more flexible, it seems closer to how serde works, but is also a massive undertaking (not in difficulty so much in time and scale).

Phew, sounds complicated. I would love to add these macros, but I don't know what to do about this without using more time on this PR. I think I'll need about two weeks before I can take a closer look, @Xaeroxe @WaDelma feel free to decide on your own or wait, whatever you prefer.

@LinearZoetrope Are you still interested in this PR?
Also pinging @WaDelma @Xaeroxe @jojolepro @Moxinilian @omni-viral in case any of you need this feature and would like to provide a solution.

Yes I am. Sorry, I had to switch tracks for work but I can poke at this some more soon, especially if anyone else has any ideas about how to handle some of the issues.

While I do need this feature, I don't think I will be of much help. I'm not advanced enough in macro and generics yet to fully understand how to fix the implementation.

I can look and see if I can improve it.

I think it would be good idea to split the custom derive and the macro to separate prs.
I feel like there are too many moving parts as is.

Closing in favor to #460 and #461


Convert 0.7-1 to ["0.7", "1"], et cetera

Resurrection of #5051
Script:
import Pkg

for (root, dirs, files) in walkdir(".")
    old_to_new = Dict{String, Vector{String}}()

    old_to_new["0.7-1"] = ["0.7", "1"]
    old_to_new["0.7-1.0"] = ["0.7", "1.0"]
    old_to_new["0.7-1.0.0"] = ["0.7", "1.0.0"]
    old_to_new["0.7.0-1"] = ["0.7.0", "1"]
    old_to_new["0.7.0-1.0"] = ["0.7.0", "1.0"]
    old_to_new["0.7.0-1.0.0"] = ["0.7.0", "1.0.0"]

    old_to_new["0.7-1.1"] = ["0.7", "1.1"]
    old_to_new["0.7-1.1.0"] = ["0.7", "1.1.0"]
    old_to_new["0.7.0-1.1"] = ["0.7.0", "1.1"]
    old_to_new["0.7.0-1.1.0"] = ["0.7.0", "1.1.0"]

    old_to_new["0.7-1.2"] = ["0.7", "1.2"]
    old_to_new["0.7-1.2.0"] = ["0.7", "1.2.0"]
    old_to_new["0.7.0-1.2"] = ["0.7.0", "1.2"]
    old_to_new["0.7.0-1.2.0"] = ["0.7.0", "1.2.0"]

    for file in files
        filename = joinpath(root, file)
        if endswith(filename, "Compat.toml")
            i_modified_this_compat_file = false
            compat = Pkg.TOML.parsefile(filename)
            for pair in compat
                compat_entries = pair[2]
                for entry in compat_entries
                    name = entry[1]
                    value = entry[2]
                    if lowercase(strip(name)) == "julia"
                        value_nowhitespace = replace(value, r"\s"=>"")
                        if haskey(old_to_new, value_nowhitespace)
                            compat[pair[1]][name] = old_to_new[value_nowhitespace]
                            i_modified_this_compat_file = true
                        end
                    end
                end
            end
            if i_modified_this_compat_file
                rm(filename; force = true, recursive = true)
                open(filename, "w") do io
                    Pkg.TOML.print(io, compat; sorted = true, by = key -> (Pkg.Types.project_key_order(key), key))
                end
            end
        end
    end
end

This PR will immediately become obsolete as soon as anything is merged to General, so I have to merge it sooner rather than later.
If this PR causes any issues whatsoever, feel free to immediately revert it.


fix: Clear defaultArgs on withEntrypoint by default

Fixes https://github.com/dagger/dagger/issues/6044
What?
When Container.withEntrypoint is set, it will clear Container.defaultArgs, unless withEntrypoint(args: [...], keepDefaultArgs: true) is set.
Breaking change
May have low impact since in most cases users are probably erasing defaultArgs manually. Only breaks for users that change the entrypoint but depend on the default args remaining the same.

In draft due to following next actions, but ready for review in the meantime[^1]:

[ ] Merge https://github.com/dagger/dagger/issues/6044
[ ] Decide when to release[^2]
[ ] Break doc snippet changes into a separate PR[^3]

[^1]: There's a single commit that needs reviewing, choose it from the filter.
[^2]: Possibly after holidays, however this should have a low impact so I'm ok publishing it on next release.
[^3]: It's so we don't publish that before it's released. Added the changes here to help review what will need to change.

Reframing as a fix, since I agree with @jedevc:

I think I read it more of a "fix", which brings the behaviour of dagger's entrypoint+args inline with how users expect it to work with docker/other runtimes.

- Originally posted in Discord

LGTM! Not a blocker: but should this behavior also apply to withoutEntrypoint from https://github.com/dagger/dagger/pull/6278? Since the entrypoint is changing, the args wouldn't necessarily apply. I'd argue we should also have the same behavior there for consistency.

LGTM! Not a blocker: but should this behavior also apply to withoutEntrypoint from #6278? Since the entrypoint is changing, the args wouldn't necessarily apply. I'd argue we should also have the same behavior there for consistency.

Yeah, that's a good point!


Would this support Docker Swarm?

Will this work in a Docker Swarm setup?
My goal is to have dynamically defined A records pointing at Traefik reverse proxy instances.

I'm sorry I'm not familiar with how docker swarm does DNS and service
discovery. Maybe someone with more docker swarm experience can chime in.
On Mon., Feb. 24, 2020, 3:59 p.m. Leopere<EMAIL_ADDRESS>wrote:

Will this work in a Docker Swarm setup?
My goal is to have dynamically defined A records pointing at Traefik
reverse proxy instances.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kevinjqiu/coredns-dockerdiscovery/issues/14?email_source=notifications&email_token=AAAUSYLUYMRVZVI4WOJTZ3DREQYMBA5CNFSM4K2SDRA2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IP3WKMA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUSYKBJQSRYFYK4PT2Z3TREQYMBANCNFSM4K2SDRAQ
.

I believe it’s mostly the same I know Traefik should have an example.
On Sun, Mar 1, 2020 at 11:50 AM Kevin J. Qiu<EMAIL_ADDRESS>wrote:

I'm sorry I'm not familiar with how docker swarm does DNS and service
discovery. Maybe someone with more docker swarm experience can chime in.
On Mon., Feb. 24, 2020, 3:59 p.m. Leopere<EMAIL_ADDRESS>wrote:

Will this work in a Docker Swarm setup?
My goal is to have dynamically defined A records pointing at Traefik
reverse proxy instances.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<
https://github.com/kevinjqiu/coredns-dockerdiscovery/issues/14?email_source=notifications&email_token=AAAUSYLUYMRVZVI4WOJTZ3DREQYMBA5CNFSM4K2SDRA2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IP3WKMA
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAAUSYKBJQSRYFYK4PT2Z3TREQYMBANCNFSM4K2SDRAQ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kevinjqiu/coredns-dockerdiscovery/issues/14?email_source=notifications&email_token=AAIE2VQPJDRSC2GQI6UUU6LRFKG5BA5CNFSM4K2SDRA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENNEHUA#issuecomment-593118160,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIE2VWUEYUJ42OM6XZ7SXDRFKG5BANCNFSM4K2SDRAQ
.


bug: ursa cli hangs requesting content not stored on the node

With content put through rpc to node A, and get through rpc cli through a node B which doesn't have the content and bitswap performs a query, the cli never resolves and hangs indefinitely.
Running this command from node B:
./ursa-bin rpc get bafybeifyjj2bjhtxmp235vlfeeiy7sz6rzyx3lervfk3ap2nyn4rggqgei asdf

node B logs (with a debug placed on all bitswap events):
2022-12-08T04:43:26.316279Z  INFO ursa_rpc_server::api: getting and storing the file at: asdf
BitswapEvent: Progress(QueryId(0), 1)
BitswapEvent: Complete(QueryId(0), Ok(()))

and the rpc command hangs indefinitely from there
Cancelling and doing a second get request resolves extremely quickly and works as expected, so the node is getting the content but just not responding to rpc on that first request

Resolved with latest libp2p 0.50 upgrades


Swift Package Manager Support Request

Flurry need to provide a Swift Package Manager Support , Right now am not sure it is supporting .

The SPM package doesn't seem to work for iOS simulators running on M1 Macs. Is this a known issue? I get this error:
ld: warning: ignoring file /Users/zulfishah/Library/Developer/Xcode/DerivedData/SimpleList-bkylkdabwgxlstdympoknglfewum/Build/Products/Debug-iphonesimulator/libFlurry.a, missing required architecture arm64 in file /Users/zulfishah/Library/Developer/Xcode/DerivedData/SimpleList-bkylkdabwgxlstdympoknglfewum/Build/Products/Debug-iphonesimulator/libFlurry.a (2 slices)
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_Flurry", referenced from:
      objc-class-ref in SLAppDelegate.o
      objc-class-ref in UpcomingEventsViewController.o
      ...
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

It works fine when building and running to a device. Though I do want to be able to use the iOS simulator, so what's the best way to work around it?

@zulfishah Please reset the package cache and try again using Flurry 11.3.0.
A fix was previously released for this issue but the tag was not updated to point to the new commit. This has been corrected.

Also looking forward to this feature release.

I am also having an issue of trying to build my app with Flurry for the simulator on a M1 MBP. When I reset the cache and try to load 11.3.0 it says "Package Resolution Failed." There is no TAG for 11.3.0  FWIW, I can successfully load 11.2.0 but that (of coarse) doesn't fix the issue. And as you probably already know the library is missing a compiled version for the simulator.
$ lipo -archs libFlurry.a
i386 x86_64

Hello @rspears,
Are you looking at the correct repo? See the releases and tags listed here: https://github.com/flurry/FlurrySwiftPackage/releases
ios-arm64_i386_x86_64-simulator % lipo -archs libFlurry.a
i386 x86_64 arm64
`

My confusion was that the documentation shows:
"https://github.com/flurrydev/FlurrySwiftPackage/"
instead of:
"https://github.com/flurry/FlurrySwiftPackage"

@rspears I am sorry for that typo and the inconvenience it caused. I have updated the documentation on the master branch.

I'm trying to resolve the package https://github.com/flurry/FlurrySwiftPackage but it seems that it's trying to resolve a non public url:
https://github.com/flurrydev/FlurrySwiftPackage/
Do you know why is this happening?
In a different computer this is NOT happening
UPDATE:
Xcode 13.2
(Btw, removing Flurry from "recently used packages", restarting Xcode, and re-adding the dependency worked :/ )

Flurry has added official support for Swift Package Manager(SPM). Please visit https://github.com/flurry/FlurrySwiftPackage and https://developer.yahoo.com/flurry/docs/integrateflurry/ios/


[SPARK-37384][CORE][TESTS] Increase timeout for job termination in SchedulerIntegrationSuite

What changes were proposed in this pull request?
This PR proposes to increase timeout for job termination in SchedulerIntegrationSuite to deflake the tests.
Why are the changes needed?
Currently HealthTrackerIntegrationSuite.If preferred node is bad, without excludeOnFailure job will fail is flaky:
sbt.ForkMain$ForkError: java.util.concurrent.TimeoutException: Futures timed out after [10 seconds]
	at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:259)
	at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:187)
	at org.apache.spark.util.ThreadUtils$.awaitReady(ThreadUtils.scala:334)
	at org.apache.spark.scheduler.SchedulerIntegrationSuite.awaitJobTermination(SchedulerIntegrationSuite.scala:274)
	at org.apache.spark.scheduler.HealthTrackerIntegrationSuite.$anonfun$new$3(HealthTrackerIntegrationSuite.scala:50)
	at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
	at org.apache.spark.scheduler.SchedulerIntegrationSuite.withBackend(SchedulerIntegrationSuite.scala:261)
	at org.apache.spark.scheduler.HealthTrackerIntegrationSuite.$anonfun$new$1(HealthTrackerIntegrationSuite.scala:48)
	at org.apache.spark.scheduler.SchedulerIntegrationSuite.$anonfun$testScheduler$1(SchedulerIntegrationSuite.scala:98)
	at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
	at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
	at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
	at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
	at org.scalatest.Transformer.apply(Transformer.scala:22)
	at org.scalatest.Transformer.apply(Transformer.scala:20)
	at org.scalatest.funsuite.AnyFunSuiteLike$$anon$1.apply(AnyFunSuiteLike.scala:226)
	at org.apache.spark.SparkFunSuite.withFixture(SparkFunSuite.scala:190)
	at org.scalatest.funsuite.AnyFunSuiteLike.invokeWithFixture$1(AnyFunSuiteLike.scala:224)
	at org.scalatest.funsuite.AnyFunSuiteLike.$anonfun$runTest$1(AnyFunSuiteLike.scala:236)

e.g.) https://github.com/apache/spark/runs/4259932001
This PR fixes it.
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
Should monitor GitHub Actions builds after it got merged.

cc @Ngone51, mind taking a quick look please?

Test build #145433 has started for PR 34661 at commit c9a615a.

Thanks @dongjoon-hyun !

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49906/

Thanks @Ngone51 !!

Tests passed (https://github.com/HyukjinKwon/spark/runs/4260376896?check_suite_focus=true).
Merged to master.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49906/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49906/

Test build #145433 has finished for PR 34661 at commit c9a615a.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145433/


Add rebase action

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 8 committers have signed the CLA.:white_check_mark: wlkrm:white_check_mark: GoetzGoerisch:x: iansu:x: mubarakn:x: jafin:x: psiservices-justin-sullard:x: wisammechano:x: fishmandevYou have signed the CLA already but the status is still pending? Let us recheck it.

Closed via c5126ba699bd2ceb475c9d23b7837489e4554ca3


Support multiple senders

It would be useful to support scenarios like registering a SMTP sender and a Logging sender in production.

Flags in startup.cs using DI should accomodate this?

@bjcull Can you give an example Please


dataset format

Hi, what a great work! I truly like the structure you put forward. However, when I follow the instructions given in the README to add my own datasets such as citeseer, I encountered with the following problems:

As you can see, the data structure in the folder Cora and the Citeseer are not the same, leading to the problem of missing important attributes needed for the training session.(Plus: the Citeseer dataset is loaded using the pyg)
So I'm wondering if it is because of the dataloader(I guess the dataloader I used might be different from the one you used) or if it is a must that we implement the categories.csv and add the attributes all by ourselves?
I would appreciate it if you could reply!

Hi @AMark-CS ,
Sorry for the late reply. We got the cora.pth from here and not from pyg. Pyg's version does not contain raw text about abstracts and titles. They have script to collect cora raw text. I don't think they have citeseer provided, and I think if you want to add citeseer, you will need to collect raw text for citeseer yourself.
Hope this helps.

Thank you for sparing your precious time to reply!
Your suggestion perfectly solved my problem and I think improved my coding skills as well^_^, many thanks for that!
In addition, when I was wandering around github I found something that might tackle the citeseer issue and help those who has the same prob as me: GLBench

It implemented the citeseer dataset in ofa, which I think is also a great work.


Requirement for kernel.core_pattern sysctl is unusual

In Fuzzer.swift on linux, there's a requirement that /proc/sys/kernel/core_pattern starts with |/bin/false, which disables all core dumps on the target system.
https://github.com/googleprojectzero/fuzzilli/blob/172778a3397774a337edee803fb372a48b99f5bd/Sources/Fuzzilli/Fuzzer.swift#L702-L714
This is a bit awkward to force on anything other than a short-lived VM of some sort. Even when running in docker, or podman or another container runtime, this kernel config value is set for the host and all containers equally, and so requires a privileged container to even set. It also overwrites the value for the host, which is awkward if it is a desktop distro like Ubuntu that expects to route crash dumps through a tool like apport.
Would it make more sense  to patch the JS runtimes to set something like prtcl(PR_SET_DUMPABLE, 0) when running through fuzzili if this is the desired effect?
 PR_SET_DUMPABLE (since Linux 2.3.20)
              Set the state of the "dumpable" attribute, which
              determines whether core dumps are produced for the calling
              process upon delivery of a signal whose default behavior
              is to produce a core dump.

Yeah, I agree, we should do it in a different way.
I would propose https://man7.org/linux/man-pages/man2/setrlimit.2.html.
Specifically we should set RLIMIT_CORE to 0 in Fuzzilli and then let the child process inherit this limit.
RLIMIT_CORE
              This is the maximum size of a core file (see [core(5)](https://man7.org/linux/man-pages/man5/core.5.html)) in
              bytes that the process may dump.  When 0 no core dump
              files are created.  When nonzero, larger dumps are
              truncated to this size.

The benefit of using this is that we can then also use prlimit() to query the fuzzed JS engine's RLIMIT_CORE value to check whether the process is actually not dumping, and notify the user before we create tons of core dumps during fuzzing.
This way we don't actually need to change any of the patches.

Fixed now with d386a83812496b7e590ce93c8fdc50208dacbd26.


Empty structure for sdmxthon.model.definitions.DataFlowDefinition

Running the following code returns a NoneType. Is this expected?
import sdmxthon

url = "https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/MET_EDAT_LFSE4/1.0?detail=full"

message = sdmxthon.read_sdmx(url)
resource = message.payload[list(message.payload)[0]]
df = resource[list(resource)[0]]

df.structure

I would expect it returns <s:Structure>, for example:
<Ref id="MET_EDAT_LFSE4" version="18.0" agencyID="ESTAT" package="datastructure" class="DataStructure"/>
Is this correct or is there another way to handle it?
Thank you very much in advance.

Hi!
Actually, the issue is that, in your query, you are not getting the descendants, so, if you check the sdmx file you get, there is no DSD. The read_sdmx method reads what it gets, it does not look for the descendants itself.
I normally use the references parameter in the query with all or descendats value. Eurostat's  API does not implement the all option. If you run the following script:
`    url = "https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/dataflow/ESTAT/MET_EDAT_LFSE4/1.0?detail=full&references=descendants"
message = read_sdmx(url)
dataflow = list(message.payload['Dataflows'].values())[0]
print(dataflow.structure)`

You'll get the structure

Dear @antonio-olleros , thank you very much. Indeed, you are absolutely correct - it works.
Thank you again for this library.


bundle.md: various updates to latest spec

Move to single root filesystem, as the configuration specification now
only supports a single process
Clarify that signatures are just another kind of content directory
Cross-reference configuration specification for config.json

I think my understanding w.r.t. the rootfs stuff is correct, but I could be totally off-base on this; if so it's not at all clear to me what the purpose of multiple rootfs directories is.

@jonboulle Some background here: I think the original idea behind multiple root filesystems was to be able to support POD-like functionality. I am not sure where the conversation on PODs has headed, so it's possible we're going in a different direction.

LGTM

LGTM

Thanks for the merge! I'm still curious on thoughts on https://github.com/opencontainers/specs/pull/55#discussion_r33834913 - would it be simpler to just mandate a well-known location for the rootfs given there can be only one?

I think that keeping it configurable would help later if we support multiple of them down the line.

@jonboulle I agree with @mrunalp. However, we should have a list of strongly encouraged conventions:
rootfs
signatures


HADOOP-19128. Unified use of placeholder for log calling.

Description of PR

Unified use of placeholder for log calling
https://issues.apache.org/jira/browse/HADOOP-19128

How was this patch tested?
N.A
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?

[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
N.A

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
N.A

[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?
N.A

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 22s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 9 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
13m 18s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m 34s

trunk passed

+1 :green_heart:
compile
10m  1s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
8m 51s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
2m 15s

trunk passed

+1 :green_heart:
mvnsite
8m 34s

trunk passed

+1 :green_heart:
javadoc
7m 25s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
7m 39s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

-1 :x:
spotbugs
1m 22s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-client-warnings.html
hadoop-hdfs-project/hadoop-hdfs-client in trunk has 1 extant spotbugs warnings.

+0 :ok:
spotbugs
0m 23s

branch/hadoop-hdfs-project/hadoop-hdfs-native-client no spotbugs output file (spotbugsXml.xml)

+0 :ok:
spotbugs
0m 20s

branch/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
21m 24s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 23s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 17s

the patch passed

+1 :green_heart:
compile
9m 42s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
9m 42s

the patch passed

+1 :green_heart:
compile
9m  8s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
9m  8s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
2m 28s
/results-checkstyle-root.txt
root: The patch generated 60 new + 1213 unchanged - 11 fixed = 1273 total (was 1224)

+1 :green_heart:
mvnsite
8m 36s

the patch passed

+1 :green_heart:
javadoc
7m 15s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
7m 34s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+0 :ok:
spotbugs
0m 21s

hadoop-hdfs-project/hadoop-hdfs-native-client has no data from spotbugs

+0 :ok:
spotbugs
0m 20s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site has no data from spotbugs

+1 :green_heart:
shadedclient
24m 36s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
15m 52s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m  0s

hadoop-kms in the patch passed.

+1 :green_heart:
unit
1m 56s

hadoop-hdfs-client in the patch passed.

-1 :x:
unit
234m 33s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
unit
6m 19s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
unit
2m 35s

hadoop-hdfs-nfs in the patch passed.

+1 :green_heart:
unit
3m 37s

hadoop-yarn-server-applicationhistoryservice in the patch passed.

+1 :green_heart:
unit
88m 34s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
unit
21m 44s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
unit
114m 10s

hadoop-mapreduce-client-jobclient in the patch passed.

+1 :green_heart:
unit
15m 17s

hadoop-distcp in the patch passed.

+1 :green_heart:
unit
0m 46s

hadoop-yarn-server-sharedcachemanager in the patch passed.

+1 :green_heart:
unit
21m 30s

hadoop-yarn-applications-distributedshell in the patch passed.

+1 :green_heart:
unit
0m 56s

hadoop-yarn-applications-unmanaged-am-launcher in the patch passed.

+1 :green_heart:
unit
0m 28s

hadoop-yarn-site in the patch passed.

+1 :green_heart:
unit
0m 49s

hadoop-mapreduce-examples in the patch passed.

+1 :green_heart:
unit
6m 11s

hadoop-streaming in the patch passed.

+1 :green_heart:
asflicense
0m 58s

The patch does not generate ASF License warnings.

750m  9s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestReadStripedFileWithDecoding

hadoop.hdfs.server.namenode.ha.TestBootstrapStandby

hadoop.hdfs.tools.TestDFSAdmin

hadoop.hdfs.server.datanode.TestDataNodeReconfiguration

hadoop.hdfs.TestDFSInputStreamBlockLocations

hadoop.hdfs.server.namenode.TestReconstructStripedBlocks

hadoop.hdfs.server.namenode.ha.TestStandbyIsHot

hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA

hadoop.hdfs.TestDFSStripedInputStreamWithRandomECPolicy

hadoop.hdfs.TestBlocksScheduledCounter

hadoop.hdfs.server.namenode.TestNameNodeMXBean

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6680/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6680

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
Linux 001401fdc2fb 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 68e98b00ea98c640a3a7ffcf07d10300e1812ad0

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6680/1/testReport/

Max. process+thread count
4007 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs-native-client hadoop-hdfs-project/hadoop-hdfs-nfs hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient hadoop-tools/hadoop-distcp hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-sharedcachemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site hadoop-mapreduce-project/hadoop-mapreduce-examples hadoop-tools/hadoop-streaming U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6680/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 12s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+0 :ok:
markdownlint
0m 01s

markdownlint was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 00s

The patch appears to include 9 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
2m 24s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
89m 44s

trunk passed

+1 :green_heart:
compile
40m 14s

trunk passed

+1 :green_heart:
checkstyle
6m 09s

trunk passed

-1 :x:
mvnsite
4m 29s
/branch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in trunk failed.

+1 :green_heart:
javadoc
74m 41s

trunk passed

+1 :green_heart:
shadedclient
325m 01s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 17s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
73m 34s

the patch passed

+1 :green_heart:
compile
40m 26s

the patch passed

+1 :green_heart:
javac
40m 26s

the patch passed

+1 :green_heart:
blanks
0m 00s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
7m 08s

the patch passed

-1 :x:
mvnsite
4m 31s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
javadoc
73m 24s

the patch passed

+1 :green_heart:
shadedclient
336m 00s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
5m 47s

The patch does not generate ASF License warnings.

924m 09s

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/6680

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
MINGW64_NT-10.0-17763 100c2ae9c020 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 68e98b00ea98c640a3a7ffcf07d10300e1812ad0

Default Java
Azul Systems, Inc.-1.8.0_332-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6680/1/testReport/

modules
C: hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs-native-client hadoop-hdfs-project/hadoop-hdfs-nfs hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient hadoop-tools/hadoop-distcp hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-sharedcachemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-unmanaged-am-launcher hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site hadoop-mapreduce-project/hadoop-mapreduce-examples hadoop-tools/hadoop-streaming U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6680/1/console

versions
git=2.44.0.windows.1

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Suppress warnings

Suppress library warnings by using -isystem so that it won't affect native regexbench.


Refactor DynamoDB update expressions

Hi, I've done some refactoring to the if/else/for hell in the DynamoDB update-method. (Think I'm allowed to call it that.. considering I've contributed to it as well :) )
Major changes:

Internal representation is now nested DynamoTypes.
Before, only the toplevel was a DynamoType:

DynamoType('M', {'foo': 'bar', 'foo2': ['bar2']

and is now
DynamoType('M', {'foo': DynamoType('S': 'bar'), 'foo2': DynamoType('L', [DynamoType('S', 'bar2')])})

Updating nested items is now the responsibility of the (DynamoType) item itself, rather than inside the update-method
Thanks to the new DynamoType structure, updates uses recursion rather than a for-loop.

IMHO, this is a lot more readable/understandable now.
LMKWYT - open to suggestions

Coverage increased (+0.02%) to 93.55% when pulling 04b778fea94fb2c2cf61afe6fe8689987f7a8ad4 on bblommers:refactor-dynamodb-update into b433399cb582cb5084c88e8d70ba08e9395c1d07 on spulec:master.

I've left one suggested edit to documentation if you'd like to make a follow-up PR. But it's no reason to block the merge here.


How to include other arduino libraries in a LUFA sketch?

I'm trying to read an sdcard file within my lufa sketch but including the arduino <SD> library will give compile errors when the LUFA board is selected. What should I do to use it as I would normally do? .

Could you please post the exact compiler errors you're seeing? Normally other libraries work just fine with LUFA.

I don't have the exact errors now but it's about all kinds of undefined types if included in a .c file and about undefined Serial when included in the .ino, manually removing serial usage from the library fixed it.


how do i do the query?

i tried https://twitter.com/search?f=tweets&q=from%3AItMeIRlNEW
and https://api.twitter.com/1.1/users/search.json?f=tweets&q=from%3AItMeIRlNEW
it doesn't work

also is it soposed to say
null
Next run: 2018-08-10T10:50:25-05:00
null
Next run: 2018-08-10T10:50:27-05:00
null
Next run: 2018-08-10T10:50:29-05:00
null
Next run: 2018-08-10T10:50:31-05:00
null

I'm having the same problems. Curious what is wrong too


onBackgroundEvent no longer works in App.js

Hi all,
Previously, when using Notifee v. 7.7.1, I was able to put and respond to the onBackgroundEvent method in App.js. This was handy because I could use navigation in response to background notifications on Android. Since installing Notifee v. 7.8.2, I can no longer do this as I receive an Invalid hook call even though the method is within the functional component of App.js.
onBackgroundEvent does work if it's in index.js, but the Notifee site is lacking on examples of how to manage interaction between the event there and other components. Can support for App.js be re-introduced or can the site provide some examples of how to manage this when onBackgroundEvent is in index? I'm seeing a lot of questions regarding this on Discord, etc.

Looks like this issue was caused by me accidentally having a RN Navigation hook inside of the onBackgroundEffect method. Without it there, the method does work in App.js. I do think that having some more examples of how to use onBackgroundEffect in index.js (where the documentation says to put it) would be helpful just in case one finds it necessary to have it there. I'll open another issue with that.


Bind for <IP_ADDRESS>:6711 failed: port is already allocated

When trying to run:
docker-compose -f hh.yml up

I get the following error:
Error response from daemon: driver failed programming external connectivity on endpoint chainlink-node-1 (f0eb0fe8a8bf4c248c14c10bd23dcef33d928c341d3cbcb6dfdfe86e302a4686): Bind for <IP_ADDRESS>:6711 failed: port is already allocated

It seems like the ports inside of service.yml under node are conflicting.


Adding docker files to tag each runnable module

@stevehu @ddobrin Hey, could you guys please review the method of creating these images and let me know if it's an ok substitute?

Let's have a discussion. I see your point that we should build in a docker container so that we can eliminate local environment influence. If that is the case, we might need to create our own docker instead of using jimschubert/8-jdk-alpine-mvn which haven't been updated for the last two years. Our dockerfiles are reviewed by our customers and there are a lot of restrictions applied.


A simple question about directoryAsNamespace

[unplugin-vue-components] component "Table"(...) has naming conflicts with other components, ignored.
[unplugin-vue-components] component "Search"(...) has naming conflicts with other components, ignored.
[unplugin-vue-components] component "Table"(...) has naming conflicts with other components, ignored.
[unplugin-vue-components] component "Search"(...) has naming conflicts with other components, ignored.
[unplugin-vue-components] component "Table"(...) has naming conflicts with other components, ignored.

in my opinion, it is common while coding vue project with repeated file name components between different directory, so why not set directoryAsNamespace default true? or may it's not common i wrong?
is there any side effect by setting it true?

Just an option, why not default to false then? You have to pick one.


route53 public hosted zone is not supported

creating a hosted zone with a hosted zone configuration for PrivateZone=False always create a private hosted zone (PrivateZone=True) when looking into the private zone flag of retrieved hosted zone created for a given test VPC.
Request:
self.route53.create_hosted_zone(Name="Zone1", VPC={"VPCRegion": "us-east-1", "VPCId": "vpc-1234567"},                                         CallerReference="TestReference",                                         HostedZoneConfig={"Comment": "TestComment",                                                           "PrivateZone": False})
Config information in when fetched above created Hosted Zone:
'Config': {             'Comment': 'TestComment',             'PrivateZone': True         }
When I try create hosted zone without providing VPC and HostedZoneConfig info, no hosted zone is created.

Hi @pinkjosh, do you have an example test case that showcases the problem?

Let me provide you the test class for this test:
`import unittest
from collections import Counter
import boto3
from moto import mock_ec2, mock_sts, mock_route53, mock_acm, mock_iam
from generator.aws_api import AWSApi
@mock_acm
@mock_sts
@mock_route53
@mock_ec2
@mock_iam
class MyTestCase(unittest.TestCase):
def setUp(self):
self.ec2_resource = boto3.resource("ec2", "us-east-1")
def test_hosted_zone(self):
    self.ec2_resource = boto3.resource("ec2", "us-east-1")
    vpc_resource = self.ec2_resource.create_vpc(CidrBlock='<IP_ADDRESS>/24')
    vpc_resource.create_tags(Tags=[{'Key': 'Name', 'Value': 'vpc-123456'}])
    self.route53.create_hosted_zone(Name='testzone.testdomain.com.',
                                    VPC={"VPCRegion": "us-east-1", "VPCId": vpc_resource.id},
                                    CallerReference="TestReference",
                                    HostedZoneConfig={"Comment": "TestComment","PrivateZone": False})
    hosted_zones = self.route53.list_hosted_zones_by_vpc(VPCId=vpc_resource.id, VPCRegion='us-east-1')
    self.assertEqual('testzone.testdomain.com.', hosted_zones['HostedZoneSummaries'][0]['Name'])
    hosted_zone_details=self.route53.get_hosted_zone(Id=hosted_zones['HostedZoneSummaries'][0]['HostedZoneId'])
    self.assertFalse(hosted_zone_details['HostedZone']['Config']['PrivateZone'])`

This is not something I can test against AWS atm, but it looks like the docs specifically say that when passing a VPC, the hosted zone has to be private.
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/route53.html#Route53.Client.create_hosted_zone
On the VPC-parameter: (Private hosted zones only)

Finally I had some time to verify this against AWS, and it looks like AWS behaves the same: if a VPC is provided, then the PrivateZone is marked as True. The actual value in the HostedZoneConfig is ignored.
I'll close this - let me know if I've missed anything though.


Jupyter notebook doesn't start and returns errors: KeyError: 'cookie_secret' and TypeError: Missing required parameter 'digestmod'.

Hi,
I've just cloned this repo on a new anaconda installation, Ubuntu 20.04. I followed the instructions and after the "make pip-tools" finished, I tried to run "jupyter notebook".  I'm getting the following error.
I've spent quite some time trying to troubleshoot this with no success. Can someone confirm if they're having the same issues or if it's just me?
(fsdl-text-recognizer-2022) gekaklam@eru:~/projects/fsdl-text-recognizer-2022$ jupyter notebook
Traceback (most recent call last):
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/traitlets/traitlets.py", line 537, in get
    value = obj._trait_values[self.name]
KeyError: 'cookie_secret'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/bin/jupyter-notebook", line 8, in <module>
    sys.exit(main())
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/jupyter_core/application.py", line 264, in launch_instance
    return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs)
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/traitlets/config/application.py", line 845, in launch_instance
    app.initialize(argv)
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/traitlets/config/application.py", line 88, in inner
    return method(app, *args, **kwargs)
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/notebook/notebookapp.py", line 1507, in initialize
    self.init_webapp()
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/notebook/notebookapp.py", line 1265, in init_webapp
    self.web_app = NotebookWebApplication(
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/notebook/notebookapp.py", line 152, in __init__
    settings = self.init_settings(
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/notebook/notebookapp.py", line 247, in init_settings
    cookie_secret=jupyter_app.cookie_secret,
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/traitlets/traitlets.py", line 577, in __get__
    return self.get(obj, cls)
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/traitlets/traitlets.py", line 540, in get
    default = obj.trait_defaults(self.name)
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/traitlets/traitlets.py", line 1580, in trait_defaults
    return self._get_trait_default_generator(names[0])(self)
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/traitlets/traitlets.py", line 977, in __call__
    return self.func(*args, **kwargs)
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/site-packages/notebook/notebookapp.py", line 709, in _default_cookie_secret
    h = hmac.HMAC(key)
  File "/home/gekaklam/anaconda3/envs/fsdl-text-recognizer-2022/lib/python3.8/hmac.py", line 51, in __init__
    raise TypeError("Missing required parameter 'digestmod'.")
TypeError: Missing required parameter 'digestmod'.

I'm pretty stuck on this too. Did you manage to fix this?

should be fixed now! required a version bump of the notebook library


feat: revise Helm chart structure

After consuming this template everybody gets charts in charts/openshift-quickstart, which is a little clunky.  I suggest charts/app or something similarly generic.
NOTE: This change could cause scripting problems and revisiting previous repos.

should be done now

Thanks and closing!  @mishraomp


fix firefox Connection

firefox send "Connection: keep-alive, Upgrade\r\n" and does not match previous array filter

Shouldn't be it handled inside headers parsing layer? According to HTTP protocol spec Connection: keep-alive + \r\n + Connection: Upgrade equals to  Connection: keep-alive, Upgrade. While array of values passed  it is more expected that array values are standalone header values.

Facing same issue.

superseded by #16


[CELEBORN-1504][FOLLOWUP] Start test nodes in random ports to allow multiple builds run in the same ci server

What changes were proposed in this pull request?
Start test nodes in random ports to allow multiple builds run in the same ci server, which improves the test implementations so that it starts test nodes in random ports instead of using the hardcoded ones.
Follow up #2619.
Why are the changes needed?
The test nodes are started in the hard coded ports, this prevents to run multiple builds in the same CI/CD server at present.
Bump the changes of #2237.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
RemoteShuffleMasterSuiteJ

@turboFei, #2901 should also change the flink-1.16 module.
Ping @mridulm, @reswqa.


Fix changing url bug(#52)

#52 Because Router shouldn't change url.
What I did

I think router dosen't need to decodeURI, So I remove this function.
Change  location.pathname + location.search + location.hash  -> location.href.replace(location.origin, "")

How to test

Input url with query like /foo?, /foo?a%26b=c&d=e and see whether it’s changed

Tested: Safari, Chrome, Fire Fox on mac

Thanks.
But, this should directly needs to go to the page.js: https://github.com/visionmedia/page.js/issues
Would you mind sending a PR to them?
Then we'll take the updated page.js

Okay, So close this PR?

Yeah. And let's track the via #52


[FZ Editor] Add rename operation to context menu

@niels9001 , @enricogior
Though about a way to adding rename function to context menu. But because we ned a additional simple ui for just renaming, I think this should be a seperate pr/issue.
Two implementation ideas:

Simple dialogue with input, save button and abort button.
Change name label in gridview into input and show x button and checkmark button behind. (Like in wt on renaming color sheme.)

Originally posted by @htcfreek in https://github.com/microsoft/PowerToys/issues/11066#issuecomment-831849250

@htcfreek Now looking at the description.. Right-click => Rename => Enter name requires two clicks.. where as the current implementation (click on the edit button) would require 1. So the question would be: what does this solve?
If the Name textbox would live in the Editor screen like it did before, then it would make more sense to add.

@niels9001
beside what you just pointed out, we also should not add more features that are not essential to not increase the testing load.
I'm going to close this one.

@niels9001
Oh, you're right. I hadn't noticed that at all.


Implement user guidance

When the replay strategy determines that the current Screenshot/WindowState is sufficiently different from the expected state in the recording, we would like to prompt the user to take over and demonstrate how to complete the task in that situation:

compare the current state to the expected state in the current recording.
if not found, compare the current state to states in other recordings with the same description.
if not found, pause replay
notify the user that they need to demonstrate how to continue
start a new recording (with the same description as the one being recorded) as soon as the user starts generating InputEvents
wait for the user to finish the demonstration (e.g. 10s of inactivity)
restart replay from where we left off

Here are some questions and thoughts I had to address for some of these steps:

We can compare the screenshot captured during the replay to the screenshot captured during the recording(and subsequent screenshots) using computer vision tool such as OpenCV. The issue is how can we determine if its sufficiently different.

Image comparison techniques such as thresholding and matching [1][2][3]. Thresholding involves setting a threshold value to determine if two images are similar or different, while matching involves comparing the features of two images using a distance calculation.
Is this what you had in mind?

For the case when the user needs to demonstrate how to continue, we can use a desktop notification tool such as the WinToast library for Windows or the pynotify library for Linux.

For waiting for the user to finish the demonstration (e.g. 10s of inactivity), we can use a Python timer such as the time module.

Also need to store this in the database, along with replays


Crash with Bloodmoon and wolfarmor

When enabling Wolfs howling on full moon + bloodmoons happening every full moon at the first bloodmoon in the world i got a crash (first gist). The second gist is when i reattempt to open the world.
https://gist.github.com/vpontin/bc493c6d86d3984a1a1e3e691f25a3fd
Since i dont know what mod is responsible i will drop the same issue here an there.
https://github.com/lumien231/Bloodmoon/issues/28

hey, a getMoonPhase issue.  This is actually also my fault, and it's even the same problem! See #37

Strange, @lumien231 also claimed it was their fault, but anyway thanks for the reply! Very useful mod!


Automate cleaning up excessive App Engine versions

Add a build stage that executes a new script that cleans up all but the last 5 App Engine versions.

Also deleting all these versions will get rid the testing versions @another-rex has been working on. Is this alright / annoying?

I'll let @another-rex be the judge of that :-)

We also should be running the script on the production branch.

Yeah I figured we'd prove this in the staging project first and then figure out how to move it over to production.

Will this delete master / production appengine instances? Don't we currently do a app engine release every PR merge, so if we clean up the last 5 we will "cleanup" the current production instance.
Even moving this to deploy-prod.yaml might still cause problems, since we will want to have the previous production appengine instance to roll back to if we discover something wrong with the newly deployed frontend, and if there has been more than 5 commits / PR merged between releases, we will lose the old app engine instance.

Will this delete master / production appengine instances? Don't we currently do a app engine release every PR merge, so if we clean up the last 5 we will "cleanup" the current production instance.

It keeps all but the most recent 5, not the last 5.

Will this delete master / production appengine instances? Don't we currently do a app engine release every PR merge, so if we clean up the last 5 we will "cleanup" the current production instance.

It deletes all but the most recent 5, not the last 5.

Ah yes, that was a typo, edited the message, basically each PR that is merged creates a new app engine instance that's newer than the production instance, so production will quickly become older than the 5 most recent instances, and get removed.

Yeah only keeping the most recent 5 seems a bit too little. We should keep a lot more here.
The limit is 210. Maybe let's keep half of that (105), which should be plenty of room.

Ah yes, that was a typo, edited the message, basically each PR that is merged creates a new app engine instance that's newer than the production instance, so production will quickly become older than the 5 most recent instances, and get removed.

Oh, got it. gcloud app versions delete --help says "You cannot delete a version of a service that is currently receiving traffic." so the "live" version won't get unceremoniously deleted, the question is what is the failure mode...
Let's experiment! (I <3 having a test sandbox)
$ gcloud --project=oss-vdb-test app versions list --service=default --sort-by="~version.createTime" | head
SERVICE  VERSION.ID                                TRAFFIC_SPLIT  LAST_DEPLOYED              SERVING_STATUS
default  fc61316310651bda9f81f8e1005d71f50f0d09b3  1.00           2023-04-04T12:03:46+10:00  SERVING
default  fc22abcc4f63e25241dbb35613055b1e0ec5abfc  0.00           2023-04-04T11:56:44+10:00  SERVING
default  c32463f4d86d4acedfb82d26b4f67a07d46e15aa  0.00           2023-04-03T15:10:19+10:00  SERVING
default  72be03ba2f5a43af1d3d6caaae51f356f517420e  0.00           2023-04-03T12:18:00+10:00  SERVING
default  b53b4d3ef892c53d3afc34da14439a5ca9cd8c79  0.00           2023-04-03T12:10:52+10:00  SERVING
default  886ca915731f09a59d9bb1d7ea76d397ff510fb8  0.00           2023-04-03T12:03:55+10:00  SERVING
default  816adc3e99cfcc44abda8d01cd97ca72903c950c  0.00           2023-04-03T11:57:04+10:00  SERVING
default  3aecbeaaaf78e54894e1917839ce2ac4782641b0  0.00           2023-04-03T10:51:43+10:00  SERVING
default  b7cc034bbc83c7c579d4935f7f6a17a997ea96d5  0.00           2023-04-03T09:58:08+10:00  SERVING

$ gcloud --project=oss-vdb-test app versions delete fc61316310651bda9f81f8e1005d71f50f0d09b3
ERROR: (gcloud.app.versions.delete) Version [fc61316310651bda9f81f8e1005d71f50f0d09b3] is currently serving 100.00% of traffic for service [default].

Please move all traffic away via one of the following methods:
 - deploying a new version with the `--promote` argument
 - running `gcloud app services set-traffic`
 - running `gcloud app versions migrate`

So it's going to fail messily.

Okay, I've upped the limit to 105, and explicitly filtered out versions serving traffic.


kraken.spec:  Add newline to build targets

Trivial bugfix - If the kraken config file defined by
%{KrakenConfig} happens to not have a trailing newline, the
targets: label will wind up getting tacked onto the end of the last
line of that config file rather than at BOL as it should.
For safety/paranoia, this prepends the YAML snippet with a newline
since YAML doesn't mind blank lines, and this way we don't have to
worry about whether or not the previous contents have the trailing
newline.

LGTM

LGTM