Channel Launch

cc @nicko170

[x] Code Review
[ ] Add to website
[x] Create packagist package
[x] Github actions
[x] Style CI
[ ] Scrutinizer
[x] Add badges

Hey @atymic
Any reason why it's still WIP? Gone off the radar perhaps?

I ended up just having too many issues with Expo Notifications and was already collecting the APNs and GCM tokens so just moved to using them instead :-(

I ended up just having too many issues with Expo Notifications and was already collecting the APNs and GCM tokens so just moved to using them instead :-(

That's a bummer. IIRC they reworked the Notifications system though (old one is called LegacyNotitications now). So I'd assume it to be much more robust nowadays.
I'll do some testing myself first if it really works as they promise on their docs.
But I guess you don't have any incentive now to continue maintaining this repo, now so would you be willing to move ownership, @nicko170?

I ended up just having too many issues with Expo Notifications and was already collecting the APNs and GCM tokens so just moved to using them instead :-(

That's a bummer. IIRC they reworked the Notifications system though (old one is called LegacyNotifications now). So I'd assume it to be much more robust nowadays.
I'll do some testing myself first if it really works as they promise on their docs.
But I guess you don't have any incentive now to continue maintaining this repo, now so would you be willing to move ownership, @nicko170?

Yep, I am happy for you to take ownership / collab on it.
I might look back into it at some stage, but part way through a dart / flutter re-write so probably not depending how that goes!

Yep, I am happy for you to take ownership / collab on it.
I might look back into it at some stage, but part way through a dart / flutter re-write so probably not depending how that goes!

A'ight, cool. That sounds like a plan.
I'll try taking a look at Expo Notifications this week.
How'd you like to proceed further with the transition? Any communication medium I can reach you on?
I'm not in a hurry, so take your time and enjoy the sun 🙂
Thanks for the quick replies. 🤘

Hey man @nicko170 👋🏼
Just got time to look at this, sorry. The new notification system works really well.
So I'd definitely want to collab / take ownership if it's still fine for you.
How'd you like to proceed further? Can I reach you somewhere?
Thanks!!

Hey @atymic - looking to start using this in production and this could do with some bug fixes and support for Laravel 11. Would you mind adding me as a maintainer?
(I also look after the AWS SNS, FCM and APNS channels).

Hey @atymic - looking to start using this in production and this could do with some bug fixes and support for Laravel 11. Would you mind adding me as a maintainer?
(I also look after the AWS SNS, FCM and APNS channels).

Hey @dwightwatson
I've tried getting in touch with @atymic many times before, but unfortunately haven't received any replies. We have already created a—in my opinion—very decent implementation in this repository here. It'd be a bummer if you had to carry out this work twice because it already has support for PHP 8.3, Laravel 11, an extensive test suite, good documentation etc.
If you can get in touch with him, I'd be happy to hand over ownership for this piece of code that has been lingering in darkness!

@dwightwatson I've added you as a repo maintainer.
@mabdullahsari If you'd like to work with @dwightwatson to launch the channel you're welcome to. The person who originally created the channel never finished it.

@mabdullahsari your implementation looks good, so if you'd like move it here and release a new major version you can discuss with @dwightwatson

Cool, your implementation looks a lot more fleshed out and would be great to have under this namespace. If you're open to PRing it into this repo and we can continue maintenance here let's do that.

@mabdullahsari If you'd like to work with @dwightwatson to launch the channel you're welcome to. The person who originally created the channel is the one responsible for maintaining it.

Thanks!

Cool, your implementation looks a lot more fleshed out and would be great to have under this namespace. If you're open to PRing it into this repo and we can continue maintenance here let's do that.

Hey 👋
Awesome! I'll make sure to submit a PR as soon as possible.

@atymic could you please also add @mabdullahsari as a repo maintainer as they've graciously PR'd their work in?

Added you @mabdullahsari  :)
Thanks both


Added productBoxLayout config for manufacturer page

Description
Please describe your pull request:

Why is it necessary?
Adds productBoxLayout config to shop configuration
What does it improve?
Makes easy to change product layout of manufacturer pages
Does it have side effects?
Nope

Questions
Answers

BC breaks?
no

Tests pass?
yes

Related tickets?
If this PR fixes an existing Issue ticket, please add its complete issue URL.

How to test?
Please describe how to best verify that this PR is correct.

Thanks @shyim
We decided to close this PR because of time constraints and limited overall benefit to the product. If this change is still important to you, please create a new issue on https://issues.shopware.com so people can up-vote this feature.

Created https://issues.shopware.com/issues/SW-17483

@janbuecker how many upvotes are required to reopen :)

The issue has now 18 upvotes. Are their a interest to reopen this pr?


Statement "for" in Statement translator extended for attribute access.

Hi
I tried to convert some python code and it had statements like this:
for self.lineIndex in xrange(self.lineIndex, len(self.lines))
This threw an exception and the conversion process stopped because self.lineIndex was not supported in the for statement.
So I added this case for a smooth run in the "for" translation code. The output seems to be right I compared a few code segments between the two languages. But I'm new here in this project and may easily have overlooked something or it could be simplified or better modularised.
Additional note:
There were also problems with not included operators "%=" "\\" and "\\=" which are also in my fork but not in this branch I request here to pull into your project. I can create a pull request for these also if you wish. But honestly I did this so the App does not fail. Probably the code conversion is not 100% correct because c# has no direct equivalent for the python "\\" operator as it seems.

Could you please add a unit test for your new code in StatementTranslator.Tests.cs? You could take one of the existing foreach translations, copy it, and adapt it to your new code. Also, are you sure the resulting code is valid? As far as I can tell, C# doesn't permit anything but a variable as the iteration variable: see https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/language-specification/statements#the-foreach-statement for details.
You may need to change the code so that the resulting code looks like
foreach (var _tmp_1 in Enumerable.Range(this.lineIndex, this.lines.Count)) {
   self.lineIndex = _tmp_1;
  /* body of loop*/
}

I'll try to add a unit test.
To be honest, I quickly changed the code so it runs through for my specific python code.
The thing with the iteration variable is correct. But man...10'000 errors shown by VS. There are a lot of things which should be different. My code change was intended to let someone use your software. But I understand one can see things differently. In the coding community, long hours have been spent discussing throwing exceptions or not.

OK, took a deeper dive and fixed it as you wish. Added the intermediate variable and the assignment to the class property. Also a test case is now included. I did not run the test code, just used my own file containing the same python code.
In Git, I added the new changes to the same branch on my fork. I don't know how to restart the checks of AppVeyor and the checks for conflicts with the base branch.
Shall we close this pull request and I start a new one?

I made a small change to your code, otherwise it looks great. Thanks for the PR, and I appreciate your patience with my insistence on unit tests; I find them to be invaluable not only for testing my code as I develop it but also to guarantee no code regressions occur.


Booster and Killmark constant buffers

It seems that the killmark and booster shaders both reference the same constant buffer value, and do different things with it. Using chrome's shader editor, the cb value in question seems to be cb4[0].x, which the booster uses as an intensity value, and the killmark shader uses as the number of killmarks to display.Assuming that the shaders are correct, perhaps a different constant buffer needs to be bound to each (rather than using the same per-object PS data for both booster and killmark draw calls?)

A current work around for the problem of the shared VS/PS ShipData[0] below:
{
    this._super.constructor.call(this);

    this.boosterGain = 1;
    this.boosters = null;
    this.turretSets = [];
    this.killmarks = 0;

    this._turretSetsLocatorInfo = [];
}

EveShip.prototype.GetBatches = function (mode, accumulator)
{
    this._perObjectData.perObjectVSData.Get('Shipdata')[0] = this.killmarks;
    this._perObjectData.perObjectPSData.Get('Shipdata')[0] = this.killmarks;
    this._super.GetBatches.call(this, mode, accumulator);

    if (this.lod > 1) {
        for (var i = 0; i < this.turretSets.length; ++i) {
            this.turretSets[i].GetBatches(mode, accumulator, this._perObjectData);
        }
    }
    else {
        for (var i = 0; i < this.turretSets.length; ++i) {
            if (this.turretSets[i].firingEffect) {
                this.turretSets[i].firingEffect.GetBatches(mode, accumulator, this._perObjectData);
            }
        }
    }
    if (this.boosters)
    {
        accumulator.Render();
        accumulator.Clear();
        this._perObjectData.perObjectVSData.Get('Shipdata')[0] = this.boosterGain;
        this._perObjectData.perObjectPSData.Get('Shipdata')[0] = this.boosterGain;
        this.boosters.GetBatches(mode, accumulator, this._perObjectData);
    }
};```

Thanks to Pathfinder for his hard work finding the issue! :3

Most of the frigates don't seem to work even though I can see they have kill mark data, and I'm not sure why...

I've identified that the PS Ship data is shared more than the above.
Boosters, Killmarks and Dust shaders ( from chaos, not the current quadv5 which doesn't support dust ) all share some of these values.

I am currently looking into this thing. Will fix it with the next update, possibly tomorrow.

Should be fixed. Check sof.html demo file

Thanks Filipp, beautiful :3


Installation

Thanks for the contribution. I will update the section again as soon as the package is available on melpa.
Anyways feel free to add yourself to the contributors in org-tagged.el.


feat(integration/dagster):  dagster connector to emit dagster pipeline

Checklist

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

@shubhamjagtap639, please, can you fix the linter errors?

@shubhamjagtap639, please, can you fix the linter errors?

@treff7es There is no linter errors. CI is getting failed bacause of below error:
ERROR: Cannot install apache-airflow[snowflake]==2.0.2, apache-airflow[snowflake]==2.1.0, apache-airflow[snowflake]==2.1.1, apache-airflow[snowflake]==2.1.2, apache-airflow[snowflake]==2.1.3, apache-airflow[snowflake]==2.1.4, apache-airflow[snowflake]==2.2.5, apache-airflow[snowflake]==2.3.0, apache-airflow[snowflake]==2.3.1, apache-airflow[snowflake]==2.3.2, apache-airflow[snowflake]==2.3.3, apache-airflow[snowflake]==2.3.4, apache-airflow[snowflake]==2.4.0, apache-airflow[snowflake]==2.4.1, apache-airflow[snowflake]==2.4.2, apache-airflow[snowflake]==2.4.3, apache-airflow[snowflake]==2.5.0, apache-airflow[snowflake]==2.5.1, apache-airflow[snowflake]==2.5.2, apache-airflow[snowflake]==2.5.3, apache-airflow[snowflake]==2.6.0, apache-airflow[snowflake]==2.6.1, apache-airflow[snowflake]==2.6.2, apache-airflow[snowflake]==2.6.3 and apache-airflow~=2.2.0 because these package versions have conflicting dependencies.

Hi @treff7es
@shubhamjagtap639 did the investigation on conflicting dependency issues and below are the findings.
The dagster connector depends on:

dagster>=1.3.3 and
dagster depends on typing-extensions>=4.4.0

The conflict dependency issue arises from snowflake connector, where snowflake connector depends on:

acryl-datahub-classify==0.0.8 and
acryl-datahub-classify depends on spacy>=3.4.1,<=3.4.3 and
spacy depends on typing_extensions>=<IP_ADDRESS>,<4.2.0; python_version < "3.8".

so here the issue is the package typing-extensions, dagster needs it to be typing-extensions>=4.4.0 but spacy restricting it to be typing-extensions<4.2.0 for python version < "3.8" and hence our CI is passing for Python3.10 and failing for 3.7.
There are possible two solutions: Either one of we need to apply

Set the max range of spacy in acryl-datahub-classify to <=3.5.0 which is currently <=3.4.3
Lower the version of dagster

On #1: @mayurinehate or @Krushnakant Mardikar can comments. We did install the spacy 3.5.0 in our local environment and ./gradlew :metadata-ingestion:installDev worked fine.
On #2: The dagster lower version 1.1.20 depends on typing-extensions>=4.0.0 which resolves this conflicting dependency issue but the dagster version 1.1.20 is missing critical functions listed below which we are using to extract dagster job and ope metadata.
     Missing functions in dagster 1.1.20:
       1. get_job_snapshots
       2. get_run_stats
       3. get_execution_plan_snapshot
We do need to put more effort into #2 as we are moving to an older package version and need to find out alternate methods to perform the same task

Tested the datahub-classify functionality by changing Spacy version upper limit to 3.5.0, all tests passed. Created a pull request with this change.
https://github.com/acryldata/datahub-classify/pull/19

Tested the datahub-classify functionality by changing Spacy version upper limit to 3.5.0, all tests passed. Created a pull request with this change. acryldata/datahub-classify#19
cc: @mayurinehate @hsheth2

@mardikark-gslab
I can see some failures at CI. Are they acceptable?


Can't add goal, page just refreshes and no new goal added and all input lost

Before submit

After submit

Fixed. On branch fix-bug-bounty1


Cutscene problem on 0.7.3

Describe your bug here.

I downloaded a mod optimized for android (twiddlefinger) but whenever it gets to the part at the cutscene, it will spam the "ERROR ON LOADING" text for the rest of the song instead of loading the cutscene even though the version I downloaded was 0.7.3. I'm relatively new to coding and moding so I'm wondering if anyone can help out.
P.S. I've tried multiple APK's for 0.7.3 and none worked, and whenever I try and download the source code, it never tells me how much time is left and stops downloading when i try to check. Also the number after "SScript:" changes based on how many times it spammed me with the error during the song (Ex. the first time it says it is 1, then the next time is 2, then 3, 4, 5, etc.) Also I want to note that even though I get the error, it let's me continue the song, just without the cutscene.
Crash Log or logcat logs (if existing)
ERROR ON LOADING (/storage/emulated/0/.PsychEngine/mods/twiddlefinger( Luna Accurate Style)/scripts/VideoSpriteHandler.lua): SScript: 7209: Unknown variable: good_ending

Are you modding a build from source or with Lua?
Lua
What is your build target?
Android
Which psych engine version you're on?
0.7.3
Did you edit anything in this build? If so, mention or summarize your changes.
No, I have not

nvm, I just found a better mod

okay


Flow with exact types and subresolvers produces unusable types

Describe the bug
When using the exact types option the intersection way of writing the flow types creates unusable types as any object will fail. This is a flow issue with how exact objects interact with the '&' operator.
It is shown best when using a fragment:
To Reproduce
Steps to reproduce the behavior:

My GraphQL schema:

schema {
  query: Query
}

type Query {
  user(id: ID!): User
}

type Address {
  street: String!,
  city: String!
}

type User {
  id: ID!
  email: String!
  address: Address!
}

My GraphQL operations:

fragment UserFields on User {
  id
  email
  address {
    street
    city
  }
}

My codegen.yml config file:

schema: ./schema.json
documents: ./documents/*.js
generates:
  ./types.flow.js:
    plugins:
      - flow
      - flow-operations
    config:
      skipTypename: true
      useFlowExactObjects: true

Expected behavior
This generates the following typing for the fragment:
export type UserFieldsFragment = ($Pick<User, {| id: *, email: * |}> & {| address: $Pick<Address, {| street: *, city: * |}> |});

Unfortunately this type is unusable because of a bug in flow with intersection and exact typing. If I for example want to make an object with that type I will always get an error.
This flow try hopefully explains the issue. On line 5 I have added an alternative way of defining it in a comment that could work as a solution.

@robvk I managed to reproduce it, but I'm not sure that your solution is the right one.
Using your solution, it seems to work, but it's not really an exact type, try this one.

You are absolutely right.
Should be like this then.

Spread implemented in: https://github.com/dotansimha/graphql-code-generator/pull/2602

Fixed in 1.8.0 🚀


Wiki documentation missing menu on first page.

Could not figure out how to edit for myself....
This page is missing a menu at the top
https://github.com/mccalltd/AttributeRouting/wiki/1.-Getting-Started
This page and all others have the menu at the top
https://github.com/mccalltd/AttributeRouting/wiki/2.-Usage

Those are old wiki pages. Go to the wiki home for the new list.

Thanks. I had navigated from http://www.google.com.au/search?q=attributerouting
The "2. Usage - GitHub" is linked in the sub-links of the google result. Not sure if you can edit that.


New Gem Release

Morning guys
Just wanted to find out when you will be doing your next Gem release?, I am eagerly awaiting #114
Thank you
Dane

Sorry for the delay. v2.0.1 has been released


[Bug]: Error<EMAIL_ADDRESS>Permission denied (publickey,password).

Error Message and Logs

Steps to Reproduce
Hello, I had a problem with starting colify, don't you dare. It didn't want to turn on after the update, the website was not responding, I followed the steps to update using the command What is on the website but it resulted in server problems, how can I fix it
Example Repository URL
No response
Coolify Version
v4.0.0-beta.360
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 22.04
Additional Information
No response

https://github.com/coollabsio/coolify/issues/3664
check this may be useful

This happened to me on a fresh install on a fresh Ubuntu 22 VM, fails during onboarding for this reason.

root had to be added to AllowUsers Docs may want to reflect that as well 🤔


Consider showing all tokens under a separate category in living documentation

Under work in https://github.com/viljamis/vue-design-system/tree/feature/sections

This is a part of #15

Released in Vue Design System 2.0.0


two things

core-graphics was just updated with the stuff I pushed into there, so can remove final bits locally.
and fix for the named field shorthand.

Looks good!


Tokenizer won't open

Clicking on the avatar doesn't open up the Tokenizer window. Nothing happens.
Tried with all modules disabled except for Tokenzier on the 5e system.
Tried with Tokenizer, Tidy5e and Monster blocks in the 5e system.
Tried with all modules disabled except for Tokenizer on the PF2E system.
Tried on both Electrum & Chrome. Gives this error in the console on chrome:
Tokenizer version: 3.2.3
Foundry version: 0.8.8
Operating system: Windows 10

Please can you try version 3.2.4

Now it properly opens. Thanks for the quick fix!


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit 2e0f3f6:
:clock10: Full build: the average full build time is 7 min(s) 23 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 2e0f3f6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Minor link formatting fail in README.md.

"Full py.test documentation [here](http://pytest.org/latest/contents.html."

While you're in the doc, calling it our "public API" feels weird. Everyone should know it's public :p

Also, the spacing in the code samples isn't consistent...


[model] const-expr hoisting turned off with https://github.com/nod-ai/sdxl-scripts/pull/41

const-expr hoisting has been turned off for punet compilation  since the extsi operation in extsi -> conv gets hoisted. This should not happen. It should be easy to get the hoisting infra to know about sign extension operations and avoid this hoisting. This needs to be fixed before it can be turned on.

I reproduced this locally, and it appears that all the hosted extsi ops are on small tensors (resulting in <1mb increased size). This can be reduced with  --iree-opt-const-expr-max-size-increase-threshold while also allowing other hoisting

I think for ops that are charecterized as "dequantization ops" we should never hoist it....


SASL login brutforce mitigation

Hello,
on my private hosting, i'm getting lots of hits on mail port with SASL authentication attempts.
Could you please mention to the main page fail2ban SASL mitigation? Otherwise we would end up with lots of mail-bots. (If this issue is valid with your server).
For example:
https://bobcares.com/blog/fail2ban-postfix-sasl/

It took me some time to make it work. Main issue - with correct regex - due to wrong timezone, date wasn't properly matched, so bans were not applied. Here are my solution:
/etc/fail2ban/jail.d/saslmail.conf
[DEFAULT]
sender = root@localhost
destemail = root@localhost
action = %(action_mwl)s

[saslmail]
enabled  = true
port     = 25
protocol = udp
filter   = saslmail
logpath  = /var/lib/docker/containers/**<container>**/**<container>**-json.log
maxretry = 2
bantime = 3600

[INCLUDES]
before = common.conf

`/etc/fail2ban/filter.d/saslmail.conf`
[Definition]
failregex = ^.*\[<HOST>\]: SASL (?:LOGIN|PLAIN|(?:CRAM|DIGEST)-MD5) authentication failed.*$
            ^.*reject: RCPT from \S+\[<HOST>\]:.*Relay access denied.*$
            ^.*lost connection after .*\[<HOST>\].*$

datepattern =%%b %%d %%H:%%M:%%S

Please update README with security issues.

@saikek Thanks for filing this issue.
Could you please help us to submit a PR to update the README for the project? Because I'm not very familiar with this problem.
Thank you very much.

@saikek Thank you very much for your ground work.
I now have this:
/ # fail2ban-client status saslmail
Status for the jail: saslmail
|- Filter
|  |- Currently failed: 0
|  |- Total failed:     0
|  `- File list:        /logs/simple_mail_forward.log
`- Actions
   |- Currently banned: 0
   |- Total banned:     0
   `- Banned IP list:
/ # fail2ban-regex /logs/simple_mail_forward.log /data/filter.d/saslmail.conf

Running tests
=============

Use   failregex filter file : saslmail, basedir: /data
Use      datepattern : MON Day 24hour:Minute:Second
Use         log file : /logs/simple_mail_forward.log
Use         encoding : UTF-8

Results
=======

Failregex: 12314 total
|-  #) [# of hits] regular expression
|   1) [8110] ^.*\[<HOST>\]: SASL (?:LOGIN|PLAIN|(?:CRAM|DIGEST)-MD5) authentication failed.*$
|   2) [2] ^.*reject: RCPT from \S+\[<HOST>\]:.*Relay access denied.*$
|   3) [4202] ^.*lost connection after .*\[<HOST>\].*$
`-

Ignoreregex: 0 total

Date template hits:
|- [# of hits] date format
|  [33252] MON Day 24hour:Minute:Second
`-

Lines: 33636 lines, 0 ignored, 12314 matched, 21322 missed
[processed in 2.59 sec]

The filter is working, but somehow no bans are applied whatsoever when running the container. Any clues?

Many reasons why:

Docker container timezone and time does not correspond to a system timezone. It can have UTC timezone and host machine can have anything else.
Docker uses it's own IPTABLE rules. So fail2ban IPTABLE rules does not apply easily with docker. fail2ban solution
Docker requests are coming from ip <IP_ADDRESS> - which is not internet IP but rather Docker Gateway. (Which is caused by IP masquerading)

I've ended up stopping service until I would have time to fix it. Better safe then sorry.

It's working for me now!
I've used a docker container with fail2ban ( https://github.com/crazy-max/docker-fail2ban )
compose file:
  fail2ban:
    image: crazymax/fail2ban:latest
    container_name: fail2ban
    network_mode: "host"
    cap_add:
      - NET_ADMIN
      - NET_RAW
    volumes:
      - "${DOCKERDIR}/fail2ban/data:/data"
      - "/var/log:/var/log:ro"
      - "/var/lib/docker/containers/bf114b2df522e48cb486ad1db7cc1dae351c7c8539d64a5e111d6ef4cbfbabfd/bf114b2df522e48cb486ad1db7cc1dae351c7c8539d64a5e111d6ef4cbfbabfd-json.log:/logs/sim$
    env_file:
      - "${DOCKERDIR}/fail2ban/fail2ban.env"
    restart: always

Notice the horrible path of the docker container for simple-mail-forwarder because there is no postfix log. This path is different for every installation. You can easily find the path by running
docker inspect --format="{{.Id}}" "simple-mail-forward" | xargs find /var/lib/docker/containers -name
Where "simple-mail-forward" is the name of your SMF docker container.
saslmail.conf (filter.d)
[Definition]
failregex = ^.*\[<HOST>\]: SASL (?:LOGIN|PLAIN|(?:CRAM|DIGEST)-MD5) authentication failed.*$
            ^.*reject: RCPT from \S+\[<HOST>\]:.*Relay access denied.*$
            ^.*lost connection after .*\[<HOST>\].*$

saslmail.conf (jail.d)
[saslmail]
enabled  = true
findtime = 14400
bantime  = 93600
port     = 25
filter   = saslmail
logpath  = /logs/simple_mail_forward.log

Because the timezone is incorrect in the SMF container I have to account for 2 extra hours for findtime & bantime. This might differ according to your timezone.
Result:
fail2ban-client status saslmail
Status for the jail: saslmail
|- Filter
|  |- Currently failed: 2
|  |- Total failed:     4
|  `- File list:        /logs/simple_mail_forward.log
`- Actions
   |- Currently banned: 5
   |- Total banned:     5
   `- Banned IP list:   <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>

Send to mail log files are finally silent after continuous hammering.

@me1299 - try this line in your jail.d file:
[saslmail]
...
logtimezone = UTC
...

Maybe it would work without docker-compose file.

@me1299 - try this line in your jail.d file:
[saslmail]
...
logtimezone = UTC
...

This should would work without docker-compose file.
Also you can use path for logs:
/var/lib/docker/containers/*/*-json.log

I don't think it would create big overhead even if you are running multiple containers.
Also Also:
Are you sure that all requests are now blocked - I had occasions with "IP already blocked" - which was actually not locking anything

Timezone is now fixed in the latest release, so that isn't an issue anymore. I like your idea of mapping all log files, but I'm not a fan of the overhead it creates.
And yes, I'm 100% sure the requests are blocked.


User must have nickname

People have different and long names sometimes. We want to have possibility to mention anybody in goals/issue description or in comments. To do it right without mistakes in names and without overenginiring it would be better to add uniq nickname for ever person.

will be solved in #134


fix: the bug that the command line Usage prompt is incomplete

The full prompt is "password|bookmark|cookie|history|credit card|download|localStorage|extension"
Signed-off-by: yuxiaojun<EMAIL_ADDRESS>

LGTM! THX


get_team_roles returns champs that are not in match

champion_roles = get_data()
match = cass.get_match(3291043659, region="KR")
roles_winning_team = get_team_roles(match.blue_team, champion_roles)
print(roles_winning_team[Role.middle].id)

This prints 34 which is Anivia.
There is no Anivia in this game... https://matchhistory.na.leagueoflegends.com/en/#match-details/KR/3291043659?tab=overview

@deekay42 Fixed this. You'll have to pull the latest versions of Cassiopeia as well as our champion.gg plugin from github in order for it to work.

I uninstalled the old packages and reinstalled with:
pip install git+https://github.com/meraki-analytics/cassiopeia#egg=cassiopeia
pip install git+https://github.com/meraki-analytics/cassiopeia-plugins#subdirectory=cassiopeia-championgg&egg=cassiopeia_championgg
pip install git+https://github.com/meraki-analytics/role-identification#egg=roleidentification

Now I'm getting this error:
Connected to pydev debugger (build 173.4301.16)
Making call: https://ddragon.leagueoflegends.com/realms/na.json
Making call: https://ddragon.leagueoflegends.com/cdn/8.16.1/data/en_US/championFull.json
Making call: https://cdn.merakianalytics.com/riot/lol/resources/patches.json
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/merakicommons/cache.py", line 15, in wrapper
    return getattr(self, s)
AttributeError: 'Champion' object has no attribute '_lazy__championgg'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Applications/PyCharm CE.app/Contents/helpers/pydev/pydevd.py", line 1668, in <module>
    main()
  File "/Applications/PyCharm CE.app/Contents/helpers/pydev/pydevd.py", line 1662, in main
    globals = debugger.run(setup['file'], None, None, is_module)
  File "/Applications/PyCharm CE.app/Contents/helpers/pydev/pydevd.py", line 1072, in run
    pydev_imports.execfile(file, globals, locals)  # execute the script
  File "/Applications/PyCharm CE.app/Contents/helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
    exec(compile(contents+"\n", file, 'exec'), glob, loc)
  File "/Users/dk/Documents/code/lol/getRoles/getRole.py", line 68, in <module>
    champion_roles = get_data()
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/roleidentification/pull_data.py", line 16, in get_data
    champion.championgg.load()
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/merakicommons/cache.py", line 17, in wrapper
    value = method(self)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/cassiopeia_championgg/__init__.py", line 21, in championgg
    patch = Patch.from_str(patch_name, region=self.region)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/cassiopeia/core/patch.py", line 48, in from_str
    cls.__load__()
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/cassiopeia/core/patch.py", line 84, in __load__
    data = configuration.settings.pipeline.get(PatchListDto, query={})
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/datapipelines/pipelines.py", line 459, in get
    return handler.get(query, context)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/datapipelines/pipelines.py", line 185, in get
    result = self._source.get(self._source_type, deepcopy(query), context)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/datapipelines/sources.py", line 69, in wrapper
    return call(self, query, context=context)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/cassiopeia/datastores/merakianalyticscdn.py", line 40, in get_patch_list
    body = json.decode(body)
AttributeError: module 'json' has no attribute 'decode'

From your terminal run: conda install ujson (pip might work too but use conda if you installed python via anaconda). The normal json package doesn't have a .decode method, but ujson does so installing ujson will fix the error. I'll fix this issue sometime soon, thanks for reporting it.

That worked. Thanks.
Awesome library btw, super useful!


DCOS-13770: Pass patchUpdate=false to Marathon on edit action

This PR adds patchUpdate=false to all service edit requests the UI sends to Marathon. So that Marathon doesn't do patch but proper put update. That hopefully will fix ~it doesn't~ some related issues
Checklist

[x] Did you add a JIRA issue in a commit message or as part of the branch name?
[x] Did you add new unit tests?
[ ] Did you add new integration tests?
[ ] If this is a regression, did you write a test to catch this in the future?

LGTM 💯  ✨

Nice work @nLight! Let's 🚢


[FALSE-POSITIVE] outlook.live.com

Domains or links
outlook.live.com
More Information
How did you discover your web site or domain was listed here?
Not my website, but we observed it pretty quickly.
Have you requested removal from other sources?
Please include all relevant links to your existing removals / whitelistings.
No
Additional context
Add any other context about the problem here.
:exclamation:
We understand being listed on a Phishing Database like this can be frustrating and embarrassing for many web site owners. The first step is to remain calm. The second step is to rest assured one of our maintainers will address your issue as soon as possible. Please make sure you have provided as much information as possible to help speed up the process.
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR to mitchellkrogza/phishing repository, on the falsepositive.list file

https://github.com/mitchellkrogza/phishing/blob/main/falsepositive.list
Please include the same above information to help speed up the whitelisting process.

Already whitelisted. Closing.


Make prayerbook searchable

As per this canny task
https://saintmaker.canny.io/quest-board/p/search-functionality

Add in some default prayers


Xamarin.Forms <IP_ADDRESS> compatibility

This NuGet won't install in .Droid project because of wanting Xamaring.Android.Support.v4 <IP_ADDRESS> - but that version is not compatable with current Xamarin.Forms <IP_ADDRESS> constraint of 23.3.0

Same issue for me. Cannot install the latest version. Not compatible with Xamarin.Forms (Xamarin.Android.Support.v4 23.3.0) if I would update my Android.Support.v4 Xamarin would not work (Xamarin is using <IP_ADDRESS>)

For Forms i've released version <IP_ADDRESS>. The code base is the same as 0.0.7, but with dependency on v4 23.3.0
See Nuget for download: https://www.nuget.org/packages/Plugin.MediaManager/<IP_ADDRESS>


lohit-fonts: fedorahosted.org -> pagure.io

[x] upstream change (fedorahosted.org is closed)
[x] minor version bump
[x] make the font derivations fixed-output (https://github.com/NixOS/nixpkgs/issues/27754)

superseded by #28161


Debug build CI job crashes on stats._unuran threading test

Observed in gh-14962 (unrelated PR). Details from the CI log:
sx...................................................................... [ 99%]
......................[gw0] node down: Not properly terminated
F
replacing crashed worker gw0
........................................................ss...ssssssssss. [ 99%]
.s...........................sssssssssssssssssssssssssssssssssssssssssss [ 99%]
ssssssssssssssssys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'>
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'>

=================================== FAILURES ===================================
_ build/testenv/lib/python3.8/site-packages/scipy/stats/tests/test_sampling.py _
[gw0] linux -- Python 3.8.0 /usr/bin/python3.8-dbg
worker 'gw0' crashed while running 'build/testenv/lib/python3.8/site-packages/scipy/stats/tests/test_sampling.py::test_threading_behaviour'

Likely a bug (threading behavior is something that could indeed cause this segfault), but it's not happening on other PRs. Let's just see if it happens again.
This test came in in commit 402ac3535b8c (main PR that added UNU.RAN, Cc @tirthasheshpatel).

Likely a bug (threading behavior is something that could indeed cause this segfault), but it's not happening on other PRs. Let's just see if it happens again.

I am having a hard time replicating this locally. I fired up 1000 threads but still wasn't able to produce the failure :( I will review the code to check if I can spot something right away.

I fired up 1000 threads but still wasn't able to produce the failure

On a debug build of Python? It could be a build/packaging issue of the interpreter we're using there perhaps. I'd say don't worry too much until it happens again. A code scan would be good, but it's not urgent right now.

On a debug build of Python?

Yes. I used Python3.9-dbg.

This happened once more (log), again on the Python38-dbg job. Output:
..sssssssssssssssssssssssssssssssssssssssss [ 99%]
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'>
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'>

=================================== FAILURES ===================================
_ build/testenv/lib/python3.8/site-packages/scipy/stats/tests/test_sampling.py _
[gw0] linux -- Python 3.8.0 /usr/bin/python3.8-dbg
worker 'gw0' crashed while running 'build/testenv/lib/python3.8/site-packages/scipy/stats/tests/test_sampling.py::test_threading_behaviour'
...
=========================== short test summary info ============================
FAILED scipy/stats/tests/test_sampling.py::test_threading_behaviour
...
= 1 failed, 35655 passed, 2599 skipped, 114 xfailed, 7 xpassed in 662.35s (0:11:02) =

The crash seems to occur very infrequently.

This happened once more (log), again on the Python38-dbg job. Output:
..sssssssssssssssssssssssssssssssssssssssss [ 99%]
ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'>
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'>

=================================== FAILURES ===================================
_ build/testenv/lib/python3.8/site-packages/scipy/stats/tests/test_sampling.py _
[gw0] linux -- Python 3.8.0 /usr/bin/python3.8-dbg
worker 'gw0' crashed while running 'build/testenv/lib/python3.8/site-packages/scipy/stats/tests/test_sampling.py::test_threading_behaviour'
...
=========================== short test summary info ============================
FAILED scipy/stats/tests/test_sampling.py::test_threading_behaviour
...
= 1 failed, 35655 passed, 2599 skipped, 114 xfailed, 7 xpassed in 662.35s (0:11:02) =

The crash seems to occur very infrequently.

That looks bad. I will try to reproduce and find the root cause.

That looks bad. I will try to reproduce and find the root cause.

Thankfully, I was able to reproduce:
import threading
from scipy.stats.sampling import TransformedDensityRejection

def test_threading_behaviour():
    # Test if the API is thread-safe.
    # This verifies if the lock mechanism and the use of `PyErr_Occurred`
    # is correct.
    errors = {"err1": None, "err2": None}

    class Distribution:
        def __init__(self, pdf_msg):
            self.pdf_msg = pdf_msg

        def pdf(self, x):
            if 49.9 < x < 50.0:
                raise ValueError(self.pdf_msg)
            return x

        def dpdf(self, x):
            return 1

    def func1():
        dist = Distribution('foo')
        rng = TransformedDensityRejection(dist, domain=(10, 100),
                                          random_state=12)
        try:
            rng.rvs(100000)
        except ValueError as e:
            errors['err1'] = e.args[0]

    def func2():
        dist = Distribution('bar')
        rng = TransformedDensityRejection(dist, domain=(10, 100),
                                          random_state=2)
        try:
            rng.rvs(100000)
        except ValueError as e:
            errors['err2'] = e.args[0]

    t1 = threading.Thread(target=func1)
    t2 = threading.Thread(target=func2)

    t1.start()
    t2.start()

    t1.join()
    t2.join()

    assert errors['err1'] == 'foo'
    assert errors['err2'] == 'bar'

if __name__ == '__main__':
    for _ in range(1000):
        test_threading_behaviour()

Error:

The error occurred because I initiated an attribute lookup in the finally block in the _rvs_cont method in the base class Method once the Python error variable was set and, hence, the object destroyed:

Notice the self._callback_wrapper above. That isn't allowed after the object is garbage collected. I remember facing this issue once while working on the original PR (#14215). I think I forgot to change this at that time. It can be resolved simply by checking if self._callback_wrapper is not None at the start of the function and using the boolean value elsewhere. I will submit a patch with the changes.

Thankfully, I was able to reproduce:
import threading
from scipy.stats.sampling import TransformedDensityRejection

def test_threading_behaviour():
    # Test if the API is thread-safe.
    # This verifies if the lock mechanism and the use of `PyErr_Occurred`
    # is correct.
    errors = {"err1": None, "err2": None}

    class Distribution:
        def __init__(self, pdf_msg):
            self.pdf_msg = pdf_msg

        def pdf(self, x):
            if 49.9 < x < 50.0:
                raise ValueError(self.pdf_msg)
            return x

        def dpdf(self, x):
            return 1

    def func1():
        dist = Distribution('foo')
        rng = TransformedDensityRejection(dist, domain=(10, 100),
                                          random_state=12)
        try:
            rng.rvs(100000)
        except ValueError as e:
            errors['err1'] = e.args[0]

    def func2():
        dist = Distribution('bar')
        rng = TransformedDensityRejection(dist, domain=(10, 100),
                                          random_state=2)
        try:
            rng.rvs(100000)
        except ValueError as e:
            errors['err2'] = e.args[0]

    t1 = threading.Thread(target=func1)
    t2 = threading.Thread(target=func2)

    t1.start()
    t2.start()

    t1.join()
    t2.join()

    assert errors['err1'] == 'foo'
    assert errors['err2'] == 'bar'

if __name__ == '__main__':
    for _ in range(1000):
        test_threading_behaviour()

Error:

The error occurred because I initiated an attribute lookup in the finally block in the _rvs_cont method in the base class Method once the Python error variable was set and, hence, the object destroyed:

Notice the self._callback_wrapper above. That isn't allowed after the object is garbage collected. I remember facing this issue once while working on the original PR (#14215). I think I forgot to change this at that time. It can be resolved simply by checking if self._callback_wrapper is not None at the start of the function and using the boolean value elsewhere. I will submit a patch with the changes.

Great, nice debugging Tirth!

Great, nice debugging Tirth!

Hi @rgommers,
I noticed that I was still sometimes getting attribute lookup errors. I think this is happening because Cython looks up the class attribute to find the release method of the _lock variable when I call _lock.release(). At least, that's what the generated C code says:

Although the _lock variable is not destroyed, python doesn't allow ANY attribute lookups when a live exception is set. The workaround is to fetch the error before calling _lock.release() and restore the error once the lock has been released:

I tried this and reran my experiment 100,000 times. It doesn't give me an attribute lookup error anymore and I am confident this would resolve the issue.
Sorry for not noticing this before #15331 was merged! I will reopen this issue and submit another PR. At some point, it will be better to rewrite the base class in C.

Hi @rgommers,
I noticed that I was still sometimes getting attribute lookup errors. I think this is happening because Cython looks up the class attribute to find the release method of the _lock variable when I call _lock.release(). At least, that's what the generated C code says:

Although the _lock variable is not destroyed, python doesn't allow ANY attribute lookups when a live exception is set. The workaround is to fetch the error before calling _lock.release() and restore the error once the lock has been released:

I tried this and reran my experiment 100,000 times. It doesn't give me an attribute lookup error anymore and I am confident this would resolve the issue.
Sorry for not noticing this before #15331 was merged! I will reopen this issue and submit another PR. At some point, it will be better to rewrite the base class in C.

Cool, thanks for being thorough!

At some point, it will be better to rewrite the base class in C.

Yeah, when you have to start using the CPython C API anyway, that's a sign that Cython maybe isn't the optimal choice anymore.

Cool, thanks for being thorough!

At some point, it will be better to rewrite the base class in C.

Yeah, when you have to start using the CPython C API anyway, that's a sign that Cython maybe isn't the optimal choice anymore.


[Port] Update open existing dialog icons (#13571)

This PR fixes #13437. This updates the placeholder icons with the icons from UX.
PR in Main: https://github.com/microsoft/azuredatastudio/pull/13571

Pull Request Test Coverage Report for Build 394725055

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 41.267%

Totals

Change from base Build 392661845:
0.01%

Covered Lines:
21858

Relevant Lines:
48612

💛  - Coveralls

Merging as this is approved


First time deployment of prometheus to a external bosh director

I see the following issue
Task 328 | 00:28:09 | Preparing deployment: Preparing deployment (00:00:00)
                L Error: Instance group 'prometheus' does not specify jobs key

Task 328 | 00:28:09 | Error: Instance group 'prometheus' does not specify jobs key

Hi. Have you made any changes to the pipeline? Are you using master (with prometheus-boshrelease v21) or branch (with v22)? Full output could be helpful as well. Thanks

I am using prometheus-v22 branch
Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone
-------- Original message --------
From: Michal Kuratczyk<EMAIL_ADDRESS>Date: 6/4/2018  4:11 PM  (GMT-06:00)
To: pivotal-cf/pcf-prometheus-pipeline<EMAIL_ADDRESS>Cc: manaspatkar21<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [pivotal-cf/pcf-prometheus-pipeline] First time deployment of
prometheus to a external bosh director (#18)
Hi. Have you made any changes to the pipeline? Are you using master (with prometheus-boshrelease v21) or branch (with v22)? Full output could be helpful as well. Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"@context":"http://schema.org","@type":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"https://github.com/pivotal-cf/pcf-prometheus-pipeline/issues/18#issuecomment-394500829","url":"https://github.com/pivotal-cf/pcf-prometheus-pipeline/issues/18#issuecomment-394500829","name":"View Issue"},"description":"View this Issue on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}}
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/pivotal-cf/pcf-prometheus-pipeline","title":"pivotal-cf/pcf-prometheus-pipeline","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/pivotal-cf/pcf-prometheus-pipeline"}},"updates":{"snippets":[{"icon":"PERSON","message":"@mkuratczyk in #18: Hi. Have you made any changes to the pipeline? Are you using master (with prometheus-boshrelease v21) or branch (with v22)? Full output could be helpful as well. Thanks"}],"action":{"name":"View Issue","url":"https://github.com/pivotal-cf/pcf-prometheus-pipeline/issues/18#issuecomment-394500829"}}}
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "37567f93-e2a7-4e2a-ad37-a9160fc62647",
"title": "Re: [pivotal-cf/pcf-prometheus-pipeline] First time deployment of prometheus to a external bosh director (#18)",
"sections": [
{
"text": "",
"activityTitle": "Michal Kuratczyk",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@mkuratczyk",
"facts": [
]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueComment",\n"repositoryFullName": "pivotal-cf/pcf-prometheus-pipeline",\n"issueId": 18,\n"IssueComment": "{{IssueComment.value}}"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueClose",\n"repositoryFullName": "pivotal-cf/pcf-prometheus-pipeline",\n"issueId": 18\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/pivotal-cf/pcf-prometheus-pipeline/issues/18#issuecomment-394500829"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "MuteNotification",\n"threadId": 341919439\n}"
}
],
"themeColor": "26292E"
}


MAINTAINERS: LoRa and LoRaWAN: update maintainer and collaborators

I suggest to promote @JordanYates as the new maintainer for LoRa and LoRaWAN. He has reviewed all recent PRs and driven the discussions around LoRa/LoRaWAN.
Some references:

Discord channel
#55073
#62817
#62086
#60461
#58744
https://github.com/zephyrproject-rtos/loramac-node/pull/13

The previous maintainer @Mani-Sadhasivam is presumably busy with other work and has not been very active in Zephyr recently.
@Mani-Sadhasivam please let us know if I got a wrong impression and if you would like to keep maintainership.
Also adding myself as a collaborator. I have contributed time synchronization services and some bug fixes in
the past and I'm going to work on Class B support in the future.
Some references:

#43315
#43324
#46667
#46473
#51328

+1 from me, but @JordanYates needs to accept :)

Sure. I've already asked him on Discord and I'm sure he will approve here as well.


support for the new akka-http release

Hi,
would you plan to provide support for the new akka-http releases ?
Thanks,

@mazorigal Sure thing. I made https://github.com/Backline/akka-http-metrics/pull/10 and once it passes I'll release 0.4.0.

@mazorigal You should be able to pull 0.4.0 for scala 2.11 now. Let me know if you run into any issues.


Remove parallel streaming

Parallel streams are run on a seperate thread causing AssertionError: must be run on client thread when calling ItemManager.getItemPrice

I confirmed this fixes the crash. Can we get this merged in?


Fix flow types related to fs-extra

Was actually changed in previous PR but not published.

What's up?
On Oct 3, 2018 13:12, "Paul Le Cam"<EMAIL_ADDRESS>wrote:
Was actually changed in previous PR but not published.
You can view, comment on, or merge this pull request online at:
https://github.com/MainframeHQ/erebos/pull/54
Commit Summary

Fix flow types related to fs-extra

File Changes

M CHANGELOG.md
https://github.com/MainframeHQ/erebos/pull/54/files#diff-0 (1)
M packages/api-bzz-node/package.json
https://github.com/MainframeHQ/erebos/pull/54/files#diff-1 (2)
M packages/swarm-browser/package.json
https://github.com/MainframeHQ/erebos/pull/54/files#diff-2 (2)
M yarn.lock
https://github.com/MainframeHQ/erebos/pull/54/files#diff-3 (30)

Patch Links:

https://github.com/MainframeHQ/erebos/pull/54.patch
https://github.com/MainframeHQ/erebos/pull/54.diff

—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/MainframeHQ/erebos/pull/54, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLCbvInltVaNjBxgpa-WnaIi6sM2Jn3ks5uhJuJgaJpZM4XFy3Y
.


I can't open This *.bundle file? Can we do something?

Hi! This file is Unity 2019.4.15f1
And I got this file from Pokemon Unite.
When I try open them I got big problem like image
All file bundles from this game got the same error. Are they encrypted?
Url File: https://drive.google.com/file/d/1-HaEv_JnXLgLxTcmxUZRIMJ6BqfEWQfq/view?usp=sharing

Unite is known for being encrypted. Decrypting it is something I won't add to uabea.

Wait! Wait! Don't close<EMAIL_ADDRESS>Can you support this game for me personally?
Is that okay? I can pay for this. And do you have Discord?


Missing some icons in Automatic theme

[WARN] [XMB] Asset missing: assets\xmb\automatic\png\input_LB.png
[WARN] [XMB] Asset missing: assets\xmb\automatic\png\input_RB.png
[WARN] [XMB] Asset missing: assets\xmb\automatic\png\input_LT.png
[WARN] [XMB] Asset missing: assets\xmb\automatic\png\input_RT.png

Since we're using #262 for this issue comprehensively, I'm going to go ahead and close this issue.


NAT/IP configuration troubleshooting links broken

Problem description
The "Network" and "Settings" links in the NAT/IP configuration section of the Docker Desktop for Windows Logs and troubleshooting page don't go anywhere.
Problem location

I saw a problem on the following URL: NAT/IP configuration

Project version(s) affected

Suggestions for a fix

By the wording those links should be going to a separate page that describes the settings rather then sub-sections of the troubleshooting guide. I don't know where that page is though.

Closing issue as it refers to content that no longer exists.


Fix Codecov badge

Codecov Report

Merging #5 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #5   +/-   ##
=======================================
  Coverage   20.93%   20.93%
=======================================
  Files          18       18
  Lines        1151     1151
=======================================
  Hits          241      241
  Misses        904      904
  Partials        6        6

Continue to review full report at Codecov.

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


No deployment Record

Deploy button triggers the deployment on vercel but it always shows "no deployment" in strapi.
How can I get deployment record/status to show inside strapi?
PS - There is no error in api's or build.

This is because the package is not compatible with all versions of Strapi, if you create a Strapi plugin using the command yarn strapi generate:plugin vercel and copy the code from strapi-plugin-vercel into this freshly created template which is compatible with your version of Strapi, it should work. That's what I did and it works perfectly.
Don't forget to update the services/vercel.js and add the ?teamId=<vercel-team-id> param to work with Teams project and change the API paths from the right ones.
I'll create and maintain an npm package asap.

Hey @Zedashe. Why would you create a new npm package?

Hey @f3l1x, sorry mate I thought you weren't active, I'll suggest a PR then 😄.

Nope. I am alive and active. :D

Hi @Lokeshm24 and @GeorgS. Version 0.0.7 solved personal vs team deployments and also scoped tokens.


Merge 5.0 to main

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

As we effectively publish the results from the branch v5.0.x to:
channel_targets:
- conda-forge main

I would suggest to merge the branch v5.0.x with main and remove it afterwards.


Token renewal fails

hi there,
so using the singinRedirect method works, both authorize redirect and code request work as expected.
However, when the automatic renewal should take place, something weird happens. The code request is being made to https://localhost:3000/?code=...

I'm using Auth0 and the config is at it follows:
export const oidConfig: AuthProviderProps = {
  authority: '....',
  client_id: '...',
  userStore: new WebStorageStateStore({
        store: new InMemoryWebStorage()
      }),
  stateStore: new WebStorageStateStore({
    store: window.sessionStorage
  }),
  staleStateAgeInSeconds: 60,
  extraQueryParams: { audience: '...' },
  redirect_uri: '...'
}

I believe that is something related to the IFrame because if I try to force it when the token expiration event is sent, the frame would time out.

Does your application eventually wrongly redirect from HTTP://localhost:3000 to HTTPS://localhost:3000?

Without any detailed full log of Console with DEBUG level and network tab log, both with Preserve Log we have no chance to see your problem...
If you see the request out with HTTP inside as redirect param and the identity server comes back with HTTPS, the problem must be on the identity server side (configuration?). There is not much we can do unless we send any param wrongly or missing...

Setting HTTPS=true as env variable solved the problem for now.

if you have more information please let us know, for now i close this issues, as we can not do anything here


Question: what are the files cmp_initial_states.txt and cmp_target_states.txt for?

I used constructSTG.fsx on my gene expression data, but I'm unsure how I should make/generate these other files.

SCNS works by looking for a Boolean network that can transition from a set of initial states to a set of target states by making a series of single-gene transitions. These files give the identifiers of the two sets of states.
In the synthetic CMP example, there is a single initial state, and all other states are required to be reachable from it. In the experimental case from our NBT paper, we used cells measured on 'day 1' of our time course experiment as the initial states, and cells measured on the final day as our target states.


Run build commands without declared outputs

It is possible to declare build commands without outputs and the expectation is that those would still run. Currently, that is not the case, since the only condition that makes llbuild run build commands is that there's a client for the output files (either compilation or copying of resources).
This change adds a phony output to any command that has no declared outputs and declares these phony outputs as input for any targets that are asking for the plugin to be applied. This will lead to these commands running unconditionally, fixing the current silent failure to run these.
rdar://100415491

I need to add a test for this.

@swift-ci please test

I wonder whether we should make this change conditional on the tools-version?

I wonder whether we should make this change conditional on the tools-version?

seems like a good idea

Will this allow for swift build --product [SomeLib|SomeExe]?

Will this allow for swift build --product [SomeLib|SomeExe]?

Not sure I understand the question, how is that related to plugins? 🤔

I think what I'll do is make the new behavior 5.11 only but emit a warning on all earlier tools-versions. It is probably never intentional to declare a plugin usage that doesn't actually do anything and it's good to inform people that upgrading will give them the desired behavior.

Rebased, added tests and made the fix conditional on the tools-version. On older tools-version, we emit a warning that should explain what's happening and that it can be resolved by upgrading the tools-version.

@swift-ci please test

@swift-ci please test windows

@swift-ci please test windows


[Coverity CID :187905] Incorrect expression in /arch/arc/core/thread.c

Static code scan issues seen in File: /arch/arc/core/thread.c
Category: Incorrect expression
Function: _new_thread
Component: Architectures
CID: 187905
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

@ruuddw  @nashif  I can't access the details of coverity result.  It needs approval which i applied in Sept. 5th.
But current status is still Pending Approval

@Wayne: Coverity access approved


Conditionally allow dependencies to resolve where specific versions conflict with optional dependency bounds

Description of problem
Some optional dependencies can introduce additional version constraints. E.g., I may introduce a package that requires numpy pinned to version 1.x.x. I would ideally like this not to impact the resolved packages when not using this optional dependency.
Scenario 1: optional dependency upper bound is incompatible with lower bound of dependency
pyproject toml
[project]
name = "uv-test"
version = "0.1.0"
description = "an example showing conflict resolution"
requires-python = ">=3.12.7"
dependencies = [
  "numpy>=2.0.0",
]

[project.optional-dependencies]
mediapipe = [
    "mediapipe>=0.10.20",
]

Sync the dependencies
❯ uv sync
Using CPython 3.12.7
Creating virtual environment at: .venv
  × No solution found when resolving dependencies:
  ╰─▶ Because your project depends on numpy>=2.0.0 and mediapipe==0.10.20 depends on
      numpy<2, we can conclude that mediapipe==0.10.20 and your project are incompatible.
      And because only mediapipe<=0.10.20 is available, we can conclude that
      mediapipe>=0.10.20 and your project are incompatible.
      And because uv-test[mediapipe] depends on mediapipe>=0.10.20 and your project
      requires uv-test[mediapipe], we can conclude that your project's requirements are
      unsatisfiable.

Workaround
[project]
name = "uv-test"
version = "0.1.0"
description = "an example showing conflict resolution"
requires-python = ">=3.12.7"
dependencies = []

[dependency-groups]
numpy = [
  "numpy>=2.0.0",
]

[tool.uv]
default-groups = ["numpy"]
conflicts = [
    [
      { group = "numpy" },
      { extra = "mediapipe" },
    ],
]

[project.optional-dependencies]
mediapipe = [
    "mediapipe>=0.10.20",
]

Ugly workaround
uv sync --extra mediapipe --no-group numpy

Anything I'm missing?

I don't think there's a better way to do this right now than the workaround you have above.

I figured poking through the code :) I think it's a worthwhile feature to support.


Run plugin on the scipy codebase

[ ] check that all doctests from refguide-check are included
[ ] make sure doctesting run passes
[ ] run on scipy CI

Ongoing over at https://github.com/scipy/scipy/pull/19242


Update browser-support section from README.md

The browser-support section is kinda outdated.

--
Things to consider:

Add the Edge browser to the browser support list
Not using exact version numbers where possible as they rapidly get outdated

Cc: @addyosmani.

Very well pointed out. Agree we should update that section and definitely cover Edge too. Thanks @alrra!


Add tests for ClearCommand, EchoCommand and HelpCommand

The original PR build failed for some reason to do with git credentials. I kicked off another one that succeeded but for some reason the PR isn't updating it to show that. Going to go ahead and merge regardless.


It's just a VIRUS, DO NOT INSTALL IT!

It cames from my installation of "nodejs 10.13.0" msi file without any OBIOUS PROMPT!
It RESTART  my comupter without any prompt!
It BROKE my administrator privileges after restart!
And guess what, It's hard to UNINSTALL both from windows or choco!

Duplicate of #371.

@sleep2death thank you for reaching out.  While I can appreciate that you may be frustrated, I would ask that you don't use language like that when raising an issue here, there is simply no need for it.
NOTE: I have removed the offending words from your original post.
Let's start with the basic....
Boxstarter is not a virus.  It provides a mechanism to reliably and repeatably, perform a series of installations on your machine, and we like to think that it does this very well.
Hopefully you will have had a chance to read through the duplicate issue pointed out by @flcdrg as well as the linked issues to the Node JS issues.  Almost all of the issues that came out of decisions that were made to include Boxstarter in the Node JS installer have been addressed.

@gep13 First of all, I love nodejs and its community, but the installation with the "Boxstarter" was such a pain. There are so many Serious safty complains and issues about the "boxstarter". I just lost my 15 minutes of the work because of the "restart".
Sorry for the offending words I posted, but I will keep telling people stay away from this project before these issues are fixed.

Boxstarter is just a tool. It's not perfect but it does what it does pretty well. The real issue here in my opinion was the Node installer trying to use Boxstarter in an unconventional way, and possibly with not enough testing before it was released publicly.
Don't blame Boxstarter for that.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Aspirin Shi<EMAIL_ADDRESS>Sent: Thursday, May 2, 2019 6:00 pm
To: chocolatey/boxstarter
Cc: David Gardiner; Mention
Subject: Re: [chocolatey/boxstarter] It's just a VIRUS, DO NOT INSTALL IT! (#397)
@gep13https://github.com/gep13 First of all, I love nodejs and its community, but the installation with the "Boxstarter" was such a pain. There are so many Serious safty complains and issues about the "boxstarter". I just lost my 15 minutes of the work because of the "restart".
Sorry for the offending words I posted, but I will keep telling people stay away from this project before these issues are fixed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/chocolatey/boxstarter/issues/397#issuecomment-488590543, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAC5523FUCAIA2CJLU3P2Y3PTKRC7ANCNFSM4HJ3IKKA.

@sleep2death said...
but I will keep telling people stay away from this project before these issues are fixed.

Before doing that, I would encourage you to try Boxstarter out in isolation first.  As @flcdrg points out, a lot of the issues that you are referring to came from the "way" that Boxstarter was being used in this context, and the small amount of testing that was done prior to it shipping.
I don't know if you saw them, but I created a couple of videos that show the entire installation process of Node JS, using Boxstarter, and it does work:
https://youtu.be/gwFpXXIJTvs
https://youtu.be/OgJBFSfsRP0
However, there are lots of edge cases, and things that can happen, that result in some of the things that you mention in your first post.

I agree with @gep13 and @flcdrg. Boxstarter is awesome. It's used extensively within our organization and combines it with an internal chocolatey feed, it excels at what it's designed for.  I can vouch for BoxStarter on any given day.


WIP: chore(CI): add pipeline to test go CI logic.

Why do we need it

To gain quality through reliable feedback

What changed

Added CI pipeline to test the backend logic

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ce147c9). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #17   +/-   ##
=========================================
  Coverage          ?   39.21%
=========================================
  Files             ?        1
  Lines             ?      102
  Branches          ?        0
=========================================
  Hits              ?       40
  Misses            ?       60
  Partials          ?        2

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Request for External] codeunit 6620 "Copy Document Mgt."

hi,
please set the following procedures to global:
    local procedure CopySalesDocSalesLineArchive(..)

    local procedure CopyPurchDocPurchLineArchive(..)

thanks!

Was fixed in version 22.


Proposal: Supplementing Implicit Types

In a type expression, I would like to be able to extend the implicitly known type of a value with specific type information.
The purpose is to get the most from the implicit type information and suplement it when some type information is missing.
Also, this will pull typescript even closer to ES6 by allowing common ES6 patterns like argument destructuring which results in the any type (where the type cannot currently be specified).
Syntax
// Like normal type information
const { req, opt = '', def = 'DEFAULT' }: { req: string, opt?: string, def?: string } = values;

// But 'extends' implicit typing
const { req, opt = '', def = 'DEFAULT' }: extends { req: string } = values;

The extends keyword would only modify the type information for the part of the type expression that was specified.
Useful Cases
Argument Destructuring with Type Information
Refer to: https://github.com/Microsoft/TypeScript/issues/7576#issuecomment-198443953
And my comment there: https://github.com/Microsoft/TypeScript/issues/7576#issuecomment-340190459
Full Typing (Absolutely no advantage from implicit type information)
export const Fun = ({ req, opt = '', def = 'DEFAULT' }: { req: string, opt?: string, def?: string }) => {
    // ...
};

Current Best Solution
This uses Pure Implicit Typing, but it requires a default parameter that allows an unintended invalid call.
export const Fun = ({ req, opt = '', def = 'DEFAULT' } = { req: '' }) => {
	// GOOD: All variables are implicitly typed
	// ...
};

export const Fun_Call = () => {
    // BAD: It is possible to call without arguments (i.e. pseudo-required)
    Fun();
    // GOOD: But if any object is given, it works right
    Fun({ req: '' });
};

With Extends
export const Fun_extends = ({ req, opt = '', def = 'DEFAULT' }: extends { req: string }) => {
    // ...
};

export const Fun_Call = () => {
    // GOOD: This is not allowed
    // Fun();
    // GOOD: An object must be given with the correct typing
    Fun({ req: '' });
};

Extending Return Values
Current Best Solution
// Complex Objects:
const ComplexReturn = () => { return { a: 'a', b: 'b', c: 'c' }; };

const obj = ComplexReturn();
const objWithD_typeofWithObject = obj as typeof obj & { d: string };

With Extends
// Complex Objects:
const ComplexReturn = () => { return { a: 'a', b: 'b', c: 'c' }; };

const objWithD_extends = ComplexReturn() as extends { d: string };

Checklist
Syntactic

[x] What is the grammar of this feature?

'extends' at the beginning of type expression like 'typeof' or 'keyof'

[x] Are there any implications for JavaScript back-compat? If so, are they sufficiently mitigated?

No

[x] Does this syntax interfere with ES6 or plausible ES7 changes?

No

Semantic

[x] What is an error under the proposed feature? Show many examples of both errors and non-errors

The keyword would work in any type expression, just like 'keyof'

[x] How does the feature impact subtype, supertype, identity, and assignability relationships?

For inheritance, it could be used to extend class members from their supertype

[x] How does the feature interact with generics?

It would not change how the keyword is used with generics

Emit

[x] What are the effects of this feature on JavaScript emit? Be specific; show examples

This is pure typing, it would be removed from runtime emit

[x] Does this emit correctly in the presence of variables of type ‘any’? Features cannot rely on runtime type information

N/A

[x] What are the impacts to declaration file (.d.ts) emit?

The keyword would need to by included in the declaration file typing information

[x] Does this feature play well with external modules?

Yes

Compatibility

[ ] Is this a breaking change from the 1.0 compiler? Changes of this nature require strong justification

Unknown

[x] Is this a breaking change from JavaScript behavior? TypeScript does not alter JavaScript expression semantics, so the answer here must be “no”

no

[x] Is this an incompatible implementation of a future JavaScript (i.e. ES6/ES7/later) feature?

no

Other

[x] Can the feature be implemented without negatively affecting compiler performance?

Yes

[x] What impact does it have on tooling scenarios, such as member completion and signature help in editors?

It will provide a new type for that type expression

This is definitely the most interesting solution to the destructuring arguments typing problem that I've seen proposed.

@aluanhaddad Cool!
I don't know how the typescript code-base or how it works in the engine.
Is it easy to access the known type at the time the type expression is being processed?
If the known type is already available, I would think it would be easy to accomplish what I described (extending the known type with a supplemental description).
Also, I think this pattern would be preferable to a union in many cases.

Any feedback on this concept? Is there a better place to promote this idea?

The in-place typing is shorter, easier to think through, and less repetitive. They closed this idea out before, perhaps over syntax, but I don't see why is can't be used.
// Previous example
const { req, opt = '', def = 'DEFAULT' }: extends { req: string } = values;
// Just simple in-place typing
const { req is string, opt = '', def = 'DEFAULT' } = values;

@tjpalmer Yeah, that could work for function parameters.
However, I would think “as” would make more sense because “as” indicated type coercion, whereas “is” indicates type comparison.

I suggested is because they've previously rejected as for fear of potential future conflicts with ECMAScript. Some people would like to change destructure renaming to similar syntax as import renaming. Haven't seen it on the tc39 proposal list, but that's still been a concern on the TypeScript team.

Ah, yeah I think ECMAscript destructured renaming is the worst design decision I have seen in modern languange design (especially when they knew very well that this would fly in the face of TypeScript).
Like what were they thinking...
‘’’
// Since everybody understands this well
const x = {
a : “value”,
b: “value”,
};
// And this is clear
const {a,b} = x;
// And we need Default values
const { a, b, c=42 } = x;
// What about renaming?
// This would be too easy
const { a2:a, b2:b} = x;
// Oh, I know, let’s just reverse them because it makes sense - after all we have exactly no examples in the entire languange where a value assignment flows from left to right. So let’s just go in reverse from expected order for no good reason at all.
const { a:a2, b:b2} = x;
// Not only will this send a clear sign to TypeScript that we can do whatever we feel like, it will bring back the good old days when everyone made fun of horrible JavaScript design decisions.
‘’’
I don’t think that was the exact thought process, but I just don’t get it.


Sample

A sample to query a Feature Layer, determine what features have attachments, update a field with a value and push the updates back to the layer

see samples.


DaphneDSL map(): UDFs in Other Languages (e.g., Python, C++) #525

This PR introduces a new kernel for invoking map kernels from other programming languages and provides methods for the data transfer between DAPHNE and Python (see Issue #525 ).
Features:

New kernel for invoking map kernels of other programming languages.
Four Python map kernels offering different data transfer methods: Binary file, CSV file, Copy, Shared Memory.

Details:

New Kernels:
- Kernel for invoking map kernels: src/runtime/local/kernels/MapExternalPL.h
- Four Python map kernels: src/runtime/local/kernels/MAP_EXTERNAL/..
Python Interpreter Singleton:
- Integrated a global PythonInterpreter singleton class to manage Python interactions: src/util/PythonInterpreter
Tests
- Basic functionality tests for different map kernels: test/runtime/local/kernels/AlternativeMapTest
Scripts:
- General use-case scripts:
scripts/examples/map/map-GeneralExample.daph
scripts/examples/map/mapExternalPL-UtilityExample.daph
- Performance testing scripts: scripts/examples/map/performanceTest/..
IR Extensions:
- New operation (MapOpExternal) for Lowering of new Kernel: src/ir/daphneir/DaphneOps.td
Documentation Updates:
- New map entry: doc/DaphneDSL/Builtins.md
- Guidance for extending the map kernel: doc/developement/ImplementBuiltinKernel.md

Thanks for this contribution @StoeckOverflow! Enabling DaphneDSL map() with UDFs written in other programming languages, such as Python, is a very interesting feature that can be used to do value-based processing beyond what DaphneDSL is currently able to do.
The two of us have already discussed this matter and I will provide some feedback on your code soon.


[Bug] someone made the navbar sticky

Is there an existing issue for this?

[X] I have searched the existing issues

Bug Description?
the navbar used to move up when scrolled down and move down when scrolled up, now in some recent changes, someone changed it to be sticky, you need to fix it in this issue also navbar is looking very full fix it too.

Add Screenshots
No response
What browsers are you seeing the problem on?
No response
Record

[X] I agree to follow this project's Code of Conduct
[ ] I'm a GSSOC contributor
[ ] I want to work on this issue (Optional)
[ ] I'm willing to provide further clarification or assistance if needed.

Hi @Luson045, Can you please assign this issue to me?
I Would like to work on this.

@Suraj-kumar00 okay 👍

Hi @Luson045 , Can you please assign this issue to me?
I Would like to work on this.


[Question] Do we have any callback method on drag end to get the sizes?

Hi,
I really like your work. It's a great library for react.
Just want to know if there's any callback function through which I can get the sizes of each pane.
Or are there any props that am missing?
Thanks

Getting the size seems unrelated to this library. For example if you look at the demos, sizing the window will change the sizes of the panes but this library isn't even running any code in that case.

This seems to work?
function SomeContent(props) {
  const ref = useRef(null);
  const [dims, setDims] = useState({width: 0, height: 0});

  useEffect(() => {
    const {width, height} = ref.current.getBoundingClientRect();
  	setDims({width, height});
  });

  return (

      size: {`${dims.width.toFixed(1)}x${dims.height.toFixed(1)}`}

  );
}

Example:
https://jsfiddle.net/greggman/pqL043hz/

Getting the size seems unrelated to this library. For example if you look at the demos, sizing the window will change the sizes of the panes but this library isn't even running any code in that case.

This seems to work?
function SomeContent(props) {
  const ref = useRef(null);
  const [dims, setDims] = useState({width: 0, height: 0});

  useEffect(() => {
    const {width, height} = ref.current.getBoundingClientRect();
  	setDims({width, height});
  });

  return (

      size: {`${dims.width.toFixed(1)}x${dims.height.toFixed(1)}`}

  );
}

Example:
https://jsfiddle.net/greggman/pqL043hz/

Getting the size seems unrelated to this library. For example if you look at the demos, sizing the window will change the sizes of the panes but this library isn't even running any code in that case.

This seems to work?
function SomeContent(props) {
  const ref = useRef(null);
  const [dims, setDims] = useState({width: 0, height: 0});

  useEffect(() => {
    const {width, height} = ref.current.getBoundingClientRect();
  	setTimeout(_ => setDims({width, height}));
  });

  return (

      size: {`${dims.width.toFixed(1)}x${dims.height.toFixed(1)}`}

  );
}

Example:
https://jsfiddle.net/greggman/pqL043hz/

Getting the size seems unrelated to this library. For example if you look at the demos, sizing the window will change the sizes of the panes but this library isn't even running any code in that case.

This seems to work?
function SomeContent(props) {
  const ref = useRef(null);
  const [dims, setDims] = useState({width: 0, height: 0});

  useEffect(() => {
    const {width, height} = ref.current.getBoundingClientRect();
  	setTimeout(_ => setDims({width, height}));
  });

  return (

      size: {`${dims.width.toFixed(1)}x${dims.height.toFixed(1)}`}

  );
}

Example:
https://jsfiddle.net/greggman/pqL043hz/

Hi,
I wanted the size (specifically height) of each panes to set Max-size to its inner components so that I get to see a scroll bar when the gutters are moved.
I tried by changing the css property of pane class to overflow: auto.
But that's not the behaviour I wanted. I have a accordion which by default is open. So when I drag the gutter, the contents inside accordion should show scrollbars.
I tried with your above snippet. But the width is changing correctly. The height is same.
https://codesandbox.io/embed/mystifying-bash-rh8hf?codemirror=1
Here I have reproduced it. The height remains same even if I move the gutter.
Please help me if I am wrong.
Thanks

Hi,
I wanted the size (specifically height) of each panes to set Max-size to its inner components so that I get to see a scroll bar when the gutters are moved.
I tried by changing the css property of pane class to overflow: auto.
But that's not the behaviour I wanted. I have a accordion which by default is open. So when I drag the gutter, the contents inside accordion should show scrollbars.
I tried with your above snippet. But the width is changing correctly. The height is same.
https://codesandbox.io/embed/mystifying-bash-rh8hf?codemirror=1
Here I have reproduced it. The height remains same even if I move the gutter.
Please help me if I am wrong.
Thanks

Figured out that my nested component had issues with scrolling. Had to change the layout.
Thanks for your help.

Figured out that my nested component had issues with scrolling. Had to change the layout.
Thanks for your help.


NullPointerException with Map containing null values

Trying to create or update a Node from an Object with a Map annotated with
@JcrReference and containing null values lead to a NullPointerException in the
Reference Mapper.

Unit test: https://gist.github.com/amischler/a370a17c28ecb2fad48f

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 25 Feb 2015 at 2:17

fixed


Add Alby logo to the extension window

As as user I would like to see the awesome Alby bee when I use the extension.
The picture is only a suggestion. I am not sure yet where to place the display of the wallet amount

.

Okay, I'll search for something there, thanks

Is this something we still want to do?

I think we should first really think about some design concept before we do this.

@dvoroneca can this be closed?


Version 0.19.0 does not compile on Mac 12.1 (non-M1)

Hello !
I tried to install anchor 0.19.0 by using this command:
cargo install --git https://github.com/project-serum/anchor --tag v0.19.0 anchor-cli --locked
But I got these errors :
error[E0658]: arbitrary expressions in key-value attributes are unstable
 --> /Users/mycomputername/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-3.0.0-beta.4/src/lib.rs:8:10
  |
8 | #![doc = include_str!("../README.md")]
  |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: see issue #78835 <https://github.com/rust-lang/rust/issues/78835> for more information

error[E0658]: use of unstable library feature 'osstring_ascii'
   --> /Users/mycomputername/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-3.0.0-beta.4/src/parse/matches/matched_arg.rs:130:19
    |
130 |                 v.eq_ignore_ascii_case(val)
    |                   ^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #70516 <https://github.com/rust-lang/rust/issues/70516> for more information

error: aborting due to 2 previous errors

Installing version 0.18.2 works just fine.
I am under Mac OSX 12.1 (not M1).
rustc version is rustc 1.57.0 (f1edd0429 2021-11-29)
rustup version is rustup 1.24.3 (ce5817a94 2021-05-31)
solana version is solana-cli 1.9.1 (src:b66e2ae3; feat:4100269022)

have you installed the nightly rust channel?

No, I'll try it

Thanks @paul-schaaf Tried and installing nightly rust worked.


waitforall() hides errors

mx.nd.waitforall() doesnt check for errors and rethrow any that have occurred users will get an error when reading the output data. But I ran into an issue where I was gathering performance data, measuring elapsed time over an inference via model.forward() and mx.nd.waitforall() but I had hit an error and it was being hidden by waitforall(). I would have gotten the error had I actually read the output data, though.
For this issue, we should fix waitforall() to have the ability to check for errors on each of the outputs.

this is by design and has been documented in the PR: https://github.com/apache/incubator-mxnet/pull/9681 . The waitforall is generally used for synchronization and benchmarking purposes. If you want to throw the exception you can call wait to read on the variables before or after the waitall call. Adding waitall support requires a global exception ptr and complicates the implementation. To workaround you should read the the output data before or after caliing waitall.

@mxnet-label-bot add [Feature Request]

@mxnet-label-bot add [NDArray]


Galley watcher panic

https://prow.istio.io/view/gcs/istio-prow/logs/integ-galley-k8s-tests_istio_postsubmit/1899
Tentatively assigning to @ayj since I don't know who else works in this area anymore

https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/22481/integ-galley-k8s-tests_istio/10315

https://prow.istio.io/view/gcs/istio-prow/logs/integ-k8s-115_istio_postsubmit/1150
https://prow.istio.io/view/gcs/istio-prow/logs/integ-k8s-116_istio_postsubmit/1799

https://prow.istio.io/view/gcs/istio-prow/logs/integ-galley-k8s-tests_istio_postsubmit/1906
https://prow.istio.io/view/gcs/istio-prow/logs/integ-k8s-114_istio_postsubmit/1938
Seems like a major regression, bumping to "release blocker"

I think its because we are deleting CRDs now as of #22336. I'll fix that, but Galley probably shouldn't panic regardless

Thanks John. Can we keep this issue open to track the fix in Galley itself?

Yeah, I think that makes sense


Update sbt-ci-release-early to 2.0.22

Updates io.shiftleft:sbt-ci-release-early from 2.0.19 to 2.0.22.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.shiftleft", artifactId = "sbt-ci-release-early" } ]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #939.


feat: provide consistency across data sources in terms of case sensitivity

What does this fix or implement?

Checklist

[x] PR name added as appropriate (e.g. feat:/fix:/doc:/test:/refactor:)
[ ] Tests added or updated
[x] Documentation updated
[x] Changelog updated and version incremented (label: upcoming release)
[ ] Github Issue linked if any
[x] Jira task updated

TO DO after merge of improvement branch: implement partial_match on image + remove version


test: update for CI 4.3

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
331

Relevant Lines:
420

💛  - Coveralls


Can join the session, but the window is not visible

I'm using the 0.2.7 version and the latest steam client.
My friend can join my session and see my screen. But when I press shift+tab, the window giving mouse and keyboard permissions doesn't show up. So I couldn't play it. I tried installing an old version of the steam, but it didn't turn on as it crashed. What should I do to play remotely?
Below is a tab that does not appear

Same issue.


adds dns support for BuddyDNS

@tonybaloney check it man :)

@jetbird another great contribution! just a couple of small changes, you need to add the Apache license header to the 2 files I noted.

@tonybaloney thanks man! Done :)

@jetbird Since this is a bigger change please make sure to submit an ICLA (http://libcloud.readthedocs.org/en/latest/development.html#contributing-bigger-changes) and select to notify the Libcloud project :)

Is this pull request sill work in progress or considered complete?
I'm wondering because I only see methods for zone (domain) management, but no methods for managing records.

As Anthony has said, nice work so far :+1:

@Kami the provider does not support operation on records.

ACK the receival of ICLA. Thanks.

@jetbird one more thing, I tagged you in a commit since I missed it on the other 2 PRs.
You need to update libcloud/dns/providers.py

@jetbird I also noticed you don't have your git name and email fully configured.
Please follow the instructions at https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup and configure your git name and email. This way it's easier for us to track commits back to actual contributors.