Added configurable delimiters support to Config object

Added configurable delimiters support which is a modified version of #381
@mike1158, @shootfast, @mplec and @lgritz can you take a look also

What do you think colorspace name should be returned from this string "somefile-Gamma22-ACEScg.exr”? Currently we return the longest right most colorspace name e.g. Gamma22 not ACEScg. This is what the old code looked like it did but maybe now with delimiters it should just be the first delimited colorspace found (ACEScg in this example).
I have set the default delimiters to be [-, _, /, , .] what are your thoughts?
Note. To get the old behaviour you just need to add ‘’ to the delimiters list.

-- CHANGES

added getNumDelimiters()
added getDelimiterByIndex()
added addDelimiters()
added clearDelimiters()
added containsToken()
Set default delimiters  [-, _, /, , .]
Updated parseColorSpaceFromString to use containsToken()
Added unit tests for containsToken() and parseColorSpaceFromString()
Updated pyglue and jinglue bindings
Added missing EnvironmentMode.java file

Makes sense to me. There probably aren't too many cases where that was an
issue, but it's definitely better to be open to different file naming
conventions.
On Thu, Sep 22, 2016 at 1:44 AM, Malcolm Humphreys<EMAIL_ADDRESS>
wrote:

Added configurable delimiters support which is a modified version of #381
https://github.com/imageworks/OpenColorIO/pull/381
@mike1158 https://github.com/mike1158, @shootfast
https://github.com/shootfast, @mplec https://github.com/mplec and
@lgritz https://github.com/lgritz can you take a look also

What do you think colorspace name should be returned from this string
"somefile-Gamma22-ACEScg.exr”? Currently we return the longest right most
colorspace name e.g. Gamma22 not ACEScg. This is what the old code looked
like it did but maybe now with delimiters it should just be the first
delimited colorspace found (ACEScg in this example).
I have set the default delimiters to be [-, _, /, , .] what are your
thoughts?
Note. To get the old behaviour you just need to add ‘’ to the
delimiters list.
-- CHANGES

added getNumDelimiters()
added getDelimiterByIndex()
added addDelimiters()
added clearDelimiters()
added containsToken()
Set default delimiters [-, _, /, , .]
Updated parseColorSpaceFromString to use containsToken()
Added unit tests for containsToken() and parseColorSpaceFromString()
Updated pyglue and jinglue bindings
Added missing EnvironmentMode.java file

You can view, comment on, or merge this pull request online at:
https://github.com/imageworks/OpenColorIO/pull/413
Commit Summary

Added configurable delimiters support to Config object

File Changes

M export/OpenColorIO/OpenColorIO.h
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-0 (20)
M src/core/Config.cpp
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-1
(203)
M src/core/OCIOYaml.cpp
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-2 (23)
M src/core/TruelightTransform.cpp
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-3 (1)
M src/jniglue/JNIConfig.cpp
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-4 (56)
M src/jniglue/org/OpenColorIO/Config.java
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-5 (8)
A src/jniglue/org/OpenColorIO/EnvironmentMode.java
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-6 (44)
M src/jniglue/tests/org/OpenColorIO/BakerTest.java
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-7 (2)
M src/jniglue/tests/org/OpenColorIO/ConfigTest.java
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-8 (17)
M src/jniglue/tests/org/OpenColorIO/GlobalsTest.java
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-9 (1)
M src/jniglue/tests/org/OpenColorIO/TransformsTest.java
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-10 (2)
M src/pyglue/DocStrings/Config.py
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-11
(61)
M src/pyglue/PyConfig.cpp
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-12
(67)
M src/pyglue/tests/ConfigTest.py
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-13
(13)
M src/pyglue/tests/MainTest.py
https://github.com/imageworks/OpenColorIO/pull/413/files#diff-14 (1)

Patch Links:

https://github.com/imageworks/OpenColorIO/pull/413.patch
https://github.com/imageworks/OpenColorIO/pull/413.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/imageworks/OpenColorIO/pull/413, or mute the thread
https://github.com/notifications/unsubscribe-auth/AVHKaihiv6mdHQAkjsM_23hOKVw5Fti3ks5qsj_YgaJpZM4KDp0z
.

Echoing my comments from #381 :

Curious if we feel like the new OCIO v2 file rules section solves this adequately. It's a different solution, but since it supports wildcards and regex it is more flexible. @hodoulp @doug-walker do you think it would be useful to support a special ${name} variable or similar in file rules regex strings to imply the placement of a color space name, rather than needing to have a pattern that accounts for every color space naming convention?

Michael, the FileRules does already allow a special rule that applies the parseColorSpaceFromString type matching.  An optional parameter could be added to that rule that would specify the delimiters to use.  I think it would be cleaner and clearer to put it there rather than add a separate "delimiters" attribute in the config.  That would also be a lot easier to implement than allowing a ${name} parameter in the other rule types.


[feature request]: Improve releasing version so that build number become patch number in version or something like that

Contact Details
No response
Is your feature request related to a problem? Please describe.
n/a
Describe the solution you'd like
Improve releasing version so that build number become patch number in version or something like that
Describe alternatives you've considered
Improve releasing version so that build number become patch number in version or something like that
Additional context
No response
Priority Level
Medium
Code of Conduct

[x] I agree to follow this project's Code of Conduct

In most environments, there's many more builds and consequent build numbers, than their are versioned releases. I like to use a scheme where there's two flavors of build. One for testing pull requests and one for building and publishing a new package.

this will be part of #100


Improve precision of polygon area calculations

As reported in https://github.com/mapbox/tippecanoe/issues/866, the area of very small polygons can sometimes be miscalculated in ways that cause their area to be found to be negative, causing the features to drop out.
In addition, the opposite error occurs in the low zoom levels of the GEBCO bathymetry data, causing Iceland and Cuba to be covered with contour polygons when the holes cut out for them are calculated as having positive area.
These behaviors are not consistent between x86 and ARM architectures, which apparently differ in small details in their floating-point math.
This PR fixes both errors by offsetting coordinates closer to the origin so they are more likely to be able to be multiplied without loss of precision. It abandons the use of long double for extra precision since this does not actually give additional precision on M1 Macs. Because the sign of the area is more important than the area itself, if overflow is detected during the calculation, it is repeated from a scaled-down geometry until it can be completed without overflow.

Returning to draft status because something is still going wrong with the polygon around Cuba at zooms 0 through 2.


Can not input on Safari

Can not input on safari, but works fine on Chrome.
Details

Browser version : Safari 10.0.1 (126<IP_ADDRESS>.7)
OS version: macOS Sierra 10.12.1 (16B2555)
xterm.js version: master (2cba2ff3d4dc545d10efcc2cc040b150a9bb5685)

Steps to reproduce

clone source code from github
npm install then npm start
open http://localhost:3000 on Safari
input some char, nothing displayed back

This may not always happen, It seems to be something with the input focus.

This could be the WebSocket closing. Could you please try refreshing the window and us know if it works after refreshing?

Refresh doesn't work, it seems not related to websocket, I can input a char by clicking on the cursor and type quickly.
I'm trying to port ttyd from hterm to xterm.js (https://github.com/tsl0922/ttyd/pull/22), can't input on safari, too.

Just tried this out and works 👍  for me.
Can you try in a private window please? It might be an extension / addon issue.

Tried in a private window, not work, then removed all the safari extension, not work too.

🆒 . Do you get any console logs/errors?
Also can you please:

make a test by binding to the keydown event and see if keystrokes are being captured properly
take a look at the websocket frames sent and see if the proper character sequences are being sent to the back-end?

Hi, @parisk
I can confirm the key event not captured properly, this is my test code (demo/main.js), nothing logged when I type.
function runRealTerminal() {
  term.attach(socket);
  term._initialized = true;
  term.on("keydown", function(e){
    console.log(e);
  });
  term.on("key", function(key, e){
    console.log(key, e);
  });
}

If I click the terminal with mouse and input quickly, key event can be captured, but only one click one char.

Hi, again.
I've resolved this issue by clearing the browser cache from safari's developer menu. Don't know why this helps, but thanks for your help!

🆒  happy it worked out at last!

I have faced the same problem. Cache clearing didn't work for me, but I found that manually giving focus to the cursor by click the white rectangle by mouse or dragging some rows in the terminal while typing allows me to type something. Without those, I have to press multiple keys within a short time to ensure some of them to be typed. Interestingly, Korean IME works fine! 😮
On other browsers, I got mixed results, so here I list them below:

Safari (10.0.3)

🇺🇸 : ❌ need to keep focus by clicking cursor or dragging the terminal rows simultaneously while typing, otherwise each keystroke is mostly (but not all if I type fast) ignored
🇰🇷 :  ✅ works well

Chrome (56.0.2924.87)

🇺🇸 : ✅ works well
🇰🇷 : ❌ does not work (only a space is typed after composition)

Firefox (51.0.1)

🇺🇸 : ❌ every character is duplicated
🇰🇷 : ✅ works well

My environment: MacBook Pro mid-2015 15" with macOS Sierra 10.12.3


[Syntax highlighting] for of loop with comment

for (/*const*/ let x of X) {

}

As stable FireFox not yet supports const in for of loops I replaced all const those loops by let, but kept the const as inline comment for easier refind later. This breaks syntax highlighting from the next function on.
The following however works perfectly:
for (let /*const*/ x of X) {

}

Looks fine?

After the last update of atom-typescript I cannot reproduce that behavior anymore.
I thought I had updated before writing the report but it seems that it was not the case (maybe I forgot to restart atom after the plugin update).
Thank you.


Module error running Empire

Hi on initial install Empire was working fine, not sure what has changed or if its a kali/python issue:
checked that I've got the latest pull from git also tried googling with no luck a point in the right direction would be greatly appreciated:
root@kali:/opt/Empire# ls
changelog  data  empire  lib  LICENSE  README.md  setup
root@kali:/opt/Empire# ./empire
Traceback (most recent call last):
File "./empire", line 6, in
from lib.common import empire
File "/opt/Empire/lib/common/empire.py", line 15, in
from pydispatch import dispatcher
ImportError: No module named pydispatch
root@kali:/opt/Empire# python -V
Python 2.7.3
root@kali:/opt/Empire# pip install pydispatch
Requirement already satisfied (use --upgrade to upgrade): pydispatch in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied (use --upgrade to upgrade): colorama>=0.2.7 in /usr/local/lib/python2.7/dist-packages (from pydispatch)
Requirement already satisfied (use --upgrade to upgrade): six>=1.5.2 in /usr/local/lib/python2.7/dist-packages (from pydispatch)
Cleaning up...
root@kali:/opt/Empire# pip install pydispatch --upgrade
Requirement already up-to-date: pydispatch in /usr/local/lib/python2.7/dist-packages
Requirement already up-to-date: colorama>=0.2.7 in /usr/local/lib/python2.7/dist-packages (from pydispatch)
Requirement already up-to-date: six>=1.5.2 in /usr/local/lib/python2.7/dist-packages (from pydispatch)
Cleaning up...
root@kali:/opt/Empire#

Sounds like a kali/python issue. Can you go into the setup folder and run ./install and ./reset and see what happens?

root@kali:/opt/Empire/setup# ./install.sh
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-pip is already the newest version.
The following packages were automatically installed and are no longer required:
libhttp-parser2.1 ruby-ansi ruby-dataobjects ruby-dataobjects-mysql ruby-dataobjects-postgres ruby-dataobjects-sqlite3 ruby-dm-core ruby-dm-do-adapter
ruby-dm-migrations ruby-dm-sqlite-adapter ruby-em-websocket ruby-execjs ruby-http-parser.rb ruby-librex ruby-libv8 ruby-msfrpc-client ruby-parseconfig ruby-ref
ruby-therubyracer
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-dev is already the newest version.
The following packages were automatically installed and are no longer required:
libhttp-parser2.1 ruby-ansi ruby-dataobjects ruby-dataobjects-mysql ruby-dataobjects-postgres ruby-dataobjects-sqlite3 ruby-dm-core ruby-dm-do-adapter
ruby-dm-migrations ruby-dm-sqlite-adapter ruby-em-websocket ruby-execjs ruby-http-parser.rb ruby-librex ruby-libv8 ruby-msfrpc-client ruby-parseconfig ruby-ref
ruby-therubyracer
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-m2crypto is already the newest version.
The following packages were automatically installed and are no longer required:
libhttp-parser2.1 ruby-ansi ruby-dataobjects ruby-dataobjects-mysql ruby-dataobjects-postgres ruby-dataobjects-sqlite3 ruby-dm-core ruby-dm-do-adapter
ruby-dm-migrations ruby-dm-sqlite-adapter ruby-em-websocket ruby-execjs ruby-http-parser.rb ruby-librex ruby-libv8 ruby-msfrpc-client ruby-parseconfig ruby-ref
ruby-therubyracer
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
swig is already the newest version.
The following packages were automatically installed and are no longer required:
libhttp-parser2.1 ruby-ansi ruby-dataobjects ruby-dataobjects-mysql ruby-dataobjects-postgres ruby-dataobjects-sqlite3 ruby-dm-core ruby-dm-do-adapter
ruby-dm-migrations ruby-dm-sqlite-adapter ruby-em-websocket ruby-execjs ruby-http-parser.rb ruby-librex ruby-libv8 ruby-msfrpc-client ruby-parseconfig ruby-ref
ruby-therubyracer
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Requirement already satisfied (use --upgrade to upgrade): pycrypto in /usr/local/lib/python2.7/dist-packages
Cleaning up...
Requirement already satisfied (use --upgrade to upgrade): iptools in /usr/local/lib/python2.7/dist-packages
Cleaning up...
Requirement already satisfied (use --upgrade to upgrade): pydispatcher in /usr/local/lib/python2.7/dist-packages
Cleaning up...
[>] Enter server negotiation password, enter for random generation: test
Traceback (most recent call last):
File "./setup_database.py", line 98, in
)''')
sqlite3.OperationalError: table config already exists
root@kali:/opt/Empire/setup# ls
cert.sh install.sh reset.sh  setup_database.py
root@kali:/opt/Empire/setup# ./reset.sh
[>] Enter server negotiation password, enter for random generation: test
[*] Database setup completed!
rm: cannot remove `empire.debug': No such file or directory
Traceback (most recent call last):
File "./empire", line 6, in
from lib.common import empire
File "/opt/Empire/lib/common/empire.py", line 15, in
from pydispatch import dispatcher
ImportError: No module named pydispatch
root@kali:/opt/Empire/setup#

What version of Kali is this on?

Kali 1.0.8
root@kali:/opt/Empire/setup# uname -a
Linux kali 3.18.0-kali3-amd64 #1 SMP Debian 3.18.6-1~kali2 (2015-03-02) x86_64 GNU/Linux

Could be something with the python packages. Is this a fresh install? If so, I will find a 1.0.8 image and test it.

Nope it one I've had for a while, ill look into trouble shooting the python and post back if I fix it, ta for the assist.

Cool. Let me know what you find and let me know if there is anything I can do.


[SPARK-46484][SQL][CONNECT] Retain plan_id in ResolveUnpivot and UnpivotCoercion

What changes were proposed in this pull request?
Retain plan_id in ResolveUnpivot and UnpivotCoercion
Why are the changes needed?
they drop the plan id and cause:
In [1]: df = spark.createDataFrame([(1, 2, 3, 4, 5, 6)], ["f1", "f2", "label", "pred", "model_version", "ts"])
   ...: df.melt("model_version", ["label", "f2"], "f1", "f2").groupby("f1").count().count()
23/12/22 11:37:52 WARN CheckAllocator: More than one DefaultAllocationManager on classpath. Choosing first found
---------------------------------------------------------------------------
AnalysisException                         Traceback (most recent call last)

...

AnalysisException: When resolving 'f1, fail to find subplan with plan_id=2 in 'Aggregate ['f1], ['f1, count(1) AS count#125L]
+- Expand [[model_version#117L, label, label#115L], [model_version#117L, f2, f2#114L]], [model_version#117L, f1#126, f2#127L]
   +- Project [f1#101L AS f1#113L, f2#102L AS f2#114L, label#103L AS label#115L, pred#104L AS pred#116L, model_version#105L AS model_version#117L, ts#106L AS ts#118L]
      +- LocalRelation [f1#101L, f2#102L, label#103L, pred#104L, model_version#105L, ts#106L]

JVM stacktrace:
org.apache.spark.sql.AnalysisException
	at org.apache.spark.sql.catalyst.analysis.ColumnResolutionHelper.$anonfun$resolveUnresolvedAttributeByPlanId$3(ColumnResolutionHelper.scala:521)
	at scala.Option.getOrElse(Option.scala:201)
	at org.apache.spark.sql.catalyst.analysis.ColumnResolutionHelper.$anonfun$resolveUnresolvedAttributeByPlanId$2(ColumnResolutionHelper.scala:516)
	at scala.collection.mutable.HashMap.getOrElseUpdate(HashMap.scala:469)
	at org.apache.spark.sql.catalyst.analysis.ColumnResolutionHelper.resolveUnresolvedAttributeByPlanId(ColumnResolutionHelper.scala:511)
	at org.apache.spark.sql.catalyst.analysis.ColumnResolutionHelper.tryResolveColumnByPlanId(ColumnResolutionHelper.scala:494)

Does this PR introduce any user-facing change?
yes, bug fix
How was this patch tested?
added ut
Was this patch authored or co-authored using generative AI tooling?
no

close in favor of https://github.com/apache/spark/pull/44462


Spam in the Server Logs

im using 1.16.5 mohist server with plugins
theres no problem other than spamming
(it spams more if you got stuck in a ramp)

I can look into this. It may be one of your plugins though.

I can look into this. It may be one of your plugins though.

i think it is not, i tried without plugins too. Normally it sends this regular but sometimes you get stuck while riding(it is not a big deal you can get out easily by just moving in another way) and when you get stuck it just spams.

https://youtu.be/aZOzhSizWqk

Yikes, I completely forgot about this issue, sorry. There's some sort of desync between server and client. Do you have the mod on both sides? If yes, then do you have the server config option for "cancel_rand_rearing" on or off?

Its not a big deal, i also did forget about it since i saw your response in my e-mails. I had it on both sides with forcing the controls enabled from server config. Imma look at your suggestion as soon as i have access to my pc. But does it solve the "getting stuck" issue or did you solve it on newer updates cuz i didn't check it recently.

Its not a big deal, i also did forget about it since i saw your response in my e-mails. I had it on both sides with forcing the controls enabled from server config. Imma look at your suggestion as soon as i have access to my pc. But does it solve the "getting stuck" issue or did you solve it on newer updates cuz i didn't check it recently.

I will get back to you after i try. I can give the logs if you want too.


Add FractionalAge Logical Type

As a user, I wish I could use Woodwork with a FractionalAge Logical Type ([1.5, 2.4, 3.5]).
This should use the np.float64 dtype as the Physical Type.

class FractionalAge(LogicalType):
    """
    Examples:
        .. code-block:: python
            [1.5, 2.4, 3.5]
            [30.0, 62, 87.7]
    """
    primary_dtype = 'float64'
    standard_tags = {'numeric'}

While serialization will change, this should not be a breaking change, as it just adding a new Logical Type (not removing/renaming an existing one).

@gsheni do we need to bump the serialization schema? from 11.1.0 to 11.1.1 maybe?

@tamargrey Yes, we should bump the serialization schema version


Localization Support

Currently, the progress bar text is in English only. It would be great to add localization support for different languages so users can see the progress in their preferred language.

@DhanushNehru I would like to work on this issue under hacktoberfest


{Package} extend homebrew package test timeout value

Description
Sometimes, when ADO resources are limit in the evening, homebrew package test may fail because of timeout. Extend this value to 3 hours.
Also remove monitor module from parallel running list.
Testing Guide
ADO tasks should be passed.
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

homebrew package


Unable to push the application to Cloud

I can build the package successfully on my mac using swift 4.2.1. However, when i try to push to bluemix, its gets hanged at Fetching https://github.com/IBM-Swift/OpenSSL.git . Also, I noticed that the packages that are fetched are different for mac and IBM cloud. Could be due to Linux. But no clue how to proceed.

@sangy05  Thanks for raising an issue!
We will take a look into recreating your issue now and get back to you when we have more information.
In the meantime could you provide the contents of your Package.swift file?
Thanks again!

@ddunn2 : Sure david, here is the package content.
// swift-tools-version:4.2
// The swift-tools-version declares the minimum version of Swift required to build this package.
import PackageDescription
let package = Package(
name: "SocketServer",
dependencies: [
.package(url: "https://github.com/IBM-Swift/Kitura.git", from: "2.6.1"),
.package(url: "https://github.com/IBM-Swift/HeliumLogger.git", .upToNextMinor(from: "1.7.0")),
.package(url: "https://github.com/IBM-Swift/Kitura-WebSocket.git", from: "2.1.1")
],
targets: [
// Targets are the basic building blocks of a package. A target can define a module or a test suite.
// Targets can depend on other targets in this package, and on products in packages which this package depends on.
.target(
name: "SocketServer",
dependencies: ["Kitura", "HeliumLogger", "Kitura-WebSocket"])
]
)

Thanks @sangy05
The issue is with this line in your Package.swift:
.package(url: "https://github.com/IBM-Swift/HeliumLogger.git", .upToNextMinor(from: "1.7.0")),
Kitura 2.3 onwards requires HeliumLogger at version 1.8 or above.
A solution to your issue would be to update the line in your Package.swift to pull in the correct version of HeliumLogger:
.package(url: "https://github.com/IBM-Swift/HeliumLogger.git", from: "1.8.0"),
If there is a reason you need HeliumLogger at version 1.7 please let me know and I'll help guide you through this.
I hope this helps!

Excellent!! It worked. Thanks.. But I just wonder how the same didn't fail when I run in the local. ?


End of Tibialyler?

Looks like it migh be end of Tibialyzer :(
http://forum.tibia.com/forum/?action=thread&threadid=4532071

I'm pretty sure it'll get whitelisted.
I hope it does.

Not sure if they will take the effort but lets hope so!

I made a proposal here that would allow Tibialyzer to keep on functioning without reading Tibia's memory. We will see what comes of it.

@Mytherin Unfortunately, I wouldn't get your hopes up that CipSoft will take your proposal seriously. However, according to an alleged BattlEye employee that showed up on the reddit thread in /r/TibiaMMO discussing the news, you can inject a library into the client and BattlEye will ignore it because BattlEye only cares about external processes trying to interfere with the client.
Knowing this, you could easily write a DLL in C++ that does the core work of Tibialyzer, inject it with C#, and use IPC (e.g., a named pipe) to communicate between your DLL and your C# code; as long as BattlEye doesn't protect against it. Otherwise, you would need to do everything from the injected DLL. I'll know more when the new clients are released. From what I've gathered, BattlEye probably uses kernel-mode hooks to detect when an external process calls Read/WriteProcessMemory, or any other low-level Windows API functions, on the client.
If you don't know who I am, I've been around the Tibia/OT scene since 2004. Most notably, my contributions to TPForums (which gives me a bad rap for being a "bot" community), maintaining (for a short time) SharpMapTracker, and detailing protocol changes. Also, I work in the security industry as a software engineer. I'm interested in getting my hands on the client with BattlEye integration and seeing exactly what's going on. If I can find a simple solution to allow Tibialyzer to continue working (in the case that it does get blocked), I'd be more than happy to share it with you, and let you be the judge on whether or not you want to implement it.

From what I gathered from his response was not that BattlEye ignored injections into the client, but rather that the injection would still work if it was whitelisted by them. As far as I know, injecting code into the client is still against Tibia's rules. Thus even if the injection works without them whitelisting it, if they detect it you will still get banned.
If they make an explicit exception for Tibialyzer and whitelist an injected module that would allow us to gather that information, then sure, that would be a valid solution. But I think the chance of that happening is very low. At least, much lower than the chance of them adding an option to dump log messages into a file.
The reason I think my suggestion is a good solution is that it is very easy for CipSoft to implement, and it couldn't be used in any malicious way by botters as server log messages do not carry enough information for them.

From what I gathered from his response was not that BattlEye ignored injections into the client, but rather that the injection would still work if it was whitelisted by them.

Allow me to quote that BattlEye employee:

That's right, but they could work around that by e.g. injecting a module into the game, which would then be allowed by BE.

Tibialyzer would need to be rewritten to inject a component that does the reading into the game.

It's possible that their injection method needs to be updated for them to still work, but other than that they should be fine.
If Tibialyzer is solely an external tool it will be completely be blocked by the protection system though.

What I'm inferring here is that BattlEye only protects against external tools. Any modules inside the client, whether they were put there by CipSoft or not, are excluded from BattlEye protection. Maybe I'm wrong, but I'll know more when the client is released.

As far as I know, injecting code into the client is still against Tibia's rules. Thus even if the injection works without them whitelisting it, if they detect it you will still get banned.

Code injection isn't against the rules, as long as you're not gaining an unfair advantage. There's nothing in the client that detects code injection, and there's no data being sent to the server that would report that. As you can see from the officials rules that I quoted below, CipSoft will not offer support for any loss from client manipulation. Nowhere do they state that it's against the rules (as long as you're not gaining an unfair advantage).

Rule 3b) Using Unofficial Software to Play
Manipulating the official client program:
Manipulating the client program to try gaining an advantage compared to other players is not only extremely unfair but may also cause serious errors in the game. In such cases you cannot expect any assistance from CipSoft concerning level, skill, item or character loss due to manipulating their software or the game protocol. Also, manipulating the client program may lead to a punishment.

I'm not saying your suggestion isn't good, I'm just saying that I wouldn't hold my breath for CipSoft to even consider it let alone implement it. If they even acknowledge your suggestion, they'll probably tell you to use the client's built-in 'save messages' feature when you right-click a channel tab.
Sorry if I'm coming on strong, it's just that I know how popular Tibialyzer is to the Tibia community, and I would like to help keep it alive, if possible, after the client update; if it so happens to get blocked.

I feel good about the future of tibialyzer, and again appreciate all your effort! Further more don't let me forget about all the other individuals who are putting in input/ideas to help Mytherin your effort inst going un noticed either, Again more shout outs to you.. Anyways ~ Could someone give me a run down on tibialyzer how i can fix my HUD list is there something i need to  have set on the tibiaclient its self ie "Battle List/Window" options or do i have something wrong with how i am setting it up in tibializer its self? there isnt really any instructions/vids in how to set this up~ also just recently my popups loot keeps being reset too 2000 it doesnt save or something maybe something is up with my program and ideas? would be  super helpful and kindly appreciated! other then that it seems the program is running perfect.
PS
Keep up your work, Dont go a changing
;)
Wader

@jo3bingham If Battleye doesn't protect from DLL injections then I suppose that could be an easy way for bots to keep working as they could gather all they need from a modified DLL.
Which would be a shame IMHO, defeats the sole purpose of implementing BE.
I truly hope they won't let a flaw like that pass unnoticed

It seems CipSoft plans to implement Tibialyzer features into Tibia 11, which is nice.
@gabrielrdrguez I agree, allowing injected modules gives bot makers a easy way around. Once I get the new client I'll see how easy that is to achieve.
SharpMapTracker is open-source, it just needs to be updated. As far as I know, there aren't any publicly available map trackers for the current clients.


ignoring Boxfile when specifying python34

I've specified
build:
  runtime: python34

in my Boxfile, but nanobox doesn't seem to recognize this and I get a box with python27.

Oh, it looks like the docs haven't been updated to reflect the changes since the overlay feature. The attribute has been renamed to "python_runtime". That change was introduced to allow engines with the potential to pull in other runtimes, such as nodejs_runtime if bower or some other frontend compiler is needed.
Thanks!

did a nanobox update and updated the Boxfile with the python_runtime attribute and now sniff is detecting a nodejs app.

That was an issue this week that has been resolved with a new docker build image. Try the following:
nanobox reload
nanobox update-images
nanobox dev

:+1: got it. thanks!


[FIXED, RELEASE IN V3.0.0] UIWebView iOS Deprecated API Usage Warning ITMS-90809

THIS HAS A MERGED FIX - IT WILL RELEASE IN V3.0.0 HERE*
See https://github.com/react-native-community/react-native-webview/issues/819
I have not yet submitted a new version of the app, but I searched my node_modules and found that this module referenced UIWebView too.
See: https://github.com/react-native-community/react-native-device-info/blob/8efe2efaba6b01a1d48a0238ff91ab8e9d39f4ab/ios/RNDeviceInfo/RNDeviceInfo.m#L118

I could submit a PR for that but then the Android part would also have to be asynchronous (as WKWebView evaluateJavascript is asynchronous). Is that fine @mikehardy?

Dang. This may be the time to finally do the big promise-based breaking change. I've got a bit of time this morning maybe I can crank it out. I don't want to just trickle in async changes when everything needs to go async really.
@Johan-dutoit / @radko93 I read through the linked discussion and did not see any statement on when it would become a hard requirement and fail an app store build vs just a warning. Could one of you guys dig and find when this becomes a hard fail? That will help prioritize

@radko93 I would definitely appreciate a PR that implemented the required API change - while I may not ingest it as is (because I want to do all the async changes at once) it would be really really helpful to me to have the ObjC portion of the PR from someone who knew what they were doing :-). If you converted it to a Promise at the same time I could probably just include the commit raw into the promise-ify commit stream anyway, to maintain attribution

@mikehardy can we assume it's going to be with iOS 13?  i.e. anything that targets iOS 13, which would mean less than 2 months away.
The documentation currently states the following, although we will have to check back once 13 is released.

Other than that, I've been unable to find a concrete timeline.

No one seems to know concretely in the react-native-community Discord chats or the webview component or stackoverflow. I think that's a reasonable guess though, thank you. If anyone posted the recommended ObjC changes that would help me :pray: and we could get something up quickly to start working through project-specific testing etc

This is merged and will release with v3

Điều này được hợp nhất và sẽ phát hành với v3

When will v3 be released? I am really in need @mikehardy

No, no you aren't really in need. You're strongly in want, nothing more. It's a warning, the app store will still accept submissions.
Asking for your free stuff faster is not polite in the open source world :-)
That said, I might have a release candidate up tomorrow morning.
But if I met my untimely demise and you really thought you were in need for some reason, you could use patch-package to integrate the merged patch, or fork. You'd be fine because the source is open and you're a programmer

This is released.
If anyone wants to try v3.0.0-beta.1 of react-native-device-info is up tagged on npm as @latest - it's a big ol' breaking change because instead of making your app startup really slow (like .6 seconds slower than it would otherwise) by loading everything in constants in init, it's all Promises now. It also evicts the deprecated WebView stuff that causes App Store warnings. I would especially love a Windows tester, I don't even have a test environment there so I just hacked it and prayed https://github.com/react-native-community/react-native-device-info/releases/tag/v3.0.0-beta.1

I am planning on letting it incubate at least a couple days - plenty of time for good feedback. Final release maybe early next week. But you can rely on the v3 git branch, or the @next npm tag now if you want

@mikehardy Is it possible to remove UIWebView from 2.x release? 3.0 requires new API to use and it breaks old API usage..

Waiting for the v3 release to be stable. Btw I don't think your "No, no you aren't really in need. You're strongly in want, nothing more. It's a warning, the app store will still accept submissions." is valid. The Apple mail explicitly mentioned "Apple will stop accepting submissions of apps that use UIWebView APIs."

@rnnyrk tell me the date and I'll listen, until then my statement stands.
3.0.0-rc.1 has had no issues logged so I believe it's stable though I may add a companion sync API to it.

Been using (only like 5% of it anyway) 3.0.0-rc.1 for a while now and no issues yet.

@mikehardy I didn't mean this as an offense in any way. Just state what the Apple mail mentioned, which made me a little scared for my release. Updated to the RC now. Seems to run without any issues.

No worries @rnnyrk I don't take offense but I must be firm in my stance as the project as huge and wishy-washy remarks result in comment discussions that take time I don't care to spend ;-). So I wanted to be very concrete, for others that might come.
So to restate (since this will be the last comment now): Apple will continue accepting app submissions for now. There is no known date when they will stop. It is suspected they may stop when iOS 13 is in full release but that is a guess.
And of course we are working to resolve it.
Thanks everyone for the RC1 testing. I had so much difficulty with a semi-synchronous code-base and the fully async RC1 that I'm adding a parallel sync API for RC2 which is unfortunately a big change so I'll really appreciate further testing once it's out. Please follow along on #307  and #760
Thanks

email: We identified one or more issues with a recent delivery for your app, "****" 1.0.0 (1.0.0). Your delivery was successful, but you may wish to correct the following issues in your next delivery:
ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information.
After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to App Store Connect.
Best regards,
The App Store Team
So, currently my app is blocked completely due to the uiwebview thingy. I'm assuming this is across the board now.

@kaphoto this is thoroughly resolved through the ecosystem, the relevant issue in the react-native-webview repository has some good strategies to discover why you are still referencing the symbol, if you are. But the symbols are no longer in use in this repo.

Find solution here!

Find solution here!

that is resolved for react-native-webview, but what to do for resolving the same for react-native-device-info?

that is resolved for react-native-webview, but what to do for resolving the same for react-native-device-info?

In my project I use "react-native-device-info": "^5.6.2" and everything goes just well.


[feature request] Native app (eg Electron?)

Google will restrict their chrome apps to only run Chrome notebooks(notebooks running Chrome OS) Ending Windows/Mac support for chrome apps, link: (https://www.windowscentral.com/chrome-apps-support-windows-will-end-2018)
https://blog.chromium.org/2016/08/from-chrome-apps-to-web.html
By replacing the chrome app with a Native app(Electron) before the support ends, anyone will be able to use your app(Linux, Windows & Mac). When will you offer a Native app for the ledger chrome wallet?

No ETA yet, we are still working on it. If we are not ready to release the new application once Google removed Chrome apps from their store, we will release a electron based version of our current apps (those apps are already working).


OneFuzz CLI command onefuzz status pool <pool_name> fails

Version: 5.2.0 (both API and CLI)
Running onefuzz status pool <pool_name> consistently fails with the following error:
onefuzz status pool <pool_name>
ERROR:cli:command failed: too many values to unpack (expected 2)

➜ ./onefuzz.exe --version
onefuzz.exe 5.2.0
➜ .\onefuzz.exe status pool "default"
{
"node_state": {
"free": 20
},
"tasks": {}
}
I could not repro on Windows from powershell
@jagunter  what OS and shellS are you using ?

This is on Ubuntu 18.04 (via WSL). Apologies should have noted that earlier. Testing further, it appears only some pools are affected.

Running the query with -vvv reveals the issue in the stack trace:
ERROR:cli:traceback: Traceback (most recent call last):
ERROR:cli:traceback:   File "$HOME/.pyvenv/onefuzz/lib/python3.10/site-packages/onefuzz/cli.py", line 586, in execute_api
ERROR:cli:traceback:     result = call_func(args.func, args)
ERROR:cli:traceback:   File "$HOME/.pyvenv/onefuzz/lib/python3.10/site-packages/onefuzz/cli.py", line 74, in call_func
ERROR:cli:traceback:     return func(**myargs)
ERROR:cli:traceback:   File "$HOME/.pyvenv/onefuzz/lib/python3.10/site-packages/onefuzz/status/cmd.py", line 49, in pool
ERROR:cli:traceback:     task_id, _task_state = entry
ERROR:cli:traceback: ValueError: too many values to unpack (expected 2)
ERROR:cli:traceback:
ERROR:cli:command failed: too many values to unpack (expected 2)

The query likely succeeds when there are no tasks in the pool to unpack.

Issue is still present in 5.16.0


Wait for the expected number of connectors to be present

@enmasse-ci run tests testcase=bridging.** profile=isolated test_only ocp4

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: isolated
TEST_CASE: bridging.**
TOTAL: 19
PASS: 19
FAIL: 0
SKIP: 0
BUILD_NUMBER: 265


Window not moveable on OSX

In macOS Sierra, I'm not able to move the window around by dragging the menu bar.

I'll compile the latest version and take a look at this.

If I am right, I believe this is because on MacOS there is no window frame, therefore no moveable. I cannot perform tests on MacOS, but if this is still a bug I will attempt to fix it.
@braindump or @HaydenSD Would you mind testing for me once I commit the fix?

Sure, can do.

Am 14.01.2017 um 11:21 schrieb Matthew<EMAIL_ADDRESS>If I am right, I believe this is because on MacOS there is no window frame, therefore no moveable. I cannot perform tests on MacOS, but if this is still a bug I will attempt to fix it.
@braindump or @HaydenSD Would you mind testing for me once I commit the fix?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm trying out the current version and i'm able to move the window by click/dragging the topmost pixel.

@braindump if the last version fixes this bug, i'll proceed to close the issue

@braindump @thien Can you try to pull my fork and see if it works for you? https://github.com/kontrollanten/Protonmail


Different Level Design

Rearrange the positions of the blocks.

git fetch origin
git checkout 21-different-level-design


Improve request decoding, handle base64 and gzinflate errors

As per https://github.com/simplesamlphp/saml2/pull/55, seeing this bundle provides its own bindings we should do the same.

@rjkip @arothuis

Awesome. Some nits, but :+1:

:+1:


How to set port range for different application

there are two kinds of applications in one container

application 1:  need 1 port, port range: [10000, 10100]
application 2: need 3 ports, port range:[10101, 11000]
how to achieve this ?
thanks

@weiranzhixin Currently, range schedule hasn't been supported.

thanks, another question is,

when does node manage reports available ports to resource manager , reporting when  node manager activated or periodically
if node manager periodically report available ports, how does resource manager deal with it ?
does yarn offer CLI to check available port ranges of node

@weiranzhixin
NM will periodically report ports info, wrapped by heartbeat. Then RM will update the resource.
You could run command yarn node -list -showDetails to get node port info.

@scarlett2018
Most of this issue is about hadoop implementation and usage, I think an issue is enough. We shouldn't include too much hadoop details into our faq.

Let's close this issue and track port issue in #1983

@mzmssg - got it, fair enough.


Create a set of port ranges for known and unknown services

There will be a set of fixed/known services, for example:

maverick-discovery
maverick-api@system
maverick-web
visiond
webrtc
cloud9

Then there will be sets of variable/unknown services, eg.:

mavlink instances
rosmaster instances
mavros instances
maverick-api@ vehicle instances

Define:

a set of port ranges for the known services (eg. 6001-6200), and
a set of port ranges for the variable/unknown services (eg. 7001-7200)

Within the set of known services, we should define fixed ports for the various services.  This is particularly important for services such as -discovery, which need to be consistently available on the same port at all times. eg:

(web) -discovery non-ssl: 6001
(web) -discovery ssl: 6002
(web) -api@system: 6003
(web) webrtc: 6005
(web) visiond: 6006
(web) cloud9: 6009

Port 6000 is blocked by most browsers as it's standard X11 port, so start from 6001.

This is a new list of fixed/known ports:

[ ] maverick-discovery : non-ssl : 6001
[ ] maverick-discovery : ssl : 6002
[ ] maverick-api@system : non-ssl :
[ ] maverick-api@system : ssl :
[ ] webrtc : ssl (only) :
[ ] visiond : tbd
[ ] cloud9 : tbd

Docs for mavlink need to be updated to reflect new port ranges;
https://goodrobots.github.io/maverick/next/#/modules/mavlink

Refactor mavlink ports.  Current the ports are all over the place, depending on the service which are usually unrelated, eg. for FC:

mavlink-router: 5770-5773 tcp, 14570-14576 udp
ROS master: 11311 tcp
maverick-api: 6800

For SITL/default dev instance:

SITL port: 5000
mavlink-router: 6000-6003 tcp, 14000-14006 udp
ROS master: 11000 tcp
maverick-api: 7000

New FC ports:

mavlink-router: 6051-6053 tcp, 6054-6059 udp
ROS master: 6060 tcp
maverick-api: 6061 tcp

New Dev SITL ports:

mavlink-router: 6070-6073 tcp, 6074-6079 udp
ROS master; 6080 tcp
maverick-api: 6081 tcp
SITL: 6082 tcp

OK, now document.

Also need to refactor px4 sitl.  Currently on:
ROSmaster: 6131
maverick-api: 6132
mavlink-tcp: 6133-6135
maverick-udp: 6136-6141


Add a new recurrenceLastExpansion column to the BillingRecurrence table

This will be used to determine which recurrences are in scope for
expansion. Anything that has already been expanded within the past year is
automatically out of scope.
Note that the default value is set to just over a year ago, so that, initially,
everything is in scope for expansion, and then will gradually be winnowed down
over time so that most recurrences at any given point are out of scope. Newly
created recurrings (after the subsequent code change goes in) will have their
last expansion time set to the same as the event time of when the recurring is
written, such that they'll first be considered in-scope precisely one year
later.

This change is

See https://b/233070128


Add support for AKS/EKS/GKE/etc based Kubernetes Clusters

Currently there exists support for OCP, and K8s. Depending on the provider, K8s annotations can vary. For example, in GKE, we use the the annotation:
ingress.gcp.kubernetes.io/pre-shared-cert
to provide a cert that gets applied on the ingress. This means that a user either needs to add these annotations in manually post-run, or the automation needs to provide additional functionality that supports these additions.

we use the the annotation:
ingress.gcp.kubernetes.io/pre-shared-cert
to provide a cert that gets applied on the ingress.

@johnrevans6 is this still the case in K8s 1.16+ with networking.k8s.io/v1/Ingress ?
There is TLS support without annotations now https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
AKS/EKS/GKE cluster types can be selected as well.
https://github.com/konveyor/move2kube/tree/main/assets/built-in/transformers/kubernetes/clusterselector/clusters
Feel free to comment on this issue or create a new one if this is still relevant in the latest Move2Kube version v0.3.x


Remove version specific links where possible and use 1.4 otherwise

[#164510120]
Signed-off-by: Jeremy Alvis<EMAIL_ADDRESS>

Thank you!


Option to define excluded statuses instead

We have several projects each with their own set of statuses, each of which may need to be adjusted from time to time. The Done status, however, is the least likely to change, and it happens to be the only status we don’t need to move from one iteration to another.
I think it would be helpful to have the option to declare a set of excluded statuses that should not cause issues to be moved, as opposed to a set of statuses that should be moved (as is currently implemented). Would you accept a PR that implements this as an optional feature?

Hey @agarzola this definitely seems like a good idea so feel free to open a PR 👍

I’ll submit a PR this week, then. Thanks, @blombard!


subdirectories in /src - linker errors

My project (on arduino) is structured in modules like:
/src/main.ino
/src/file1.[h|cpp]
/src/shared/debug.[h|cpp]
...

in file1.h, I have #include "shared/debug.h" which worked until platformio auto-upgraded to 1.4.0 (not sure from which version it upgraded, I haven't run it in about a month), and I'm now getting a linker error when compiling:
/src/file1.cpp:95: undefined reference to `debug_func(char const*, ...)'
[...]
collect2: error: ld returned 1 exit status
scons: *** [.pioenvs/autogen_uno/firmware.elf] Error 1

(debug_func is in shared/debug.h)
I tried tweaking build_flags in platformio.ini but unless I use absolute paths in the -L and -I options, a "script" prefix is added, so either it doesn't work, or it's not portable.
What happened during the upgrade that broke my project? I don't want to flatten my file structure, is there a proper way to fix platformio.ini for this?

Could I ask you to provide PlatformIO-based project where I can reproduce this issue?
Thanks in advance!

Ok, after testing on simplified code, the problem seems to be that
/src/shared is in fact a symbolic link to ../other_directory (I'm on linux).
if I move other_directory to /src/other_directory, there is no issue, even with the symbolic link.
The reason for the link is that I was sharing some code between two platformio projects.
I can live with it, so feel free to close the issue, but I wonder what changed in platformio that broke it.

I can live with it, so feel free to close the issue, but I wonder what changed in platformio that broke it.

Could you provide real example and pack it to archive? I will look on it. Thanks,

yes, I just tried to upload here, but github doesn't like it, so I emailed you a tarball instead.
Hope it helps!

Thanks a lot! I've just fixed it. Please install the latest development version http://docs.platformio.org/en/latest/installation.html#development-version
I will release new 1.5.0 in the next week.

Thanks Ivan! Brilliant work!


Are there plans to support NCCL local repository?

NCCL is usually installed along with CUDA as a base library, and it is convenient to have a rule.

See this example https://github.com/bazel-contrib/rules_cuda/tree/main/examples/nccl you can copy them to you repo.

I mean find some possible path of installed nccl and import them just like cudatoolkit library.在 2024年12月31日，14:59，cloudhan @.***> 写道：
See this example https://github.com/bazel-contrib/rules_cuda/tree/main/examples/nccl you can copy them to you repo.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Nope, this repo will only include cudax library.


Change fabfile virtualenv from pypy to python

This is requireded since building with pypy no longer works

Building with pypy should not be an issue.


How to remove avaritia recipes on 3x3 crafting?

Checks / 检查

[X] I confirm that I have searched for existing issues / pull requests before reporting to avoid duplicate reporting./我确认在报告之前我已经搜索了现有的问题或者拉取请求，以避免重复报告。
[X] I confirm that I noted that if I don't follow the instructions, the issue may be closed directly./我确认我已经检查，如果我不按照说明进行操作，该问题可能会被直接关闭。

Description / 描述
Im creating a modpack for me and my friends i was trying to modify some avaritia recipe, and i wanted to remove the crystal matrix ingot recipe but idk what is the code to remove it, can someone tell me if its possible to remove it?
(My Modpack version 1.18.2)

well im using crafttweakers but the problem is idk the code to remove recipes from avaritia on a 3x3 crafting table
i alr tried using "mods.avaritiva.tablecrafting.remove(...)" and "mods.avaritia.crafting.remove(...)" but it doesnt work


flutter pub get return Package not available (authorization failed). error!

Is there an existing issue for this?

[X] I have searched the existing issues
[x] I have read the guide to filing a bug

Steps to reproduce
running flutter pub get on version 3.10.5 stable
Expected results
it should install dependencies successfully.
Actual results
After upgrading to Flutter 3.10.5, running flutter pub get or dart pub get return the below error:
> flutter packages get
Resolving dependencies... (3.0s)
Package not available (authorization failed).

Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
> flutter packages get
Resolving dependencies... (3.0s)
Package not available (authorization failed).

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.10.5, on Microsoft Windows [Version 10.0.19045.3086], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[!] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    X cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    X Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.
[√] Chrome - develop for the web
[!] Visual Studio - develop for Windows (Visual Studio Enterprise 2022 17.5.1)
    X Visual Studio is missing necessary components. Please re-run the Visual Studio installer for the "Desktop development with C++" workload, and include these components:
        MSVC v142 - VS 2019 C++ x64/x86 build tools
         - If there are multiple build tool versions available, install the latest
        C++ CMake tools for Windows
        Windows 10 SDK
[√] Android Studio (version 2021.3)
[√] VS Code (version 1.79.2)
[√] Connected device (3 available)
[√] Network resources

! Doctor found issues in 2 categories.

I can't find anything about this error on the web or even in dart or flutter documentation!

Thanks for the report @parsadoc
I am unable to replicate the behavior you are seeing upon running flutter pub get.
Are you consistently getting the error everytime you run the command ?
Did you add any community package after which this error started to occur or just upgraded to latest stable ?
Can you run flutter pub get -v and see if you get any more details on the error that you can provide here ?

run : flutter pub get -v

I think the problem is Google apis flag or filter the VPN IPs we are using. because literally, I can open any website. But when it comes to fetching Flutter dependencies, I've been getting 403 since this morning. I send the same link that Flutter tries to fetch to my colleague in Germany and he can download it, but I get 403 or 404.
for example below link is a pub package. but I cannot open it and I get a 403 and a message that this service is not available in my country.
https://storage.googleapis.com/dartlang-pub-public-packages/packages/fhir-0.9.3.tar.gz

and for native dependencies that are on Google servers, I get the below error

This may not be the place to ask this question. But Flutter is open-source why should I not be able to use it freely in my country? I get there are sanctions and all. but it's open source. GitHub's free/open-source services were not available in Iran and they fixed it. can't folks at Google do that for us?

SLVR: Version solving took 0:00:08.261752 seconds.
    | Tried 1 solutions.
FINE: Resolving dependencies finished (8.286s).
IO  : Get package from https://pub.dartlang.org/packages/serverpod_auth_email_flutter/versions/1.1.1.tar.gz.
FINE: Downloading serverpod_auth_email_flutter 1.1.1...
IO  : Created temp directory /var/folders/zg/g1nhxgfj04l20_dw92rp3lc80000gn/T/pub_ZJqPS0
IO  : HTTP GET https://pub.dartlang.org/packages/serverpod_auth_email_flutter/versions/1.1.1.tar.gz
    | X-Pub-OS: macos
    | X-Pub-Command: get
    | X-Pub-Session-ID: EED009EF-FE1D-4486-9FA6-A9AD43CFD2BD
    | X-Pub-Environment: flutter_cli:get
    | X-Pub-Reason: direct
    | user-agent: Dart pub 3.0.5
IO  : HTTP response 403 Forbidden for GET https://pub.dartlang.org/packages/serverpod_auth_email_flutter/versions/1.1.1.tar.gz
    | took 0:00:01.655992
    | alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
    | cache-control: private, max-age=0
    | date: Fri, 30 Jun 2023 21:46:41 GMT
    | content-length: 193
    | x-guploader-uploadid: ADPycdtnuPR6D7xoJWse4mrVL-UYeuz_zz60mht6aqeWMIkH812sdFcNj9X149d7kCcUTIJ74xRhkIwrvkeTBdFdQ3oP9bByy7N1
    | content-type: application/xml; charset=UTF-8
    | server: UploadServer
    | expires: Fri, 30 Jun 2023 21:46:41 GMT
IO  : Deleting directory /private/var/folders/zg/g1nhxgfj04l20_dw92rp3lc80000gn/T/pub_ZJqPS0.
ERR : Package not available (authorization failed).
FINE: Exception type: PackageNotFoundException
FINE: package:pub/src/source/hosted.dart 1356:7              HostedSource._throwFriendlyError
    | package:pub/src/source/hosted.dart 1193:9              HostedSource._download.<fn>
    | ===== asynchronous gap ===========================
    | dart:async                                             Future.catchError
    | package:pub/src/utils.dart 113:52                      captureErrors.wrappedCallback
    | package:stack_trace                                    Chain.capture
    | package:pub/src/utils.dart 126:11                      captureErrors
    | package:pub/src/command.dart 198:13                    PubCommand.run
    | package:args/command_runner.dart 212:27                CommandRunner.runCommand
    | package:dartdev/dartdev.dart 226:30                    DartdevRunner.runCommand
    | package:args/command_runner.dart 122:25                CommandRunner.run.<fn>
    | dart:async                                             new Future.sync
    | package:args/command_runner.dart 122:14                CommandRunner.run
    | package:dartdev/dartdev.dart 58:29                     runDartdev
    | /opt/s/w/ir/x/w/sdk/pkg/dartdev/bin/dartdev.dart 11:9  main
---- End log transcript ----
IO  : Writing 2705143 characters to text file /Users/alireza/.pub-cache/log/pub_log.txt.
MSG : Logs written to /Users/alireza/.pub-cache/log/pub_log.txt.
[+10596 ms] pub failed
                     command: "/Users/alireza/flutter/bin/cache/dart-sdk/bin/dart pub --suppress-analytics get -v --example --directory ."
                     pub env: {
                       "FLUTTER_ROOT": "/Users/alireza/flutter",
                       "PUB_ENVIRONMENT": "flutter_cli:get",
                     }
                     exit code: 69

[   +5 ms] "flutter get" took 10,670ms.
[   +1 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      _DefaultPub._runWithStdioInherited (package:flutter_tools/src/dart/pub.dart:447:7)
           <asynchronous suspension>
           #2      _DefaultPub.interactively (package:flutter_tools/src/dart/pub.dart:530:5)
           <asynchronous suspension>
           #3      PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:303:7)
           <asynchronous suspension>
           #4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1336:27)
           <asynchronous suspension>
           #5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:296:9)
           <asynchronous suspension>
           #8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #9      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:244:5)
           <asynchronous suspension>
           #10     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:91:9)
           <asynchronous suspension>
           #11     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #12     main (package:flutter_tools/executable.dart:91:3)
           <asynchronous suspension>

[   +3 ms] Running 0 shutdown hooks
[   +1 ms] Shutdown hooks complete
[        ] exiting with code 69

As a result, I can say that flutter pub does not work in regions under US sanctions such as Crimea, Lugansk and Donetsk regions, as well as Iran

Also it doesn't work on Cuba.

that's my whole point. it's open source so there is no point for flutter pub to be unavailable in Countries under US sanctions.

Checkout this link for further reference.

Is there an existing issue for this?

[x]  I have searched the existing issues
[x]  I have read the guide to filing a bug

Steps to reproduce
running flutter pub get on version 3.10.5 stable
Expected results
it should install dependencies successfully.
Actual results
After upgrading to Flutter 3.10.5, running flutter pub get or dart pub get return the below error:
> flutter packages get
Resolving dependencies... (3.0s)
Package not available (authorization failed).

Code sample
Code sample
Screenshots or Video
Screenshots / Video demonstration
Logs
Logs
Flutter Doctor output
Doctor output

Looks like you are in a banned country
Solution: Run proton vpn and it will work properly

In Iran, even most popular VPNs do not work. however, I found a solution for this that should work in any banned region.
try launching pub using proxychains package:
proxychains flutter pub get
before that, you need to configure /etc/proxychains.conf to use a proxy (a local socks5 proxy if you're in Iran since normal proxies constantly get flagged)
so you need to put something like this at the end of the config file:
socks5 <IP_ADDRESS> 1080
(protocol) (ip) (port)
the package should be available in pretty much any distro.
if the problem persists, you can comment out proxy_dns in the same config file and try again. (disabling it fixes most of the problems with proxychains)

In my opinion, the best thing is to set DNS
It works well for me😏


BRS-615 adding subArea UID

###Jira Ticket
BRS-615
https://bcparksdigital.atlassian.net/jira/software/projects/BRS/issues/BRS-615
This ticket adds a unique ID number to each subarea. The numbers are sequential; the next sequential number can be used to identify new subareas as they need to be created. This UID is a better unique identifier to use both in partition/sort keys and in API calls, so the DynamoDB seeding script and lambdas have been updated accordingly. The updated data models are as follows:
Park:
pk: park
sk: <orcs>
example: park, 0001 = 'Strathcona Park'

SubArea:
pk: subarea::<orcs>
sk: <subAreaId>
example: subarea::0001, 0403 = 'Buttle Lake'

Config:
pk: config::<subAreaId>
sk: <activity>
example: config::0403, Day Use = 'Buttle Lake - Day Use (config)'

Record:
pk: <subAreaId>::<activity>
sk: <date>
example: 0403::Day Use, 202205 = saved record for 'Buttle Lake - Day Use - May 2022'

The databases will have to be reseeded using the convertParksSheet.js node script as the seeding table has been updated to include the new UIDs. A 'TEST PARK/SUBAREA' has also been added with orcs = subAreaId = 'TEST'.

You'll want to update this comment based on new logic.
Addressed in 5996e1b


Refactor range search for binary idmap

Signed-off-by: yudong.cai<EMAIL_ADDRESS>Issue: #91

/lgtm


Add Follow / Unfollow functionality

We'll need to add these mutations to the API: https://github.com/Glimesh/glimesh.tv/issues/718

This is done in https://github.com/Glimesh/glimesh_app/pull/44


Avoid exposing chainerx.Scalar to Python

Depends on #6481.

Rebased.

Jenkins, test this please

Jenkins CI test (for commit f0135ba848f8bb91a52629a2523e92b59e41c880, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

LGTM


fix django secret key

put the secret key in a not version controlled file

put the secret key in a config.json


bootstrap-vcpkg.sh does not build on clang-10

Describe the bug
vcpkg does not build on Clang-10
Environment

OS: Ubuntu 18.04
Compiler: clang 10.0.0

To Reproduce
Steps to reproduce the behavior:

./bootstrap-vcpkg.sh
See error

CMake Error at CMakeLists.txt:63 (message):
535  Can't find which C++ runtime is in use

Expected behavior
vcpkg to build
Failure logs
https://travis-ci.com/github/acgetchell/CDT-test/jobs/314214540#L508
Additional context
https://github.com/acgetchell/CDT-test/blob/master/.travis.yml

https://github.com/acgetchell/CDT-test/blob/65757c280d0a4e7f857f347111ad6713f0a6b6e0/.travis.yml#L44
Should be - if [[ "$CXX" == "clang++" ]]; then export CXX="clang++-10" CC="clang-10"; fi

Indeed.
https://travis-ci.com/github/acgetchell/CDT-test/jobs/314409425
Thanks for pointing out my mistake!


feat: Add World::get_reflect() and World::get_reflect_mut()

Objective
Sometimes one wants to retrieve a &dyn Reflect for an entity's component, which so far required multiple, non-obvious steps and unsafe-code.
The docs for MutUntyped contain an example of the unsafe part.
Solution
This PR adds the two methods:
// immutable variant
World::get_reflect(&self, entity: Entity, type_id: TypeId) -> Result<&dyn Reflect, GetComponentReflectError>

// mutable variant
World::get_reflect_mut(&mut self, entity: Entity, type_id: TypeId) -> Result<Mut<'_, dyn Reflect>, GetComponentReflectError>

which take care of the necessary steps, check required invariants etc., and contain the unsafety so the caller doesn't have to deal with it.
Testing

Did you test these changes? If so, how?

Added tests and a doc test, also (successfully) ran cargo run -p ci.

Are there any parts that need more testing?

Could add tests for each individual error variant, but it's not required imo.

How can other people (reviewers) test your changes? Is there anything specific they need to know?

Run cargo test --doc --package bevy_ecs --all-features -- world::World::get_reflect --show-output for the doctest
Run cargo test --package bevy_ecs --lib --all-features -- world::tests::reflect_tests --show-output for the unittests

If relevant, what platforms did you test these changes on, and are there any important ones you can't test?

Don't think it's relevant, but tested on 64bit linux (only).

Showcase
Copy of the doctest example which gives a good overview of what this enables:
use bevy_ecs::prelude::*;
use bevy_reflect::Reflect;
use std::any::TypeId;

// define a `Component` and derive `Reflect` for it
#[derive(Component, Reflect)]
struct MyComponent;

// create a `World` for this example
let mut world = World::new();

// Note: This is usually handled by `App::register_type()`, but this example can not use `App`.
world.init_resource::<AppTypeRegistry>();
world.get_resource_mut::<AppTypeRegistry>().unwrap().write().register::<MyComponent>();

// spawn an entity with a `MyComponent`
let entity = world.spawn(MyComponent).id();

// retrieve a reflected reference to the entity's `MyComponent`
let comp_reflected: &dyn Reflect = world.get_reflect(entity, TypeId::of::<MyComponent>()).unwrap();

// make sure we got the expected type
assert!(comp_reflected.is::<MyComponent>());

Migration Guide
No breaking changes, but users can use the new methods if they did it manually before.

Open question: I think these might also make sense for EntityRef (and the mutable variant of that), and someone on Discord also mentioned it. Should I implement it, and if so, in this PR or a follow-up one?

Question: Would it make sense to add something similar for Resources as well? Only thinking about it cause they can also be Reflect. But I don't really have an idea here, just wondering if then maybe the functions should not be called just get_reflect{_mut}(), but maybe get_component_reflect{_mut}()? But the other methods on World also don't use an infix for Components, just for Resources, so it would probably be get_resource_reflect{_mut}() then.

Also, just realized that relying on AppTypeRegistry is maybe not ideal.. But a World doesn't have an own TypeRegistry I think, so that's what I used.
A possible alternative would be to extend the arguments of World::get_reflect{_mut} to also take a &TypeRegistry argument. This would not create a coupling between World and AppTypeRegistry, but would add some overhead for the caller. In practice, that might be ok though. It would also remove one of the error cases, which is "no AppTypeRegistry-Resource in the world".

@futile ping me when you've addressed review comments (or if you're happy enough with the PR for now) and I'll give this the second review you need :)

generally very happy with this succinct and useful PR. it definitely could be merged as it is, i've just left a few comments/questions!
i reviewed this on my phone so the comment quality might not be great.
regardless, the bulk of the changes might be better off in their own file under the bevy_ecs::reflect module since the file there currently in is already exorbitantly long!

Thank you for the review! :) You mean like in a trait, e.g., WorldReflectExt or similar, which "adds" the methods to World? I also thought of that, can definitely do that :+1: As long as it doesn't use unsafe/internal APIs of World I'd think that is fine, because otherwise it easily be missed when changing some other code..

it's even simpler than using an extension trait. since it's in the same crate you can write an inherent impl (impl World {}) from a module like bevy_ecs::reflect::world_ext.

Is there a common practice for this in the bevy repo that I should follow?

Not particularly. For trivial / boring fixes (typos, code style), I tend to resolve it as an author or third-party reviewer. For particularly complex stuff, or where there's disagreement, I leave it open until the OP comes by. For particularly interesting threads, I leave it open even after it's fully resolved to help teach folks.

Not particularly. For trivial / boring fixes (typos, code style), I tend to resolve it as an author or third-party reviewer. For particularly complex stuff, or where there's disagreement, I leave it open until the OP comes by. For particularly interesting threads, I leave it open even after it's fully resolved to help teach folks.

Ah ok, yeah, makes sense. In that case I went ahead and resolved a few more issues, where the solution should be pretty obvious & expected. Thanks! :)

I didn't add world::reflect::world_ext, because world::reflect was already a new, empty module, and I thought it would be fine to keep the nesting level more shallow until it's required.

Makes sense to me!

Oh yeah, open question from before: Is it fine to depend on AppTypeRegistry here, or should the functions instead take a &TypeRegistry parameter or similar? :thinking:

Let's stick to using AppTypeRegistry for now. It's cleaner and easier to use. If we need to add a parameter for the registry we can always do so in a later PR. And that could even be a non-breaking change if we did it like ReflectCommandExt.

Just a couple cleanup suggestions. Everything else looks good!

Got it, fixed them. Nice catches, ty!

Let's stick to using AppTypeRegistry for now. It's cleaner and easier to use. If we need to add a parameter for the registry we can always do so in a later PR. And that could even be a non-breaking change if we did it like ReflectCommandExt.

Sounds good to me as well :+1:


Type mismatches when using Interfaces with _NoncopyableType decoration

Creating this as a child issue of https://github.com/shader-slang/slang/issues/3671 where the problem was originally found while writing the following targeted test:
Test Case: ctor-retval-legal.slang.txt
The root-cause is that there is a mismatch between the call operands and the callee signature when invoking a constructor or a member function within a struct that is derived from an interface.
Something like this:
interface IFoo
{
    ...
}

[__NonCopyableType] struct Impl : IFoo
{
     ...
}

The function signature of the following
__init(float);
__init();
are represented as

for ordinary constructor:

{272}	func %Implx5Fx24init	: Func(%Impl, Float)
    ....
	{329}	return_val(%21)

{234}	func %Implx5Fx24init1	: Func(%Impl)
    ...
	{338}	return_val(%23)

for  NonCopyableType constructor

{277}	func %Implx5Fx24init	: Func(Void, Float, Ref(%Impl))
    ....
 	{333}	return_val(void_constant)

{236}	func %Implx5Fx24init1	: Func(Void, Ref(%Impl))
    ....
	{341}	return_val(void_constant)`

Further digging down to the kIROp_Call where the crash happens, there is only one operand set as kIROp_Func with the assumption of ordinary struct type function signatures
{234}	func %Implx5Fx24init1	: Func(%Impl)

but for this case, it should be two:
{236}	func %Implx5Fx24init1	: Func(Void, Ref(%Impl))

that is why the assertion happens, when we do a
auto arg = inst->getArg(argCounter++);

when argCounter is 1 to access the Ref(%Impl), but the total args is 1.
Some comments from Yong on this topic:
The problem is that in the generic function, T is assumed to be an ordinary type, so the call to ctor is in the ordinary form. When we substitute the callee with the actual ctor, that will cause a mismatch. In general, the function signature defined in the interface must be binary compatible with the function signature of the actual implementation. In the case of non copyablr type, this assumption is broken.
The right fix is for the type system to not think that a noncopyable type’s ctor can satisfy the ctor requirement defined in the interface. Or we need to make compiler understand what it means for an interface to be decorated noncopyable, and only allow a noncopyable type to implement a noncopyable interface.

The issue here is calling for some language design around non copyable types.
Copyability is currently not a concept modeled in the type system, and we generally assume all types are copyable.
When a builtin type is decorated as [NonCopyableType], we enable some special IR gen rules to avoid generating copies, but this is completely transparent to the type system, and therefore leading to issues such as when specializing a generic function with non copyable type.
WIthout extending the type system to reason about copyability, our best solution here is to disallow non copyable type to implement any interface.

Leaving this as backlog for now, because this is an internal compiler interface, but should get cleaned up once we're on to tail end test perfection.


iso_mount throws exception when trying to mount

[x] I am using the latest SDK version
[x] This API is compatible with my vCenter version (You can get the info from 'vcenter_version' in each sample)
[x] I have searched existing issues and Troubleshooting wiki

Environment

sdk package version:
pyvmomi               <IP_ADDRESS>8.12
vapi-client-bindings  1.5.0
vapi-common-client    2.10.2
vapi-runtime          2.10.2
vmc-app-python-sdk    <IP_ADDRESS>.2.11053635
vmc-client-bindings   1.3.1

python version:
python 3.7.0

vSphere version:
6.7 update 1

Operating System/Shell (used to run SDK-based apps):

centos 7/bash
Steps or code snippet to reproduce
running the sample iso_mount.py file by:
python3 iso_mount.py -s vcenter-fqdn -u user -p password -v --datastorename vsan-hx --vmname test-linux-from-packer
Actual behavior
server: vcenter
Datastore MoId: datastore-1597
Local library created, ID: 7bb61fb6-00d8-4d80-94b1-0411e4a5b89d
Library item created id: 7222b04d-2249-4fd6-a12f-659b9589df47
Uploaded iso file to library item 7222b04d-2249-4fd6-a12f-659b9589df47
Found VM 'test-linux-from-packer' (vm-2116)
Traceback (most recent call last):
File "/home/user/vsphere-automation-sdk-python/samples/vsphere/common/sample_base.py", line 79, in run
attr()  # calling the method
File "iso_mount.py", line 92, in _execute
device_id = self.client.iso_service.mount(library_item_id, vm_id)
File "/usr/local/lib/python3.7/site-packages/com/vmware/vcenter/iso_client.py", line 99, in mount
'vm': vm,
File "/usr/local/lib/python3.7/site-packages/vmware/vapi/bindings/stub.py", line 317, in _invoke
return self._api_interface.native_invoke(ctx, _method_name, kwargs)
File "/usr/local/lib/python3.7/site-packages/vmware/vapi/bindings/stub.py", line 275, in native_invoke
self._rest_converter_mode)
com.vmware.vapi.std.errors_client.InternalServerError: {messages : [LocalizableMessage(id='vapi.bindings.method.impl.unexpected', default_message='Provider method implementation threw unexpected exception: com.vmware.vapi.std.errors.InternalServerError', args=['com.vmware.vapi.std.errors.InternalServerError']), LocalizableMessage(id='com.vmware.vdcs.iso-main.vm_reconfigure_failed_for_iso_mount', default_message='File [vsan-hx] contentlib-7bb61fb6-00d8-4d80-94b1-0411e4a5b89d/7222b04d-2249-4fd6-a12f-659b9589df47/CentOS-7-x86_64-Minimal-1810_3168940e-e1c6-4fe2-8868-2c2651243a2e.iso could not be mounted on the virtual machine test-linux-from-packer due to VirtualMachine reconfiguration failure.', args=['[vsan-hx] contentlib-7bb61fb6-00d8-4d80-94b1-0411e4a5b89d/7222b04d-2249-4fd6-a12f-659b9589df47/CentOS-7-x86_64-Minimal-1810_3168940e-e1c6-4fe2-8868-2c2651243a2e.iso', 'test-linux-from-packer'])], data : None}
Traceback (most recent call last):
File "/home/user/vsphere-automation-sdk-python/samples/vsphere/common/sample_base.py", line 79, in run
attr()  # calling the method
File "iso_mount.py", line 92, in _execute
device_id = self.client.iso_service.mount(library_item_id, vm_id)
File "/usr/local/lib/python3.7/site-packages/com/vmware/vcenter/iso_client.py", line 99, in mount
'vm': vm,
File "/usr/local/lib/python3.7/site-packages/vmware/vapi/bindings/stub.py", line 317, in _invoke
return self._api_interface.native_invoke(ctx, _method_name, kwargs)
File "/usr/local/lib/python3.7/site-packages/vmware/vapi/bindings/stub.py", line 275, in native_invoke
self._rest_converter_mode)
com.vmware.vapi.std.errors_client.InternalServerError: {messages : [LocalizableMessage(id='vapi.bindings.method.impl.unexpected', default_message='Provider method implementation threw unexpected exception: com.vmware.vapi.std.errors.InternalServerError', args=['com.vmware.vapi.std.errors.InternalServerError']), LocalizableMessage(id='com.vmware.vdcs.iso-main.vm_reconfigure_failed_for_iso_mount', default_message='File [vsan-hx] contentlib-7bb61fb6-00d8-4d80-94b1-0411e4a5b89d/7222b04d-2249-4fd6-a12f-659b9589df47/CentOS-7-x86_64-Minimal-1810_3168940e-e1c6-4fe2-8868-2c2651243a2e.iso could not be mounted on the virtual machine test-linux-from-packer due to VirtualMachine reconfiguration failure.', args=['[vsan-hx] contentlib-7bb61fb6-00d8-4d80-94b1-0411e4a5b89d/7222b04d-2249-4fd6-a12f-659b9589df47/CentOS-7-x86_64-Minimal-1810_3168940e-e1c6-4fe2-8868-2c2651243a2e.iso', 'test-linux-from-packer'])], data : None}
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "iso_mount.py", line 114, in
main()
File "iso_mount.py", line 110, in main
iso_mount_sample.main()
File "/home/user/vsphere-automation-sdk-python/samples/vsphere/common/sample_base.py", line 97, in main
self.run()
File "/home/user/vsphere-automation-sdk-python/samples/vsphere/common/sample_base.py", line 85, in run
raise Exception(e)
Exception: {messages : [LocalizableMessage(id='vapi.bindings.method.impl.unexpected', default_message='Provider method implementation threw unexpected exception: com.vmware.vapi.std.errors.InternalServerError', args=['com.vmware.vapi.std.errors.InternalServerError']), LocalizableMessage(id='com.vmware.vdcs.iso-main.vm_reconfigure_failed_for_iso_mount', default_message='File [vsan-hx] contentlib-7bb61fb6-00d8-4d80-94b1-0411e4a5b89d/7222b04d-2249-4fd6-a12f-659b9589df47/CentOS-7-x86_64-Minimal-1810_3168940e-e1c6-4fe2-8868-2c2651243a2e.iso could not be mounted on the virtual machine test-linux-from-packer due to VirtualMachine reconfiguration failure.', args=['[vsan-hx] contentlib-7bb61fb6-00d8-4d80-94b1-0411e4a5b89d/7222b04d-2249-4fd6-a12f-659b9589df47/CentOS-7-x86_64-Minimal-1810_3168940e-e1c6-4fe2-8868-2c2651243a2e.iso', 'test-linux-from-packer'])], data : None}
disconnecting the session
Expected behavior
It keeps failing at the mounting of the ISO. I can see in the datastore that the folder is created with the iso in there. I saw the iso uploaded successfully, adds the cdrom, connects the cdrom and actually connects the iso from the content library after it errors out, but then the python script errors out with the error above.

I just submitted a change so the sample should fail right away when exception occurs. I am talking to the content library team about the actually exception now.

@abshelto
The iso service (which provides mount operation) requires:

Content library be backed by datastore and not NFS. A datastore backed by NFS should be fine.
The datastore of the content library where the iso item is mounted be accessible from the host or cluster on which the vm resides.

Can you check if these two requirements are satisfied? Were you able to mount the iso from UI?

Close this for now. @abshelto Please reopen is the issue still exists.

I ran into the exact same issue...My content library is backed by vSAN datastore. Is there a solution to this problem


F1 2018 corruption on characters in CG

Operating System            : Ubuntu 20.04
ASIC                                 :  Navi 10
DRIVER                             : amdvlk https://github.com/GPUOpen-Drivers/AMDVLK
setup steam
Set resolution to 1920x1080
Set quality to Ultra High
When entering time trial mode choose "Classic F1 Cars" otherwise corruption is obscured by car cockpit view.

add barrier in generated SPIRV can workaround this issue.

add barrier in generated SPIRV can workaround this issue.

Which shader exactly?
We generate barriers when the orginal DirectX shader contains barriers. If there is none, this is a game bug.

Which shader exactly?
We generate barriers when the orginal DirectX shader contains barriers. If there is none, this is a game bug.

do you need the spirv file or renderdoc capture?

do you need the spirv file or renderdoc capture?

The SPIR-V so I can correllate it to the original shader.

The SPIR-V so I can correllate it to the original shader.

spirv.zip

spirv.zip

*_edited.dis shows where I added barriers

*_edited.dis shows where I added barriers

Same bug as in F1 2019. We have a workaround for that already which we can enable for both games.

Same bug as in F1 2019. We have a workaround for that already which we can enable for both games.

Hi @doitsujin  thank you for this. I have steam proton environment now, could you tell me how to verify with the workaround you enabled? can I replace some dx binaries of steam proton?

Hi @doitsujin  thank you for this. I have steam proton environment now, could you tell me how to verify with the workaround you enabled? can I replace some dx binaries of steam proton?

DXVK binaries are located in .steam/steam/steamapps/common/Proton 5.13/dist/lib64/wine/dxvk and can just be replaced.

DXVK binaries are located in .steam/steam/steamapps/common/Proton 5.13/dist/lib64/wine/dxvk and can just be replaced.

thank ya!

thank ya!

hi @doitsujin  when building dxvk, I encountered following errors:
In file included from ../../../../../root/Downloads/dxvk-master/src/dxgi/dxgi_adapter.cpp:8:
../../../../../root/Downloads/dxvk-master/src/dxgi/dxgi_factory.h:13:41: error: ‘IDXGIFactory7’ was not declared in this scope; did you mean ‘IDXGIFactory2’?
13 |   class DxgiFactory : public DxgiObject {
do you know how to resolve it?

hi @doitsujin  when building dxvk, I encountered following errors:
In file included from ../../../../../root/Downloads/dxvk-master/src/dxgi/dxgi_adapter.cpp:8:
../../../../../root/Downloads/dxvk-master/src/dxgi/dxgi_factory.h:13:41: error: ‘IDXGIFactory7’ was not declared in this scope; did you mean ‘IDXGIFactory2’?
13 |   class DxgiFactory : public DxgiObject {
do you know how to resolve it?

The latest MinGW release (8.0, not to be confused with the GCC version) ships up to date DXGI headers which are required to build DXVK.

The latest MinGW release (8.0, not to be confused with the GCC version) ships up to date DXGI headers which are required to build DXVK.

thanks, it works :)

thanks, it works :)


rikai: based on ParquetDataSourceV2

We can probably to manipulate over the path send to parquet datasource to implement the versions tho.

The difference between this pr and the master is that this PR are using Data Source API v2 of Apache Spark.
See https://databricks.com/session/apache-spark-data-source-v2

We need to build a few things to improve training performance.
Rikai format should be a combination of

Petastorm https://github.com/uber/petastorm
Delta lake https://delta.io/

For further customization, we could define:

RikaiFileFormat like https://github.com/delta-io/delta/blob/master/src/main/scala/org/apache/spark/sql/delta/DeltaFileFormat.scala
RikaiTable like https://github.com/delta-io/delta/blob/master/src/main/scala/org/apache/spark/sql/delta/DeltaTable.scala
RikaiDataSource like https://github.com/delta-io/delta/blob/master/src/main/scala/org/apache/spark/sql/delta/sources/DeltaDataSource.scala
...

For now, we should keep the implementation as simple as possible.

Here is how CarbonData defines the file format:
https://github.com/apache/carbondata/blob/master/integration/spark/src/main/scala/org/apache/spark/sql/carbondata/execution/datasources/SparkCarbonFileFormat.scala

CarbonData are using Apache Spark 2.x. For Apache Spark 3.x, we need to provide a RikaiWriteBuilder like https://github.com/apache/spark/blob/v3.1.1/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/v2/parquet/ParquetWriteBuilder.scala

@changhiskhan  What's your opinion? Two option:

Merge this PR and use spark.read.format("rikai") and df.write.format("rikia")
Close this PR and use spark.read.format("parquet") and df.write.format("parquet")

@da-tubi do we want to keep this open?


The HackMD workspace is not public

Question
The readme claims that the leadership council HackMD workspace is public. However, when I visit the link, it just says "Forbidden". Perhaps it was not configured correctly?

Sorry, will send a PR soon to fix the link. It should be https://hackmd.io/@rust-leadership-council for public viewing.


Issues with the focal colorizer

Describe the bug
The colorizer GUI shows up even without the research.
Also, there are still issues with UI scaling via #4
To Reproduce
Steps to reproduce the behavior:

DON'T research Focus Colorizers
Make and place a focal manipulator
Right-click the focal manipulator
See problems

Expected behavior
The colorizer gui not appear if I don't have the research and it being on the bottom center of the ui when not in AUTO.
Additional context
I thought it was due to Thaumic Fixes (fixes the XP display on the focal manipulator) but still happens without.
Using PA 1.4.0-pre5 (saw issue in pre4)

oh yeah this is a bug, ill look into it

fixed in pre6

So the research bug is fixed, but I'm still having the UI scale issue (Using large):


requests 2.5.0 uninstall fails

Installing the latest (2.5.1) or 2.5.0 (in the examples, below), installs a version that can't be uninstalled or upgraded, though it imports without a problem. I show how 2.2.0 (my previous version) didn't have this problem.
Install 2.5.0:
dustin@deploy1:/usr/local/lib/python2.7/dist-packages$ sudo pip install requests==2.5.0
Downloading/unpacking requests==2.5.0
  Downloading requests-2.5.0-py2.py3-none-any.whl (464kB): 464kB downloaded
Installing collected packages: requests
Successfully installed requests
Cleaning up...

Can successfully import:
dustin@deploy1:/usr/local/lib/python2.7/dist-packages$ python
Python 2.7.6 (default, Mar 22 2014, 22:59:56)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import requests
>>>

Can't uninstall, though:
dustin@deploy1:/usr/local/lib/python2.7/dist-packages$ sudo pip uninstall requests
Traceback (most recent call last):
  File "/usr/bin/pip", line 9, in <module>
    load_entry_point('pip==1.5.4', 'console_scripts', 'pip')()
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 519, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2630, in load_entry_point
    return ep.load()
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2310, in load
    return self.resolve()
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2316, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 11, in <module>
    from pip.vcs import git, mercurial, subversion, bazaar  # noqa
  File "/usr/lib/python2.7/dist-packages/pip/vcs/mercurial.py", line 9, in <module>
    from pip.download import path_to_url
  File "/usr/lib/python2.7/dist-packages/pip/download.py", line 25, in <module>
    from requests.compat import IncompleteRead
ImportError: cannot import name IncompleteRead

Cleanup, manually:
dustin@deploy1:/usr/local/lib/python2.7/dist-packages$ sudo rm -fr requests*

Installing 2.2.0 (the okay version):
dustin@deploy1:/usr/local/lib/python2.7/dist-packages$ sudo pip install requests==2.2.0
Downloading/unpacking requests==2.2.0
  Downloading requests-2.2.0-py2.py3-none-any.whl (623kB): 623kB downloaded
Installing collected packages: requests
Successfully installed requests
Cleaning up...

Uninstalls, fine:
dustin@deploy1:/usr/local/lib/python2.7/dist-packages$ sudo pip uninstall requests
Uninstalling requests:
  /usr/local/lib/python2.7/dist-packages/requests-2.2.0.dist-info/DESCRIPTION.rst
  /usr/local/lib/python2.7/dist-packages/requests-2.2.0.dist-info/METADATA
  /usr/local/lib/python2.7/dist-packages/requests-2.2.0.dist-info/RECORD
  /usr/local/lib/python2.7/dist-packages/requests-2.2.0.dist-info/WHEEL
  /usr/local/lib/python2.7/dist-packages/requests-2.2.0.dist-info/pydist.json
  /usr/local/lib/python2.7/dist-packages/requests-2.2.0.dist-info/top_level.txt
  /usr/local/lib/python2.7/dist-packages/requests/__init__.py
  /usr/local/lib/python2.7/dist-packages/requests/__init__.pyc
  /usr/local/lib/python2.7/dist-packages/requests/adapters.py
...
  /usr/local/lib/python2.7/dist-packages/requests/sessions.pyc
  /usr/local/lib/python2.7/dist-packages/requests/status_codes.py
  /usr/local/lib/python2.7/dist-packages/requests/status_codes.pyc
  /usr/local/lib/python2.7/dist-packages/requests/structures.py
  /usr/local/lib/python2.7/dist-packages/requests/structures.pyc
  /usr/local/lib/python2.7/dist-packages/requests/utils.py
  /usr/local/lib/python2.7/dist-packages/requests/utils.pyc
Proceed (y/n)? y
  Successfully uninstalled requests

This isn't our fault I don't think: your exception comes from pip. @dstufft?

This looks like you installed pip using your system package manager and it needs a version of requests installed.
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Yea what @sigmavirus24 said. Some systems unbundle requests from pip.

@dstufft is this maybe related to debian preventing pip from removing packages installed by the system package manager?

No, I think it's just because Debian unbundles requests. So whatever version of requests you install to the system needs to be compatible with what pip expects.

Interesting that there's a difference in our compat module between 2.2.0 and 2.5.0.

Seems it was removed in https://github.com/kennethreitz/requests/commit/47d0517d66e8cf5832768262221f0357ae134ad1
I assume pip has already worked around this?

pip itself doesn't use it anymore, but the version of pip that Debian has in it's system packages is older than when we worked around it.

Yeah, so I'm pretty sure this is one of those cases where we shouldn't have let @jschneier remove that import in requests.compat (our fault) mixed with the constant of "sudo pip install x is evil; use virtualenvs".
We could add the import back, but I would then mark it for deletion in 3.0 so this problem would just pop up again. So I'm going to close this since there's no solution that won't result in further breakage of other packages down the road.

Interesting. Thanks for considering the issue. So it's generally considered bad to install PIP via the OS's package manager?

It's generally considered best practice to do development inside of virtualenvs and in some cases, deploy inside of them as well so inter-application dependencies don't conflict with each other (unless you have a very sophisticated way of ensuring that two applications relying on the same dependencies don't break). Using the operating system's package manager for certain things (like pip) is okay most of the time. It totally depends on what you're doing. With that said, this ticket isn't the place to discuss in depth downstream redistributors of python packages or what happens when they package python software.

I agree with the virtualenv usage. I didn't realize that was decoupled
from the OS's version of pip (how else would it even be available?).
Dustin
On Mon, Jan 26, 2015 at 9:20 AM, Ian Cordasco<EMAIL_ADDRESS>wrote:

It's generally considered best practice to do development inside of
virtualenvs and in some cases, deploy inside of them as well so
inter-application dependencies don't conflict with each other (unless you
have a very sophisticated way of ensuring that two applications relying on
the same dependencies don't break). Using the operating system's package
manager for certain things (like pip) is okay most of the time. It
totally depends on what you're doing. With that said, this ticket isn't the
place to discuss in depth downstream redistributors of python packages or
what happens when they package python software.
—
Reply to this email directly or view it on GitHub
https://github.com/kennethreitz/requests/issues/2423#issuecomment-71466842
.


Crashing on Launch - iPhone 5S iOS 7 and iPad Air iOS 7 Simulator

After implementing DMPasscode in my project, iPhone 5S iOS 7 Simulator and iPad Air iOS 7 Simulator crashes on launch.
Console error:
dyld: Symbol not found: _objc_isAuto
Referenced from: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
Expected in: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.1.sdk/usr/lib/libobjc.A.dylib
in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
(lldb)
I'm sure it has to do with TouchID (iPhone 5S and iPad Air) and iOS 7 (since iOS 8 doesn't crash).
I found this thread on stack overflow about it:
http://stackoverflow.com/questions/26505658/ios-simulator-7-1-crash-running-on-yosemite-with-weak-linked-new-frameworks-sym
Have you experienced that ? Is it a xcode bug in Yosemite ?
Thanks

To my knowledge this library currently doesn't support versions earlier than 8.0. It relies on LocalAuthentication which is not available before iOS 8. We added macro to let it compile but it will still crash.

When I have time I will work on this but not sure when this will happen

Thank you

Actually it does support iOS 7. You just need to compile it with the newest Xcode / iOS 8 SDK. I think @dpopov added an ifdef, so maybe it even works with an older SDK.
Anyway, I'm using it in my app BitStore which works fine on iOS 7.
It seems to be a bug in Xcode, just use the 5 instead of the 5S (7.0 / 7.1) Simulator and it all works fine.
"If an app is weak linked against frameworks new in iOS 8 SDK and OS X 10.10 SDK, it may fail to run if the run destination is an iOS Simulator for older iOS runtimes and the host system is running OS X Yosemite. (17807439)"


Fixed issue with unhandled nils

Wrote some tests
Cleaned up a few non-rubisms
added .rspec file so it uses color and shows the tests

I hope you don't mind.
If you want, you can add me as a contributor and I can push up
some more cleanups...

Wow, this is great! I just wrote this as a quick one-off, but I'm glad people are finding it and using it :smile:  Since you offered I'll go ahead and add you as a contributor as well, and I'll pull the code later to update the gemspec and release a new version to rubygems.

Great! I can see about adding Travis as well.


💡Feature: Schema and handling for website and iframe

Description
With reference to #1078 and #1077, we need the schema to be updated properly.

We would need a website field (not required) and a iframe field (not required) in the schema.
We need to make sure that whenever the club is signing up, the fields are updated too as per the data that is received.

Screenshots
No response
🥦 Browser
Brave
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[ ] I am willing to work on this issue (blank for no)

Assignees me this one

Hey there we encourage 1 issue at a time, so until #27 is merged I would not assign you this, might be a mess-up. I'll keep this open for a while so that others can contribute too !

Sure that would be awesome. You can start to work on it.
📑 Checklist in case you missed something

Local project setup, .env for the backend.
Contributing guidelines to be followed.

Please maintain structure, use conventional pull request titles, and avoid spam to avoid closure or bans.