workaround flaky "Operation not permitted" failures in mongo tests

mongo tests intermittenly fail with an "Operation not permitted"
IOException when trying to execute the mongod extracted by
de.flapdoodle.embed.process; this seems to be related to surefire
running tests in parallel. Work around that here by forcing serial
execution of the mongo tests.

Is this needed for module log4j-mongodb3 as well?

Also, I thought {{forkCount=1}} was the default?

We do the same thing in log4j-core here
Is this module inheriting from the root pom.xml? https://github.com/apache/logging-log4j2/blob/master/pom.xml#L1101-L1112

@garydgregory I'm going to merge this commit later today given that this is the first time in recent memory that travis has passed tests. Please let me know if you'd prefer that I hold off.

Go for it.

Merged, thanks!


Relative path for baseURL not working

If I configure instead of
baseURL = "http://example.com"
the base url with a relative path like
baseURL = "http://example.com/somewhere/deeper/"
the hugo server works properly in the localhost environment, however, if I put the site online at the address http://example.com/somewhere/deeper/
it displays only the footer on the main page.

This is a known issue, it probably has nothing to do with relative path. Sometimes I run into this when running hugo server locally, but with the latest version of Hugo, this never appears. If you experience this, just rebuild your site, it should work.
I can't find any ways to reproduce this, so it's hard to sort this out, especially I don't understand a single line of Hugo source codes. I'm not sure if it's the theme is doing something wrong or Hugo itself has a bug…

I'm facing the exact same issue somehow. Everything works fine locally, but whenever I'm publishing to github pages the index.html looks differently. It seems like some step is overwriting the original index.html with the layout for a blog post page.
My config, and the generated index.html.
When running locally and serving from the in-memory Hugo version I see the div#spotlight which seems to be the main page but it's not generated into the public directory.
Any ideas @Track3? I'm quite new to hugo and have no clue where to start looking.

Hi @truemped , I think I found out what causes this problem.
You just need to delete category = "" in your config.toml, in this case is line 14:
https://github.com/truemped/truemped.github.io/blob/51b840be9b8bc262c2c496c4b2b3a5657d82a1ff/config.toml#L14
This is a misconfiguration, it's used to be in the example config.toml file, commit 39cbfb324a96c6e039987df9dfacb67612d34045 has fixed it, but the problem is, when people update the theme, they probably don't change their configs according to the example one.
The below explains why it was there and why it's wrong

I want to disable the category taxonomy and I did this in my config.toml:
[taxonomies]
  tag = "tags"
  category = ""

Turns out it's wrong, according to the docs. The below is enough to override the default taxonomy:
[taxonomies]
  tag = "tags"

This misconfiguration is cousing a lot of problems, it's not a really obvious mistake, and problems it causes are really uncertain, like this one, when running hugo server it's fine, but running hugo it's not.
I'm going to try my best to remind more people to update their configs.
cc @nachsommer

The problem is solved. Thank you so much!

Perfect! Thanks a lot @Track3


image-related markdown will hang app

If I try to render the following in a Markdown view, my app hangs:
![alt text](image.jpg)
This was originally part of a large block of markdown our QA threw at the app, and I whittled it down to this single line.
Note that there is no actual image image.jpg anywhere, but I wouldn't expect malformed markdown to crash/hang the app. This will be displaying arbitrary markdown that the user inputs as a message so I have little control over it.
Additional info:
I have done some more narrowing down of this issue and found that when placed in a simple view, the markdown above works (doesn't display anything, but doesn't hang the app either). But if I embed the view into, say, a TabView, then the app hangs.
I am attaching a sample project with 3 tabs: 2 dummy tabs, and one containing the markdown snippet above. The app hangs on launch trying to render the view w/ markdown.
MarkdownUITest.zip
In addition, here's the relevant view code which triggers the issue:
struct ContentView: View {
    @Binding var selected: Int
    var body: some View {
        TabView(selection: $selected) {
            // Home View
            Text("Home")
            .tabItem {
                Image(systemName: "house")
            }

            // Browse View
            Text("Browse")
                .tabItem {
                    Image(systemName: "folder")
            }

            // Notifications View
           MarkdownTestView()
            .tabItem {
                Image(systemName: "bell")
            }
        }
    }
}

struct MarkdownTestView: View {
    var body: some View {
        Markdown("![alt text](image.jpg)")
    }
}

Anything that I can provide to help reproduce/resolve this let me know. If I can't find a fix or workaround for this I'm going to need to change directions and try to find a different markdown parser, but I really like the SwiftUI simplicity of this one.

I have done some more narrowing down of this issue and found that when placed in a simple view, the markdown above works (doesn't display anything, but doesn't hang the app either). But if I embed the view into, say, a TabView, then the app hangs. I will edit my original issue above to add more detail.

I think I have found a hack workaround. If I give it a (bogus) starting URL on the Markdown initializer, the hang goes away:
Markdown(<markdown including the image tag shown above>, baseURL: URL(string: "http://")!)
Not thrilled with it, but at least it pushes us forward.

我也遇到了这个问题, 在列表中展示相对路径的图片时, APP会无响应, 并且内存持续增加.
而如果是绝对路径, 哪怕图片其实不存在也不会有问题.
最后的解决方案跟tsfischer一样, 给定一个baseURL就能避免这个问题了
I also encountered this problem, when displaying pictures with relative paths in the list, the APP would become unresponsive, and the memory continued to increase.
And if it is an absolute path, there will be no problem even if the image does not actually exist.
The final solution is the same as tsfischer, given a baseURL to avoid this problem

Hi @tsfischer,
Sorry for the late response. Thanks for all the info to reproduce this issue. I will look into it.

Hi @tsfischer,
The fix for this issue will be included in the next release. Thanks again for providing the sample code to reproduce the problem, it was instrumental to find the cause.
Cheers!


Spatial mapping appears in the incorrect location

I have an issue where the anchors appear stable, but the spatial mapping exhibits some strange behaviour. This occurs in the WorldLockingBasic example (adapted to use the XRSDK) as well as an internal sample.
The spatial mapping appears stable for a few seconds, then begins slowly drifting, then extremely drifting. The anchors remain stable the entire time. Here's a video demonstrating this: https://drive.google.com/file/d/1-U0Bj8Gn3og2gPxtg_2PWbb7MVLvRq_E/view?usp=sharing
I haven't found much discussion of spatial mapping aside from FrozenSpatialMapping, where it states:

This is unnecessary when using MRTK's spatial mapping, which provides this and other enhancements over the native spatial mapping.

In device portal, the spatial mesh appears as normal.
Steps to reproduce:

Clone latest master https://github.com/microsoft/MixedReality-WorldLockingTools-Unity/commit/8333fcedf57cb4d2c649981cbebc53f040e5f9d0
Open with Unity 2019.4.16f1 (performs project upgrade)
Import XR Plugin Management (3.2.17) via UPM
Import Windows XR Plugin (2.4.1) via UPM and enable for UWP in XR Plugin Management
Open scene WorldLocking.Examples/Scenes/WorldLockingBasic
Change the MRTK profile to DefaultXRSDKConfigurationProfile
Change the WorldLockingManager ARSubsystem to XRSDK
Build with scene WorldLocking.Examples/Scenes/WorldLockingBasic configured for HoloLens>ARM64
Deploy to Device with Visual Studio (Release ARM64)

(Build runs correctly)

Replace MRTK 2.4.0 with MRTK 2.5.1

(Build exhibits strange behaviour described above)
Subsequently I suspect this is related to the MRTK version upgrade.

I'm having some trouble verifying that this is the cause.
Building this repo (master) in U2019.4.16f1 with no other changes other than to the profiles/XRSDK seems to work as expected.
Modifying the project (i.e. MRTK upgrade as described above) seems to break it and cause this issue.
Attempting to match the configuration (including a copy+paste of the exact MRTK from master) in an existing project also causes this issue.

Am I missing a critical dependency relationship here? Or is something being cached in an unexpected manner? I have turned off Save/Load, and uninstalled, and cleared the Library folder:

This sounds just like this MRTK issue I found and fixed recently. #8920
To verify that you have the fix, could you open Assets\MRTK\Providers\XRSDK\GenericXRSDKSpatialMeshObserver.cs, and verify that all reference to the class PlayspaceAdapter has been removed? (You can text search for Adapter in that file and it should come up as not found.)
Thanks!

Ah, I just saw a comment above. Excellent write-up, by the way, it is very much appreciated that you take the time to be clear about the issues.
If I am reading your comments correctly, the problem happens when you update to MRTK v2.5.1. That makes sense. The fix that I implemented above is in the latest mrtk_development branch (so will be in the next release), but didn't make it into the v2.5.1 release.
If you want to recreate the fix locally onto your v2.5.1 branch, it's actually a very simple fix. Just remove the creation and addition of the GameObject anchorHolder in RequestMesh(). That makes the declaration of the PlayspaceAdapter class superfluous. You can delete it for cleanliness or leave it.

Let me know if the fix to the issue linked above doesn't resolve the problem.

Let me know if the fix to the issue linked above doesn't resolve the problem.

Thanks, the issue is resolved with your proposed changes. Apologies for the delay in getting back to you.
It looks like it will be included in the MRTK 2.6 milestone so hopefully it will be included then :)

Thanks, the issue is resolved with your proposed changes. Apologies for the delay in getting back to you.
It looks like it will be included in the MRTK 2.6 milestone so hopefully it will be included then :)


Proxy should allow duplicate ownKeys when returning getOwnPropertyDescriptors

Fixes test262 test\built-ins\Object\getOwnPropertyDescriptors\duplicate-keys.js and OS: 8729344
Simple spec update to allow duplicate keys to be returned in Object.getOwnPropertyDescriptors by always assigning the return array value. We do not need to keep track of the count because we always remove all instances from the property map in spec code.

I think it will be good to have it so bugs are caught early in CI run itself.
Thanks,
Kunal
From: Tom Care<EMAIL_ADDRESS>Sent: Thursday, June 29, 2017 3:19 PM
To: Microsoft/ChakraCore<EMAIL_ADDRESS>Cc: Kunal Pathak<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Microsoft/ChakraCore] Proxy should allow duplicate ownKeys when returning getOwnPropertyDescriptors (#3266)
@tcare commented on this pull request.

In lib/Runtime/Library/JavascriptProxy.hhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FChakraCore%2Fpull%2F3266%23discussion_r124926120&data=02|01|kunal.pathak%40microsoft.com|fdec04bcad8e4e700eb308d4bf3cdd49|72f988bf86f141af91ab2d7cd011db47|1|0|636343715514837694&sdata=BM7UgRX0noS4G%2FrmhMyX2Qkd1z93wmxo5gqrxWRZYxU%3D&reserved=0:

               if (fn(propertyRecord))

               {

                   trapResult->DirectSetItemAt(trapResultIndex++, element);

               }

           // We explcitly allow duplicates in the results. A map is sufficient since the spec steps that remove entries

Test262 is run in nightlies and should sufficiently cover this case. I could add that one though..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FChakraCore%2Fpull%2F3266%23discussion_r124926120&data=02|01|kunal.pathak%40microsoft.com|fdec04bcad8e4e700eb308d4bf3cdd49|72f988bf86f141af91ab2d7cd011db47|1|0|636343715514837694&sdata=BM7UgRX0noS4G%2FrmhMyX2Qkd1z93wmxo5gqrxWRZYxU%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAL6NfDd2ci2wYBGWxg5ZJaYDv2IF-Aibks5sJCLcgaJpZM4OJ7oc&data=02|01|kunal.pathak%40microsoft.com|fdec04bcad8e4e700eb308d4bf3cdd49|72f988bf86f141af91ab2d7cd011db47|1|0|636343715514837694&sdata=6Gh5vep7XRhnzU7%2FcZsPuae1zoeJ6TUyEIAVHR0npaY%3D&reserved=0.

:shipit:

:shipit:


Make responsive.

Nvm. just adding the correct classes to the images solved the problem.

Cool! Just for people searching, I think you can just set max-width: 100% on the images to do this. Although vjustov might have had another solution!


SSO with AAD B2C fails

Hi,
We've been hitting issues similar to #208. We are using AAD B2C and have Single Sign On configured on the policies correctly. No issues when using MVC OpenID Connect apps, we get the expected SSO behavior. First time we login to B2C and subsequent apps, pressing the login button redirects to B2C and then instantly returns.
We have not been able to get MSAL.js to work. I strongly suspect the prompt=select_account is interfering with SSO. The suggested workarounds did not work as we got errors back saying login_required despite having an active SSO session.
Repro is this: Two apps sharing a B2C signup or sign in policy configured with SSO. First app is an ASP.NET Core app using MVC and the OIDC middleware. Second app is a SPA app with MSAL.js. Login with the ASP.NET Core app first. Now in the same browser tab, go to the SPA app. You should still be signed into B2C, but when you press login on the SPA site, the redirect to B2C forces a sign in.
The ask is this: MSAL.js, out-of-the-box, needs to support SSO with AAD B2C. No special workarounds, it just needs to work. We have validated that MSAL.js is the issue, and not B2C, since other apps using hello.js, for example, do work correctly.

Can I ask how you managed to remove the prompt parameter using msal? We are facing the same issue, I think

@onovotny we just released msal 0.2.3 and it has support for SSO. SSO can be achieved by passing either login_hint or SID.
Can you please tell me if you were passing either login_hint or SID?

@nehaagrawal I have a problem with this. This is my scenario: We have two applications, one SPA that uses msal.js and another MVC application which is not using msal.js. I log in to the MVC application through azure B2C with out SignInSignUp policy and now I have an existing session on Azure, then when I redirect to the SPA and pass a login_hint which msal.js recieves and sends in the extraQueryParams of the loginRedirect. The problem is that when loginRedirect executes it take me to azure using the same policy and it shows the login page and I see the login_hint in the url. Isn't is suppose to log me in or am I doing something wrong?

@SimeonBanev Please try passing the login_hint extraQueryParameter to the acquireTokenSilent method in order to get silent SSO. the login methods are interactive and pass a prompt parameter which is why you are seeing the login page again.

@navyasric But how could that work when there is no logged in user. I tried calling acquireTokenSilent but every time I get the error: 'user_login_error: User login is required' which is understandable give the fact that the clientApplication has no user when you enter the app initially. That is why i tried calling the loginRedirect method so I can get an id_token. Is there something I am missing here which should make the acquireTokenSilent work? I have followed the steps in this article and I am calling it the same way as described - https://github.com/azuread/microsoft-authentication-library-for-js/wiki/Sso

Okay so I debugged the acquireTokenSilent method and it turns out that the problem was that the token request with the loginHint failed and that caused my app to just call it again without an extraQueryParameter so that is why I got the user_login_error. The real problem is that when acquireTokenSilent tries to get the tokens with the login_hint an error is returned: "interaction_required: AADB2C90077: User does not have an existing session and request prompt parameter has a value of 'None'." but that can't be right since I literally logged in to another application with the same tenant and policy 1 minute before that so I have an azure session. I looked up some threads on this issue but I couldn't seem to find any real solution. Any ideas?

@onovotny  We have a PR in progress to remove prompt=select_account hardcoding. Once this feature is released. I will update the details here.

PR https://github.com/AzureAD/microsoft-authentication-library-for-js/pull/489

Is it resolved... ?
Please address ot ASAP, its really urgent for me.
I am using azure-msal package in angular 6

Hi @SimeonBanev ... Have you find any solution
@nehaagrawal is there anything done. If yes please please please let me know

@azure/msal-angular npm package is not updated yet, is it in progress or all have ignored this issue... ?

@zamzowd In MSAL.js we require an authenticated user context to be established in the library before the acquireTokenSilent method starts fetching tokens that provide access to APIs.  Secondly, the library is also used in scenarios where there can be multiple accounts having active sessions for a user. The acquireTokenSilent method cannot determine which user session to pick and establish the context. Hence a login_hint is required for establishing the user context before providing the silent SSO capability.
Since we removed the default prompt=select_account from the login requests as well, can you try calling the login methods and see if you get the SSO behavior for the user session?

@navyasric If the loginRedirect is called, it does get a token from an active session on the authority without the user needing to select an account or log in again.
I would like to be able to check for this active session on the authority silently on application load.
I understand that you require either a cached token for user context or a hint (login_hint or sid) for acquireTokenSilent.  That's what I would like to see changed.  In my pull request #541, I kept the existing behavior of as the default, while allowing my desired behavior with a configuration change.
Could you elaborate on the use case of multiple accounts having active sessions on the client?  I couldn't find this in the wiki.
Fundamentally, MSAL.js should be a convenient interface for web developers to get tokens with the OAuth2 authorization flow and cache the tokens for the application.  While additional features such as allowing multiple accounts with active sessions may be nice, it shouldn't be provided in such a way that it preempts the call/redirect to the authority without an opt-in or opt-out configuration option.

@navyasric How about different approach, rather than a configuration that changes part of the acquireToken processes:
A new loginSilent function.  This will be similar to loginRedirect and loginPopup, except it will go through a hidden iframe with prompt=none to try to get an existing session from the authority.  So the sole purpose of this new function is to support the behavior that I am trying to achieve.
It has a couple benefits over my existing pull request:

It doesn't add an additional config / change existing behavior.
It rounds out the login / acquireToken sets.  loginX functions will be used for the initial get of an id token from the authority, while acquireTokenX will be follow-up functions used to get the token from cache, refresh tokens, or get access tokens.

I'll try to get the time to write up a new pull request.  I'll leave the existing pull request open as well, leaving the decision of which to take on your team.  I expect this new approach will be preferable, though.


No shuffle layer when training condensenet?

Dear @ShichenLiu ,
I did not found any shuffle layer related stuff in models.condensenet, which use layers.LearnedGroupConv as LGC. However, the paper says we should use it clearly. Is it a mismatch?
Thanks

Hi @hiyijian ,
Actually we implicitly include it in LearnedGroupConv for training speed consideration, so it is not a mismatch. Specifically, here we drop weights from shuffled convolution weights, which is equivalent to an appended shuffle layer. The shuffle layer is explicitly appended to CondenseConv here when converted.

Thanks. So shuffle layer is implicitly appended after the first stage. During the first stage, we dont need such a shuffle layer?

@hiyijian Yes. Only in testing stage do we need shuffle layers.

@ShichenLiu , I am still confused about this question.
Isn't the learned feature map has the learned mapping with the 1x1-conv-filter here?
Why is shuffle layer is applied here?


docs(Cypress integration.md): add return keyword in setupNodeEvents

:tada: This PR is included in version 1.31.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[staging-21.11] libinput: 1.19.1 → 1.19.4

Description of changes
Backport of #150019 plus 1.19.3 -> 1.19.4 update, fixes CVE-2022-1215
https://gitlab.freedesktop.org/libinput/libinput/-/compare/1.19.3...1.19.4
https://lists.x.org/archives/wayland-devel/2022-April/042161.html
See https://github.com/NixOS/nixpkgs/pull/169399 for nixos-unstable
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build libinput

It's unclear to me if the clean up, docs build fix and maintainer changes need to be backported. I know jtojnar does not maintain things on stable anyway.
The bump to 1.19.4 should include Fixes: CVE-2022-1215.

docs build fix and maintainer changes need to be backported

I don't see a reason not to. If no breaking changes are introduced by it, then anyone willing to "put in the work" should be free to backport changes. And in this case, I would call them improvements.


Fix test async

@rafie is the the failure related to the redis version?

@ashtul it's because we changed the redisearch-py client to not support Async

@ashtul it's because we changed the redisearch-py client to not support Async

Just came across this when looking for a RediSearch AIO client. Is there a plan to support Async in the future?


iOS - crash: change camera feed while on the call

What's the right way to switch the camera from the front-camera to the rear-camera while the call is going.
I tried this, it works a few times, then it crashes. Any idea why?
[self.localVideoTrack removeRenderer:(RTCEAGLVideoView*)[self.viewController localVideoTrackViewForCallController:self]];
        RTCMediaStream* lms = self.peerConnection.localStreams[1];
        [lms removeVideoTrack:self.localVideoTrack];
        [self.peerConnection removeStream:lms];

        NSString *newVideoTrackId = nil;
        NSString *oldVideoTrackId = nil;
        if (_rearCamera) {
            oldVideoTrackId = @"ARDAMSv1";
            newVideoTrackId = @"ARDAMSv0";
        }
        else {
            oldVideoTrackId = @"ARDAMSv0";
            newVideoTrackId = @"ARDAMSv1";
        }

        RTCVideoCapturer* capturer = [RTCVideoCapturer capturerWithDeviceName:newCameraID];
        self.videoSource = [_peerConnectionFactory videoSourceWithCapturer:capturer constraints:self.videoConstraints];
        self.localVideoTrack = [_peerConnectionFactory videoTrackWithID:newVideoTrackId source:self.videoSource];

        [lms addVideoTrack:self.localVideoTrack];
        [self.peerConnection addStream:lms];

        RTCSessionDescription* remoteDesc = self.peerConnection.remoteDescription;
        RTCSessionDescription *localDesc = [[RTCSessionDescription alloc] initWithType:self.peerConnection.localDescription.type sdp:[self.peerConnection.localDescription.description stringByReplacingOccurrencesOfString:oldVideoTrackId withString:newVideoTrackId]];

            [self.peerConnection setLocalDescriptionWithDelegate:self sessionDescription:localDesc];
            [self.peerConnection setRemoteDescriptionWithDelegate:self sessionDescription:remoteDesc];

I think you would have better luck opening an issue with the WebRTC issue tracker (https://code.google.com/p/webrtc/issues) as this deals more with the workings of WebRTC itself and not these scripts for building it.

thanks, you are right. I added the issue there. closing here


Image and Katex inserted to start of the document and not where cursor is placed.

Most of the time while inserting image or Katex, It does not get inserted where mouse is placed but it gets inserted at the start of the document.

This issue is not reproduced.


Update documentation after Merging Go Strings

After merging the recent changes to the Go strings module, the README file needs to be updated to reflect the modifications and provide accurate information.

Also, let's consider updating the help text (floss -h).


Add [Binance Withdrawals binance.com] #exchange GC5LF6…D6Z6FH

Address: GC5LF63GRVIT5ZXXCXLPI3RX2YXKJQFZVBSAO6AUELN3YIMSWPD6Z6FH
Tags: exchange
Title: Binance Withdrawals  Domain: binance.com
Requested by @jesse6484

Hello @jesse6484
I am not sure what you are asking. This wallet has already been tagged as Binance Withdrawals. Can you give more details about your request?
Looking towards the future with you,
Rob

Hello @jesse6484
If the issue is related to a transaction you sent without a memo you will bee to contact the Binance support team.
Stellar Expert is just a blockchain explorer and does not have any control of transactions on the block chain.
They will also need to know the transaction ID which can be found by clicking on the operation number next to the transaction.
Looking towards the future with you,
Rob


Extend "transform" with ability to transform date of entity status

Checklist

[x] I am running the latest version of the card
[x] I checked if there isn't another feature request opened with the same request
[x] I checked that the feature is not already available in the dev branch

Is your feature request related to a problem? Please describe.
The transform-option offers the ability to transform the entity value throught he 'x' value.
For sensor date which registers e.g. utility data which are consistently at least 24h old, it would be very convenient to be able to skew the date of the series to the correct one by using transform.
Describe the solution you'd like
I would like what would amount to a 'date' parameter in addition to the 'x' parameter of the tranaform-option such that the following is possible (I am not sure of datetime calculations in JS, so bear over with that detail here):
type: custom:apexcharts-card
series:
  - entity: sensor.water_day_data
    transform: "delta=<timedelta(1d)>; return (date, x) === (d-delta, x);"

Describe alternatives you've considered
I am the author of a couple of integrations where the returned data is at least 24h delayed - yesterday's consumption basically.  So far I put the data in the attributes of the last state and use data_generator to chart the data at the correct point in time.   It would however be a lot more convenient if the true sensor data could be used instead.
Additional context
As an example.  The sensor data is updated when the data becomes available:

However this number is actually valid for the day before.  Which is done with the apexchart and attribute data in the data_generator option:

Because attribute data is solely present on the latest sensor status the integration will have to fetch historical data as far back as seems reasonable.  This is not as elegant as just skewing the history data one day using a transform.

Good approach, however to avoid a breaking change, I'll introduce a new parameter instead of reusing transform

Still valid.

Bump.


Escape tool escapes new lines as (#1)

Text Escape/Unescape Newline Encoding Options

Please check the type of change your PR introduces:

[ ] Bugfix
[x] New feature or enhancement
[x] UI change (please include screenshot!)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Internationalization and localization
[ ] Other (please describe):

What is the current behavior?

Currently escaping or unescaping newlines in text only handles \r
Issue Number: #468
What is the new behavior?
Allows the user to choose encoding option for newlines between CRLF (\r\n) (Windows), CR (\r) (Mac) and LF (\n) (Linux)

Adds a combox withe the following options in the Text Escape/Unescape UI: CRLF (\r\n) (Windows), CR (\r) (Mac) and LF (\n) (Linux)
Replaces all newline charcters to the option selected when escaping
Converts all escaped newline charcters to the option selected

Other information

before

after

Quality check
Before creating this PR:

[x] Did you follow the code style guideline as described in CONTRIBUTING.md
[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? On Windows, you can use Accessibility Insights for this.
[x] Did you verify that the change work in Release build configuration
[x] Did you verify that all unit tests pass
[x] If necessary and if possible, did you verify your changes on:

[x] Windows
[ ] macOS (DevToys 2.0)
[ ] Linux (DevToys 2.0)

Hello,
Sorry for the long wait before looking at it. We're actively working on DevToys 2.0 and what you are addressing in this PR is done in DevToys 2.0 already. I will close this PR as we don't work on DevToys 1.0 anymore. Thank you for your contribution though! We appreciate :)


Remove unneeded (?!) includes

As I see it, the application defendant includes are not needed, though I'm not entirely sure about it. @changtengfei can you please carefully check this?

@PeterKietzmann those includes are required when the apps=applications options is used in compiling. The CI doesn't have compile with apps options by default.


question of configuration

Hi,
I want to configure sensu-grid but I don't know the way to configure the service start up on centos 7. I tried to do it by hand and this is the result and the log.
[root@ardc02sensu01 start-scripts]# /usr/bin/gunicorn -n sensu-grid --user sensu-grid --group sensu-grid --chdir /opt/sensu-grid --reload --workers 3 --bind <IP_ADDRESS>:5000 --log-file /var/log/sensu-grid.log--log-level info --access-logfile /var/log/sensu-grid.log --error-logfile /var/log/sensu-grid.log
[root@ardc02sensu01 start-scripts]# cat /var/log/sensu-grid.log
[2018-02-23 15:38:23 +0000] [23516] [INFO] Starting gunicorn 19.7.1
[2018-02-23 15:38:23 +0000] [23516] [INFO] Listening at: http://<IP_ADDRESS>:5000 (23516)
[2018-02-23 15:38:23 +0000] [23516] [INFO] Using worker: sync
[2018-02-23 15:38:23 +0000] [23532] [INFO] Booting worker with pid: 23532
[2018-02-23 15:38:23 +0000] [23532] [ERROR] Exception in worker process
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/gunicorn/arbiter.py", line 578, in spawn_worker
worker.init_process()
File "/usr/lib/python2.7/site-packages/gunicorn/workers/base.py", line 126, in init_process
self.load_wsgi()
File "/usr/lib/python2.7/site-packages/gunicorn/workers/base.py", line 135, in load_wsgi
self.wsgi = self.app.wsgi()
File "/usr/lib/python2.7/site-packages/gunicorn/app/base.py", line 67, in wsgi
self.callable = self.load()
File "/usr/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 65, in load
return self.load_wsgiapp()
File "/usr/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py", line 52, in load_wsgiapp
return util.import_app(self.app_uri)
File "/usr/lib/python2.7/site-packages/gunicorn/util.py", line 352, in import_app
import(module)
ImportError: No module named info
[2018-02-23 15:38:23 +0000] [23532] [INFO] Worker exiting (pid: 23532)
[2018-02-23 15:38:23 +0000] [23516] [INFO] Shutting down: Master
[2018-02-23 15:38:23 +0000] [23516] [INFO] Reason: Worker failed to boot.
[root@ardc02sensu01 start-scripts]#

hi, could you let me know what version / commit sha (?) you're working with ?
the latest version (that comes with centos7 unit script) should no longer even need gunicorn
also the output of these would be useful:

pip --freeze
uname -r
linux distribution you're using

in case it's a bug I need the above to try to replicate it ...
Thanks
alex

Hi ALex,
Thankd for your repply. This is the output of the commands.
[root@ardc02sensu01 ~]# pip --freeze
Usage:
pip  [options]
no such option: --freeze
[root@ardc02sensu01 ~]# uname -r
3.10.0-693.5.2.el7.x86_64
[root@ardc02sensu01 ~]# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
[root@ardc02sensu01 ~]#
Maybe I am starting the service in a different way. I included the
sensugrid.conf here.
[root@ardc02sensu01 system]# ls -ltr
total 20
-rw-r--r--. 1 root  root   208 Oct 10 14:48 sensu-server.service
-rw-r--r--. 1 root  root   208 Oct 10 14:48 sensu-client.service
-rw-r--r--. 1 sensu sensu  202 Oct 10 14:48 sensu-api.service
drwxr-xr-x. 2 root  root    44 Nov 17 09:32 system-update.target.wants
drwxr-xr-x. 2 root  root    32 Nov 17 09:32 getty.target.wants
drwxr-xr-x. 2 root  root    87 Nov 17 09:32 default.target.wants
drwxr-xr-x. 2 root  root    29 Nov 17 09:32 sockets.target.wants
lrwxrwxrwx. 1 root  root    57 Nov 17 09:33
dbus-org.freedesktop.nm-dispatcher.service ->
/usr/lib/systemd/system/NetworkManager-dispatcher.service
lrwxrwxrwx. 1 root  root    46 Nov 17 09:33
dbus-org.freedesktop.NetworkManager.service ->
/usr/lib/systemd/system/NetworkManager.service
drwxr-xr-x. 2 root  root    89 Nov 17 09:33 sysinit.target.wants
lrwxrwxrwx. 1 root  root    37 Nov 17 09:36 default.target ->
/lib/systemd/system/multi-user.target
drwxr-xr-x. 2 root  root    24 Nov 17 10:05 redis.service.d
drwxr-xr-x. 2 root  root    24 Nov 17 10:05 redis-sentinel.service.d
drwxr-xr-x. 2 root  root    25 Nov 17 10:06 rabbitmq-server.service.d
drwxr-xr-x. 2 root  root    31 Nov 21 12:47 basic.target.wants
drwxr-xr-x. 2 root  root  4096 Feb 23 14:18 multi-user.target.wants
-rw-r--r--. 1 root  root   756 Feb 23 15:25 sensu-grid.conf
[root@ardc02sensu01 system]#
On Mon, Feb 26, 2018 at 4:52 AM, Alex Leonhardt<EMAIL_ADDRESS>wrote:

hi, could you let me know what version / commit sha (?) you're working
with ?
the latest version (that comes with centos7 unit script) should no longer
even need gunicorn
also the output of these would be useful:

pip --freeze
uname -r
linux distribution you're using

in case it's a bug I need the above to try to replicate it ...
Thanks
alex
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alex-leonhardt/sensu-grid/issues/14#issuecomment-368416998,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjEeC8wCebnG2cVV-qylZ6qJealyBVFfks5tYmLQgaJpZM4SRTk5
.

apologies, the first command should've been without the -- ... could you re run: pip freeze and send me that output ?
also, what "version" of sensu-grid are you using? could you pull the latest version (current master) and use the unit file that comes with it? it should not need gunicorn anymore ..

please don't send the sensu-grid.conf as it may contain secrets ... (api password) ... please sanitise it (remove passwords, some environmental specifics that you feel should not be public) before attaching

Hi Alex,
When I checked the log for /var/log/sensu-grid.log
[root@ardc02sensu01 sensu-grid]# tail -f /var/log/sensu-grid.log
2018-03-05 15:43:25,371 - griddata - DEBUG - Retrieving filters for datacenter: dev
2018-03-05 15:43:25,377 - griddata - ERROR - Got exception while filtering on clients: 403 Client Error: Forbidden for url: http://x.x.x.x:4567/clients
2018-03-05 15:43:25,377 - griddata - ERROR - no reponse
2018-03-05 15:43:25,377 - griddata - ERROR - No response data
2018-03-05 15:43:25,377 - griddata - DEBUG - Filter Retrieval for datacenter dev complete
2018-03-05 15:43:27,691 - griddata - DEBUG - Retrieving filters for datacenter: dev
2018-03-05 15:43:27,697 - griddata - ERROR - Got exception while filtering on clients: 403 Client Error: Forbidden for url: http://x.x.x.x:4567/clients
2018-03-05 15:43:27,697 - griddata - ERROR - no reponse
2018-03-05 15:43:27,697 - griddata - ERROR - No response data


Borrow the most useful functions from the grml config

I’m thinking about stuff like mkcd.
Maybe sort them by use and put them in different plugins?

@Profpatsch Feel free to submit a PR


Raw Accel

Whenever i applied classic curve it is not applying, it switches to linear curve. please fix this

Classic curve with power of 2 is the same as linear curve. This is known, purposeful, and we have no intention of "fixing".


Focus group loading forever

Describe the bug
List Web PubSub and click the "Focus Group. The focused resources seem loading forever.

To Reproduce

Exceptions (if any)

Further technical details

SDK and its version you use

It could be done but extremely slow... Same slow for other resource type. I think it's caused by upstream extension (azure resource group extension)

Fixed in https://github.com/Azure/azure-webpubsub/pull/739


Bump to python3 and change things to bytes where needed

Bumps to python3.
Some things in python3 that were previously str are now bytes, change
those things.

Thanks!


Updated Huawei cloud support as per new bucket management CRUD

What type of PR is this?
/kind enhancement
What this PR does / why we need it:
This PR updates the UI with following:

Support registration of Huawei cloud without the bucket name.
Update the Lifecycle UI to allow bucket selection when Huawei cloud backend is selected.

Which issue(s) this PR fixes:
Fixes #540
Test Report Added?:
/kind TESTED
Test Report:

Special notes for your reviewer:

code changes looks fine.
can you please raise this to master?


make the build process "quieter"

This commit modifies the Makefile in order to allow for a quieter build. It does hide the executed commands but they can be shown by running make S=. This also fixes the build on my machine by commenting out a line that apparently does nothing useful. I left it in on the rare chance that we do need it.

mp told me that he accidentally committed that line
gonna go ahead and outright remove it


Getting an error "Could not send authentication request." when trying to listen on a private channel

When trying to make a simple example of using Laravel and Laravel Echo Server, I get an error "Could not send authentication request."

What did I do:

I created a new fresh Laravel 5.3 project $ laravel new laravel53. Laravel app is served on http://laravel53.dev
$ npm install
$ npm install --save laravel-echo laravel-echo-server pusher-js socket.io-client (for some reason laravel-echo needs pusher-js although I'm not using Pusher)
$ laravel-echo-server init with a config below

uncommented App\Providers\BroadcastServiceProvider::class, in config/app.php
appended the following code to resources/assets/js/app.js

import Echo from 'laravel-echo';
window.io = require('socket.io-client');

window.Echo = new Echo({
    broadcaster: 'socket.io',
    host: 'http://localhost:6001'
});

window.Echo.private('user.1')
    .listen('NewMessageSent', (e) => {
        console.log(e.update);
    });

added the following code to BroadcastServiceProvider

Broadcast::channel('user.*', function ($user, $userId) {
    return true;
});

$ laravel-echo-server start
$ gulp
$ touch database/database.sqlite
set sqlite as DB driver in .env
$ php artisan make:auth
$ php artisan migrate
visited http://laravel53.dev/register, created account and landed on http://laravel53.dev/home as authenticated user
Could not send authentication request. shows up in the terminal

laravel echo server and laravel php server must use one host name.
...
window.Echo = new Echo({
    broadcaster: 'socket.io',
    host: 'http://localhost:6001'
});
...

{
	"appKey": "9te930q989itok355krkfrs95j92ais01iim3i5sjs1k93g87kt8qdd0ur91",
	"authEndpoint": "/broadcasting/auth",
	"authHost": "http://localhost:8000",
	"database": "redis",
	"databaseConfig": {
		"redis": {},
		"sqlite": {
			"databasePath": "/database/laravel-echo-server.sqlite"
		}
	},
	"devMode": true,
	"host": "localhost",
	"port": "6001",
	"protocol": "ws",
	"referrers": [],
	"sslCertPath": "",
	"sslKeyPath": "",
	"verifyAuthPath": true,
	"verifyAuthServer": false
}

Thanks. Maybe it could have a better error message or smth to show what's probably wrong.

I am also the problem, how to repair

some problem

I am also facing same problem.
My code is on https://github.com/gdbhosale/laravel-5.3-socket-io-vue.js
Any way out  ?

The problem happend to me. Make sure you check the following:

No error occured, for example with the broadcast check; check your logs
Check if the result returns true. When false, it fails but gives the error null - Could not send authentication request.

Would be nice if it just said the response failed with status 500 or the actual message, and showed when the request is rejected.

I am also facing same problem.
Any way out ?

any solution yet

Did you try what I said?

Apoloze,... I am totally new in the matter. Thats why I am quite confused on your last solution... Can you indicate the changes with files name?

I mean in your Laravel application. This error could indicate that your user is not correctly authenticated. So either you get an error while trying to verify this, or the user is not authenticated.
So check your laravel logs (storage/logs/laravel.log) to see if an error occured. Or set some logging in your broadcast provider, to log the status.
And don't forget to enable the provider of course:
class BroadcastServiceProvider extends ServiceProvider
{
    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        Broadcast::routes();

        /*
         * Authenticate the user's personal channel...
         */
        Broadcast::channel('App.User.*', function ($user, $userId) {
            return (int) $user->id === (int) $userId;
        });
    }
}

Thanks for your faster replying....

Also, please make sure you don't have any redirects for the /broadcasting/auth route. Any status except 200 will cause an error in Laravel Echo Server. It can be language redirects like /en/broadcasting/auth or some others.

FYI, I created a PR (#101) to show the difference between invalid configuration and just not getting authenticated. That should be more clear to see what's actually wrong here.

Thank you @barryvdh. Useful improvement. Voted for it.

I have same problem. storage\laravel.log is clean.
If i use only Broadcast::routes() I will get status: 403
If i use this Broadcast::routes(['middleware' => ['auth', 'web']]); "unauthorized" status: 401
I use laravel-echo-server/redis/socket.io,
I tried jwt-auth because of csrf token and got same errors.
Any solution?

You need to explicitly authorize all private /presence channels, did you do that?

What does that mean?

https://laravel.com/docs/5.3/broadcasting#defining-authorization-callbacks

Yeah. It was defined.
Broadcast::channel('message-received', function ($user, $userId) {
            return true;
        });

And are you using default authorization? (sessions with cookies), or something else?

I use default authorization.

These are the headers that are sent by the request: https://github.com/tlaverdure/laravel-echo-server/blob/95d6a111cf5c3a5fb307a1d837c67f12de50439a/src/channels/private-channel.ts#L71-L82
So if you're using custom headers, they're not sent. We should probably send all custom headers.
How are you defining your Echo config client-side?

this is my client side code:
import Echo from "laravel-echo"

window.Echo = new Echo({
    broadcaster: 'socket.io',
    host: 'http://localhost:6001',
});

window.Echo.private('message-received')
    .listen('MessageWasReceived', (e) => {
        console.log(e.statusMessage);
    });

Sorry, the auth headers are correctly sent. Strange that you are not authorized.

Yeah, no problem, I don't understand also.

I solved it. I just a mistake.
laravel-echo-server.json:
"authHost": "http://test.dev",
"host":"test",

on the client side use localhost that is the problem:
window.Echo = new Echo({
broadcaster: 'socket.io',
host: 'http://localhost:6001',
});
change localhost to test.dev.
Now It works.

It doesn't work for me http://prntscr.com/dxwb4o my BroadcastServiceProvider is enabled. I got this:
`<?php
namespace App\Providers;
use Illuminate\Support\ServiceProvider;
use Illuminate\Support\Facades\Broadcast;
class BroadcastServiceProvider extends ServiceProvider
{
/**
* Bootstrap any application services.
*
* @return void
*/
public function boot()
{
Broadcast::routes();
    /*
     * Authenticate the user's personal channel...
     */
    Broadcast::channel('check-channel', function () {
        return true;
    });
}

}
`
and
` window.Echo = new Echo({
broadcaster: 'socket.io',
host: 'http://<IP_ADDRESS>:6001'
});
window.Echo.private('check-channel')
.listen('Message', (e) => {
console.log('HERE', e);
});`
and my laravel-echo-server config
{ 	"authHost": "<IP_ADDRESS>", 	"authEndpoint": "/broadcasting/auth", 	"clients": [ 		{ 			"appId": "APP_ID", 			"key": "93cca48913d0b9590070bb8784b9052e" 		} 	], 	"database": "redis", 	"databaseConfig": { 		"redis": { 			"port": "6379", 			"host": "<IP_ADDRESS>", 			"password": "mypassword" 		}, 		"sqlite": {} 	}, 	"devMode": true, 	"host": "<IP_ADDRESS>", 	"port": "6001", 	"protocol": "http", 	"socketio": {}, 	"sslCertPath": "", 	"sslKeyPath": "" }
for public channels work but for private doesnt please give me some advice. Thanks

Fixed. I've forgot to put this meta on top of the document.
<meta name="csrf-token" content="{{ csrf_token() }}">

@xscence It appears to me that your original issue was related to the fact that authHost requires an absolute address of the Laravel site and not just a hostname. Your screenshot tells us exactly that.
You may read more here.

Hi! I'm using your laravel-echo-server with socket.io in my project on Silex.
I tested authentication with cookie and it works. But i don't use sessions, so i need to add header with token for authentication request.
I've seen your answer with link for private-channel.ts file. But i don't understand where i can customize request?


Update to SlurmGCP 6.6.0

Upgrade Slurm to 23.11.8
Update NVIDIA driver to 550.90.07
TPU test. Update JAX version and dependencies

lgtm after all tests pass


Add documentation for properties and methods relating to Data Types.

We are shipping the new Data Types feature in Excel, and along with this, we've added some methods and properties that allow developers to create and interact with them.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/Excel.Range.ConvertToLinkedDataType.md
:white_check_mark:Succeeded
View

api/Excel.Range.DataTypeToText.md
:white_check_mark:Succeeded
View

api/Excel.Range.HasRichDataType.md
:white_check_mark:Succeeded
View

api/Excel.Range.LinkedDataTypeState.md
:white_check_mark:Succeeded
View

api/Excel.Range.SetCellDataTypeFromCell.md
:white_check_mark:Succeeded
View

api/Excel.Range.ShowCard.md
:white_check_mark:Succeeded
View

api/Excel.XlLinkedDataTypeState.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@astegmaier Later today I'll add these to the TOC. Could you let me know where in the TOC you'd like them? https://docs.microsoft.com/en-us/office/vba/api/overview/excel

Most of the new articles should be under Excel > Object Model > Range, except for the new enum (XlLinkedDataTypeState), which should be under Excel > Object model.
For future reference, is there a file in the repo that controlls the table of contents? I can make sure to make that a part of future PRs.

@astegmaier Yes, there is a TOC file; however, it's huge, so it's safer if you just let us know where you want the files, and we can make the TOC updates. There are about 70,000 entries, and one glitch can break it. ;-)
I assume you want the enum file to be under Excel > Object Model > Enumerations? https://docs.microsoft.com/en-us/office/vba/api/excel(enumerations)

@astegmaier I updated the TOC and the corresponding navigation pages with the new topics.  Changes should be live by tomorrow. Thanks for contributing!

Your contribution is now live: https://docs.microsoft.com/en-us/office/vba/api/excel.range(object)
Let me know if you have any questions.


Feature request: Human friendly Camera API for SceneView

Hi,
Currently we are not allowed to modify various camera parameters while in the SceneView. What is possible is to set the near and far planes, and albeit a warning is raised, to set the projection matrix. However the Filament Camera class (https://github.com/google/filament/blob/master/filament/src/Camera.cpp) is quite rich and some of the functions may be exposed. For example the corresponding Camera class in iOS SceneKit has much friendlier API - https://developer.apple.com/documentation/scenekit/scncamera. I have implemented the functionality that we need (orthographic projection and scale) using the projection matrix but I don't like to do that manually. I think at least the Camera API should allow us to set the view volume (l,r,b,t,n,f), perspective / orthographic option, orthographic scale, and horizontal/vertical field of view for perspective.
Thanks.

+1 on this.

+1 please


[DOCFIX]Update Chinese doc for Key-Value-System-API

Update Chinese doc for Key-Value-System-API.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14713/
Test PASSed.


Not removing Biscuits when deleting a line

When I delete a line (e.g. with dd) , the biscuit associated with the line stays, without any way to remove it (AFAICT).
I'm using the cusor_line_only option, in case this is relevant.

Interesting. Thanks for reporting this. I will have to look into it.
Have you tried without cursor_line_only as well? No worries if not, just curious.

Just tried it. Same thing happens without cursor_line_only.

FWIW, adding a call to nvim_buf_clear_namespace before the while has_nodes loop in init.lua solves the problem for the case when cusor_line_only is set. However it introduces additional issues in case it is not set, moving the biscuit to an incorrect line.

FWIW, adding a call to nvim_buf_clear_namespace before the while has_nodes loop in init.lua solves the problem for the case when cusor_line_only is set. However it introduces additional issues in case it is not set, moving the biscuit to an incorrect line.

That is a great fix. I'm not sure that is a new bug with the biscuit being on the wrong line. It is likely just a failure of the tree-sitter parser because the code no longer actually validates in the cases I have seen.


Graph not showing with v9.11.4210

Hello
I'm not sure if it's just me, but it seems like the solver log is formatted slightly differently in v9.11.4210 (Python 3.8.10), which means graphs are no longer parsed correctly.
I've attached an example log: urgent_sets_log.txt
The offending line is:
3 helper subsolvers: [neighborhood_helper, synchronization_agent, update_gap_integral]

#1       0.05s best:40    next:[39,39]    no_lp (fixed_bools=0/6)

If I remove the newline in between the two lines, the graph now shows correctly.
I'm not sure if there's any other whitespace differences that are hiding other graphs...

Thanks for letting me know. I haven't made the switch yet but I will check it soon and fix it if necessary. Looks unfortunately more annoying to parse. 🤔

I can confirm the bug with the new version.

Should be fixed now. Not pretty but I unfortunately do not have the time to rewrite that part properly. I used the empty lines to separate the blocks and find the right parser for each, but this block now being split into two (but being a single block in older versions) requires a different handling. My current workaround is just to find and remove that specific empty line so the old blocks are restored.

@d-krupke i tried the log file provided in the 1st comment, and i get:
Could not render block Search progress: of type <class 'cpsat_log_parser.blocks.search_progress.SearchProgressBlock'>. Error: '<class 'streamlit.errors.StreamlitDuplicateElementId'>' - 'There are multiple plotly_chart elements with the same auto-generated ID. When this element is created, it is assigned an internal ID based on the element type and provided parameters. Multiple elements with the same type and parameters will cause this error.

To fix this error, please pass a unique key argument to the plotly_chart element.'. Please check the raw log. If you think this is a bug, please report it [here](https://github.com/d-krupke/CP-SAT-Log-Analyzer/issues).

manually removed the newline suggested did not help.

@d-krupke i tried the log file provided in the 1st comment, and i get:

Could not render block Search progress: of type <class 'cpsat_log_parser.blocks.search_progress.SearchProgressBlock'>. Error: '<class 'streamlit.errors.StreamlitDuplicateElementId'>' - 'There are multiple plotly_chart elements with the same auto-generated ID. When this element is created, it is assigned an internal ID based on the element type and provided parameters. Multiple elements with the same type and parameters will cause this error.

To fix this error, please pass a unique key argument to the plotly_chart element.'. Please check the raw log. If you think this is a bug, please report it [here](https://github.com/d-krupke/CP-SAT-Log-Analyzer/issues).

manually removed the newline suggested did not help.

That is odd. I will check and fix it later today. Thanks for letting me know. Seems to be an issue with plotly.

Was able to reproduce the problem. Seems to be linked to an update of either streamlit or plotly. Will open a new issue.

@eyaler it should be fixed now.


Spring Boot 2.0 Support

@yungez @xscript @yaweiw

@snicoll It seems our starters can work well with SB 2.0 after a few minor changes.

We're thinking about a better version name. How about 0.2.0-SB2? Any suggestion?

Should we release it and make it available in Spring Initalizr before Spring One?

It seems our starters can work well with SB 2.0

Cool!
I remember that the active directory bits are much more easier with Spring Security 5 and perhaps some code on your side could be removed? I've pinged @rwinch on the original issue, perhaps he can share more details?

We're thinking about a better version name

I wouldn't change the version structure (besides the version bump). First I would create a 0.2.x branch (or whatever the current  version is) and I'd switch master to be Spring Boot 2 only and the branch to be Spring Boot 1 only. I guess you're going to continue improving the support for Spring Boot 1 users for some time still. 0.3.x could be the range for Spring Boot 2 (or you could switch to 1.x

Should we release it and make it available in Spring Initalizr before Spring One?

I don't know. If you feel confident that it works well with Spring Boot 2, perhaps you could release a milestone of your own? There are a few issues in the PR though, I'll comment.

Add our PMs  @Matthew-Dong @selvasingh

I remember that the active directory bits are much more easier with Spring Security 5 and perhaps some code on your side could be removed?

Spring Security 5 provides all you should need to do log in with OpenID Connect or an OAuth2 based log in. You can refer to https://docs.spring.io/spring-security/site/docs/current-SNAPSHOT/reference/htmlsingle/#jc-oauth2login for details
cc @jgrandja

Hello,
Do you have any ideas when new version will be available?

@sshogunn We plan to resume the Spring Boot Support work in January 2018. New release could happen during that month or later.

Upgraded to Spring Boot 2.0 in other PRs.


eCALPlayer: Hangs when trying to access non-existant measurement

Describe the bug
When trying to open an non-existent measurement via "File" -> "Recent Measurements" ->
the Graphical User Interface hangs.
To Reproduce
Steps to reproduce the behavior:

Open a measurement in eCALPlayer
Close the eCALPlayer
Delete the measurement or move it to another location
Reopen eCALPlayer
Try to open the measurement via "File" -> "Recent Measurements" ->

Expected behavior
An error message that the measurement does not exist any longer
Desktop (please complete the following information):

Device: Laptop
OS:Windows
Version:eCAL 5.7.2

I can confirm the issue. It is caused when the deleted measurement was loaded from a directory (not an .ecalmeas file). In that case, the eCAL Player will try to load the parent directory, which will probably contain many files. This may take very long and look like the player is freezing.


Issue-1337: Fix unstable concurrent code in PointcutLatch, fix subscr…

…iption tests getting latch exceptions due to missing expectations, make hapi-fhir-jpaserver-subscription tests load StructureDefinitions outside latch timers, as this can be slow on busy machines
https://github.com/jamesagnew/hapi-fhir/issues/1337

Stig,
This is great work!  Please merge master into your branch to pick up the jococo fix @jamesagnew committed last night.  Would be good to see green on Travis before merging.
Ken

@fil512 Thanks, rebased.


Add package MikTeX

MikTeX is a popular TeX implementation in windows. It can be built dynamically fluently, however, statically building failed due to faults in tex components which haven't support static building. Static building is temporarily disabled.

Just wondering: Are you using the tex libraries in a c++ project?

Nope actually. 😸

/azp run

/azp run


Medium clue - Arrow hints not following some NPCs

Instead of following the NPC, Edmond's arrow is pointing toward the ground as if it was a dig clue

Here's for Gabooty medium clue

Here's Captain Khaled's clue in Kourend

I am pretty sure cff46bb3d891eb0109882f80d22f2bcfe72da08f has fixed this. I can at least confirm that the last picture you posted is fixed now because of said commit.

I can confirm that this issue if fixed for weeks now. (Forgot to take a picture of Gabooty...)

@MalakaJones if this issue is fixed you can close it


Zeek Setup

Finish setup scripts
Create service and start on boot

Works now. Local environment settings moved to hoot.sh, for post install config


fix: #15 issue with missing and incorrect values

Alaska Airlines Pull Request
Fixes: #15
Summary:
Update tokens to address incorrect and missing values.
Type of change:
Please delete options that are not relevant.

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Orion Design System Team

:tada: This PR is included in version 2.9.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Hotfix: Accommodate escaping of wildcard in permissions

e800dcc cherry-picked to release/3.6 for deployment tonight.


Build issue on Crystal 0.18.4

Looks like its todo with building it as static however i do have these libraries installed.
[brian@orville crt.cr]$ make
crystal compile --release examples/hello.cr -o bin/hello --link-flags "-static"
/usr/bin/ld: cannot find -lrt
/usr/bin/ld: cannot find -lncursesw
/usr/bin/ld: cannot find -lgpm
/data2/crystal-0.18.6-1/embedded/lib/../lib/libevent.a(evutil.o): In function test_for_getaddrinfo_hacks': evutil.c:(.text+0x1488): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /data2/crystal-0.18.6-1/embedded/lib/../lib/libevent.a(evutil.o): In function evutil_unparse_protoname':
evutil.c:(.text+0xf0d): warning: Using 'getprotobynumber' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
collect2: error: ld returned 1 exit status
Error: execution of command failed with code: 1: cc -o "/data2/Projects/crt.cr/bin/hello" "${@}" -static -rdynamic  -lpcre -lgc -lpthread /data2/crystal-0.18.6-1/src/ext/libcrystal.a -levent -lrt -lncursesw  -lgpm -ldl -L/usr/lib -L/usr/local/lib
Makefile:17: recipe for target 'hello' failed

Hi, Brian!
I've just pushed dynamic build version as a trial.
But it will not resolve the problem cause I guess you are in os x.
If so, could you try osx branch?

I'm on Arch Linux actually but that seems to fix it thanks !


Where to ask?

Is GitHub the best place to ask "How-To" design questions?

https://stackoverflow.com/questions/tagged/clickhouse is probably better

Follow the instructions :)

Make sure to check documentation https://clickhouse.yandex/docs/en/ first. If the question is concise and probably has a short answer, asking it in Telegram chat https://telegram.me/clickhouse_en is probably the fastest way to find the answer. For more complicated questions, consider asking them on StackOverflow with "clickhouse" tag https://stackoverflow.com/questions/tagged/clickhouse

If you still prefer GitHub issues, remove all this text and ask your question here.

Generally GitHub is mostly for ClickHouse development related discussions / issues / bug reports / feature requests and similar.

Generally GitHub is mostly for ClickHouse development related discussions / issues / bug reports / feature requests and similar.

Thanks for your reply. In your opinion, design question is "development related discussions" and should be asked here or SO? Since SO is not exactly suitable for design discussions, such a question would be closed as "too broad" definition

Personally I would prefer to answer the ClickHouse question, not a question about where to ask questions ;)
If you think that github suits better for your question - put it here. I can't know what the question is :)

Personally I would prefer to answer the ClickHouse question, not a question about where to ask questions ;)

Here you go :)
https://github.com/yandex/ClickHouse/issues/5662


globalDependencies doesn't revaluate on unset environment variable

What version of Turborepo are you using?
1.2.5
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Linux
Describe the Bug
Whenever adding a globalDependencies relying on $NODE_ENV, the cache is only revaluated if $NODE_ENV is set to a non-empty value. If empty or unset, it will be ignored and turbo will run as if the last value had been provided.
Expected Behavior
I would like that whenever $NODE_ENV was previously provided as production and then a second time, not provided at all, the cache would be revaluated. Since production  != undefined
To Reproduce
turbo.json
{
  "$schema": "https://turborepo.org/schema.json",
  "globalDependencies": ["$NODE_ENV"],
  "pipeline": {
    "lint": {
      "outputs": []
    }
  }
}

package.json
{
  "name": "@scope/a",
  "scripts": {
    "lint": "echo NODE_ENV:$NODE_ENV",
  }
}

running with NODE_ENV=production (first time)
$ NODE_ENV=production npx turbo run lint --scope=@scope/a
• Packages in scope: @scope/a
• Running lint in 1 packages
@scope/a:lint: cache miss, executing 03b196778cd445c2
@scope/a:lint:
@scope/a:lint: > lint
@scope/a:lint: > echo NODE_ENV:$NODE_ENV
@scope/a:lint:
@scope/a:lint: NODE_ENV:production

 Tasks:    1 successful, 1 total
 Cached:    0 cached, 1 total
   Time:    319ms

running a second time without declaring NODE_ENV (should revaluate cache)
$ npx turbo run lint --scope=@scope/a
• Packages in scope: @scope/a
• Running lint in 1 packages
@scope/a:lint: cache hit, replaying output 03b196778cd445c2
@scope/a:lint:
@scope/a:lint: > lint
@scope/a:lint: > echo NODE_ENV:$NODE_ENV
@scope/a:lint:
@scope/a:lint: NODE_ENV:production <<<<<<<<<<<<<<<<<<<<<

 Tasks:    1 successful, 1 total
Cached:    1 cached, 1 total
  Time:    107ms >>> FULL TURBO

This should definitely work, I've added a test case in https://github.com/vercel/turbo/pull/6238 to make sure


Do you support screen clean?

Can you also provide the Screen Clean mode similar to the OneSwitch's？

Can you also provide the Screen Clean mode similar to the OneSwitch's？

Sorry, I don't have plan to provide Screen Clean mode so far.


add help/app tour

An IdeaScale user and some TestFlight feedback have requested a help section and/or app tour feature. I think a first run app tour would be sufficient with an option for the user to access that app tour again from the Info tab.

I've started adding callouts for features that need explanations and will do more in the future as need and opportunity dictate.


weights for full yolo not available on link

Weights for full yolo are not available on link available in readme. Where can I find the weights for full yolo?

I also got this problem. https://1drv.ms/f/s!ApLdDEW3ut5feoZAEUwmSMYdPlY is invalid.

https://github.com/rodrigo2019/keras_yolo2/releases


Functional testing

Coverage remained the same at 100.0% when pulling e505b01d48986e5908bd3fd1921401f185612be9 on functional-testing into 8ec28b28ddad1c228a91592a7c937963a28fdad5 on master.


Support externally created tensors

Following #265, I was wondering if this API addition is something consider accepting into upstream.
It resulted in massive performance wins for us when manipulating huge tensors that are externally allocated by TensorRT.
Are there any changes that should be added?

Merged, thanks for the PR!


Release Google.Cloud.EssentialContacts.V1 version 1.1.0

Changes in this release:

Commit ac367e2: feat: Regenerate all APIs to support self-signed JWTs

Created release for Google.Cloud.EssentialContacts.V1-1.1.0


[CC] Groundwork for semver

Our project does not (yet) have a way to manage Semantic Versioning (semver).
It is time to lay the groundwork for automatic sem versioning.
Please keep in my that the first version in our project is always v0.1.0-alpha+{CI_BUILD_NUM}
UserStory
As a contributor,
I want to be able to make sure I always specify the semantic version of my PR changes,
so that the CICD system can automatically run tests against past releases,
and determine the correct semver of my PR,
and push a new git tag for the semver when my PR is merged to master or a release branch.
Behaviours
Scenario 1: Check the existence of PR semver on non-master
Given a branch that is not master branch,
When a PR is created from this branch without any +semver:xxx in its title or description,
Then Github Action should fail
Scenario 2: Print semver on a new commit
Given a PR with title or description containing +semver:major or +semver:minor or +semver:patch or +semver:pre or +semver:build,
and there is currently NO tag,
and the latest CI build number is 100,
When a new commit is pushed,
Then Github Action should print the correct version of the PR which means:
- +semver:major should print v1.0.0-alpha+100
- +semver:minor should print v0.2.0-alpha+100
- +semver:patch should print v0.1.1 (The semver:patch PR should be targeted against a release branch, not master branch)
- +semver:pre should start with -alpha then move to -beta and finally -rc, which means in this case, it should print v0.1.0-beta+100
- +semver:build should use the CI Build Number as its value which means in this case, it should print v0.1.0-alpha+100
Scenario 3: Check whether semver is removed from the PR title and description
Given a PR with title or description containing +semver:major or +semver:minor or +semver:patch or +semver:pre or +semver:build,
When the +semver:xxx is removed from both its title and description,
Then Github Action should fail.
Scenario 4: Create a release branch when a PR with major or minor is merged
Given a PR with title or description containing +semver:major or +semver:minor,
When the PR is merged to master branch,
Then Github Action should tag the master commit with the correct version,
and a new branch prefixed with release/vX.Y is created from the merged commit, where X and Y are the major and minor version of the semver number respectively.
Scenario 5: Prevent a patch PR to master
Given a PR with title or description containing  +semver:patch,
and the PR is targeted to the master branch,
When the Github Action runs
Then Github Action should fail.
Scenario 6: Check PR  patch version is compatible with the release or not
Given a PR with title or description containing  +semver:patch,
and the PR is targeted to branch release/vX.Y where X and Y are the major and minor version of the semver number respectively,
When the Github Action runs
Then Github Action should pass.
Scenario 7: Create a tag for release when merging a PR
Given a PR with title or description containing  +semver:patch,
and the PR is targeted to branch release/vX.Y where X and Y are the major and minor version of the semver number respectively,
When the PR is merged
Then Github Action should tag the merged commit with the correct version.
Scenario 8: Create a tag for a pre-release or build when merging a PR to master
Given a PR with title or description containing  +semver:pre or +semver:build,
and the PR is targeted to master branch,
When the PR is merged
Then Github Action should tag the merged commit with the correct version,
and the previous tag of the same precedence should be deleted.
Scenario 9: Check if a beta tag should be promoted to an rc tag or fail if an rc tag already exists
Given a PR with title or description containing  +semver:pre,
and the PR is targeted to master branch,
and the current CI Build Number is 100,
and the latest tag is either
- v0.1.0-rc+99
- or v0.1.0-beta+99
When the Github Action runs
Then Github Action should
- fail in case of v0.1.0-rc+99
- print version number v0.1.0-rc+100 in case of v0.1.0-beta+99

Propose solutions
Scenario 1: Check the existence of PR semver on non-master
if PR is 'opened' from a non-master branch
then use 'grep' to check whether regex is contained in github.event.pull_request.body or title
Scenario 5: Prevent a patch PR to master
When a PR is opened  to master, get the semver and compare with master's semver
If only the patch version is change then exit 1


Relocate without shrinkning

Hi,
I want to relocate AWS SDK for https://github.com/burrunan/gradle-s3-build-cache, and it looks like proguard is either "relocate+obfuscate" or "just keep old package names".
What I want is to just relocate packages under com.github.burrunan.s3cache.relocated package, and I don't want all the classes to be renamed as a.class so the stacktraces are understandable.
Do you know if there's a proguard configuration for that?
It looks like -keep would keep the original names (which would defeat the purpose of shading as it would conflict with other dependencies), however, -flattenpackagehierarchy and -repackageclasses obfuscate the names.

You might want to try -dontshrink. @hvisser has had some success with that recently.

Actually looks like -dontobfuscate might be a better bet according to this SO question.

-dontobfuscate keeps the original package names, so it does not really help :-/
software/amazon/awssdk/...
org/apache/http/..

Turns out it just landed in R8 main: https://r8.googlesource.com/r8/+/81ae5c8b3ef02120cea8ac15bfc0f71aac66f72f
I'll give it a shot this week end.

Turns out this is working since version 0.6 that uses R8 3.4 sorry I forgot to update this issue. To use it use -dontobfuscate together with -repackageclasses
-dontobfuscate
-repackageclasses com.example.relocated


Improve performance through bundling

With the recent VSCode update, it is now possible to use bundling tools to reduce the size of extensions. For performance reasons, Kotlin for FRC should be updated to use bundling.
Website detailing bundling: https://code.visualstudio.com/api/working-with-extensions/bundling-extension

[x] Install Webpack
[x] Install ts-loader
[x] Configure Webpack
[x] Add webpack to package.json
[x] Configure package.json main property
[x] Update .vscodeignore
[x] Merge into master

Addressed by 60b33cb


Replaced RotatingFileHandler with ConcurrentRotatingFileHandler to support multi-worker WSGI HTTP Server

When running the application with multi-worker WSGI HTTP Server such Gunicorn, the included RotatingFileHandler can't handle file rotation properly. Thus the introduction of concurrent-log-handler.
Requirements analysis
The packages has the following requirements. At Pinterest we use Gunicorn, so the analysis is based on Gunicorn.

Concurrent Log Handler (CLH) is designed to allow multiple processes to write to the same logfile in a concurrent manner. It is important that each process involved MUST follow these requirements:

You can't serialize a handler instance and reuse it in another process. This means you cannot, for example, pass a CLH handler instance from parent process to child process using the multiprocessing package in spawn mode (or similar techniques that use serialized objects). Each child process must initialize its own CLH instance.

[x] Gunicorn uses os.fork() so this is doesn't apply. Reference. Also deploy_board doesn't have such behavior.

When using the multiprocessing module in "spawn" (non-fork) mode, each child process must create its OWN instance of the handler (ConcurrentRotatingFileHandler). The child target function should call code that initializes a new CLH instance.

This requirement does not apply to threads within a given process. Different threads within a process can use the same CLH instance. Thread locking is handled automatically.
This also does not apply to fork() based child processes. Child processes of a fork() call should be able to inherit the CLH object instance.
This limitation exists because the CLH object can't be serialized, passed over a network or pipe, and reconstituted at the other end.

[x] Gunicorn uses os.fork() so this is doesn't apply. Reference

It is important that every process or thread writing to a given logfile must all use the same settings, especially related to file rotation. Also do not attempt to mix different handler classes writing to the same file, e.g. do not also use a RotatingFileHandler on the same file.

[x] All log settings are in deploy-board/deploy_board/settings.py  and they only has one configuration per logfile.

Special attention may need to be paid when the log file being written to resides on a network shared drive. Whether the multiprocess advisory lock technique (via portalocker) works on a network share may depend on the details of your configuration.

[x] This doesn't apply to deploy_board.

A separate handler instance is needed for each individual log file. For instance, if your app writes to two different logs you will need to set up two CLH instances per process.

[x] deply_board uses 1 handler per logfile. See details in deploy-board/deploy_board/settings.py.

The following issues describe similar use cases of the concurrent-log-handler package. They further confirm the design goal of this package aligns with the Gunicorn use case.

Additional parameter for alternative lock file directory #49

@Preston-Landers As in this library According to the instructions at "https://github.com/Preston-Landers/concurrent-log-handler#important-requirements", each process must create a separate instance of ConcurrentRotatingFileHandler
But since we use --preload when starting gunicorn, the initialization code here is run before the worker processes are created. That would mean the processes end up sharing this object. would that impact?
https://github.com/Preston-Landers/concurrent-log-handler/issues/44#issuecomment-1015082680

Testing
Changed log file limit to 2KB

Tested as a single stand alone application
Tested running under gunicorn with 8 workers
Checked and ensured log rotation were properly executed. Inode number and creation time are both decreasing when file name sorted ascendingly, because older files are renamed with larger suffix.

(venv_teletraan) $ ls -C -c -gtOi -UT
total 200
13846730 -rw-r--r--  1 staff  -  634 Jul 22 14:58:42 2022 request.log
13846727 -rw-r--r--  1 staff  - 2534 Jul 22 14:58:42 2022 request.log.1
13846726 -rw-r--r--  1 staff  - 2559 Jul 22 14:58:42 2022 request.log.2
13846725 -rw-r--r--  1 staff  - 2550 Jul 22 14:58:42 2022 request.log.3
13846724 -rw-r--r--  1 staff  - 2514 Jul 22 14:58:42 2022 request.log.4
13846695 -rw-r--r--  1 staff  - 4203 Jul 22 14:58:42 2022 template.log
13846694 -rw-r--r--  1 staff  - 4203 Jul 22 14:58:42 2022 template.log.1
13846693 -rw-r--r--  1 staff  - 4223 Jul 22 14:58:42 2022 template.log.2
13846692 -rw-r--r--  1 staff  - 4218 Jul 22 14:58:42 2022 template.log.3
13846691 -rw-r--r--  1 staff  - 4217 Jul 22 14:58:42 2022 template.log.4
13846625 -rw-r--r--  1 staff  - 2098 Jul 22 14:58:39 2022 service.log
13846563 -rw-r--r--  1 staff  - 2077 Jul 22 14:58:36 2022 service.log.1
13842307 -rw-r--r--  1 staff  - 2101 Jul 22 14:02:58 2022 service.log.2
13842196 -rw-r--r--  1 staff  - 2678 Jul 22 14:02:38 2022 service.log.3
13828395 -rw-r--r--  1 staff  - 3214 Jul 22 11:16:21 2022 service.log.4
13828197 -rw-r--r--  1 staff  - 2555 Jul 22 11:15:21 2022 server.log
13828071 -rw-r--r--  1 staff  - 2552 Jul 22 11:13:21 2022 server.log.1
13827973 -rw-r--r--  1 staff  - 2555 Jul 22 11:11:21 2022 server.log.2
13826408 -rw-r--r--  1 staff  - 2553 Jul 22 11:09:21 2022 server.log.3
13826143 -rw-r--r--  1 staff  - 2554 Jul 22 11:07:22 2022 server.log.4

@tylerwowen - I don't have any experience with gunicorn, but it should likely be fine to preload the concurrent-log-handler object then fork worker processes. The remarks which prompted that comment were lacking clarity, but it was mainly meant for users of multiprocessing where it might serialize or pickle objects.
If you observe that it's causing a problem, you might try to defer the logging setup. For instance, Flask has a before_first_request decorator which could be useful for that. But I suspect the preload-then-fork shouldn't be a problem.


question: How does this library compare versus the official @capacitor/push-notifications plugin?

I am confused as to what the benefit is for using this library over the official @capacitor/push-notifications plugin.
I tried to look for it in the docs/issues, and the only thing I found about it was this comment (https://github.com/capacitor-community/fcm/issues/11#issuecomment-515796247) of you (@stewones) saying

Capacitor will never send you fcm tokens, that’s why I created this plugin.

But, actually, the Capacitor plugin does support retrieving the token (maybe it wasn't at the time of your writing, but it is now): https://capacitorjs.com/docs/apis/push-notifications#token
So that leaves me wondering: what is the benefit of this plugin?

The official does not support subscribing to topics (yet).

@capacitor/push-notifications uses FCM on Android and APNS on iOS
@capacitor-community/fcm uses FCM on both Android and iOS
The token you linked is going to be an APNS token on iOS, unless you follow this guide to integrate FCM into your iOS app, that would make it possible to get a FCM token on iOS without needing @capacitor-community/fcm.
@capacitor-community/fcm has some methods that @capacitor/push-notifications doesn't have, like the mentioned about subscribing to topics.

Thanks for explaining @jcesarmobile


Incompatible with Android Studio 3.4.1

Hello there! Small issue here. Unable to build and run the project as it is.
Nothing else to add here. It is probably low priority but still an issue.

Thanks for the bug report. I'll take a look.


Add PUID and PGID to palworld docker image.

This is pretty simple. It checks that the PUID and PGID aren't 0 (root) and then just sets the steam user and group to them. The default is 1000:1000 to match the current behavior.
Switched to bash for the [[ ]] style if.
Should resolve https://github.com/thijsvanloef/palworld-server-docker/issues/15.

Oops, forgot the readme and example compose file!

Thank you @fryfrog very helpful :)

I would like to revisit this, as this means that the main process of the container can only be started as root, to be able to usermod and groupmod.
The main question seems to be, which one of the following is better:

Change file permissions to allow the ID of the user running the process in the container to write to the volume
Change the user ID to match the file permissions on the volume

If backup systems are the reason for this change, I would question these backup solutions, as an external system, that just copies files, can (in most cases) not be sure that those files are not currently being accessed or written to.
Please let me know, what your opinion on this is, maybe I'm missing something.

I think you are saying it'd be better to run the whole container as one user via Docker's own --user uid:gid right? I would totally agree w/ that, but it'd require quite a bit of change and of course you wouldn't be able to do anything that needs to be done as root.
I would make a new github issue and discuss it, maybe put up a pull request that does it?
I'm a big fan of not running containers as root, but they're pretty rare.

And to be clear, before this change it was hard coded doing things as either root or uid:gid 1000:1000 which was the steam user inside the container. This change did not make it run as root (in fact it does less as root).

My proposal wouldn't even work with --user uid:gid as the user steam has a fixed uid and gid in the base image. Changing this would only be possible during build time.

Sure, that is what I mean right? Making this a non-root docker image would require a pretty big re-jiggering of the image. It should be possible, it just means that any chown or chmod needs to be done by the user outside the image. It really only does the two things, runs steam command to get the game and then runs steam command to run the game. Both of which are not literally hard coded to steam user, but obviously if you re-work everything to just run as the user it runs as (and probably error out if you accidentally do it as root.
All possible, just... makes setting up the image a little harder and more technical for people.

That's why I dropped the whole change-uid stuff again. For me UID 1000 is perfectly fine and I have no need to change it (because I change the file permissions on the mounted volume). My main goal is to have an Image that contains a USER steam before the ENTRYPOINT that's basically it. This way no process in the running container is spawned by root.

If you set PUID and PGID to 1000, you have literally the same previous behavior. I'm not understanding something about what you want.

From an application perspective, the behaviour is the same. The main difference is this:
The currently provided image
root@palworld-server-866c5db9b5-fvz6q:/home/steam/server# ps aux
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root           1  0.0  0.0   3896  3076 ?        Ss   14:06   0:00 /bin/bash /home/steam/server/init.sh
root         119  0.0  0.0   3896  3052 ?        S    14:08   0:00 /bin/bash ./start.sh
root         187  0.0  0.0   4160  3400 pts/0    Ss   14:08   0:00 bash
root         199  0.0  0.0   6200  3508 ?        S    14:08   0:00 su steam -c ./PalServer.sh -queryport=27015
steam        200  0.0  0.0   2480   512 ?        Ss   14:08   0:00 sh -c ./PalServer.sh -queryport=27015
steam        201  0.0  0.0   2480   516 ?        S    14:08   0:00 /bin/sh ./PalServer.sh -queryport=27015
steam        208 13.6  0.8 5102408 1179044 ?     Sl   14:08   0:14 /palworld/Pal/Binaries/Linux/PalServer-Linux-Test Pal
root         269  0.0  0.0   6756  2856 pts/0    R+   14:10   0:00 ps aux

Mine, with removed usermod and groupmod, switched to USER steam during build time
steam@palworld-server-58bc74cf78-6jfp4:~/server$ ps aux
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
steam          1  0.0  0.0   3896  2904 ?        Ss   Jan24   0:00 /bin/bash /home/steam/server/init.sh
steam         99  0.0  0.0   3896  2940 ?        S    Jan24   0:00 /bin/bash ./start.sh
steam        170  0.0  0.0   2480   584 ?        S    Jan24   0:00 /bin/sh ./PalServer.sh -queryport=27015
steam        177 28.9  2.5 8969332 3301520 ?     Sl   Jan24 326:33 /palworld/Pal/Binaries/Linux/PalServer-Linux-Test Pal
steam        627  0.0  0.0   4160  3448 pts/0    Ss   14:07   0:00 bash
steam        634  0.0  0.0   6756  3016 pts/0    R+   14:07   0:00 ps aux

In the currently published image, PID 1 and immediate children are run as root. This is what I am addressing and changing in my fork, to not have any processes in the container run as root.

Ah, I got ya! That's what you'd get from a proper --user uid:gid designed image too. You've just hard coded it.

Exactly, but with --user uid:gid the already existing files in the image are not writable, so might not be applicable in this case.

Yeah, exactly! A proper --user uid:gid docker image, the admin is the one that has to get ownership and permissions setup properly. Its really one of the biggest reasons a lot of containers run as root and then drop down using the PUID and PGID for the app. It lets them make sure that stuff is setup properly.
I bet you could make an image that works in both ways by simply checking if the uid/gid is 0 at startup. If it isn't, just don't run any commands that need to run as root and you're set.

I'm sure we could. I personally don't yet understand the need to change from 1000:1000 in the first place. The permissions only become an issue when sharing a filesytem between host processes and the container. I would always prefer volumes over bind mounts. With volumes, this problem does not exist, or is easily solvable by changing the volumes file permissions.
I think I will maintain my fork for myself for the time being, until this is something that finds it's way back here 😃
Thanks @fryfrog for the discussion, I appreciate your effort!

I personally don't yet understand the need to change from 1000:1000 in the first place.

Really? This one is dead easy to explain. My personal user has the uid:gid 1000:1000 on all my hosts because it was the first one to be created. Why should anyone have to architect their system uid/gids around one docker image that hard coded it to 1000:1000?


Update README.md

:wave: Hope you don't mind some edits ;-)

I do not mind. In fact - adding these changes was on my to-do list anyway. 😉
Thanks for the PR!


[CT-3515] [Bug] Source freshness: loaded_at_field set to null at table level doesn't overwrite value set at source level

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
While defining source freshness we use 2 properties: freshness and loaded_at_field.
Value resolution is different (from hierarchy perspective) for these 2 properties:
When freshness is set to None at table level (using freshness:  or freshness: null) it overwrites freshness set at source level, but loaded_at_field set to None at table level doesn't overwrite value set at source level.
Expected Behavior
loaded_at_field set to None at table level overwrites value set at source level
Steps To Reproduce
version: 2
sources:
  - name: source_name
    database: db_name
    schema: schema_name
    freshness:
      warn_after:
        count: 1
        period: day
      error_after:
        count: 4
        period: day
    loaded_at_field: loaded_at
    tables:
      - name: loaded_at_is_overwritten
        loaded_at_field: xxx
      - name: loaded_at_is_NOT_overwritten
        loaded_at_field: null
      - name: loaded_at_is_NOT_overwritten2
        loaded_at_field:
      - name: loaded_at_is_NOT_overwritten3
        loaded_at_field: ~
      - name: freshness_disabled_OK
        freshness: null

Relevant log output
No response
Environment
- OS: Windows/Linux
- Python: 3.11
- dbt-core: 1.7.4
- dbt-snowflake: 1.7.1

Which database adapter are you using with dbt?
snowflake
Additional Context
No response

Here is DBT project (using sqlite) which shown the error:
yaml_null_error.zip
Steps to reproduce:

unpack
pip install -r requirements.txt
dbt seed
dbt source freshness

Sources yaml (present in the project):
version: 2
sources:
  - name: sources_db
    database: test
    schema: main
    freshness:
      warn_after:
        count: 1
        period: day
      error_after:
        count: 4
        period: day
    loaded_at_field: absent
    tables:
      - name: freshness_fails
        identifier: example
        loaded_at_field: null
        description: |
          loaded_at_field is set to null and thus DBT should use warehouse metadata (at least try)
          Notice error message:
          16:07:56    Runtime Error in source freshness_fails (models\sources.yml)
            Database Error
              no such column: absent
      - name: freshness_skipped
        identifier: example
        freshness: null

Thanks for reaching out @kokorin !
The crux is that it's tricky to within the dbt implementation details to determine the difference between an explicit null / none and an implicit one. Our current implementation treats them both as the same thing, and I don't think we're inclined to change it at this point.
Either way, it doesn't look like dbt is behaving erroneously here, so I'm going to re-categorize this as a feature request.
Have you tried either of the following instead?
Option 1
Two sources. One for freshness from metadata and the other based off column names.
  # source tables with source freshness from metadata
  - name: sources_with_metadata_based_freshness
    database: db_name
    schema: schema_name
    freshness:
      warn_after:
        count: 1
        period: day
      error_after:
        count: 4
        period: day
    tables:
      - name: table_1
      - name: table_2

  # source tables with source freshness based off column names
  - name: sources_with_column_based_freshness
    database: db_name
    schema: schema_name
    freshness:
      warn_after:
        count: 1
        period: day
      error_after:
        count: 4
        period: day
    loaded_at_field: loaded_at  # default at the source level
    tables:
      - name: table_3
      - name: table_4
      - name: table_5
        loaded_at_field: xxx  # override of source-level default

Option 2
One source.  loaded_at_field is defined under each table name instead of having a default at the source level.
  - name: sources_with_metadata_freshness
    database: db_name
    schema: schema_name
    freshness:
      warn_after:
        count: 1
        period: day
      error_after:
        count: 4
        period: day

    # no source-level default for loaded_at_field

    tables:

      # source tables with source freshness from metadata
      - name: table_1
      - name: table_2

      # source tables with standardized loaded_at_field
      - name: table_3
        loaded_at_field: loaded_at
      - name: table_4
        loaded_at_field: loaded_at

      # other source tables with custom loaded_at_field
      - name: table_5
        loaded_at_field: xxx

@dbeatty10 thank you for the reply and for suggestions. I thought about the same options.

Either way, it doesn't look like dbt is behaving erroneously here, so I'm going to re-categorize this as a feature request.

Sorry, but I can't agree. I still consider this as bug because behavior is different for freshness and loaded_at_field properties.
Freshness set to explicit null at table level overwrites freshness at source level, while loaded_at_field does not.
The problem is that those 2 properties are often used together and should behave similar, otherwise it's not clear for end users.
I can work on pull request if you consider it possible.

... behavior is different for freshness and loaded_at_field properties.
Freshness set to explicit null at table level overwrites freshness at source level, while loaded_at_field does not.

Thanks for pointing this out @kokorin 👍 Agreed that it's less clear for end users if freshness and loaded_at_field don't behave similarly to each other.
I'm going to label this as "refinement" for us to 1) reproduce that they are behaving differently and 2) determine how they should behave going forward.

@dbeatty10 please notice that I have attached zip archive to this ticket with minimal project reproducing the issue

I can work on pull request if you consider it possible.

That would be awesome if you work on a pull request for this @kokorin 🏆
@graciegoheen and I discussed briefly offline, and we're planning to keep this labeled as a feature request and not backport it to dbt-core 1.7.
Acceptance criteria

To align with freshness, when loaded_at_field is set with an explicit null at the table level, it should overwrite loaded_at_field which is set at the source level
When loaded_at_field is null, then it uses metadata-based source freshness checks


Instructions for Magento 2.3

This project looks interesting for us, do you have an instructions how to integrate it with Magento 2.3? I mean how to install it globally for whole website (not for a single module)?

Hi, As this is a headless architecture we can connect magneto API directly


Few tactic implementations

I have implemented Lean 4 equivalents of by_contradiction guard_expr_eq guard_target guard_hyp introv

Also it would be nice to have some tests for the tactics.  In mathlib we have test directory for tests of tactics.  We don't have that in mathlib4 yet, but in the meantime we could add examples in the same file as the tactic.


Gandi DNS: Unexport Endpoint variable

Prior to 47219ad, the Gandi DNS tests ran in a separate package from the provider itself, called gandi_test. Following that commit they were changed to run in the provider's package.
The Endpoint variable was only exported in order to be usable from gandi_test. Since the tests now run in gandi, it should be unexported and it's comment changed, since the comment is now inaccurate.

Tests are passing locally, so not sure what's up with CI.

CI says remote: Daily bandwidth rate limit exceeded for IP <IP_ADDRESS>.. I guess that could be it.


PHP-JSON7 missing in umpleonline docker image.

Specify a Brief Description
Brief, one or two sentences explaining the problem.
When running the umple/umpleonline docker image, I get the following error in the container logs:
PHP message: PHP Fatal error:  Uncaught Error: Call to undefined function json_decode() in /var/www/scripts/tab_control.php:125

Give the minimum Steps to Reproduce

Create container running umple/umpleonline
Select one of the examples in the WUI.
Observe the nginx access logs (docker logs <container name>)

Describe the expected result that didn't happen
The example didn't load.
Actual Result
Just get the loading "spinning wheels" in the WUI.
Resolution
Workaround
Run apk add php7-json inside the container, and restart.
Permanent fix
Add php7-json to Dockerfile

I have added php7-json to umpleonline/Dockerfile-base in PR #1455. I will The base is normally only created during a 'release'. I intend to do a release in the next week, that should clear this up.

This was fixed as of 1.30.1


Github actions

https://github.com/unaio/una/commit/fdf0794856898ec89f5e247b957a6e3cac3a2e5f

https://github.com/unaio/una/commit/c42545e19d6dc08a307539518619c3a03adbe9cd


improve support for boundary, gradient and normal

Some domains already define the boundary function, e.g., the boundary of the unit disk is the unit circle. It would be good to extend this to all domains that can be used in geometry. At the same time, we can define gradients and normal directions when they make sense.
Right now we have
julia> using DomainSets; boundary(UnitCube())
D₄ ∪ D₂ ∪ D₃

D₁ = Point{Float64}(0.0) ∪ Point{Float64}(1.0)
D₂ = (0.0..1.0 (Unit)) × D₁ × (0.0..1.0 (Unit))
D₃ = (0.0..1.0 (Unit)) × (0.0..1.0 (Unit)) × D₁
D₄ = D₁ × (0.0..1.0 (Unit)) × (0.0..1.0 (Unit))

This is not wrong, but it may be better to support hyperfaces, so that the boundary of all polytopes can be a collection of hyperfaces (of the same type).

Closing in favour of #100