Handle scalar problems

The other day, I tried implementing the scalar Stefan problem with Phaseflow, while debugging the coupled  concentration equation. This was apparently the first time I'd ever tried a scalar problem with Phaseflow, i.e. one not using mixed finite elements. There seem to be a lot of differences in FEniCS between using a fenics.FiniteElement and a fenics.MixedElement. We'll have to make this more abstract.
I wanted to apply indirection to the finite element library anyway (see #265), allowing one to use other libraries such as Firedrake. Ideally these would be done at the same time to avoid more refactoring; but the urgently need scalar support for #195 .

#195 is currently being explored in 1D with just FEniCS, so supporting this in Phaseflow is less urgent now.


Preparations for release 1.2

Please confirm that this PR has done the following:

[x] Tests Added
[x] Documentation Added
[x] Description in RELEASE_NOTES.md Added

Description
This PR brings in two new features for message_ix for commodity-balance equality and better treatment of emissions prices in models with non-equidistant period durations.
The PR also implements the corresponding changes in the message_ix.Scenario to the new features in ixmp.Scenario for cloning across platforms and better treatment of IAMC-style timeseries for reporting of model results.
The PR depends on https://github.com/iiasa/ixmp/pull/142

Hi @danielhuppmann, thanks for the PR! I went ahead and restarted ci (with a git commit --amend) after .
This is a pretty big PR. Can you please suggest 2-3 reviewers that can look over specific aspects? I think tackling it by a single reviewer is probably too large a task.
Also, can you enumerate any outstanding issues? I believe there is at least the discounting issue discussed previously, but are there any others?

It looks like python2 tests are failing? @khaeru did we remove them in ixmp in the release candidate?

I've asked @khaeru to do a review of the implementation, I will look at the GAMS code as well to try to see the discount factor issue..

Ok, @danielhuppmann I think we see the light of day here. Let me know when all comments have been addressed and unit tests pass. The merge can happen soon after!

Ok, ready to merge after tests pass!

thanks @gidden and @khaeru for this diligent review of a way-too-large PR. Should be good to go now (with some follow-up work to be done in #208)

Integer-division with Python 2, therefore leading to different results in some tests. Fixed.
But we are running into Java heapspace issues in the tests on the global models... @gidden, can you take a look?

Those sometimes happen. We could probably try to set the heapspace higher, but rerunning them thus far has always yielded passing results on the second run through. Just restarted it.

Congrats to all, especially @danielhuppmann for pushing this through! I will leave the branch alive until the release is official. It should be deleted after that.


Debug Breakpoints not working in Windows 10

The debugging of single test works fine on Mac Machines with Node version >=8. But, on the windows machine, the debug doesn't work properly, which means, placing a breakpoint and debug the test, the debugger doesn't stop at breakpoint, it inturns run the test making the breakpoint turned to grey and saying that "unverified breakpoint, breakpoint ignored because generated code not found (source map problem?)."
In Windows machines, the trace log is below:
SourceMaps: expanded globs and found 63709 scripts
SourceMaps: could not preload for generated script<EMAIL_ADDRESS>Error: Error: EMFILE: too many open files, open<EMAIL_ADDRESS>I am trying with below versions:
"@types/jest": "^22.2.3",
"jest": "^22.4.3",
"ts-jest": "^22.4.4",
"babel-jest": "^22.4.3",
node: 8.9.4

Please read this to configure source maps propeperly https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_source-maps

I followed that and this is my config:
{
"type": "node",
"request": "launch",
"name": "Debug Tests In Current File",
"sourceMaps": true,
"program": "${workspaceFolder}/node_modules/jest/bin/jest.js",
"cwd": "${workspaceFolder}",
"args": ["--i", "--config", "jest.config.json", "${relativeFile}"],
"outFiles": ["${workspaceFolder}/**/*.js"]
}

SourceMaps: expanded globs and found 63709 scripts
Error: Error: EMFILE: too many open files, open<EMAIL_ADDRESS>
It looks like your outFiles pattern matches tons of files. Is there any way you can make it more precise? I will have to change the debug adapter to not open so many files at once.

Actually, it's not likely that I'll work around this in the debug adapter. It will also launch a lot faster if you narrow down the outFiles pattern, so that's definitely the best fix.

@roblourens  : Thanks for getting back. But, I think jest will generate the .js files in its memory. How do we know the path, where the .js files are being generated? Please correct me if my understanding is wrong.

Yeah, in that case, outFiles is not useful, and you can remove it.

I tried that, same problem. Between, how do we make debugger stop at breakpoint? I am using node 8.9.4, Windows 10, vscode 1.21.1. I tried with ts-jest 21.2.3 and 22.4.4 (latest)
Same configs on mac works perfectly fine.

Can you run the .scripts command in the console to see if it's resolving your sourcemaps correctly?

I ran the .scripts and checked the log, the symlinks are generated only for files in the node_modules folder and not for files in the workspaces.

Can you paste some of the output here?

› assert.js
› async_hooks.js
› bootstrap_node.js
› buffer.js
›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>› c:\Users\rojidaga\Desktop\teams-code-space\teams-modular-packages\node_modules\abab\index.js
› c:\Users\rojidaga\Desktop\teams-code-space\teams-modular-packages\node_modules\abab\lib\atob.js
› c:\Users\rojidaga\Desktop\teams-code-space\teams-modular-packages\node_modules\abab\lib\btoa.js
› c:\Users\rojidaga\Desktop\teams-code-space\teams-modular-packages\node_modules\ansi-styles\index.js
› c:\Users\rojidaga\Desktop\teams-code-space\teams-modular-packages\node_modules\arr-flatten\index.js
› c:\Users\rojidaga\Desktop\teams-code-space\teams-modular-packages\node_modules\asn1\lib\ber\errors.js
› c:\Users\rojidaga\Desktop\teams-code-space\teams-modular-packages\node_modules\asn1\lib\ber\index.js
› c:\Users\rojidaga\Desktop\teams-code-space\teams-modular-packages\node_modules\asn1\lib\ber\reader.js

Can you paste the portion that has the files you want to set breakpoints in? That's the point of looking at that command's output.

I don't see those files in the output. I only see that symlinks are being generated for files in the node_modules folder and not for files in the workspaces folder.

If the files don't show up there, then they are not loaded. Double check that the files you expect are actually running.

The files are not being showed up there. That is the problem we are facing. I tried to setup the config in 2 sample projects(with jest and without jest). The symlinks are generated correctly in project without jest but with jest, I get this same issue. Can you please share some jest configuration?

Have you seen this example? https://github.com/Microsoft/vscode-recipes/tree/master/debugging-jest-tests


Add Tuple input and token support to all-gather and reduce-scatter.

@hjm-aws Can you please resolve conflicts? Thank you!

@hjm-aws Can you please sign CLA. Thank you!

@hjm-aws Can you please sign CLA. Thank you!
Done. Thanks!

@hjm-aws It still shows CLA is pending, can you please sign CLA. Thank you!

Thanks, overall this looks like a very good change! Added @Kariddi and @blakehechtman for clarifications.

Overall it seems this is attempting to add tuple support for all-gather and reduce-scatter as well as add a optional dummy token input to the all-gather, the purpose of which is unclear.
I think we should split this into 2 PRs, one for tuple support and discuss support for token types in all-gather separately before adding it.

@hjm-aws Can you please check @jurahul's comments and keep us posted ? Thank you!

@hjm-aws Any update on this PR? Please. Thank you!

@hjm-aws Any update on this PR? Please. Thank you!

Overall it seems this is attempting to add tuple support for all-gather and reduce-scatter as well as add a optional dummy token input to the all-gather, the purpose of which is unclear.
I think we should split this into 2 PRs, one for tuple support and discuss support for token types in all-gather separately before adding it.

@gbaned @jurahul , the revived PR on openxla is https://github.com/openxla/xla/pull/5740 .


[Task] use Flyway to manage database versions, instead of jpa auto ddl

Description
jpa auto ddl 在添加新表或添加新列时效果很好，但是无法对数据库进行细粒度管理，例如删除列、删除索引、删除检查等。
Flyway可以很好地解决这个问题。
Task List

[ ] 引入Flyway并配置升级脚本

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Description
jpa auto ddl works great when adding new tables or adding new columns, but cannot do fine-grained management of the database, such as dropping columns, dropping indexes, dropping checks, etc.
Flyway can solve this problem very well.
Task List

[ ] Introduce Flyway and configure the upgrade script

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Using JPA AutoDDL can satisfy different databases, but Flyway can't do it temporarily, so close it


Add more documentation for beginner tutorial

PR Details
This just adds some comments to the code to point the user to the online tutorials if they didnt know. There is also a readme file with a small amount of extra info.
Related Issue
https://github.com/stride3d/stride/issues/1751
Motivation and Context
This should help some new users who may not have known about the online tutorials.
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Thanks !


add keyid and apikey

This will solve issue #17

I did this myself. Thanks anyway. Just published 1.4.1


Create an integration test for the registry that essentially runs the demo script

The now broken (and disabled) acme_r2d2 agent test (I'll create a separate Issue to track fixing it) also tests the registry functionality.
We should either fix that test or make a different integration test that makes sure the registry works.
We should have this test essentially run the current version of the main AgentOS project demo.

This test exists now at web/registry/tests/test_integration.py.


test(e2e,playwright): Flash

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Solves "UI Components/Flash" >  #51705

camperbot cant code

Waiting for https://github.com/freeCodeCamp/freeCodeCamp/pull/51893 to get merge as it contains tthe solution for CI error.

Hi, unfortunately we need to keep the code that's deleting the csrf_token cookie for the foreseeable future. It seems to be necessary for some users and we won't have time to dig into why for a while. Since that means this spec will not pass on webkit, could you skip it for that browserName?

Hi, unfortunately we need to keep the code that's deleting the csrf_token cookie for the foreseeable future. It seems to be necessary for some users and we won't have time to dig into why for a while. Since that means this spec will not pass on webkit, could you skip it for that browserName?

Fixed it by skipping test for webkit as described by you.


Mikeechen add classname to dots

Deployed to https://beghp.github.io/gh-pages-rc-9It resolves https://github.com/brainhubeu/react-carousel/issues/396- [ ] package.json:version has been updated with npm version patch (or major/minor as appropriate)- [ ] @brainhubeu/react-carousel version has been updated in docs-www/package.json to the same which is in package.json:version

Thank you man! When do you plan on merging this change in?

@mikeechen
I see TypeError: this.getProp is not a function error in some places.

@mikeechen
I see TypeError: this.getProp is not a function error in some places.

My fix is in PR 399

thanks @mikeechen
we need another review to merge it (I hope it'll happen within the next 12 hours)

thanks @mikeechen
we need another review to merge it (I hope it'll happen within the next 12 hours)

Sounds good! Thank you! Probably need your help on rebasing this branch too.

@mikeechen
I'll click Update branch but before that, a few other PRs could be merged.


Bug 2067886: Upgrade the prometheus client to a newer version

/cc @yevgeny-shnaidman @pacevedom

/lgtm


[Bug] corrupted file when downloading from modsbase.com

Every time I try to download any file from ModsBase, the downloaded file comes corrupted and has a fixed size of 256 bytes. I tried downloading different files, and the issue is the same with all of them. However, the download works normally when I do it through the browser.
Example link: here.

@idkwhoami666 Thanks for reporting this. I will check that.

@idkwhoami666 Hello again. I tested the link you provided and it works proeperly.

can you send me the exact link that you have faced the problem ?

@amir1376 The link I sent as an example had this issue, but I tested a few other links here and it's no longer causing the problem. I don't know what happened.


Implement a hero animation for the podcast tile

A hero animation is when you click on a podcast tile that contains an image, and that image grows in size and moves to the place where that image will be located on the next page. Basically, it's a fancy smooth page transition animation
Acceptance criteria:

clicking a podcast tile should trigger the page transition (already does)
the cover art of the podcast should smoothly scale and translate into the place of the cover art in the Podcast Episodes page

Note: no need for such a transition backwards (i.e. from Podcast Episodes to Podcast Gallery), but if it's easy to implement then by all means go for it

Sorry, I lied, it's actually called a "Shared Element Transition". Apparently we have an open bug in SvelteKit, https://github.com/sveltejs/kit/issues/628, that references duplication of page content. Generally, from the looks of it, transitions like that are not too easy to implement in a generic, non-fragile way, so maybe we should just close this issue and the linked PR.


Kubeflow_istio_ issue

Bug Description
I was trying to install kubeflow version v1.5.0 on OpenShift cluster. I have deployed all the components of Kubeflow then pods should be in running state so some're up and when it comes to Istio-init is not able to running state due to error Failed to execute: iptables-restore --noflush /tmp/iptables-rules-1669007447751581007.txt771627809, exit status 2.
Version
kubeflow version: v1.5.0
Kubernetes platform: OpenShift
version:4.10

Additional Information
2022-11-21T05:10:47.751488Z info Istio iptables environment:
ENVOY_PORT=
INBOUND_CAPTURE_PORT=
ISTIO_INBOUND_INTERCEPTION_MODE=
ISTIO_INBOUND_TPROXY_ROUTE_TABLE=
ISTIO_INBOUND_PORTS=
ISTIO_OUTBOUND_PORTS=
ISTIO_LOCAL_EXCLUDE_PORTS=
ISTIO_EXCLUDE_INTERFACES=
ISTIO_SERVICE_CIDR=
ISTIO_SERVICE_EXCLUDE_CIDR=
ISTIO_META_DNS_CAPTURE=
INVALID_DROP=
2022-11-21T05:10:47.751537Z info Istio iptables variables:
PROXY_PORT=15001
PROXY_INBOUND_CAPTURE_PORT=15006
PROXY_TUNNEL_PORT=15008
PROXY_UID=1337
PROXY_GID=1337
INBOUND_INTERCEPTION_MODE=REDIRECT
INBOUND_TPROXY_MARK=1337
INBOUND_TPROXY_ROUTE_TABLE=133
INBOUND_PORTS_INCLUDE=*
INBOUND_PORTS_EXCLUDE=15090,15021,15020
OUTBOUND_OWNER_GROUPS_INCLUDE=*
OUTBOUND_OWNER_GROUPS_EXCLUDE=
OUTBOUND_IP_RANGES_INCLUDE=*
OUTBOUND_IP_RANGES_EXCLUDE=
OUTBOUND_PORTS_INCLUDE=
OUTBOUND_PORTS_EXCLUDE=
KUBE_VIRT_INTERFACES=
ENABLE_INBOUND_IPV6=false
DNS_CAPTURE=false
DROP_INVALID=false
CAPTURE_ALL_DNS=false
DNS_SERVERS=[],[]
OUTPUT_PATH=
NETWORK_NAMESPACE=
CNI_MODE=false
EXCLUDE_INTERFACES=
2022-11-21T05:10:47.751753Z info Writing following contents to rules file: /tmp/iptables-rules-1669007447751581007.txt771627809

nat
-N ISTIO_INBOUND
-N ISTIO_REDIRECT

Did you configure the OpenShift according to: https://istio.io/latest/docs/setup/platform-setup/openshift/

Yes I configured the same and still pods are crashing due to Istio sidecar.

Still it is not resloved...
can anyone suggest how to resolve this issue ?


[DNM] UP² ADSP DMA test

It's using PR #21241 as a dependency

@nordic-krch could you comment these on #21241 ? this current PR is only about 1 commit only on top of #21241

@tbursztyka done

@nordic-krch note: the "fixed" comments from me just now are actually for the original PR (where you also commented). I was supposed to comment there.


WalletConnect modal cannot close

update?

update to beta 47 does not solve the problem

https://example.walletconnect.org/ modal can be closed

https://github.com/WalletConnect/walletconnect-monorepo/blob/fbf4d48553942bf23c6ea4475fde35b45e0ec2e8/packages/helpers/qrcode-modal/src/browser.ts#L72

modal is opened twice, related to https://github.com/WalletConnect/walletconnect-monorepo/issues/170


Distributed key-value store over RDMA

Recently I have been thinking about what to do with my Master's degree graduation project. Today, I came across this idea as mentioned in the title. Is it valuable? If so, is it feasible?

I am open to any suggestions. Is there anything I can do for any of your open source projects that would help me graduate? @chrislusf A graduation project need to have two innovation points.


Enable EZProxy authentication

This might help! http://matthew.reidsrow.com/articles/20

Going to do CAS authentication instead


Added  a simple chat bot with the interactive ui

Hey maintainers,
I have added a really interactive chat bot with a comparatively better UI...

As a beginner to open-source you can contribute to hacktoberfest2023
You can also checkout our Idea-Arca, the project idea bank for any languages, for open-source contributions.
Happy Contributing season!
Keep up the good work!


Weird numbers in Matches Results

When I went to my stats, I've ran into weird sums in my daily games. See screen.
Played with two decks, total 29:29, above, you can see 29:30, below 30:29. Seems like one game is somehow invalid.

STR:
https://mtgarena.pro/u/Qawaya see stats for Oct 20.

I'm trying to locate this floating bug, no luck for now.

Maybe this could help. There is 11PM (CET) and this last match was calculated to next day ..
Another funny behavior occured.


Documentation: API routes and file structure

Description:
After what was discussed during the API meeting and dev team agreements, we need to document in the API docs (docs/backend/api-design.md):
1) API routes don't need to mirror frontend routes. They should match the object they're fetching

GET "object-to-be-fetched/{id}"
GET "object-to-be-fetched?some_param=123&other_param=..."

example:
GET "report-version/{version_id}"
GET "facility-report/{facility_report_id}" OR "facility-report?...params..."

2) API files should minimize the amount of routes they declare for readability & testability. Rule of thumb is one file per resource with GET PUT POST ...

example: report-version.py

File path can include subdirectories following the API endpoint's URL.

Acceptance Criteria:
Given I am a developer
When I make a new API endpoint
Then I know which route to assign to it, how parameters will be queried, and in which file to write it
Development Checklist:

[ ] api-design.md file updated
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

@Sepehr-Sobhani for API team visibility

In case we want to include it in docs: Path Parameters vs. Query Parameters
We have used query params for paginating and sorting a list of items for a specific data grid.


ssl protocol version switch trough erlang VM (attach) for dderl modul

VM shall provide following three functions on dderl modul:
list getSupportedSSLProtocols()
boolean setSSLProtocols(list)
list getSSLProtocols()

setter should return false if operation was not successfull of if list is null or contains any invalid options and return without change. If possible a message shall be issues after every set "PLEASE RESTART SERVICE..."
setter should not underly any restriction, so even ssl3 shall be allowed, hence ssl3 shall still be deactivated on dderl startup

No practical need identified!


fix issue #1: doesn't work for images with width > 256

Like said in the issue, a Uint8array for _bitrev was just enough to deal with 256 entries so it failed with larger images.

merged commit, thanks a lot.


Misc fixes and features

A collection of minor fixes and improvements that I ran across while converting a legacy codebase to use sharpmake.

Fixed the tabs.


[FLINK-35988][table]Reduce the number of state queries in the AppendOnlyFirstNFunction

What is the purpose of the change
Reduce one state query in the AppendOnlyFirstNFunction and optimize the processing performance for large states.
Brief change log

Query the state only once.
Change "currentRank += 1" to "currentRank++".

Verifying this change
This change is already covered by existing tests, such as AppendOnlyFirstNFunctionTest.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not documented)

run azure

@flinkbot run azure

@flinkbot run azure

@lexluo09 could you rebase the latest master to see if the ci can pass?

Thank you, I have already performed the rebase.

@lexluo09 could you rebase the latest master to see if the ci can pass?
Thank you, I have already performed the rebase.

@flinkbot run azure


PPLBench Interface to BMG Statistics

Summary: A new statistics gathering package about the BMG graph was introduced in Diff 38284547. The current diff contains code for interfacing PPLBench to the statistics package. The modifications are in main.py, to generate the output file containing the statistics, and in inference.py, which contains the code to actuall call the statistics package upon the formation of the graph. The graph does not change during the PPLBench runs, even with different inference methods, so one call is sufficient to produce the results.
Differential Revision: D38406849

Closing this PR because it's been superseded by https://github.com/facebookresearch/pplbench/pull/120


Branch 2.10 build failing, Pls fix it and publish to mvn repository

Jedis version:
2.10

Please ask this question in the mailing list. github is used for design discussions and bugs mainly.
http://groups.google.com/group/jedis_redis


Document platform config parameter (DC/OS 1.9)

What are your changes?
Document new optional telemetry param.
Code change: https://github.com/dcos/dcos/pull/645
What type of changes does your doc introduce?

[ ] Bug fix
[X] New feature

What is the urgency level of this change?

[ ] Blocker
[X] High
[ ] Medium

I have completed these items:

[X] I have tested all commands and code snippets.
[X] I have built locally and tested for broken links and formatting.
[X] I have made this change for all affected versions (e.g. 1.7, 1.8, and 1.9).
[X] My doc follows the style guide: https://github.com/dcos/dcos-docs#contributing.

@joel-hamill suggestion accepted.


Currently "join the testnet button" does not link anywhere

Problem statement
Is the intention to link to a section of the website or some docs?

Where should  "join the testnet button" link to?

Where does the cosmos faucet link to currently?

SDK Documentation

Link to docs/guide/join-network.md then
On Tue, Apr 2, 2019, 6:47 PM CUI DI<EMAIL_ADDRESS>wrote:

SDK Documentation
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/terra-project/faucet/issues/5#issuecomment-478923963,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABjx-MoY5Iwsp5fC5iOIRBXOuo1lKNcrks5vcycYgaJpZM4cWKNK
.


Problem with LAEA projection

This issue was imported from CodePlex
Yvan_B wrote 2013-02-24 at 23:56
Hello,
I'm new to Dot Spatial and really enthusiast to play with this great tool.
I am trying to convert lat/lng values to ETRS LAEA Europe coordinate system (EPSG:3035) but I always get NAN values (Not A Numeric). I think that this closed issue is probably the same:
http://dotspatial.codeplex.com/workitem/22212
here is my code (VB.NET) :
        Dim xy(1) As Double
        xy(0) = 5
        xy(1) = 50
        Dim z(0) As Double
        z(0) = 1
        Dim pStart As ProjectionInfo = KnownCoordinateSystems.Geographic.World.WGS1984
        Dim pEnd As ProjectionInfo = ProjectionInfo.FromProj4String("+proj=laea +lat_0=52 +lon_0=10 +x_0=4321000 +y_0=3210000 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs")
        Try
            Reproject.ReprojectPoints(xy, z, pStart, pEnd, 0, 1)
        Catch ex As Exception

        End Try
        MsgBox("The points have been reporjected." & vbCrLf & xy(0) & "," & xy(1))

The code works well with other coordinate systems. It doesn't work with KnownCoordinateSystems.Projected.Europe.ETRS1989LAEA nor if I use the definition found in AuthorityCodeToProj4.txt (line 1006)
The Proj4 definition I use in the code is correct (verified in the epsg file of PROJ4).
Any idea?
Yvan
IvanD79 wrote 2013-03-05 at 18:47
Same problem trying to convert from LAEA (3035) to WGS84 (4326), it's a real BIG issue...
For coordinates like, for example, 4175490.5731252655 - 1997066.9173578955 I receive NaN - NaN...
ProjectionInfo pStart = ProjectionInfo.FromEpsgCode(3035);ProjectionInfo pEnd = KnownCoordinateSystems.Geographic.World.WGS1984;
SqlGeometry sqlPoint = sqlRing.STPointN(1);double[] xy = new double[2];xy[0] = sqlPoint.STX.Value;xy[1] = sqlPoint.STY.Value;Reproject.ReprojectPoints(xy, null, pStart, pEnd, 0, 1);
tmanthey wrote 2013-04-27 at 16:26
I can confirm this issue
tmanthey wrote 2013-04-27 at 16:41
Working workaround is to use the .Net Wrapper for the native dll. Some good instructions are

here
Yvan_B wrote 2013-04-30 at 22:33
Thanks for the last suggestion. I came already to the same conclusion about .Net Wrapper (and it works)
Yvan

The workaround link no longer works unfortunately. Could anyone tell me more about the workaround?


image mipmap tests do not enable extensions

The clang OpenCL headers do not expose the image mipmap functions unless cl_khr_mipmap_image* are defined.  However the CTS generated kernel sources do not actually enable the extensions.  I assume they should be enabling the extensions before using them?

Yes, we've certainly made quite a few similar changes to the CTS for other extensions.


[HUDI-1841] Tweak the min max commits to keep when setting up cleanin…

…g retain commits for Flink
If the retain commits is greater that min commits to keep, reset the
options:

min commits to keep: retain commits + 10
max commits to keep: retain commits + 20

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #2875 (d50632d) into master (a5789c4) will increase coverage by 16.68%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master    #2875       +/-   ##
=============================================
+ Coverage     53.00%   69.68%   +16.68%
+ Complexity     3743      373     -3370
=============================================
  Files           488       54      -434
  Lines         23435     1996    -21439
  Branches       2500      236     -2264
=============================================
- Hits          12422     1391    -11031
+ Misses         9913      473     -9440
+ Partials       1100      132      -968

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
?
?

hudicommon
?
?

hudiflink
?
?

hudihadoopmr
?
?

hudisparkdatasource
?
?

hudisync
?
?

huditimelineservice
?
?

hudiutilities
69.68% <ø> (ø)
373.00 <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ
Complexity Δ

...a/org/apache/hudi/io/storage/HoodieFileReader.java

...in/java/org/apache/hudi/hive/HoodieHiveClient.java

...on/table/log/block/HoodieAvroDataBlockVersion.java

.../org/apache/hudi/metadata/HoodieTableMetadata.java

...g/apache/hudi/sink/StreamWriteOperatorFactory.java

...rc/main/java/org/apache/hudi/ApiMaturityLevel.java

...ache/hudi/hive/HiveMetastoreBasedLockProvider.java

.../hudi/internal/HoodieDataSourceInternalWriter.java

.../org/apache/hudi/exception/HoodieKeyException.java

...a/org/apache/hudi/cli/HoodieTableHeaderFields.java

... and 421 more


HTTPClient fails when Content-Length is not set

When HTTP response doesn't set Content-Length, http and https client raises and closedStream(0 bytes) error.
It should calculate total length read till the end of http server connection, when this header is not set.
How to reproduce?
For this response:
HTTP/1.1 200 OK
Date: Fri, 16 Sep 2016 16:23:17 GMT
Connection: close

test

Run on the simplest http server (https://gist.github.com/vi4m/a3809caea5e4a59d27e1032f8b9657f1)
And with this swift client code:

import HTTPClient

do {
    let c = try Client(url: "http://localhost:9000")
    let request = Request(method: .get, url: "/")
    var response = try c.request(request!)
}
catch {
    print(error)
    print("Failed.")
    exit(2)
}
print("Success.")

it will fail with closedStream(0 bytes error).
When the response is completed with "Content-Lenght: 5" http request works fine.

moved to https://github.com/Zewo/Zewo/issues/130


fix: restore threadDoubleAccordion sticky effect

Close #117

Summary by CodeRabbit

New Features

Added an optional isSticky property to the AccordionTrigger component to enhance UI customization.

 Review and Fix Alpha UI/UX Regressions


Crash, segmentation fault

Hyprland Version
Hyprland, built from branch main at commit af6aae4e12b96fff701d8ae8fcb48ea8bb51009f dirty (renderer: don't use clipBox for pinned window occlusion during animations). Tag: v0.33.1-16-gaf6aae4e
Bug or Regression?
Bug
Description
It crashed when I tried to open sshfs mounted directory in vscode from terminal. coudnt reproduce after that idk
How to reproduce
idk
Crash reports, logs, images, videos
hyprlandCrashReport596824.txt

if it's not reproducible it could be anything, so closing. If you can repro, feel free to reopen


Relationship not work in v1.2.7

Hi guys, When I create new project Voyager

I choose version v1.2.6 it Works perfectly on creating relationship record
When I update version to v1.2.7 and creating with relationship It's not work

The issue template is not optional.
This can be reopened once the required informations are provided.


Info and error popup content copyable to clipboard; removes default snippets

This PR contains two changes.
The first is a simple usability win; info and error popup content is copyable to the clipboard, via a popup link/button below the content.
HTML tags are stripped from the content. Line breaks and general formatting are conserved. When the user presses the copy link, a status_message is printed confirming the text was copied.

This is the text copied to the clipboard:

The other change, which is not related to popup content at all, but which IMO is a big improvement as well, is getting rid of the snippets that are bundled with this plugin.
These snippets are all based on, or are identical to, the snippets that ship with Sublime Text's default JavaScript package, and which pretty much everyone agrees were a mistake.
Just to give one egregious example, the "improved" for loop:
for (var i = Things.length - 1; i >= 0; i--) {
    Things[i]
}

There are some good comments in that thread, especially from @Thom1729 , regarding why bundling snippets with a package is a bad idea, even if said snippets aren't as wacky as the one above.
Maybe someone thought copying Sublime's default JS snippets to this package would be comforting for existing Sublime users, but it was copying a misfeature, and just creates noise and makes autocomplete less useful for everyone.
I'd be glad to separate this into its own PR if it's necessary, but it seems like such a clear usability win that I figured the sooner it gets merged the better.

OK, so - the snippets feels a bit controversial?
I'm totally happy to get the copy button in, I copy this stuff all the time 👍

@orta
Brought the snippets back!
Fortunately, there's an upcoming ST build that's going to let us ignore default snippets using an ignored_snippets setting.
I also got the copy error functionality working again, it had broken because this PR was old and when I merged all the new commits into it there were a bunch of merge conflicts.
The sooner we get it merged the better!

@orta @DanielRosenwasser
Just bumping, because I think this is ready to merge =)

I will take a look at this but I need to get back home to NYC from my vacation to test this (I broke the last sublime text update, so I want to at least get my dev env set up to validate master and PRs are working as expected)
so thanks for the update! (and if you don't hear from me by next Friday, ping this PR)

@orta
Just bumping to see if you can eyes on this and we can get it merged. Thank you!


CQUI not working for persian empire

When my game started with Persian empire (Cyrus) CQUI was not working it was actually being conflictive, no access to production in cities and similar annoying issues. I tried to load a new game with a  different civ and it worked perfectly, so it seems it only occurs for Persia.

Hello, can you test with the latest update if you still have the issue ? If so, can you post the save game and the logs (next to the mod folder)


Thoughts on Deleting False Positives

There will come a time when infected keys are actually determined to be false or not infected. In this case, clients need to remove those keys from their local cache.
This thread is for discussion on how this should best work.
At its simplest level, not caching infected IDs would solve this, but this app is intended for mass distribution and potentially large numbers of infected keys over any 14 day span. Therefore scaling is important, since the entire set of keys can't be downloaded in the background by every client constantly.

A few of options off the top of my head:

What if the client included the list of infected keys that its cached when it makes a request to GET /api/infected? The server could then tell the client if the key is still valid or not. The client only needs to include keys from the last 14 days? Giving up infected keys is only sharing already published information. The downside is the client's request is going to get larger and larger the more infected keys it stores.

What if there was a new endpoint that published keys that have changed? So it works similar to GET /api/infected except it only returns a list of keys which have been determined to be false. The client could then compare that list with its cache and remove the offending keys.

What if the client never did any caching and instead always sent the keys it's seen. The server can respond with a list of keys that match only if there was infection. It's a hybrid of options 1 and 2. The downside is that all clients are giving up keys which have otherwise not been published so we have to trust the server is doing the right thing by not storing them. The other downside is that the client requests get larger and larger based on the number of keys its seen.

I think the problem is that the number of keys could potentially grow very large, so some level of caching is likely necessary.
I think your point 2 is the way to go. Although since the false positives list would be small it could just be included in /api/infected as a separate array.
Now that I've grouped each list of submitted keys in the server update I just committed, you could just flag a single submission and that'd also change the state of associated keys the be returned in the delete list.

I've begun implementing a compatible server with a similar objectives to this project. I've published the code under the same MIT license. It's compatible with this sample app as of ed96a6a309f81840f4ec7cea72fde077f7a77037. The repo is https://github.com/tatey/trace_privately.
Adding statuses is brilliant. Statuses with the since parameter will go a long way to making the server sustainable even if the number of keys grows. I'll go ahead and implement this soon.

Awesome! What’s the best way to link to it in this repos? Just a link in the KeyServer README?
Another thing I need to do is create a Swagger file for the API so we can ensure the interfaces line up across server implementations.

Awesome! What’s the best way to link to it in this repos? Just a link in the KeyServer README?

Sure, that sounds great.

Another thing I need to do is create a Swagger file for the API so we can ensure the interfaces line up across server implementations.

Makes sense. Would you like me to help with this?

FYI I've opened a bunch of issues on tatey/trace_privately so you can see what I'm thinking. Feedback welcome.

Thanks - I'll check those out.
Regarding the Swagger file - I've built one in the KeyServer/KeyServer.yaml file, based on the current iOS app implementation.
I'm sure it's by no means complete at this point, but it aligns with what the app currently supports at least (except for deleted keys, but I'm still working on that).


[RFR] [Feature] s3 bucket exception handling

Jira Issue OSF-5442
This is a resubmission of github PR #4851
Purpose
Periods in buckets are currently not allowed in Amazon s3 buckets on the OSF, although they are allowed by Amazon s3, because of restrictions in boto.  (for example "mybucket.with.periods") The new version of boto, currently in staging, will allow buckets with periods to be created, but not linked.  This will create a 500 error on the server and disrupts our error messaging.  The workaround is to set calling_format=OrdinaryCallingFormat() in S3Connection.  We already do this in bucket_exists.  (Thanks to @felliott for exploring this and being amazing).
Changes

set calling_format=OrdinaryCallingFormat() in S3Connection
set that periods are allowed in the exception handling.

Things to check

Buckets with and without periods should be added and linked.
Check case sensitivity for buckets, which should already be supported but just make sure.

The WaterButler side of this PR has been merged and updated on staging.

Sorry, this got closed automatically when the release/0.62.0 branch was deleted. @billyhunt Can you please resend this to release/0.63.0?


Exporting + Importing a profile with an icon doesn't preserve the icon

Testing #194038

On machine 1, create an empty profile "Zap" with the squirrel icon.
Export the profile to a file
On machine 2, import the profile. After clicking the "Create Profile" button, you'll see this:

The gear icon is shown in the "Create New Profile" quick pick, not the squirrel icon.

@alexr00 It is working for me. Can you please check if insiders is on latest on the second machine?

Yes, They were both on latest yesterday.

I tried again and it is working for me. Can you please share the profile?

Zap.code-profile.txt

Closing this issue as we can no longer repro it


run client failed with httpx.ReadError

Step1: Start the server with docker
docker run --rm -it -p 5000:5000 -v ~/.llama:/root/.llama --gpus=all llamastack/llamastack-local-gpu
Step2: run the client
python -m llama_stack.apis.inference.client localhost 5000
Logs:
(LStack) opea@acc:~/Repo/llama-stack$ python -m llama_stack.apis.inference.client localhost 5000
User>hello world, write me a 2 sentence poem about the moon
Traceback (most recent call last):
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpx/_transports/default.py", line 72, in map_httpcore_exceptions
    yield
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpx/_transports/default.py", line 377, in handle_async_request
    resp = await self._pool.handle_async_request(req)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpcore/_async/connection_pool.py", line 216, in handle_async_request
    raise exc from None
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpcore/_async/connection_pool.py", line 196, in handle_async_request
    response = await connection.handle_async_request(
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpcore/_async/connection.py", line 101, in handle_async_request
    return await self._connection.handle_async_request(request)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpcore/_async/http11.py", line 143, in handle_async_request
    raise exc
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpcore/_async/http11.py", line 113, in handle_async_request
    ) = await self._receive_response_headers(**kwargs)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpcore/_async/http11.py", line 186, in _receive_response_headers
    event = await self._receive_event(timeout=timeout)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpcore/_async/http11.py", line 224, in _receive_event
    data = await self._network_stream.read(
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpcore/_backends/anyio.py", line 32, in read
    with map_exceptions(exc_map):
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/contextlib.py", line 153, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
    raise to_exc(exc) from exc
httpcore.ReadError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/home/opea/Repo/llama-stack/llama_stack/apis/inference/client.py", line 178, in <module>
    fire.Fire(main)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/fire/core.py", line 135, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/fire/core.py", line 468, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/fire/core.py", line 684, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
  File "/home/opea/Repo/llama-stack/llama_stack/apis/inference/client.py", line 174, in main
    asyncio.run(run_main(host, port, stream, model, logprobs))
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
    return future.result()
  File "/home/opea/Repo/llama-stack/llama_stack/apis/inference/client.py", line 134, in run_main
    async for log in EventLogger().log(iterator):
  File "/home/opea/Repo/llama-stack/llama_stack/apis/inference/event_logger.py", line 32, in log
    async for chunk in event_generator:
  File "/home/opea/Repo/llama-stack/llama_stack/apis/inference/client.py", line 70, in chat_completion
    async with client.stream(
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/contextlib.py", line 199, in __aenter__
    return await anext(self.gen)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpx/_client.py", line 1628, in stream
    response = await self.send(
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpx/_client.py", line 1674, in send
    response = await self._send_handling_auth(
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpx/_client.py", line 1702, in _send_handling_auth
    response = await self._send_handling_redirects(
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpx/_client.py", line 1739, in _send_handling_redirects
    response = await self._send_single_request(request)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpx/_client.py", line 1776, in _send_single_request
    response = await transport.handle_async_request(request)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpx/_transports/default.py", line 376, in handle_async_request
    with map_httpcore_exceptions():
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/contextlib.py", line 153, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/opea/anaconda3/envs/LStack/lib/python3.10/site-packages/httpx/_transports/default.py", line 89, in map_httpcore_exceptions
    raise mapped_exc(message) from exc
httpx.ReadError

The problem is that the server runs on IPv6, but I don't know how to disable this using docker run

use docker run --rm -it -p 5000:5000 -v ~/.llama:/root/.llama --gpus=all llamastack/llamastack-local-gpu --disable-ipv6

add --disable-ipv6 make it works. Why should I use this options?  @Alevs2R

Fixed by --disable-ipv6


Qdrant client update

Description of changes
update qdrant client to latest, which makes use of fastembed.
Things done

Built on platform(s)

[ ] 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/)
23.11 Release Notes (or backporting 23.05 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

[ ] Fits CONTRIBUTING.md.

Just to be transparent about the latest force push.
I tested on a darwin x86_64 machine but then noticed that for fastembed, ofborg is failing with a network error, so I disabled the tests for fastembed.


Introduce two more directories for configs and tools - leave packages for real package

Which project is this feature idea for?
Turborepo
Describe the feature you'd like to request
Adding configs & tools directory to turbo default repo.
Please refer to the attached image.

The package directory to remain clean for the packages responsible for the core product.
Any configuration related artifacts is moved into a configs directory
Any tools for building the project, or its maintenance is put into a tools directory

This is to keep the apps and package directory clean and single purpose.

Describe the solution you'd like
The recommendation is for turbo repo to adapt the above  directory reorg, if possible.
Describe alternatives you've considered
Coming from NX, turbo is a fresh and clean start.  The alternative is leave things as they are now.
The tools/utils/src/loc.ts file uses loc command and injects the Line of Code into the REEADME.md. With the current structure, such scripts have to be put in the root directory, or in packages.  A dedicated tools directory is much cleaner.
Same thing for  the configs directory.

We're happy with the way the examples are structured now. Thanks for the suggestion!


fix typo in swarm/clster

Signed-off-by: kevinetc123<EMAIL_ADDRESS>

@kevinetc123 Thanks for the PR. While godoc says we should include punctuation in comments, in practice it's irrelevant for single line comments. Developers from different background have their own styles. You don't need to correct this issue, especially for old code.


Implement websocket security through xsuaa

Hi, Our project is deployed on SAP BTP, using xsuaa for permission verification. At present, we have a requirement to use websocket as a communication tool in the project, but at present I only found the example of the integration of Spring Security and websocket on the Internet, and I have not found the example of the integration of xsuaa and websocket. Is it feasible to implement websocket security through xsuaa? If it is feasible, is there any specific example for reference?

Hi @michael-kong
We don’t support authentication/authorization checks for spring-websocket, only spring security resource server, and therefore there is no example for:
<groupId>org.springframework</groupId>
<artifactId>spring-websocket</artifactId>

These are these references I've found in that context:

https://www.baeldung.com/spring-security-websockets
https://docs.spring.io/spring-security/site/docs/4.2.x/reference/html/websocket.html

This might be helpful to understand the way it’s currently implemented, like in spring-security hasRole() requires authorization the ROLE_-Prefix that’s why we’ve implemented XsuaaTokenAuthorizationConverter to be able to map it to local scopes.
I haven’t found any documentation in how to implement integration. But it might be similar to what is implemented with spring-security already?
Kind regards,
Nena

This issue is without any activity for 14 days or longer.
Thus, closing the ticket. Please reopen if the issue is still relevant.


added Recaptcha Mailhide plugin

https://github.com/mirko-pagliai/cakephp-recaptcha-mailhide

@dereuromark The suggestion of the VarCI-bot always appears after the pr has been sent. Can not it appear within the form of the pr when you send it?

No, it cannot. I fixed the missing link for you.
I do have a concern with the license you chose, however.
Is there any specific reason not to go with the recommended MIT license?

if you provide a service based on software you got under AGPL licensing, you need to provide free access to the complete software for the service

Basically, you prevent anyone from using this plugin in a commercial project - which contradicts a bit the idea of free and universally usable plugins afaik as we list them here.

I have no problem changing the license of my plugins.
In fact I'm not interested in knowing how they are used.

Please see https://github.com/FriendsOfCake/awesome-cakephp/blob/master/CONTRIBUTING.md#contribution-guidelines for the recommended license (MIT).

Okay, I can change the license with MIT. Only one thing though:

Basically, you prevent anyone from using this plugin in a commercial project - which contradicts a bit the idea of free and universally usable plugins afaik as we list them here.

I do not know where you read this/understand this. Are you sure?
It seems to me that with the AGPL license, you can use the code for commercial purposes. The difference with the GPL license is that if you modify the source, you must release your edit. Or not?

Yes, we are sure, we discussed that core internally as well.
AGPL is basically one of the strictest here.
See wikipedia etc.
Thanks for contributing by the way :)

Ok ;)

Done. Now I do it for other plugins as well

You need to also fix other places, e.g. https://github.com/mirko-pagliai/cakephp-recaptcha-mailhide/blob/master/composer.json#L6 for packagist to display it correctly.
You can also add a badge in the readme as img on the top bar :)

Done


Fix for orientation values 1-8

Included mocha locally to facilitate VS2015 with NTVS 1.1

Coverage remained the same at 98.821% when pulling ee129d1e5238d50a6c6758edac2f41e95ce4dfdb on jtobinisaniceguy:master into e576165cf1a5ca1feba086eb683f9e4e805fa11f on lovell:master.

Hello John, thanks for this fix for #382.
Are you able to update the relevant values in the withMetadata docs also?
I'd very much prefer not to introduce mocha to dependencies; test dependencies belong in the devDependencies section. If there's a specific platform this doesn't work on, I suggest the use of npm install -g mocha.

Will do today

Will push later today

Interesting if I have mocha installed locally, all test pass
When installed globally I get this

Input/output Handle Stream to Stream error :
Uncaught Error: EPERM: operation not permitted, open 'C:\Users\User Name\Documents\OpenSource\Sharp\test\fixtures\output.jpg'
at Error (native)

Some funny with mocha I believe

Sorry, I think I may have confused things. Please leave mocha where it is, in devDependencies. This PR should not require any changes to package.json.
Thanks for updating the docs. Please can you rebase against upstream/master and squash into a single commit and we can get this into the forthcoming v0.14.0.

Coverage remained the same at 98.821% when pulling 7a8aa41d6ff2857629ec0ac64f1a0d32f7242183 on jtobinisaniceguy:master into e576165cf1a5ca1feba086eb683f9e4e805fa11f on lovell:master.

Coverage remained the same at 98.821% when pulling 9ccc561a33cca4a5c16531d1a765ab2b47ef9e81 on jtobinisaniceguy:master into e576165cf1a5ca1feba086eb683f9e4e805fa11f on lovell:master.

Thanks for the changes, looking great. Are you able to squash into a single commit? I notice the commits are from (or at least are linked to) a different Github account - is this intentional?

Landed in ebfc897, thank you!


Update default card in Stripe when an existing donation is updated

For now we can keep it limited like this.

Fixed in 128947b94303cffd1534f6745b1cc10d71bf48b1 and f469d17e1bd3f543dfdf38d7d4779bcbf053e990


Flag to setLogLevel to verbose

Hey, is it any chance to wrap this feature as well?
I can turn on the dry run mode, but there's no possibility to check what's going on inside the lib itself.

Hi @pukhalski
I have been considering making this available, but I am sort of torn. One of my requisites for features making it into this library is that it can be easily used cross-platform. I'd like the feature-parity to be as good as possible.
Therein lies the problem; on Android the LogLevel & Logger itself has been deprecated in favor of using the standard Android log system with logcat.
The iOS library instead relies on the GA Logger.
I am considering implementing a solution for iOS, where this can be configured by a Info.plist setting, so that it does not impact the JS API.

It'd be nice to have. Also you can switch the logger behind the scenes - provide native for android and GA Logger for iOS, right?
Anyway, I need one of my two tickets to be resolved to actually use your library for production projects.
Thank you so much for your work! Appreciate that!

Hi, because of the divergence between the platforms I decided to let this be configurable via the Info.plist.
You can add an item with the key GAILogLevel  and set the log level (a number) according to your needs;

0: None
1: Errors
2: Warnings
3: Info
4: Verbose

Amazingly done! Thanks!


Overwolf's launcher can't detect POE client

🐞 bug report
Describe the bug

The launcher cannot detect that POE client is running, probably due to my client being the KR server client through Daum/Kakao publisher.
To Reproduce

PoE Overlay launched.
Wait for overlay launcher to show waiting for poe to launch.
Launch PoE through https://poe.game.daum.net/ launcher
/////
1A. Launch PoE through https://poe.game.daum.net/ launcher
2A. start overwolf PoE overlay

In either case, PoE Overlay cannot detect that PoE is up and running.
Expected behavior

PoE Overlay should run.
Screenshots

🌍  Your Environment

Version:  e.g. 0.6.9 portable
Not sure where to find the version, but I'm guessing it's 1.0.2 overwolf since I downloaded it on 19 Jun 2020.
PoE:  e.g. Steam 3.10.0/e English
KakaoGames 3.10.2d English locale

checking the program files, it tells me PoE Overlay version was 1.0.3

Same problem for me.

Same here

Same here too

Hi, thanks for creating an issue. The KAKAO version is currently unsupported. Overwolf is working on a fix. It should be working soon 1-3 days.

Hi, thanks for creating an issue. The KAKAO version is currently unsupported. Overwolf is working on a fix. It should be working soon 1-3 days.

thank you, will it be included in the next patch in 1.0.3 or hotfixed?

thank you, will it be included in the next patch in 1.0.3 or hotfixed?

This should get hotfixed. It's a small change at the Overwolf client which should get this over the air. They're already working and testing it. They just need to make sure everything works correctly. I'll keep you updated.

Overwolf just pushed an update for this to be supported. You may need to restart the Overwolf client once. Can you please report back? Thanks!

Overwolf just pushed an update for this to be supported. You may need to restart the Overwolf client once. Can you please report back? Thanks!

it's working fine now! thank you


Multifield validations for coral3 ui fields 1455

@schoudry / @justinedelson  - extjs review anyone? :)

@Narayan15 can you please fix the indentation for better review of changes

Please see the changes requested by @davidjgonzalez and raise the PR when done.  Thank you!


fix typo: "Kuberentes" -> "Kubernetes"

fix "Kuberentes" -> "Kubernetes" and rename file

/assign @natekartchner

@JoeWrightss please rebase and resolve the conflict.

/assign


new scope and other breaking changes.

Breaking Changes  (draft)
These changes are trying to simply a lot of duplicated codes and unite a lot of functions for future implementations.
So it will break a lot of original non-unified usages intentionally.
*As well as addressing the new scope change. #193
Just shout out if you don't like it since there are just draft ultimately.
Scope Change:
the scope scopename_READ_WRITE  =>  scopename_WRITE as its true intent.
It seems like the original scopename_READ_WRITE cause a lot of confusion for implementations.
so we will have scopename_READ and scopename_WRITE respectively.
Note: If you encounter something like the user must be signed in to make this api call. You are most likely missing the scope during the authentication process.
Function call:
Some functions require callback as arg, some do not, which causes distraction and confusion among utilizing different function calls.
Since the callback also causes many code duplication/nesting, and useless/misleading bug reports (many nesting callback functions only return customize "there is not data" instead of the true bug that cause data fetching failing).
I decided to remove the callback argument,  support async/await syntax, and directly getting error from native module.
The return data structure hopefully will remain unchanged for successful call. The difference might be the error handling.
So the usage of all functions will simply become
    GoogleFit.SomeFunction(options).then((result) => {
        console.log(result)
    });
  //or with async/await syntax
    async function fetchData() {
      const result = await GoogleFit.SomeFunction(options)；
      console.log(result);
    //do your own task based on the result
    }

These wouldn't not longer work in this merge:
const callback = ((error, response) => {
  console.log(error, response)
});

GoogleFit.SomeFunction(options, callback)

GoogleFit.SomeFunction(options, callback(error, response)=>{
 console.log(error, response)
})

this may take a while.

[x] getDailyStepCountSamples
[x] getDailyDistanceSamples
[x] getActivitySamples
[ ] getDailyCalorieSamples
[ ] getDailyNutritionSamples
[ ] getWeightSamples
[ ] getHeightSamples
[ ] getHeartRateSamples
[ ] getBloodPressureSamples
[ ] getHydrationSamples
[ ] getSleepData

Thank you for these changes!
Especially the new async direction.
May I also suggest/ request?

Body-Fat percentage

lift the location permission from the manifest, leave it to the user to use it if they are willing to ask for location permission, otherwise, users (of the lib) might be just interested in health/ activity data.

Thank you, I really appreciate your work, and if anything I could to help I'd be happy to.

Thank you for these changes!
Especially the new async direction.
May I also suggest/ request?

Body-Fat percentage
lift the location permission up from the manifest, leave it to the user to use it if they are willing to ask for location permission, otherwise, users (of the lib) might be just interested in health/ activity data.

Thank you, I really appreciate your work, and if anything I could do to help I'd be happy to.

Most permissions can be requested from permissionAndroid without the need to place permissions into AndroidManifest.xml. Place those permissions into the file will just auto guarantee normal permissions without the request process. So for "dangerous" permissions like location you still need to request. This is based on my own judge from doc and some random Stackoverflow posts Please correct me if I'm wrong.
I did write a request location permission helper function long time ago for fixing recording() when involved recording distance data. Probably I should just reuse the function and do a request check before any functions that requires location permission. Also for other permissions.

Thank you for these changes!

Especially the new async direction.

May I also suggest/ request?

Body-Fat percentage

lift the location permission up from the manifest, leave it to the user to use it if they are willing to ask for location permission, otherwise, users (of the lib) might be just interested in health/ activity data.

Thank you, I really appreciate your work, and if anything I could do to help I'd be happy to.

Most permissions can be requested from permissionAndroid without the need to place permissions into AndroidManifest.xml. Place those permissions into the file will just auto guarantee normal permissions without the request process. So for "dangerous" permissions like location you still need to request. This is based on my own judge from doc and some random Stackoverflow posts Please correct me if I'm wrong.
Nvm, you are right. I just realize I have to place dangerous permissions on AndroidManifest.xml in order to use permissionAndroid.
I did write a request location permission helper function long time ago for fixing recording() when involved recording distance data. Probably I should just reuse the function and do a request check before any functions that requires location permission. Also for other permissions.

Thank you for your reply. furthermore, gradle plugin merges manifests on build, so when lib users include it in their app, even if they don't a location-based feature, their package still shows a location permission on Google Play. Because the lib requests it in its manifest:

So what I was suggesting was to lift it up (line 3 in the manifest) from the lib, and let the user add it if their app utilizes a feature that requires location permissions. Thanks

@mhashim6  I see your point. Probably just remove the line and tell users to add the line to their  own manifest file on Readme.

@mhashim6  I see your point. Probably just remove the line and tell users to add the line to their  own manifest file on Readme.

Exactly, I'd be happy to make a PR if you don't have the time.

@mhashim6  I see your point. Probably just remove the line and tell users to add the line to their  own manifest file on Readme.

Exactly, I'd be happy to make a PR if you don't have the time.

Go ahead but it's a little bit trick. I believe that's the only function that requires the permission if you include distance to the list.
GoogleFit.startRecording((callback) => {}, ["distance"]);

@mhashim6  I see your point. Probably just remove the line and tell users to add the line to their  own manifest file on Readme.

Exactly, I'd be happy to make a PR if you don't have the time.

Go ahead but it's a little bit trick. I believe that's the only function that requires the permission if you include distance to the list.

GoogleFit.startRecording((callback) => {}, ["distance"]);

It shouldn't be an issue, code itself won't change. Users won't be able to use startRecording without including the location in their app manifest. It's just a handoff of responsibility.

@mhashim6  I mean where to put the reminder in readme, since we don't need the line for other functions.

@mhashim6  I mean where to put the reminder in readme, since we don't need the line for other functions.

Oh okay got it wrong first. Will do that.

@davidguerrerolopez sleep function is rewritten due to the new scope change, probably you might want to take a look.

Looks great! Gonna release minor version update

If possible, can you add some breaking change warning if people want to do any  npm update from old versions to this merge. I'm not exactly sure how this is handled, as well as the release tag thing.
In case if something is wrong even though I test all of them from some devices.

lets then release a major version


Document How to Set Up and Run Migrations

Add some better documentation around how to run migrations.
See #119

Add some better documentation around how to run migrations.
See #119

@ardalis This should be covered by this PR Update Headers


Keep borders square for simplicity

Nice temporary solution. Merging.
Please follow the Contributor's Guide in the future.


Handle empty cache file

I added two commits toward fixing issue #9
First, added a test case in test_skybell.py and ran 'tox' showing that it is in fact a problem.
Second, updated init.py to check for a zero size file, and if so remove it.
Third, re-ran test case in 'tox' showing it works now.

Coverage remained the same at 100.0% when pulling b8aac9996d59a9df7cb804399110dfd3db96c0ba on austinmroczek:master into 40968315dd241affae3d45c422d3dba11f2f81c3 on MisterWil:master.

@MisterWil please take a look


Concerning change - do not retire legacy exchange PowerShell commands

The retirement of Search-mailbox cmdlet is a concerning change. We use this frequently in conjunction with -deletecontent to search for and delete phishing mails that have landed in inboxes. The removal of this function without an apparent replacement to delete the content found opens our and other organizations to dangerous phishing mails that need to be removed as quickly as possible.
If I have missed the replacement feature to also allow us to quickly remove malicious email using eDiscovery my apologies, however so far I do not see a rapid way to remove malicious emails before employees might click on them.

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

ID: 34b8bac8-ffc4-8c4c-2d59-f27a96dbd414
Version Independent ID: b78fa02e-9ae3-fa72-e23a-f70cf96d2e0f
Content: Legacy eDiscovery tools retired - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/legacy-ediscovery-retirement.md
Service: o365-seccomp
GitHub Login: @v-tophillips
Microsoft Alias: v-tophillips

@TimD1999 Thank you for your feedback. I was able to perform New-ComplianceSearchAction -Purge command in Security & Compliance PowerShell to delete the message. You can use the below document to use the search and purge feature which replaced the existing search-mailbox cmdlet
https://docs.microsoft.com/en-us/microsoft-365/compliance/search-for-and-delete-messages-in-your-organization?view=o365-worldwide
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @TimD1999 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Quests with periods in name cause major issue.

After much digging around through player data files of those who were having problems with quests on my server, I was finally able to track down the offending quest, but more importantly the reason why.
If a quest name has a period in it (apostrophe seems fine, more testing needed), for example we had put one to abbreviate "Part 1" down to "Pt. 1", will incorrectly save into the player's data file.
Example:
currentQuests:

Bow of Stars Pt. 1
questData:
Bow of Stars Pt:
' 1':
item-delivery-amounts:
- 0

The issue is in "questData", where the stored name does not reflect the full quest name. The player can accept the quest just fine, but anything quest-related done after that fact results in an error, effectively breaking that player's ability to utilize quests. Removal of that quest from a player's file while they are logged out resolves the issue and stops errors in the console (even on quit). Unfortunately, each time a player joins who has that issue, it needs to be addressed.
A way to have it auto-purge a quest that is erroring in the data files of players (not matching anything in the Quests.yml), would be a huge help!

Thanks for looking into this! This is likely an issue with how YAML reads/write files (with periods often separating each node). While there likely is a workaround for this, it is somewhat intentional, so I ask that you just don't use periods in quest names for the time being.


Analysis of  discarded_futures and unawaited_futures does not work for tearoffs used as arguments and, in closures, is dependent on whether enclosing function is async

Issue description
As the title says the analysis of the discarded_futures and unawaited_futures does not work for tearoffs used as arguments. Futhermore, in closures, the reporting of issues is dependent on whether the enclosing function is async or not (instead of evaluating that for the closure itself). Finally, unawaited completely disables issue reporting for all futures used inside it, even if they are discarded in closures, which can lead to errors.
The following examples were analyzed using dart analyze, with the rules discarded_futures and unawaited_futures enabled.
I have created a gist here, which contains the execution logs of these examples, along with some print statements, to show that this incomplete analysis can lead to errors in real-world applications.
Example 1 (analysis does not work for tearoffs used as arguments + in closures, is dependent on whether enclosing function is async)
In this example, loadFromRemote is a function that returns a Future<void>. execute accepts a callback which is a function that returns a void. Therefore, by calling callback, the future returned by loadFromRemote is discarded, without the use of unawaited or ignore [unexpected].
import 'dart:async';

Future<void> loadFromRemote() async {
  await Future.delayed(const Duration(seconds: 1));
}

void execute(void Function() callback) {
  callback();
}

void load() {
  execute(loadFromRemote);
}

Notes:

If loadFromRemote is called inside a closure, with () => loadFromRemote(), the discarded_futures lint rule creates an issue [expected]. If, after this change, load is modified to be async, the issue disappears [unexpected].

Example 2 (in closures, is dependent on whether enclosing function is async)
In this example, there are two functions, tryLoadFromRemote and tryLoadFromCache that both return Future<void>. Then, there is a function, load, that also returns Future<void> and is async. tryLoadFromCache is used in load and is awaited, but tryLoadFromRemote, which is used inside a sync closure in then, is not awaited and, because of that, is discarded. No issue is reported on the tryLoadFromCache call [expected], but the tryLoadFromRemote call does not report any issues [unexpected].
import 'dart:async';

Future<void> tryLoadFromRemote() async {
  await Future.delayed(const Duration(seconds: 1));
}

Future<void> tryLoadFromCache() async {}

Future<void> load() async {
  await tryLoadFromCache().then((_) {
    tryLoadFromRemote();
  });
}

Notes:

If the signature of load is changed to void load() and the await keyword is removed, both calls report issues [expected]. If the code is wrapped in unawaited (see below), no issues are reported on the tryLoadFromCache call [expected] and on the tryLoadFromRemote call [unexpected].
void load() {
  unawaited(tryLoadFromCache().then((_) {
    tryLoadFromRemote();
  }));
}

General info

Dart 3.5.3 (stable) (Wed Sep 11 16:22:47 2024 +0000) on "linux_x64"
on linux / Linux 6.11.3-200.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Oct 10 22:31:19 UTC 2024
locale is en_US.UTF-8

Process info

Memory
CPU
Elapsed time
Command line

331 MB
133.0%
00:02
dart language-server --protocol=lsp --client-id=VS-Code --client-version=3.98.1

79 MB
22.0%
00:02
dart tooling-daemon --machine

Should it work?
The discarded_futures lint says that it warns if an asynchronous function is called within a non-async function. Likely just if anything produces a Future inside a non-async function.
There is no value of type Future in the load function of the first example.
There is a function of type Future Function() which is cast to void Function(), which is a sign that a Future will likely be lost somewhere, but that's not something that making the load function async and adding an await can fix, so it's not really within the parameters of discarded_futures.
If load is made async, the same argument applies to unawaited_futures. This is not a problem that can be fixed by adding an await.
In the second example, the tryLoadFromRemote() call should trigger discarded_futures. It might be confused by being "inside an await". That does look like a bug.

There is a function of type Future Function() which is cast to void Function(), which is a sign that a Future will likely be lost somewhere, but that's not something that making the load function async and adding an await can fix, so it's not really within the parameters of discarded_futures.
If load is made async, the same argument applies to unawaited_futures. This is not a problem that can be fixed by adding an await.

Hey, thanks for your input!
To me, it makes sense that there should be a lint issue. The correct fix I thought of for that example would be
void load() {
  execute(() => unawaited(loadFromRemote()));
}

It is a lot more verbose, but, this way, the future is explicitly discarded, instead of implicitly, which is what the discarded_futures lint rule tries to avoid.

In the second example, the tryLoadFromRemote() call should trigger discarded_futures. It might be confused by being "inside an await". That does look like a bug.

From what I tested, it's more like it's dependent on the async keyword in the load method. I think it's because discarded_futures skips analysis for async functions.
For instance, if the keyword gets removed and the future is returned instead of awaited, the code is still valid and discarded_futures reports an issue in the tryLoadFromRemote call.


set local k3s to 1.22.7

1.23 is experimental for 2.6.4, so setting default to 1.22. Changing packaged binaries back to containerd because it was
an update specific to 1.23 k3s.

https://github.com/rancher/rancher/issues/37067


Replies not being discarded

+ Hi *
- Hey!
- Hi, good to see you!
- Hey, welcome back!
- Hello to you too!

In this simple example if you type "Hi" again and again you can get the same replay even three times in a row. This isn't working as expected I presume.
I am testing on a the latest master (1.1.3) mongo 3.4.10, node v6.8.1

I don't believe it's super clear in the documentation yet, but on further inspection, any gambits (reply pairings of +-) at the root level in superscript are kept (with {keep}) implicitly and are placed in the random topic. To discard the a response one needs to create a topic (without {keep}) then place the gambit inside (with {ordered}). Here's an example I got to work just now:
> topic greeting (Hello, name)
  + {ordered} Hello
  - Howdy!
  - Bounjour.
  - Allo
  - Hola
  - Suh
  - We've said hello already
< topic

> topic random
  + Hello
  - Switching to greeting topic {topic=greeting} ^respond("greeting")
< topic

So here you'll get "Switching to random topic Howdy!" from random.Hello, followed by all of the responses in Greeting.Hello on subsequent "Hello"s submitted from a client.
I hope that helps!


Add update to list of special methods

In my apps, I use for my Views just the basic set of endpoints - index, new, post, show/get, edit, update.
I like how post uses method=["POST"] automatically, and it would be nice to have the same on update method.
This will be less usefull when we will have @method decorator, but still - just a suggestion.
Why don't I use put? Well, you can't use put in <form>. In API Views I'll of course use REST methods, but here I want my CRUD set ;)
Priority: none.
Just an idea. I realize this might also be breaking change (if someone uses update with GET method), so probably not worth it.

I don't consider this of much use, using @method("post") is simple and straightforward enough.


-es.uri in deployment.yml not picked up with  prebuilt binary

Hi Team,
First of all, Thank you for providing elastic search exporter.  i am trying with prebuilt binary "elasticsearch_exporter-1.0.3rc1.linux-amd64.tar.gz" from the link,
https://github.com/justwatchcom/elasticsearch_exporter/releases .  tried changing -es.uri in deployment.yml , some how its always picking "localhost:9200", no matter what host i give.  Any inputs.
Thanks ,
Ravi.

Hi @helloravisha,
I can't reproduce your issue. Can you give some context how you deployed the exporter?

closing this as I didn't get a reply. Don't hesitate to reopen if you encounter the problem


uint not defined in THClGeneral.h on MacOS 10.11.6

When attempting to build PyClTorch on MacOS 10.11.6 with Apple llvm 7.3.0 against cltorch b578d9c, the compiler complained about uint at THClGeneral.h#L148 not being defined. Should there be a typedef unsigned int uint; in the preceding lines?

Interesting.  Seems like that should be uint32, rather than simply uint.  I cant really remember if htats intentional or not.  Trying on Travis Mac OS X build, after changing to uint32, https://travis-ci.org/hughperkins/distro-cl/builds/159285525 Let's see what happens...

Build seems to have passed https://travis-ci.org/hughperkins/distro-cl/builds/159285525  . If you use branch tweak-int of distro-cl, (or perhaps of cltorch) to what extent does this build more completely?

I would hazard a guess that you could use uint without a typedef on Linux because the stock compile options passed to gcc by distutils didn't force it to comply with whatever recent c++ spec that no longer defines it.

Alright.  Can you confirm that the tweak-int branch works for you? If it does, I'll merge it to master.

Yes - tweak-int fixes the problem with pycltorch.

Cool :-)


Direct ingestion/delta counter support

Refactored to extend https://github.com/mikejihbe/metrics instead of forking it
Refactor involved deleting all existing files and only extending the reporters. We export the necessary files through top level exports.
Added support for direct ingestion and delta counters
Added unit tests for the same

reviewers: @vmwchuj and @lokeshgahlot


Improve test reliability

Improved tests reliability, introduced retry, fixed typo in class name.

/azp run session-singleregion-https-tests

Closing as stale


greekToEnglish function optimization

https://github.com/Go-phie/gophie-web/blob/master/src/utils/index.js#L108
The codeblock here can be optimized to use the regular myMap.get(key) instead of the for statement.
@SLKhadeeja You could look into this :)

greekToEnglish is supposed to get key from value not the other way around
-------- Original message --------From: Mmadu Manasseh<EMAIL_ADDRESS>Date: 11/05/2020  10:05 pm  (GMT+01:00) To: Go-phie/gophie-web<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [Go-phie/gophie-web] greekToEnglish function optimization (#77)
https://github.com/Go-phie/gophie-web/blob/master/src/utils/index.js#L108
The codeblock here can be optimized to use the regular myMap.get(key) instead of the for statement.
@SLKhadeeja You could look into this :)
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/Go-phie/gophie-web/issues/77",
"url": "https://github.com/Go-phie/gophie-web/issues/77",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

What's the inspiration for that? Why not the other way round?

If you look at the movie object, it comes from gophie core with it's source in english... hence the function to convert it to greek and the map to convert greek to english... basically just to avoid writing names anywhere else except this file
-------- Original message --------From: Mmadu Manasseh<EMAIL_ADDRESS>Date: 11/05/2020  11:06 pm  (GMT+01:00) To: Go-phie/gophie-web<EMAIL_ADDRESS>Cc: Diretnan Domnan<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Go-phie/gophie-web] greekToEnglish function optimization (#77)
What's the inspiration for that? Why not the other way round?
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/Go-phie/gophie-web/issues/77#issuecomment-626991023",
"url": "https://github.com/Go-phie/gophie-web/issues/77#issuecomment-626991023",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

Okay


--mimikatz not working

Hey,
I got a problem with the --mimikatz option. When I try to execute mimikatz on the remote system, the executing hangs after: "Executed command via WMIEXEC". That happen on all systems here. Several other options like -x CMD are working just fine. How is mimikatz executed on the remote system or how it is transfered to the remote system? Maybe any firewall restriction are responsible for that?

@schniggie gonna need more info, target OS & architecture and a packet capture would be awesome. Just tested it on my systems and it seems to be working fine

Closing this for now as it seems to be working for me, comment below if you have time to give me some more info

Hi there, I know it has been closed as no further info was provided, but I'm facing the same issue. My guess is that the target system doesnt have the proper proxy settings in order to download the mimikatz payload from the Kali (does it setup a web server and tell the target host to go and download it ?). Anyhow, I guess there might be some way to send mimikatz via -x CMD as à one liner, but that is beyond my personal expertise


[BrokenLinksH2] Fix path in link

Fixing broken links

Docs Build status updates of commit ba73838:
:warning: Validation status: warnings

File
Status
Preview URL
Details

windows-iotcore/learn-about-hardware/iotnxp.md
:warning:Warning
View
Details

windows-iotcore/learn-about-hardware/DriverCreation.md
:white_check_mark:Succeeded
View

windows-iotcore/learn-about-hardware/HardwareCompatList.md
:white_check_mark:Succeeded
View

windows-iotcore/learn-about-hardware/PinMappings/PinMappingsMBM.md
:white_check_mark:Succeeded
View

windows-iotcore/learn-about-hardware/SoCsAndCustomBoards.md
:white_check_mark:Succeeded
View

windows-iotcore/manage-your-device/AzureIoTDM.md
:white_check_mark:Succeeded
View

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded
View

windows-iotcore/manage-your-device/NetworkPacketCapture.md
:white_check_mark:Succeeded
View

windows-iotcore/release-notes/commercial/April2018Update.md
:white_check_mark:Succeeded
View

windows-iotcore/learn-about-hardware/iotnxp.md

Line 51, Column 58: [Warning: link-text-missing - See documentation] Missing link text for link ''. Add appropriate text.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 352e4c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/Resources.md
:white_check_mark:Succeeded
View

windows-iotcore/learn-about-hardware/DriverCreation.md
:white_check_mark:Succeeded
View

windows-iotcore/learn-about-hardware/HardwareCompatList.md
:white_check_mark:Succeeded
View

windows-iotcore/learn-about-hardware/PinMappings/PinMappingsMBM.md
:white_check_mark:Succeeded
View

windows-iotcore/learn-about-hardware/SoCsAndCustomBoards.md
:white_check_mark:Succeeded
View

windows-iotcore/learn-about-hardware/iotnxp.md
:white_check_mark:Succeeded
View

windows-iotcore/manage-your-device/AzureIoTDM.md
:white_check_mark:Succeeded
View

windows-iotcore/manage-your-device/DevicePortal.md
:white_check_mark:Succeeded
View

windows-iotcore/manage-your-device/NetworkPacketCapture.md
:white_check_mark:Succeeded
View

windows-iotcore/release-notes/commercial/April2018Update.md
:white_check_mark:Succeeded
View

windows-iotcore/release-notes/commercial/October2018Update.md
:white_check_mark:Succeeded
View

windows-iotcore/tutorials/intel.md
:white_check_mark:Succeeded
View

windows-iotcore/tutorials/quickstarter/DeviceSetup.md
:white_check_mark:Succeeded
View

windows-iotcore/tutorials/quickstarter/PrototypeBoards.md
:white_check_mark:Succeeded
View

windows-iotcore/windows-ce-app-container-getting-started.md
:white_check_mark:Succeeded
View

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel


PR: Add unambiguous file names to Breakpoints pane

Description of Changes

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

When having breakpoints in files with the same name, it was hard to tell the difference. (Although I realized at a rather later stage that there was a tooltip hover on the file name with the full path.) This PR adds unambiguous file names to the Breakpoints pane.

It should also be slightly more efficient as the name is only computed once per data update.
I also added/corrected an icon for the Breakpoints pane. After some deliberation, I thought that mdi-dots-vertical probably was the best I could find. Three stacked dots.
Earlier, it was the profiler icon, although it wasn't shown in the menu.
In addition, I right-aligned the line numbers (not shown in the screen shot), and refactored the code a bit, using constants for the different columns.
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: Oscar Gustafsson/@oscargus

Hello @oscargus! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/breakpoints/plugin.py:

Line 88:36: E128 continuation line under-indented for visual indent

Maybe mdi-dots-vertical is an option. Three stacked dots.

Oh, I realized that I want to right-align the line numbers. I'll add it to this PR as well.

@dalthviz, please review this one.

Tanks @dalthviz ! I changed the indentation (I thought that it pointed to breakpointsgui.py where I had a more obvious issue on the same line number in an earlier commit and that it hadn't updated...).

I have a question: What's shown to the right of the "Condition" column? I mean, if nothing is shown there I think we should show the entire path of the file containing the breakpoint.

That is the "default" empty column that show up in most of these "table style" widgets. I can for sure add the full path there and post an image of it (it may be a bit cluttered on small displays or if one undock and makes it narrow, but apart from that I think it makes sense)

Here are the results.
With unambiguous file names kept:

Without unambiguous file names:

I think that the last one is quite confusing as one will have to look at the right to figure out which file is which.
For the first, I'm personally not sure that it actually adds something.
(But I found a bug, so will update. Turns out that all filenames that ever had a breakpoint is stored in the breakpoint data structure, so removing breakpoints for a file still takes it into account when determining the name.)
I was considering that maybe adding the line content may help in navigating. The problem there is that the file may not be open, so probably not a good idea.

After seeing your first screenshot above, I think there's too much info in the Breakpoints pane if we add file paths to it. So we should go with your current improvement.
Thoughts @goanpeca?

add file paths to it

Agreed lets keep it simple!

@dalthviz, could you post a screenshot with the new icon introduced by @oscargus? Thanks!

@ccordoba12 a preview of the icon:

@dalthviz, I don't like that, so please remove it. We don't have the custom to assign icons to plugins, so I don't want this to be the exception.

I can remove it.
And, well, the plugins do have icons. Should I remove all of them?
Den tors 8 aug. 2019 12:25Carlos Cordoba<EMAIL_ADDRESS>skrev:

@dalthviz https://github.com/dalthviz, I don't like that, so please
remove it. We don't have the custom to assign icons to plugins, so I don't
want this to be the exception.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/pull/9913?email_source=notifications&email_token=AB55CQMSI6YJ6YDYY7WBOH3QDPYDJA5CNFSM4IHVDODKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD33FXCQ#issuecomment-519461770,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB55CQKTFNIOT5B7SMP5OS3QDPYDJANCNFSM4IHVDODA
.

All back as before with the profiler icon for the breakpoints plugin (I had to use the light theme as the icons have the same color as the program bar in the dark theme).

All back as before with the profiler icon for the breakpoints plugin (I had to use the light theme as the icons have the same color as the program bar in the dark theme).

@oscargus, I'm very sorry, I forgot that we do have icons for some plugins (like the Profiler and Find). Then I think it's find to use the three vertical dots as an icon for the Breakpoints plugin (I can't think of a better one right now).
Could you remove your last two commits and force-push to this branch again? Thanks!

Done! (I think, the earlier two commits with the same name only showed up once in the rebase, but it looks OK.)


Auto-populate relevant fields on New Record form

Auto-populate relevant fields on New Record form when passed given information.
Example: If a new record is created from a link on a ticket page, that ticket id should be carried over to the form (@record.ticket_id on records#new)

Feature added in commit: c60417e5d1f16d0b658254ad4db7e626643c346c
Enhance request closed.


URL Encode SMTP user & passowrd

[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs for a specific extension in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general Firebase discussion, use the firebase-talk
google group.
To file a bug against the Firebase Extensions platform, or for an issue affecting multiple extensions, please reach out to
Firebase support directly.

[REQUIRED] Step 2: Describe your configuration

Extension name: firestore-send-email
Extension version: 0.1.10

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Consider the following SMTPS URI: smtps://XXX:XXX/X+XXX@email-smtp.eu-west-1.amazonaws.com:465.
If passed into nodemailer / firestore-send-email configuration will result in following error when attempting to send email: getaddrinfo ENOTFOUND XXX.
To resolve an issue the password and username have to be URL encoded, which is not mentioned anywhere in the configuration description.
Expected result
There is a not-to URL encode the password and username.
Actual result
There is no such note, which results in confusing error message.

Thanks @alfredsgenkins.
I have updated this for consideration.

We should be able to update the extension itself to use encodeURI so that someone installing the extension doesn't need to figure out encoding

I think the problem is that there are no password/username fields. It is required to parse the URL with regex, then encode the result, then use it as a new URI. The biggest problem here would be the case of a password or username containing the :. This could lead to the wrong detection of username and password.
Maybe instead, we should switch to declarative transport declaration schema. The port, host, protocol, credentials should be separate fields. In this case, no URL encoding is needed.
Alternatively, the simple notice could be shown in the configuration.

@alfredsgenkins @jhuleatt  After some initial testing, I feel this may be difficult to implement.
Decoding the uri
We have specific regex for the smtp uri. With a decoded url, this would make it difficult to provide an alternative encoded regex pattern.
Splitting the uri
This would solve the issue but add extra complexity with more parameters and a longer installation process.
As we cannot simply insert an encoded uri, it would perhaps be easier for the user to simply encode the urls manually?

this is being discussed internally on what's the best way to move forward. Stay tuned!

@dackers86 since according to this link  usernames shouldn't have colons in them, I think we can solve this in the extension. Just assume the first : and the last @ as the separator and encode them before sending them to sendmail

FWIW, the firebase authentication mechanism accepts smtp configuration as a form of hostname, username, password, port and it encodes username password correctly