react-native-xcode error after upgrading to 0.46

Environment
react-native:
⇒  react-native -v
react-native-cli: 2.0.1
react-native: 0.46.1

node: v8.1.3
npm: 5.0.3
yarn: 0.27.5

Target Platform: iOS
Development Operating System: macOS Sierra
Build tools: Xcode 8.3.3

Steps to Reproduce

Project with RN 0.44
yarn upgrade --latest
react-native-git-upgrade
react-native run-ios

Expected Behavior
Expect my project to build
Actual Behavior
After upgrading to RN 0.46 from 0.44 i tried to run the project by using react-native run-ios but it fails building it with this error:
react-native run-ios produce this error:
    export WRAP_ASSET_PACKS_IN_SEPARATE_DIRECTORIES=NO
    export XCODE_APP_SUPPORT_DIR=/Applications/Xcode.app/Contents/Developer/Library/Xcode
    export XCODE_PRODUCT_BUILD_VERSION=8E3004b
    export XCODE_VERSION_ACTUAL=0833
    export XCODE_VERSION_MAJOR=0800
    export XCODE_VERSION_MINOR=0830
    export XPCSERVICES_FOLDER_PATH=myApp.app/XPCServices
    export YACC=yacc
    export arch=x86_64
    export variant=normal
    /bin/sh -c /Users/vood/dev/myApp/ios/build/Build/Intermediates/myApp.build/Debug-iphonesimulator/myApp.build/Script-00DD1BFF1BD5951E006B06BC.sh

/Users/vood/dev/myApp/ios/build/Build/Intermediates/myApp.build/Debug-iphonesimulator/myApp.build/Script-00DD1BFF1BD5951E006B06BC.sh: line 3: ../node_modules/react-native/packager/react-native-xcode.sh: No such file or directory

** BUILD FAILED **

The following build commands failed:

	PhaseScriptExecution Bundle\ React\ Native\ code\ and\ images build/Build/Intermediates/myApp.build/Debug-iphonesimulator/myApp.build/Script-00DD1BFF1BD5951E006B06BC.sh

change ../node_modules/react-native/packager/react-native-xcode.sh
to ../node_modules/react-native/scripts/react-native-xcode.sh

I met the same problem.

Same problem here as well, However I have moved the react-native-xcode.sh file to the new scripts file created and still face the same error.
react-native-cli: 2.0.1
react-native: 0.46.1
node: v8.1.3
npm: 5.0.3
yarn: 0.27.5

Thank you @AndrewJack suggestion of moving the react-native-xcode.sh script to a different folder worked, however I am wondering, why is this required? I mean is this just a workaround right ? Thank you

@sandinosaso sorry I should have been clearer.
Open in Xcode -> Select your Project -> "Build Phases" tab -> "Bundle React Native code and images"
Then change the above paths.

@AndrewJack thanks, works for me!

+1 @AndrewJack thx!

@AndrewJack I'm having the same trouble but with this error: ./node_modules/react-native/scripts/react-native-xcode.sh: No such file or directory , couldn't search for Bundle React Native code and images

@Tom29 in case you've initiated project with react-native v 0.46 and then downgraded dependency - you need to change in your ios/${Project}.xcodeproj/project.pbxproj next lines:

from export NODE_BINARY=node\n../node_modules/react-native/scripts/react-native-xcode.sh
to export NODE_BINARY=node\n../node_modules/react-native/packager/react-native-xcode.sh

thanks @andrewdacenko
i upgrade from 0,45 to 0,46 and get the same errors, ( why they renamed the folder ??? )
you need to change in your ios/${Project}.xcodeproj/project.pbxproj next lines:

from export NODE_BINARY=node\n../node_modules/react-native/packager/react-native-xcode.sh
to    export NODE_BINARY=node\n../node_modules/react-native/scripts/react-native-xcode.sh

tired of react native & npm. each time I add a package i get multiple problems for compiling, missing files etc....

I too had the same problem when upgrading from 0.44 to 0.45. A simple solution (hacky one though) was to create a new project using "react-native init", navigate to node-modules/react-native , copy the scripts folder and paste it into your actual project's node-module/react-native/ directory. Clean and re-build. This worked out for me !

Tip:
$ git grep 'react-native/packager'
ios/RPOJECT.xcodeproj/project.pbxproj:1530:                    shellScript = "export NODE_BINARY=node\n../node_modules/react-native/packager/react-native-xcode.sh";

same thing for me. the Bundle React Native code and images phase vanished.
so the above almost worked for me. But I'm on RN 0.47.2 so
export NODE_BINARY=node
../node_modules/react-native/scripts/react-native-xcode.sh
use script instead of packager to avoid script error.
hope this helped.

iam having a bit problem your help would be appreciated . iam having problem when releasing my iOS application . with my simulator every thing is okay i can build the app but when releasing i am having freeze with white screen after passing the splash screen . in android cam not having this issue . dam using the same steps of build in production as @scgough : in the project folder in Terminal run react-native bundle --platfrom ios --dev false --entry-file index.ios.js --bundle-output main.jsbundle Drag the reference to the main.jsbundle file into XCode under myapp folder In XCode, open AppDelegate.m and uncomment jsCodeLocation = [[NSBundle mainBundle]… Open Product > Scheme > Edit Scheme then change Build Configuration to Release Select myapp under the project navigator and then: under TARGETS: myappTests > Build Phases > Link Binary With Libraries press + select Workspace > libReact.a and Add compile in XCode with the ../node_modules/react-native/scripts/react-native-xcode.sh
very thing is okay in debug mode even with real device , all my provisioning profil are Okay i really need help it is blocking me . "@expo/ex-navigation": "^3.1.0", "assert": "^1.4.1", "babel-preset-react-native-stage-0": "^1.0.1", "bamlab-react-native-smooch": "^0.3.0", "base-64": "^0.1.0", "browserify-zlib": "^0.1.4", "bytebuffer": "^5.0.1", "console-browserify": "^1.1.0", "constants-browserify": "^1.0.0", "dns.js": "^1.0.1", "domain-browser": "^1.1.7", "events": "^1.1.1", "https-browserify": "0.0.1", "install": "^0.10.1", "lodash": "^4.17.4", "mockdate": "^2.0.2", "moment": "^2.19.1", "net": "^1.0.2", "numeral": "^2.0.4", "path-browserify": "0.0.0", "process": "^0.11.10", "prop-types": "^15.6.0", "querystring": "^0.2.0", "querystring-es3": "^0.2.1", "react": "16.0.0", "react-native": "0.49.3", "react-native-crypto": "^2.1.1", "react-native-datepicker": "^1.6.0", "react-native-drawer-layout": "^1.3.2", "react-native-fbsdk": "^0.6.3", "react-native-fetch-blob": "^0.10.8", "react-native-form-idable": "^1.0.2", "react-native-gcm-android": "^0.2.0", "react-native-google-analytics-bridge": "^5.0.1", "react-native-http": "github:tradle/react-native-http#834492d", "react-native-i18n": "^1.0.0", "react-native-level-fs": "^3.0.0", "react-native-linear-gradient": "^2.3.0", "react-native-md5": "^1.0.0", "react-native-os": "^1.1.0", "react-native-push-notification": "^3.0.0", "react-native-randombytes": "^3.0.0", "react-native-root-siblings": "^1.2.1", "react-native-root-toast": "^1.3.0", "react-native-svg": "^5.4.2", "react-native-swipeout": "^2.2.2", "react-native-swiper": "^1.5.13", "react-native-system-notification": "^0.2.1", "react-native-tcp": "^3.3.0", "react-native-udp": "^2.2.0", "react-native-vector-icons": "^4.4.2", "react-redux": "^5.0.6", "react-static-container": "^1.0.1", "readable-stream": "^1.0.33", "redux": "^3.6.0", "redux-enhancer-react-native-appstate": "^0.1.1", "redux-logger": "^2.7.4", "redux-persist": "^4.4.1", "redux-saga": "^0.14.3", "stream-browserify": "^1.0.0", "superagent": "^3.3.2", "timers-browserify": "^1.4.2", "tty-browserify": "0.0.0", "url": "^0.10.3", "victory-native": "^0.15.0", "vm-browserify": "0.0.4" appdelegate.m:

(BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
//jsCodeLocation = [[RCTBundleURLProvider sharedSettings]<EMAIL_ADDRESS>fallbackResource:nil];
NSURL *jsCodeLocation;
jsCodeLocation = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
RCTRootView *rootView = [[RCTRootView alloc] initWithBundleURL:jsCodeLocation
moduleName:@"x"
initialProperties:nil
launchOptions:launchOptions];
rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];
self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
UIViewController *rootViewController = [UIViewController new];
rootViewController.view = rootView;
self.window.rootViewController = rootViewController;
[self.window makeKeyAndVisible];
[Smooch initWithSettings: [SKTSettings settingsWithAppToken:@"x"]];
[[FBSDKApplicationDelegate sharedInstance] application:application
didFinishLaunchingWithOptions:launchOptions];
return YES;
}

I am using 0.50 and its moved to
export NODE_BINARY=node
../node_modules/react-native/scripts/react-native-xcode.sh
Is there ever gonna be stability in RN?

@AndrewJack So pressed for time right now and your solution has saved me twice in the last couple months. Thank you!

Same issue while downgrading from 0.51 to 0.45
in 0.51

export NODE_BINARY=node
../node_modules/react-native/scripts/react-native-xcode.sh

is already there in build phases

If someone still has this issue, check that the export NODE_BINARY path is correct. My beginner's advise:
Recommended (react-native installed as global)
You probably have already installed react-native from npm (with -g global option ). Thus it is useless to duplicate the react-native module in your project. Locate where it is installed and link it in xcode.
For me, react-native is installed in /usr/local/lib/node_modules/ and the following path worked:
export NODE_BINARY=/usr/local/lib/node_modules/react-native/scripts/react-native-xcode.sh
Not recommended
Another possibility is to install react-native and link it with the "--save" option.
in your root folder run: npm install --save react-native
and then the default path on xcode:
export NODE_BINARY=node ../node_modules/react-native/scripts/react-native-xcode.sh works.

@woshizhoujie solution worked for me


Vidzi no loinger working, 'cannot parse json file'.

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.03.20. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.03.20

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
youtube-dl --verbose https://vidzi.tv/grjtuxrkwir1.html
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'https://vidzi.tv/grjtuxrkwir1.html']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.03.20
[debug] Python version 2.7.10 (CPython) - Darwin-17.4.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.4.2, ffprobe 3.4.2, phantomjs 2.1.1
[debug] Proxy map: {}
[Vidzi] grjtuxrkwir1: Downloading webpage
ERROR: grjtuxrkwir1: Failed to parse JSON  (caused by ValueError('Invalid control character at: line 1 column 317 (char 316)',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 702, in _parse_json
    return json.loads(json_string)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 382, in raw_decode
    obj, end = self.scan_once(s, idx)
ValueError: Invalid control character at: line 1 column 317 (char 316)
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 785, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 440, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/vidzi.py", line 57, in _real_extract
    video_id, transform_source=js_to_json)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 706, in _parse_json
    raise ExtractorError(errmsg, cause=ve)
ExtractorError: grjtuxrkwir1: Failed to parse JSON  (caused by ValueError('Invalid control character at: line 1 column 317 (char 316)',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Closing this. It seems as of the update today, it is working again. 2000 thanks youtube-dl community!


FIX: Add way to change predicate and sorters for CoreDataSource

Add a way to change the predicate associated with a CoreData source
Add a way to change sorters as well
Added tests

Based on this comment, the delegate will not get notified when the results change as a consequence of the predicate changing. It might be worthwhile to add a new closure property to the CoreDataSource to let its listener know that it needs to refresh its table view or collection view entirely.

Yes, the delegate doesn't get notified (I was kind of hoping that it would).  Instead, I just do a reloadData on the collection view since I'm not going to get the inserts/deletes.  I could add a new closure method, or could just document the fact that you'll need to refetch the data.  I added this at the CoreDataSource level instead of the DataSource level because it's very CoreData specific, and I worry a bit about adding too much extra stuff to the class, but I'm open to it if you'd like me to support it...

Requested changes plus improved comments pushed, also rebased so that I pick up the new pod spec version.

That's a great point. I'd note it in the docstring comments of the properties you've added!

I think I did update the comment?


Implementation of automatic Open Graph image generation for collection pages

I'm currently working on adding automatic Open Graph image generation for collection pages, inspired by the approach detailed in this post.
My progress can be seen in the branch: feat/docs-og:

I would greatly appreciate any feedback or suggestions on this implementation. If this aligns with our project goals, I'm eager to continue refining this feature.

I have some questions:

Why is the docs collection not using a base path as the other collections? This might cause collisions with Astro pages published in the pages directory:

http://localhost:4321/guides/getting-started          (actual)
http://localhost:4321/docs/guides/getting-started     (suggested)
                      ^^^^

What do you think about requiring a title and description properties in all the collection schemas? Right now the products collection doesn't have any of this properties in the root of the schema

Why is the docs collection not using a base path as the other collections?

There is a hacky solution where we can nest the docs collection within a second docs folder like src/content/docs/docs to prefix all Starlight paths with /docs. So getting-started.md will be at http://localhost:4321/docs/docs/guides/getting-started. I tried this at first, but then reverted back to the default option.

What do you think about requiring a title and description properties in all the collection schemas?

Right now the products collection doesn't have any of this properties in the root of the schema
Yep, that's right. For the products collection, it would be main.title and main.subTitle. To be honest, I don't know; I just tried a different approach, plus reserved description for the actual long description, with its own title and subTitle.
I've read the post and checked the repo; it looks like if we are implementing automatic OG generation, the collection schemas should be identical across collections. I will refactor the products accordingly, so we can use
getImageOptions: (_path, page: (typeof pages)[number]) => {
    return {
      // Use the page title and description as the image title and description.
      title: page.data.title,
      description: page.data.description,
      // Customize various colors and add a border.
      ...
    }

from the post.

for og image generation,  this is also a good reference as well https://astro-paper.pages.dev/posts/dynamic-og-image-generation-in-astropaper-blog-posts/
Library used by this guy is very good library for image generation https://github.com/vercel/satori
with this library you can use existing html/css to generate the images. You can see the examples of input and output here
https://og-playground.vercel.app/ . Please consider this approach as well.

There is a hacky solution where we can nest the docs collection within a second docs folder

You are right, this is the only way according to the Starlight docs: https://starlight.astro.build/manual-setup/#use-starlight-at-a-subpath

In the future, we plan to support this use case better to avoid the need for the extra nested directory in src/content/docs/.

@newbeelearn thanks for the references.. I'm using a similar approach in my portfolio site with @vercel/og. I followed this guide and this is the result:

A bit harder to set up but much more flexible

i am unable to find the source code of this library https://www.npmjs.com/package/@vercel/og , it looks like it would be using vercel edge functions also refer to this https://github.com/vercel/og-image/issues/226#issuecomment-1278124064 . I am afraid this looks like a big limitation to force all the theme users to use some commercial service.

Well, if that's the case, I think it would be better to stick to Hideoo's implementation. We can always reference other options for users to decide which one to choose.


Ability to create multiple front-end apps (React plus Swift, Android, etc.)

Is your feature request related to a problem? Please describe.
We would like to be able to create a website and mobile apps for a project. It is not clear if/how it possible, plus the /amplify folder setup files appear to be wired for one front-end app only.
Describe the solution you'd like
It would be awesome if there was a way to add another front-end app with the CLI. For example, with a command like amplify frontend add or as a part of the amplify init workflow.
For example, let's say I have a React app already and now I'd like to add an iOS Swift app. Going through the CLI, perhaps I can enter the amplify init flow:
? Do you want to use an existing environment? Yes
? Choose the environment you would like to use: master
? Do you want to add another frontend? Yes
? Choose your default editor:
❯ Xcode
  Sublime Text
  Visual Studio Code
  Atom Editor
  IDEA 14 CE
  Vim (via Terminal, Mac OS only)
  Emacs (via Terminal, Mac OS only)
  None
? Choose the type of app that you're building (Use arrow keys)
  android
❯ ios
  javascript
? Enter the name of your source directory: ../packages/my-mobile-app
...

Note that it would be great to be able to specify Xcode as an IDE, as well as a different folder for the mobile app's source code. This different folder would be helpful for doing a codegen, for example.
Perhaps the amplify/.config/project-config.json file could hold an array of these frontend projects:
{
  "frontends": [
    {
      "projectName": "my-website",
      "version": "1.0",
      "frontend": "javascript",
      "javascript": {
        "framework": "react",
        "config": {
            "SourceDir": "../packages/my-website/src",
            "DistributionDir": "build",
            "BuildCommand": "npm run-script build",
            "StartCommand": "npm run-script start"
        }
      },
      "providers": [
        "awscloudformation"
      ]
    },
    {
      "projectName": "my-mobile-app",
      "version": "1.0",
      "frontend": "ios",
      "ios": {
        "config": {
          "SourceDir": "../packages/my-mobile-app"
        }
      }
      "providers": [
        "awscloudformation"
      ]
    },
  ]
}

Describe alternatives you've considered
The current work around I've been toying with is to use lerna to create multiple packages. In that approach, I have a packages directory that contains a sub-folder for each frontend. However, for one thing, this approach gets problematic when wanting to generate code for an API. Also, for the second front-end that you add, you have to go through a very manual process of trying to 'hack' the pieces together for it to work and worry about not breaking the existing app. And there are some files that don't support multiple front-ends, such as project-config.json.

Thanks for the feedbacks, marked the feature request, we will have a discussion among the team on this.

@UnleashedMind  Excellent, thanks for considering it!

+1 on this feature request, in our case React Native / React Web / and a CLI.
(Also would like two graphql endpoints, one with cognito auth and one with an api token as auth)

Same need here. Needing to evolve a previous MobileHub project (stuck in AWSSDK 2.6.x) and when everything seemed great in Amplify I ended up with this.
In my case the product has two apps, one iOS and the other one Android, and they both need to use same storage folders (private, protected, public) for same logged in user and for backend code coherence.
Please any ETA would be appreciated.

+1 for the feature!
And what is the recommended way to achieve this as of now? Where should you initialize your amplify project?
Thanks!

https://aws-amplify.github.io/docs/cli/init#amplify-configure-project
Maybe this helps @ChristopheBougere

Thanks @brunoguedes !
So if I have a monorepo with 3 frontend apps, I have to setup amplify in the first app, and then copy the config files in the other apps folders?
Couldn't this be problematic if I use the multi-env feature as well? Or maybe it's better to create a symbolic link between the amplify config files rather than copying them?
Anyway, it would be great to have a way to setup amplify config separately from the frontends.
Something like amplify init at the root of your repo and then amplify attach react/amplify attach ios/... in your frontend folders)

What happens after you copy your amplify/ throughout the front end projects and you need to update anything from the backend, like the schema or add functions? You need to copy the updates again?

Hi @ChristopheBougere and @tafelito. Sorry to disappoint but I was just having the same issue as you guys. I'm trying this for the first time now as well and found that link I sent.
I hope some one from the Amplify team pick this feature request soon, or give us a bit more guidance.
Cheers

@ChristopheBougere I've found that this procedure (even with multi-env) is not too bad. It works fairly well and is easy enough to maintain. I agree that this feature should be available natively, but the workaround isn't a dealbreaker.
I would recommend manually copying the files instead of using a symbolic link, but that's a preference issue.
These are commands that I find myself using frequently:
amplify status
amplify env pull --restore
amplify env import

@ajhool what the steps should I make to create a multi-frontend interface to the same backend?

First off, I would create a new Environment in Amplify so that you don't mess up existing infrastructure.
I have only done this with two web-based / React projects, so it's possible that it will be more difficult for different frameworks. However, check out amplify configure project in the Usage section of the docs
https://aws-amplify.github.io/docs/cli/init
Basically, you need to copy over the Amplify directory from your existing project/framework to the root of your second frontend's directory. The Amplify directory contains information about the backend stack that you're using (by copying these files over, both frontends will use the same backend info). The Amplify directory also contains autogenerated files that will be overwritten (these files are mostly included in .gitignore and you should make sure that the .gitignore in your second project includes the appropriate Amplify files/dirs)
I would also update amplify-cli to the latest version (yarn upgrade @aws-amplify/cli --latest) before doing any of this. The package has been evolving rapidly and the support for multiple environments has greatly improved.

@ajhool if you need to change anything on your schema, do you do it in any of the front-end apps and then you do the pull?
What about if you change anything directly in the AppSync console? How do you get those changes to from the cli?

@ajhool if you need to change anything on your schema, do you do it in any of the front-end apps and then you do the pull?

Correct. I make the change in a front-end app, push the change, and then pull it into the other front-end apps. I always do the changes in the same front-end app, mostly for consistency's sake but also  as a safety measure to avoid pushing/pulling conflicts.

What about if you change anything directly in the AppSync console? How do you get those changes to from the cli?

Hm. I don't believe that you can get those changes from the CLI. If you make a change to a mutation using the AppSync console, for instance, you need to use the no-gql-override flag on push. It looks like the team is building up some functionality like that though, this issue/conversation might be of interest: https://github.com/aws-amplify/amplify-cli/issues/74

@ajhool I have an "ionic app" and "react admin dashboard",
can you correct me the step as I understand?
=== First Project ===
1 - create react app
2 - initialize amplify with "dev" environment
3 - amplify add API / add auth
4 - config the schema and user auth
5 - amplify push
=== Second Project ===
1- create Ionic App.
2- amplify init
3- copy project-config.json from the first project and added to this project
4- amplify env pull
is this correct?

@ajhool when do you use no-gql-override? You mean if you change something on the appsync console and then on the cli, so you don't override the console changes?

@NuruddinBadawi yes, I believe that is mostly correct although there are a few possibly missing details.

Make sure your amplify/cli is up to date ( yarn global update @aws-amplify/cli --latest).

The Second Project step 4 might need to be amplify env pull --restore which will update the local backend to reflect the actual backend.

The Second Project step 3 needs more files than just project-config.json, I believe. It should be all of the files that aren't in your .gitignore file -- when I use VSCode and github, it's easy to tell which files I need. The files appear to be:

.config/project-config.json
team-provider-info.json
The entire backend folder EXCEPT amplify-meta.json. Using the --restore flag on pull might rebuild this backend folder, I'm not sure. Copying is easy and not harmful.
There's also a .graphqlconfig.yml in my root dir that isn't in my .gitignore, but I feel like this is a generated file that doesn't need to be copied over.

Please let me know how it goes!

@tafelito yes, when you make certain changes on the appsync console (eg. adding a custom resolver) that you don't want Amplify to override.
By default, Amplify generates all of the AppSync resolvers, mutations, queries, etc. for your Amplify API, so if you make a change to your API schema and push, Amplify will overwrite any changes you've made to those resolvers on AppSync.
However, Amplify now supports custom resolvers (https://aws.amazon.com/blogs/mobile/amplify-adds-support-for-multiple-environments-custom-resolvers-larger-data-models-and-iam-roles-including-mfa/), so you might be able to write your custom resolvers in the frontend code instead of through the AppSync console.

@NuruddinBadawi I believe it is not correct to amplify init in the second project. Note that init will create a brand new project i.e. backend and will create AuthRole and UnauthRole.
The steps for first project are correct but for the second project you need:

Create Ionic project
Copy the whole Amplify folder from the first project to the root folder of the second project.
Call amplify configure project it guides you through the rest of choice.
The last call will update the amplify configuration to work with your second project environment.

I agree that "init" might not be needed. All I know is that it is "a" way to achieve it, which worked for me, even though it might not be "the" correct way to do it. I do agree that amplify configure project is probably a better strategy and my approach might be outdated

I tried to make an experimental project supporting multiple fronteneds. I did as follows:

Created project with Android FE
Added API (and auth)
Created an Angular FE with ng and copied amplify/ dir from Android project dir to Angular project dir.
Ran amplify configure project

When running "amplify codegen" it still generated Android GraphQL, so ran "amplify configure api"
Now, when running "amplify codegen" I get:
✔ Downloaded the schema
⠋ Generating GraphQL operations2019-05-07T13:37:44.768Z - error: uncaughtException: Language android not supported
I can see no mention of android in the amplify dir.
What is the proper way of supporting multiple frontends wth one backend? There seems to be no tutorials on this.

I think we can use submodules for this situation. What thoughts about this?

I think we can use submodules for this situation. What thoughts about this?

@Jexim Have you tried it ? It seems like a good solution if you want to work with a team and with multiple clients.

It's been a good amount of time with this one being discussed. Did anybody find a stable procedure to do this without any serious downsides?
This should really be out of the box, we are many out here making several individual web apps or using both React + React Native backed by the same backend.

Hello - Looks like this issue was opened last year before the multi-env features were released which allow you to share projects between multiple frontends. This is documented here: https://aws-amplify.github.io/docs/cli/init#amplify-configure-project
Is there still an issue related to this? It's hard to determine from the thread as it goes back a while. Or is the issue that this isn't easily discoverable in the docs?

Thanks for your feedback @undefobj!
Maybe it's just me, but I don't see how multiple environments solves that without new issues.
For example, all my dynamo tables embeds the environment name as part of the table name, so if I have app1 and app2 I would not be able to share the same DB tables for both apps without modifying how Amplify names the different resources, which seems like an even bigger task, than the already proposed workarounds in this thread, and in addition I completely lose the chance to run an isolated dev and prod environment for each app also.
Is there something obvious I have missed here?

@houmark Did you read through the instructions in the link and test out the workflow on multiple apps? I only mentioned multi-env as that was the release which introduced the functionality. It has steps to share a backend in a single environment. The page says "When sharing your backend infrastructure code with multiple frontends".
So to summarize: This is supported out of the box in Amplify today. The question is around the workflow and if more functionality is required.

I did, but I had a long session, so I probably better get some sleep and read it again and try it out. Thanks for now, I'll report back here in any case, so everyone else that may not have been aware of this can get an update.

@undefobj I discovered that today and decided to give it a go.
The only thing I'm wondering is how does it work with conflicts ? What happens if two persons try to modify the same service at the same time ? Or if someone push changes before you push yours ?
I also think that it should be a little bit easier to find in the doc. A small example of the workflow would be great !
Thanks for your help

I also think that it should be a little bit easier to find in the doc. A small example of the workflow would be great !

Same for me. I did not really see how multiple frontends would be working from the docs you linked on configure. I saw this thing called "Do you want to use an existing environment?" elsewhere in the docs, where it did not mention multiple frontends, but I suspect that is part of this?
Still, having to manually copy over folders seems like a workaround/hack, so improved docs and maybe even an improved CLI to have a more guided flow to do this would be nice. I have considered different branches inside my main git for the different apps or the above mentioned submodule approach, but I don't have 1-2 days to spend on trying out options, but I need my second app out SOON and worry about how much time I will spend getting something decent working.

Ok so it's a doc discoverability issue. @kaustavghosh06 tagging as an FYI for the refresh on the doc structure.
"manually copy over folders seems like a workaround/hack" What's the alternative to this? Does the CLI ask for the other destination project and copy things for you? Does the CLI copying to a different directory really seem like less of a "hack" then you manually copying?
What if it's on another machine? Then you really need some sort of copy process. I'm not sure a git workflow is correct here, but I'm happy to be wrong. If I have a React and an Android app with a single backend this really seems like a copy process.

Someone proposed to make it possible to add several folders inside the root folder so all apps live inside there, which makes copying the amplify folder not needed.
That way each of those in theory could be their own git and so could the amplify folder (maybe using submodule).
It seems like the copying is not creating any issues for people so I’ll try that to start with.

To clarify: Several folders from the root level, one for each front end and all created by a guided Amplify CLI flow so amplify knows about each citizen.

Agreed with @houmark, having as single amplify project shared with multiple frontends would be the best. Something like this:

/amplify
/react
/react-native
The CLI could handle this with a amplify frontend add command, similarly to categories.

/amplify
/react
/react-native
The CLI could handle this with a amplify frontend add command, similarly to categories.

Exactly, just like that.

For what it's worth I contacted Amazon support regarding multiple app frontends.
Before that I tried using amplify configure project, as the doc says that it should be used "When sharing your backend infrastructure code with multiple frontends". But it was ultimately to no avail - I got all sorts of errors, especially with codegen for GraphQL API.
Instead, what they proposed was to init both frontends as separate projects. I keep the JS project as the main project, so the JS project is always in sync with the backend. I then added the API manually, using "amplify add codegen --apiId XXXXXX". When I change the GraphQL API, I run "amplify codegen", which pulls the new schema from the backend. After that the gradle plugin builds the types ec. Java classes.
It works, but I think the process is poorly documented, and I really would like to see an official tutorial.

We ended up doing almost the same, which means, we are sharing the same backend app across micro-frontends
We shared the backend amplify app as a submodule, so you can easily have access to the generated files, but then you also need to copy the aws-exports and the graphql generated files.
At the end it seems more like a patch, which at some point in time comes back to remind you that something is wrong. As, in we struggle the same trying to create our CI/CD pipelines.
For now it works, but doesn't seem to scale very well with multiple applications sharing one codebase.
We are now moving away from amplify and creating our own aws cloudformation templates with nested stacks.

Hello guys, we've added more documentation around this topic in our docs. You can checkout the amplify env import command as mentioned in  the docs  to seamlessly copy over a project info into another frontend roject.

Hi I have been following the advice detailed here https://aws-amplify.github.io/docs/cli-toolchain/quickstart#multiple-frontends to create a multi frontend app with one amplify backend. It is working fine with respects to all backend auth and graphql the only problem I face now is Hosting as when I change the hosting of the app to another bucket and then push when I pull the env in the other app it is overwriting the hosting. Is there a way to make hosting separate to the rest of the backend setup?

@magjack I have actually the same issue with hosting. I am stacked.
My Goal:

same backend
2 apps written in React => 1 hosting solution (S3+Cloudfront) for each app.

Did anyone found a solution?

Yes, I did I used the Amplify console. So remove all hosting you do with the CLI and use the console as it configures hosting in a different way and deploys the CLI configured backend. You can see more here https://github.com/aws-amplify/amplify-cli/issues/2406. It is also really useful for setting up a CI/CD as well.

@Nicosoft we added a new amplify pull and updated the multi-frontend doc to highlight the workflow: https://aws-amplify.github.io/docs/cli-toolchain/quickstart#multiple-frontends

@Nicosoft we added a new amplify pull and updated the multi-frontend doc to highlight the workflow: https://aws-amplify.github.io/docs/cli-toolchain/quickstart#multiple-frontends

NIIIIIICE!

@Nicosoft we added a new amplify pull and updated the multi-frontend doc to highlight the workflow: https://aws-amplify.github.io/docs/cli-toolchain/quickstart#multiple-frontends

Awesome!

What about when both my front-ends are in one repo? I want to codegen to multiple different places, but it's not possible currently.

@Nicosoft how would this work with 2 react apps exactly? As I don't think you can publish to a frontend (s3 + cloudfront) for the second app.
We were thinking of using the same cognito for backend/frontend access and we had split them into two different codebases.

I see the issue has been closed. What was the recommended solution if you have React, iOS and Android apps?
Right now we are maintaining three repos (amplify+react, ios, android). We make all of our changes to the backend in the amplify+react repo. Then, we run amplify pull with the --providers, --frontend, and --amplify arguments in both of our native mobile repos.  We also run amplify codegen for each.  After all of this we end up with updated config settings in the native mobile app repos.
Our current approach is very painful. It is difficult to keep all of these settings in sync across the projects. Because of how amplify manages multi-environment projects it is also difficult to build a native mobile app that can talk to either the dev, test or prod version of the backend.
The whole approach currently seems like a workaround.  Could an RFC be opened where we might collect everyone's thoughts on a possible better approach?

@magjack  @Nicosoft
How did you handle this flow?
One amplify backend.
2 React Apps (each one in different git repositories) and host them in the amplify console, and targeting the same backend?
Also, how to achieve each frontend to target to specific backend environment?

+1 on this feature request, in our case React Native / React Web / and a CLI.
(Also would like two graphql endpoints, one with cognito auth and one with an api token as auth)

me too, i also need the feature, i thought to go with yarn workspace.

I created this issue https://github.com/aws-amplify/amplify-cli/issues/6247 to address the folder structure problem


#1469 Create Spring boot application for Audit Mongo service

https://github.com/Activiti/Activiti/issues/1469

@erdemedeiros
I added your suggestional test.
Please review again.


Directional Fans

About the PR

This PR introduces the Directional Fan, a slightly less abusable version of the Tiny Fan to be used with shuttles and docking ports.
The Directional Fan blocks atmos transfer between two tiles. This is different to the Tiny Fan, which blocks atmos transfer to and from a single tile. The only practical difference this makes is that the tile the Directional Fan is on can also be spaced; it's no longer a "safe tile" to stand on if any of the tiles it's not facing gets spaced.
It's basically like a windoor you can walk through.
Why / Balance

Tiny fans are a bit of a bandaid solution but they are necessary to prevent spacing when docking and important locations like the Arrivals shuttle from being accidentally spaced.
However it is kinda jank that people can survive a spaced Evac shuttle by just standing in the shuttle doorway. Replacing those fans with this would remove that strategy and force crew to die actually put on EVA.
This is a mapping only item and should only be utilized where tiny fans are currently used. This PR does not make any map changes; it is up to mappers to replace existing tiny fans with directional fans once this PR has merged.
Technical details

Turns out this was possible with just yaml? Wow.
Media

Example of Directional Fans blocking atmos to a spaced corridor:

Example of a Directional Fan not being a "safe tile", as the area around it is spaced:

They even work in abnormal shapes:

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

no cl due to no playerfacing changes

This seems cool! I do think the sprite needs to be a bit brighter, maybe even including a splash of colour from the atmos department palette. Tiny fans are pretty noticeable, mainly because they're animated.

you missed the perfect opportunity for loss on the last image

This is a good design and would be a welcome change to fix the tiny fan exploit, but "just put on EVA lmao" is not a good solution to the shuttle bombing meta in tot rounds overall.

I swear to god I had a dream about this last night. Also, a request, can we have some sort of stationary short lived holofan that IS buildable for our shittles? Like the door opens and you got 10 seconds to get out before it closes to recharge its fan. Opening during recharge spaces

Like the door opens and you got 10 seconds to get out before it closes to recharge its fan. Opening during recharge spaces

shrimply make an airlock controller with air alarm sensor and logic gates

maybe not fan, but thin atmos holoprojection?

maybe not fan, but thin atmos holoprojection?

My reading of holoprojections are that they are temporary; this is consistent with all holoprojections, including Sec's and Janitor's.

This seems cool! I do think the sprite needs to be a bit brighter, maybe even including a splash of colour from the atmos department palette. Tiny fans are pretty noticeable, mainly because they're animated.

These are animated similar to tiny fans. I'm not particularly attached to the sprite though.

How does the sprite look under a docking port?

Closed due to feature freeze May 10th-June 14th. Comment to have it reopen after this.

Requesting this PR to be reopened.
The texture has been updated to work better with airlocks and actually look like fans. It also can now theoretically stack on the same tile without clipping issues.
https://github.com/space-wizards/space-station-14/assets/83650252/6e20f029-6d0b-4110-b969-111e1130ddc4

if directional fans are used on escape pods then you wont be able to simply unanchor a thruster to get out of the station anymore.
that is if pressure damage wasn't reduced to 1/4 of its original value.

if directional fans are used on escape pods then you wont be able to simply unanchor a thruster to get out of the station anymore.
that is if pressure damage wasn't reduced to 1/4 of its original value.

Good.
That being said this PR does not remove tiny fans so if no one changes the escape pods they'll remain as they are.

These are cool, great work. These remind me of the huge blasts of air when you wander into a supermarket through the automated doors, to keep the bugs out


Updated changes from stable-baselines update.

python train.py fails because ActionNoise as changed locations in the main stable-baselines repo. This fixes import from ddpg to common

Hello,
Do you have the latest master version?
because the backward compatibility is normally ensured (see https://github.com/hill-a/stable-baselines/blob/master/stable_baselines/ddpg/noise.py)

Oh, I see, this is the base class import...


An error occurred: Failed to get successful response from server

Super good job amigo, but I can't get it to work....
when I call var response = await client.PostAsync(APIConstants.OpenAIEndpoint_Completions, content); I get this error, any ideas?
thank you.
public async Task<string> AskQuestion(string query)
        {
            try
            {
                var completion = new CompletionRequest()
                {
                    Prompt = query
                };

                var body = JsonSerializer.Serialize(completion);
                var content = new StringContent(body, Encoding.UTF8, "application/json");

                var response = await client.PostAsync(APIConstants.OpenAIEndpoint_Completions, content);

                if (response.IsSuccessStatusCode)
                {
                    var data = await response.Content.ReadFromJsonAsync<CompletionResponse>(options);
                    return data?.Choices?.FirstOrDefault().Text;
                }
                else
                {
                    throw new Exception("Failed to get successful response from server");
                }
            }
            catch (Exception)
            {
                // Handle exception or log the error here
                // await Application.Current.MainPage.DisplayAlert("Error", $"An error occurred: {ex.Message}", "OK");
                throw;
            }
        }

My bet....
I had temperature = 7 ..... O forgot to use 0. to be 0.7 as temperature cant exeed 1
I am just leaving this for anyone else/

Hello @TheStoneMX, apologies for the delayed response. The 403 error you experienced was due to the deprecation of the text-davinci-003 model. We've since transitioned to the gpt-3.5-turbo-instruct model, which I've already updated. Thank you for bringing this issue to our attention.
https://github.com/danielmonettelli/dotnetmaui-chatgpt-oss/commit/586bded463888a0ce77f87bbc4c172d9a0ceddd6


Revert "modifications in preparation for first alpha release"

Reverts biota/sourcetracker2#38

@gregcaporaso sorry, I merged without your modifications...

@lkursell, I'll just make those changes in when I prep the release, no need to revert that merge.


bug(MatFormField/MatSuffix): first visible Mat Suffix (inside form) triggers click on input field enter event

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
?
Description
I've been experiencing issues, i've used mat suffix to display a clear button which clears the current control/input field but i experienced that input enter event also triggers a click event on mat suffix
Reproduction
Steps to reproduce:
stackblitz
Expected Behavior
Enter not causing mat suffix click event on first control
Actual Behavior
Enter on inputs causes first visible suffix to trigger click event
https://user-images.githubusercontent.com/17952364/203159699-4e252767-4b02-49e0-a1b7-3ce7e88b3404.mp4
Environment

Angular: v15.0.0
CDK/Material: v15.0.0
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows

Add type="button" to your button controls.
"submit" is the default type if the attribute is not specified for buttons associated in a form, or if the attribute is an empty or invalid value.
So pressing enter while in the form invokes the first button where you did not specify the attribute.
For reference: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button#attr-type

And here is some documentation regarding the pressing of ENTER while in a form and how it relates to buttons in the form.https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#implicit-submission


[Bug] Non-destructive resizing during drag-resize or scroll-wheel uses longest edge for portrait images causing render discrepancy between preview and reading mode

When an image is taller than wider, resizing it by dragging the edge or scrollwheeling does not work properly. I think it is because the plugin is using the longest side of the image as the size value rather than just the width.

Well spotted, and thanks for reporting.
At some point I wanted to add many more non-destructive resizing options and never got to it
| width
| widthxheight
| widthxheigh - based on longest edge
| widthxheigh - based on shortest edge
If you cannot wait for the next release -> this should fix it:
main.zip

Thanks and great work!

It should be now fixed in 1.2.13 🚀


Store ranks based on player type.

CML stores player ranks based on their player type. We don't, so if a player is #100 on hardcore ironmen but #20345 on regular hiscores, we save their rank as 100.
Currently we save regular by default. To fix this, we would have to determine the player type BEFORE saving the player's first snapshot, and from then on, every hiscores fetch would have to be directed at the correct type endpoint.
The downside is that for players who already have been tracking themselves, it would show a bump in their rank graphs as they went from 100 (on cml) to 20345 (on wom) and then back down to ~100 when this is fixed.

Okay so, these are the plans to fix this:

If a player is new or has type "unknown", determine its player type first, and then fetch snapshot data from the correct snapshot (this should fix future snapshots to have ironman rank)

It doesn't however fix snapshots from the past week, so for those, i'll have to invalidate every rank value to -1 FOR IRONMEN and make the graphs on the player page skip -1 values (so it will show a straight line from the last cml import, to the new snapshot after the fix)


.NET Microframework support ???

is there version of .NET Micro Framework 4.3 or 4.4 support
or
we need still to continue with old client  from   https://github.com/eclipse/paho.mqtt.m2mqtt

Hi,
sorry but this is not planned.
Best regards
Christian

Why Micro Framework? You can use .net core example and .net core runtime is small.

@biapar
because I'm using development boards and not pc
(such are Nucleo STM32F411 or Fez Spider 2 http://old.ghielectronics.com/catalog/product/432 )
and for a moment is compiled only https://github.com/eclipse/paho.mqtt.m2mqtt
but  i will like this ones to be able to compile client (at least too in ,NET Micro Framework)


OSCert updates

Added DayTrader10, update to java17, adminCenter config updates

Now that Fyre has fixed the content-type return to json, I have retested creating a new Fyre vm with the original logic.
I tested the fyre_provision.yaml with a small change to fixed an error with the line indent problems:
 args: "{{ extra_props| default(omit) }}"

@gmarcy @websterc87 Can we get together to review this pr?
I cleaned it up such the only updates are to the logic I use in my operations.


updated VMware homepage_url

I used one that better represents what we do in open source to replace the github org URL that only pointed one of our many GitHub orgs.
Signed-off-by: Dawn M. Foster<EMAIL_ADDRESS>

thank you @geekygirldawn, happy to take more ideas on how to make the landscape better, from filters and so on
another idea is to add OSPO related tools https://github.com/todogroup/ospolandscape/issues/26


Use link to hyperSpec class in @return

For functions, that return hyperSpec object, use link to hyperSpec class as follows:
#' @return [hyperSpec][hyperSpec::hyperSpec-class()] object.

Just a quick comment about this issue. I recently learned and began using @template for documentation that occurs a lot of places and which one might want to fine tune or change from time-to-time.  Very handy. Described here.


Automated cherry pick of #1092: 修复参数赋值问题

Cherry pick of #1092 on release/2.10.0.
#1092: 修复参数赋值问题

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@fb6565a). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff                @@
##             release/2.10.0   #1093   +/-   ##
================================================
  Coverage                  ?   7.85%
================================================
  Files                     ?     356
  Lines                     ?   56542
  Branches                  ?       0
================================================
  Hits                      ?    4444
  Misses                    ?   51701
  Partials                  ?     397

Flag
Coverage Δ

#aFlag
7.85% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/loadbalancers.go
1.96% <0%> (ø)

Continue to review full report at Codecov.

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

/lgtm
/approve


rPackages.immunotation: cache external URLs

Description of changes
Immunotation uses 3 external URL-s, and stores them variables in the package's namespace. Package installation is not possible without internet connection, and skipping load test doesn't help, because this happens before the load test.
I use fetchurl to get those external deps, and replace them in the code with a patch + substituteInPlace.
This should work in the long term for the  two MHC allele lists, but I'm not sure about the geographical region list. We'll have to see how frequently the website changes. I only found the copyright2024 notice problematic, because it could change every year, which means we'd have to update the hash. I think that would still be acceptable. If it's more frequent, we'll have to mark this as broken, I think.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build rPackages.immunotation for @jbedo

Ok, this won't work, the hash of hla6006a already changed

Stupid question: could we use an archived page for hla6006a? does the actual data of interest change or is it just the website ?

That could be an option, actually. Normally it is retrieved once, at install time, so it's not that different here. Other possibility could be to retrieve it in .onLoad() but that would require some  more excessive patching.

We could use an archive.org snapshot as a source. There are small changes from time to time, but these probably don't affect the list of valid geographical regions, only some count values, which are not needed by the script at this stage. However, it should be updated once in a while to a new snapshot. I'd prefer to move this whole connection stuff to .onLoad, like in many other packages. I don't see why not. It's just not very straightforward to do in nix.
https://web.archive.org/web/diff/20231207065757/20240205120933/www.allelefrequencies.net/hla6006a.asp


Add benchmarks

This PR adds some benchmarks. Closes #369.

bors try

bors r+

bors r+

bors r+


Fixing infinite loop issue caused by attribute parsing.

Fixing issues where if you had a ) in a comment it would cause an infinite loop mentioned in issue #17
I also added support for properly parsing "alignas" attribute

Thanks!


Make Uint128 inner value private

This will break a lot of code.
In particular, if I want to use Uint128 in a match, I cannot do:
match amount {
  Uint128::zero() => do_something(),
  _ => do_something_else(),
}

As you cannot use functions in the branches of match. Maybe this works with const fn? In any case, if you deprecate Uint128(0), please ensure there is a replacement for the above idiom (which I used twice today)

We have a getter method to get the inner value: a.u128() which can be used everywhere when you need the primary type. Then the code above becomes:
match amount.u128() {
  0 => do_something(),
  1..=234 => do_something_else(),
  _ => do_something_else_else(),
}

Hmmm... I guess this works.


Does it support GPU?

The training procedure is a little bit slow. How to add the support of GPU training?

Yes the code definitely supports GPU and I used one 980ti to trian this model.

I got it. Thanks a lot.


vtpm: add safety comments and fix small issues

This is part of the effort for #228 to enable undocumented_unsafe_blocks clippy lint.

CC @cclaudio

v2:

rebased on main fixing a conflict with #576

CI is failing https://github.com/coconut-svsm/svsm/actions/runs/12428229021/job/34699433885?pr=574#step:7:1353 with:
make[1]: bindgen: No such file or directory

@joergroedel I'm not sure if it's related to this PR.
Any change in the CI container?

It looks like for some reason now the CI container doesn't have bindgen installed, fixed in #583

v3:

rebased on main after merging #583 that fixes the CI issue

v3:
* rebased on main after merging [CI: install bindgen-cli #583](https://github.com/coconut-svsm/svsm/pull/583) that fixes the CI issue

Thanks, waiting a bit more for @cclaudio to approve.

v3:
* rebased on main after merging [CI: install bindgen-cli #583](https://github.com/coconut-svsm/svsm/pull/583) that fixes the CI issue

Thanks, waiting a bit more for @cclaudio to approve.

For some reason my inbox message filters did not pick this one, sorry about that.


Add traefik v2 helm chart

Description
This PR adds the Traefik v2 helm chart to hub.helm.sh
Traefik helm chart repo: https://github.com/containous/traefik-helm-chart
Fixes: https://github.com/containous/traefik-helm-chart/issues/211

The Artifact Hub is another place you can list your repos. To do that, you login (or create an account), create an organization, and list your repository. You can link it to a user or organization.


About min_acceleration when reversing

Is your feature request related to a problem? Please describe.
I am using the diff_drive_controller, and I want the robot to accelerate slowly when speeding up and decelerate quickly to come to a stop. To achieve this, I have set min_acceleration and max_acceleration, and the robot behaves as expected when moving forward. However, when reversing, the acceleration is fast, and the deceleration is slow, so it does not work as expected.
Describe the solution you'd like
Would it be better to reverse the handling of min_acceleration and max_acceleration when reversing?
Describe alternatives you've considered
Additional context
I found the similar issue in ros_controllers(https://github.com/ros-controls/ros_controllers/issues/290)

might be related to https://github.com/ros-controls/control_toolbox/pull/212

Thanks for reporting this, I'll have a look and fix that maybe with (or after) the PR in control_toolbox. We have a newer implementation of the speed limiter in the tricycle_controller package, where there is also a min_deceleration and max_deceleration parameter. Maybe we should consider using that one for all controllers, but it has different parameters and I'm not sure if we should change the well-established ones from diff_drive_controller.

@otamachan could you have a look at #1315 please and see if it solves your problem?

Great!! I'll try. Thank you!


Video Player doesn't work on Android 8.0 device

I built version follow steps, and it works fine in Android 9.0 device in Play Store. but the same built on Android 8.0 device, it doesn't work. Video Player  plays nothing.

Thanks for letting us know about this issue. There is a difference in the Android instant apps runtime between Android 9+ (the runtime is built into the Android framework) and Android 8.0 and earlier (it's provided by "Google Play services for instant apps").
Can you confirm that this is a Unity project? If so, what version? What library are you using to play video - a Unity API, ExoPlayer, or something else?
Also, are there any associated errors in logcat that could tell us more information about what is happening?

Details are as following:

We created Play Instant game with Unity 2019.1.4.
We used Native Video Player Component to play video clip in the game.
With same built version which we submit to Google Store, it works on Android 9.0 device, video could play. But on Android 8.0 device, the video did not play at all, but there is no error has been thrown.
However, If I install the Play Instant as APK on Android 8.0 device, the video played fine.

I suspect this is a Bug for Unity deloying App with Google Instant framework.
Thank you!

Thank you for the additional details! We will try to reproduce the issue internally and get back to you when we know more.

Thank you very much! Look forward for your feedback. :)

Hi @Zeratu,
I just wanted to share an update that we were able to locally reproduce this issue on a Pixel running Android 8.1.
Just to confirm that it's the same issue, if you look at logcat do you see an error like this?
eoplayer I/ServiceManager: Waiting for service drm.drmManager...
2019-09-25 16:02:57.851 477-477/? E/SELinux: avc:  denied  { find } for service=drm.drmManager pid=20190 uid=10572 scontext=u:r:ephemeral_app:s0:c512,c768 tcontext=u:object_r:drmserver_service:s0 tclass=service_manager permissive=0
Thanks again.

Yes, there it is!
09-27 17:45:57.773 31601 31601 D ViewRootImpl@70c5c59[UnityPlayerActivity]: ViewPostIme key 0
09-27 17:45:57.782   720   720 D SEC LightsHAL: button : 1 -
09-27 17:45:57.794   605   605 E audit   : avc:  denied  { find } for service=drm.drmManager pid=31601 uid=10381 scontext=u:r:ephemeral_app:s0:c512,c768 tcontext=u:object_r:drmserver_service:s0 tclass=service_manager
09-27 17:45:57.795 31601 31645 I ServiceManager: Waiting for service drm.drmManager...
09-27 17:45:57.813  1333  2859 D InputReader: Input event(8): value=0 when=228473451019000
09-27 17:45:57.816  1333  2859 D WindowManager: interceptKeyTq s_result=1
09-27 17:45:57.818  1333  2858 I InputDispatcher: Delivering key to (31601): action: 0x1 (0)
09-27 17:45:57.819 14075 14075 D InputMethodService: onKeyUp B key
09-27 17:45:57.819 14075 14075 D InputMethodService: onKeyUp not B key
09-27 17:45:57.819 31601 31601 D ViewRootImpl@70c5c59[UnityPlayerActivity]: ViewPostIme key 1

Hi Zeratu,
Thank you for the detailed information! We were able to track down the issue.
Unity's video player uses MediaExtractor under the hood. Unfortunately, there is a bug in Android Oreo that breaks MediaExtractor in instant apps.
The bug was fixed for Oreo after it was already released: https://android-review.googlesource.com/c/platform/system/sepolicy/+/700511
It's up to the individual OEMs to patch that fix in and push an updated Android version to their devices, so it's possible that the video player works on some devices but not others.
If you're planning on releasing an instant app that uses Unity's video player, please contact us at<EMAIL_ADDRESS>to discuss possible options.

Thanks for your relay! I will discuss with team and see what we can do in next!
Thanks again! :)

@jamcohen , I have wrote a e-mail, and look forward for option discussion.
Thank you!

Thank you! I responded to your email. Closing this issue now.


Project sustainability & governance

Hello! Currently there are two active projects I know of in this space: bump-my-version (the recognized successor to bump2version) and this one. In terms of activity and my subjective perception of sustainability, they seem fairly similar; similar number of contributors and stars on GitHub. I've used both this project and bump-my-version before. I'm making this post on both repositories (link to post on bump-my-version).
There's been a history in this space of projects dying off because the repo administrators became unavailable to continue their role (bumpversion, bump2version). Forks happened and that's great that the work continues, but I'd really like to see a stable long-running project that solves this problem and helps focus our resources.
One of the main reasons I use a version-bumping tool instead of relying on Python packaging tools that can read my Git tags is because I often write software that needs to have a DOI, and the code metadata that's used to generate DOIs needs to be kept in sync with the software version. Other metadata items like release date need to be automatically updated. Have you considered adoption by, for example, Scientific Python or pyOpenSci to provide governance and help focus community resources around the needs this project serves?

I haven't considered any such adoption, no. I maintain the project, continue to accept contributions and give guidance to anybody who wants to contribute. If somebody wants to take on a role as maintainer, to make sure the project remains sustainable, I'll be happy to consider them.
IMHO, these projects aren't too complicated. Some projects warrant continued development, some are basically complete at some point. I'm not sure that very many community resources need to be focused on either of these projects.
Some resources might be warranted to document more use cases, such as yours. If people in the pyOpenSci have such needs, I'll be happy to accept contributions to support their use-cases.

I haven't considered any such adoption, no. I maintain the project, continue to accept contributions and give guidance to anybody who wants to contribute. If somebody wants to take on a role as maintainer, to make sure the project remains sustainable, I'll be happy to consider them.

What I'm concerned about is that you're the single point of failure in this system. If you were to be suddenly unable to continue participating, the ability to add new maintainers is lost, which is what happened to bumpversion and bump2version. In each of those cases, it took a long time (~1 year IIRC) for the community to realize that the maintainer was gone and organize around a fork; lots of progress was delayed. You wouldn't have to sacrifice your ownership or authorship to gain sustainability benefits, plus name recognition and outreach programs can bring in new users and contributors.
I feel researchers are especially sensitive to churn like this, as open source practices can feel like an obstacle to research goals. Communities that support researchers in adopting open science practices need to update their documentation, workshops, etc.

IMHO, these projects aren't too complicated. Some projects warrant continued development, some are basically complete at some point. I'm not sure that very many community resources need to be focused on either of these projects.

I feel that the history of projects in this space is strong evidence of an inability to keep an individually-administrated project in this space alive long enough to reach that completion point, if there is one. I personally would argue that there isn't a completion point; version-management tools need to be just as alive as version bumping conventions, which are continuing to evolve! I believe your project was the first (and only?) in this space to support CalVer (thanks for that, by the way! :wink:).

All in all, I think my point still remains:

If somebody wants to take on a role as maintainer, to make sure the project remains sustainable, I'll be happy to consider them.

I won't be reaching out to actively look for people or organizations that might fill that role. I don't know if other people have the resources for maintenance, nor if they want to dedicate them to this project in particular. If there is such an organization, I'll be happy to work with them.


how can i solve this

i meet this one and i can't solve it

tried many times and i got this one too

can the owner please help up with this...

@MuriloChianfa  i think something is wrong with the images comparing, i started having the same issue too


Feature request: Paste without changing what's in the clipboard

Hello.
I really love the Maccy app and I would like to request a feature.
I'd like to be able to hit the app hotkey and just press on what I want to be pasted without copying it into the clipboard first (and changing the clipboard history order).
Can you please implement such feature?
Anyway, thank you for developing such an amazing app! Wish you well!

There is no such feature, but you can implement this by creating a custom workflow in the Shortcuts.app, it would look something like this:

Now, whenever you open Maccy, select the item you want to paste, and press ⌥⌘P, it will be pasted but your current clipboard item will be preserved in the system clipboard. I didn't test it extensively so probably won't work in all cases, but worth playing around with.
Please re-open if you would like Maccy to provide extra features for Shortcuts.


Isaac Extension: Reload Robot and Place on Plane

-Make robot sit on plane at start
-When I save the file it should have the most up to date urdf and settings automatically

added to scene and made extension load on start and clean up robot on hot reload


simple webpage

made a simple webpage using html and css basics.

Please attach screenshots to it

Hey, can I also contribute to this by adding another sample web page?

@nandinitrivedi05 sure go ahead

I am creating a separate issue for adding a Payment form template @biratdatta


bump golang.or/x/text for CVE-2022-32149

Fixes Or Enhances
Hi there 👋
As per title, would be nice to bump the dependency for fixing that vulnerability.
@go-playground/validator-maintainers

Coverage remained the same at 74.182% when pulling a0cd8605eca6d839608c4514074d9907c5dd1ae0 on ProvoK:patch-1 into c7e0172e0fd176bdc521afb5186818a7db6b77ac on go-playground:master.

Pinging @deankarn to try to get this merged and released ASAP.
FYI: VS Code released a new version today that includes auto govulncheck scanning, so expect a lot more folks pinging you about this (sorry 😞):

@ProvoK this is a dup of #1015

@bnevis-i  I didn't see that, gonna close it in favor of #1015 then, sorry for the noise

@ProvoK No problem.  I'm in the same situation as you, checking to see whether or not the other one got merged yet.  There seems to be something wrong with the github actions in the project that is preventing PR's from going green.


Search Input

As a follow up to https://github.com/microsoft/vscode-webview-ui-toolkit/issues/503, can you please add a search input?

Hi @sketchbuch,
I'm very sorry to say that the toolkit is being deprecated and all active development will be coming to a close.
There was an announcement last week where you can learn more details and leave any questions or comments you may have.
Beyond that, thank you so much filing this issue and apologies for never getting around to addressing it. It means a lot that you contributed to the improvement of this project. I wish you all the best in your future VS Code extension endeavors!


Account lookup example says account not transfer

Pointed out on Slack.

[x] I am very sure this PR could not affect performance.

I've tested that this correctly checks out the current commit by getting it to fail here: https://github.com/tigerbeetledb/tigerbeetle/actions/runs/4286898569/jobs/7467076727 with the bad version of zgo.sh.

@cb22 this should be good to go now.


Error occurred when updating these packages

This issue is used for tracking packages for which the automation workflow failed to update/create a pull request for them at microsoft/winget-pkgs.

Hello there, this comment will be deleted soon by the bot.

Test comment

From now, comments will be on issue 200.


add w&b tracking to book recommender app

we need to add w&b tracking to our book recommender app, we already have an example that adds w&b tracking, we can use that as reference, but feel free to make any changes
I'm not very familiar with w&b LLM tracking platform so there's room for experimentation here to ensure the tracking is useful and attractive to our community.
also, let's make the code optional so they app can still be deployed without tracking, in case users don't need it

closed by https://github.com/ploomber/doc/pull/147


Handle upcoming changes to Tweets

There are some changes happening to Tweets at some point, as outlined in this post.
I can see a couple of things that need doing:

Add the new error code 386 ("The Tweet exceeds the number of allowed attachment types") to TWITTER_HTTP_STATUS_CODE in twython/endpoints.py
Make Twython.html_for_tweet() handle tweets that have no text field but do have a full_text field. Maybe just a quick check as to which field is present, and use that? I'm not sure if the method should do anything more clever.

I've read that post a couple of times now, and I don't think there's anything more Twython needs to do to cope, but I may well be wrong. A second opinion would be good! (fwiw, requesting tweets from the API with the new tweet_mode='extended' works, returning the new format of JSON.)

FYI, submitted PR #429 to add proper support in Twython.html_for_tweet() for extended tweets. Comments are welcomed!


[w2w error] CRS not found / invalid projection

Hi, I'm running into an issue of projection or Coordinate Reference System (CRS) when running w2w to prepare a domain with LCZs for a WRF simulation.
Running this line (adapted to my case):
w2w INPUT_DATA LCZ.tif geo_em.d0X.nc
results in:
←[1m--> Set data, arguments and files ←[0m
Seems you are using a LCZ map produced by https://lcz-generator.rub.de/
I therefor use the Gaussian filtered default 'LczFilter' layer
←[1m--> Check LCZ integrity, in terms of class labels, projection and extent←[0m
LCZ labels as expected (1 to 17)
Traceback (most recent call last):
  File "C:\Users\admin\miniconda3\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\admin\miniconda3\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\admin\miniconda3\Scripts\w2w.exe\__main__.py", line 7, in <module>
  File "C:\Users\admin\miniconda3\lib\site-packages\w2w\w2w.py", line 144, in main
    check_lcz_integrity(
  File "C:\Users\admin\miniconda3\lib\site-packages\w2w\w2w.py", line 350, in check_lcz_integrity
    lcz = lcz.rio.reproject('EPSG:4326')
  File "C:\Users\admin\miniconda3\lib\site-packages\rioxarray\raster_array.py", line 433, in reproject
    raise MissingCRS(
rioxarray.exceptions.MissingCRS: CRS not found. Please set the CRS with 'rio.write_crs()'.

Now, when I use rio.write_crs to set the CRS, the following happens:
xda = xarray.DataArray('C:\\Postdoc\\Taches\\Simulations\\Description_villes\\Strasbourg\\LCZ\\w2w\\input\\lcz_wudapt_ponche.tif')
xda.rio.write_crs(4326, inplace=True)
ERROR 1: PROJ: proj_create_from_database: SQLite error on SELECT name, type, coordinate_system_auth_name, coordinate_system_code, datum_auth_name, datum_code, area_of_use_auth_name, area_of_use_code, text_definition, deprecated FROM geodetic_crs WHERE auth_name = ? AND code = ?: no such column: area_of_use_auth_name
ERROR 1: PROJ: proj_as_wkt: DatumEnsemble can only be exported to WKT2:2018
Traceback (most recent call last):
 File "rasterio\_crs.pyx", line 195, in rasterio._crs._CRS.to_wkt
 File "rasterio\_err.pyx", line 205, in rasterio._err.exc_wrap_ogrerr
rasterio._err.CPLE_BaseError: OGR Error code 6
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
 File "C:\Users\admin\miniconda3\lib\site-packages\rioxarray\rioxarray.py", line 464, in write_crs
   grid_map_attrs = pyproj.CRS.from_user_input(data_obj.rio.crs).to_cf()
 File "C:\Users\admin\miniconda3\lib\site-packages\pyproj\crs\crs.py", line 488, in from_user_input
   return cls(value, **kwargs)
 File "C:\Users\admin\miniconda3\lib\site-packages\pyproj\crs\crs.py", line 310, in __init__
   if projparams:
 File "C:\Users\admin\miniconda3\lib\site-packages\rasterio\crs.py", line 83, in __bool__
   return bool(self.wkt)
 File "C:\Users\admin\miniconda3\lib\site-packages\rasterio\crs.py", line 143, in wkt
   self._wkt = self.to_wkt()
 File "C:\Users\admin\miniconda3\lib\site-packages\rasterio\crs.py", line 131, in to_wkt
   return self._crs.to_wkt(morph_to_esri_dialect=morph_to_esri_dialect)
 File "rasterio\_crs.pyx", line 198, in rasterio._crs._CRS.to_wkt
rasterio.errors.CRSError: Cannot convert to WKT. OGR Error code 6

This is what the CRS looks like in the file:
rds = xarray.open_dataset('C:\\Postdoc\\Taches\\Simulations\\Description_villes\\Strasbourg\\LCZ\\w2w\\input\\lcz_wudapt_ponche.tif')
rds.spatial_ref
<xarray.DataArray 'spatial_ref' ()>
array(0)
Coordinates:
   spatial_ref  int32 0
Attributes:
   GeoTransform:  7.465898326317343 0.0008983152841195215 0.0 48.76863845956...

The LCZ.tif file was prepared with WUDAPT: link to LCZ Generator factsheet.
I'm confused about how to solve this CRS/projection issue. I'm also surprised that this issue has not yet been raised by other people (on the forum).
Any help, please?

Hi @FloBre33,
Could you also share your geo_em file here, so that I can have a closer look?
In addition, can you also share more information about your python environment (version + versions of all packages). This behaviour might be in line with something @dargueso previously reported, for a specific version of rioxarray. Though that was something I could not reproduce myself.

Thank you Matthias for the quick response.
You can find the geo_em files (and namelists) here: https://seafile.unistra.fr/d/885b20e2dab44542be4c/. The goal is to include LCZs in domain 4 for Strasbourg metropolis (France).
My Python version is 3.9.12 and the versions of the modules are:
w2w==0.3.0
  - ecmwflibs [required: Any, installed: 0.4.17]
    - findlibs [required: Any, installed: 0.0.2]
  - numpy [required: >=1.21, installed: 1.22.4]
  - pandas [required: Any, installed: 1.4.2]
    - numpy [required: >=1.18.5, installed: 1.22.4]
    - python-dateutil [required: >=2.8.1, installed: 2.8.2]
      - six [required: >=1.5, installed: 1.16.0]
    - pytz [required: >=2020.1, installed: 2022.1]
  - rasterio [required: >=1.1.6, installed: 1.2.10]
    - affine [required: Any, installed: 2.3.1]
    - attrs [required: Any, installed: 21.4.0]
    - certifi [required: Any, installed: 2<IP_ADDRESS>]
    - click [required: >=4.0, installed: 8.1.3]
      - colorama [required: Any, installed: 0.4.4]
    - click-plugins [required: Any, installed: 1.1.1]
      - click [required: >=4.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.4]
    - cligj [required: >=0.5, installed: 0.7.2]
      - click [required: >=4.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.4]
    - numpy [required: Any, installed: 1.22.4]
    - setuptools [required: Any, installed: 61.2.0]
    - snuggs [required: >=1.4.1, installed: 1.4.7]
      - numpy [required: Any, installed: 1.22.4]
      - pyparsing [required: >=2.1.6, installed: 3.0.9]
  - rioxarray [required: Any, installed: 0.11.1]
    - packaging [required: Any, installed: 21.3]
      - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
    - pyproj [required: >=2.2, installed: 3.3.1]
      - certifi [required: Any, installed: 2<IP_ADDRESS>]
    - rasterio [required: >=1.1.1, installed: 1.2.10]
      - affine [required: Any, installed: 2.3.1]
      - attrs [required: Any, installed: 21.4.0]
      - certifi [required: Any, installed: 2<IP_ADDRESS>]
      - click [required: >=4.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.4]
      - click-plugins [required: Any, installed: 1.1.1]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.4]
      - cligj [required: >=0.5, installed: 0.7.2]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.4]
      - numpy [required: Any, installed: 1.22.4]
      - setuptools [required: Any, installed: 61.2.0]
      - snuggs [required: >=1.4.1, installed: 1.4.7]
        - numpy [required: Any, installed: 1.22.4]
        - pyparsing [required: >=2.1.6, installed: 3.0.9]
    - xarray [required: >=0.17, installed: 2022.3.0]
      - numpy [required: >=1.18, installed: 1.22.4]
      - packaging [required: >=20.0, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - pandas [required: >=1.1, installed: 1.4.2]
        - numpy [required: >=1.18.5, installed: 1.22.4]
        - python-dateutil [required: >=2.8.1, installed: 2.8.2]
          - six [required: >=1.5, installed: 1.16.0]
        - pytz [required: >=2020.1, installed: 2022.1]

Cheers,
FB

Hi @FloBre33,
I also encountered this error. Apparently, it has to do with rioxarray version (0.11), but it is related to other packages or the environment, because @matthiasdemuzere couldn't reproduce it with that rioxarray version. We need to investigate. In the meantime, I solved it by creating a new environment with a lower version number.

We previously had reports where old rasterio versions caused issued e.g. #40. Because of this we set a lower bound requirement for rasterio to >=1.1.6 in our setup.cfg in #50. This version was the first one that worked at the time I tested it. @FloBre33 seems to have the latest version of rasterio installed ([required: >=1.1.6, installed: 1.2.10]) which is the same version our tests run against see here. So this has to be related to the dataset itself being different in some way or as @dargueso mentioned some other side effect caused by other packages which technically should not happen.

I tried to correct the CRS, which seemed to work with rioxarray v0.7.1:
>>> rds = xarray.open_dataset('C:\\Postdoc\\Taches\\Simulations\\Description_villes\\Strasbourg\\LCZ\\w2w\\input\\lcz_wudapt_ponche.tif')
>>> rds.spatial_ref
<xarray.DataArray 'spatial_ref' ()>
array(0)
Coordinates:
    spatial_ref  int32 0
Attributes:
    crs_wkt:                      GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["...
    semi_major_axis:              6378137.0
    semi_minor_axis:              6356752.314245179
    inverse_flattening:<PHONE_NUMBER>63
    reference_ellipsoid_name:     WGS 84
    longitude_of_prime_meridian:  0.0
    prime_meridian_name:          Greenwich
    geographic_crs_name:          WGS 84
    grid_mapping_name:            latitude_longitude
    spatial_ref:                  GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["...
    GeoTransform:                 7.465898326317343 0.0008983152841195215 0.0...
>>> rds.rio.write_crs(4326,inplace=True)
<xarray.Dataset>
Dimensions:      (band: 3, x: 603, y: 435)
Coordinates:
  * band         (band) int32 1 2 3
  * x            (x) float64 7.466 7.467 7.468 7.469 ... 8.004 8.005 8.006 8.007
  * y            (y) float64 48.77 48.77 48.77 48.77 ... 48.38 48.38 48.38 48.38
    spatial_ref  int32 0
Data variables:
    band_data    (band, y, x) float32 ...

However, w2w still doesn't see the CRS:
w2w C:/Postdoc/Taches/Simulations/Description_villes/Strasbourg/LCZ/w2w/input lcz_wudapt_ponche.tif geo_em.d04.nc
←[1m--> Set data, arguments and files ←[0m
> Seems you are using a LCZ map produced by https://lcz-generator.rub.de/
> I therefor use the Gaussian filtered default 'LczFilter' layer
←[1m--> Check LCZ integrity, in terms of class labels, projection and extent←[0m
> LCZ labels as expected (1 to 17)
Traceback (most recent call last):
  File "C:\Users\admin\miniconda3\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\admin\miniconda3\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\admin\miniconda3\Scripts\w2w.exe\__main__.py", line 7, in <module>
  File "C:\Users\admin\miniconda3\lib\site-packages\w2w\w2w.py", line 144, in main
    check_lcz_integrity(
  File "C:\Users\admin\miniconda3\lib\site-packages\w2w\w2w.py", line 350, in check_lcz_integrity
    lcz = lcz.rio.reproject('EPSG:4326')
  File "C:\Users\admin\miniconda3\lib\site-packages\rioxarray\raster_array.py", line 392, in reproject
    raise MissingCRS(
rioxarray.exceptions.MissingCRS: CRS not found. Please set the CRS with 'rio.write_crs()'.

I have two environments. One reproduces the error (proj), the other doesn't (w2w).  I couldn't reproduce the error. So I guess it may be due to incompatibility with older versions of packages.

We are still having trouble reproducing. We tried with all the versions you provided above on both ubuntu and windows.
Could you maybe provide a very detailed step by step guide how you can reproduce this issue? With other stuff mixed into the w2w environment it is very hard to figure out which one causes this. apparently you @FloBre33 are able to reproduce this reliably, so it would be nice if you could start from a clean environment again, setting up w2w and just paste your complete unchanged terminal output in here, including a list of all installed packages (ideally using pip freeze). We hope to figure out what is causing this from that point.

Thank you a lot of the feedback! About the reliability of error reproduction, I just tried with the sample data and got the same issue. So the issue probably has to do with environment/packages rather than input files.
I'll do exactly what you suggested (@theendlessriver13) and post it below. BRB

We are still having trouble reproducing. We tried with all the versions you provided above on both ubuntu and windows.
Could you maybe provide a very detailed step by step guide how you can reproduce this issue? With other stuff mixed into the w2w environment it is very hard to figure out which one causes this. apparently you @FloBre33 are able to reproduce this reliably, so it would be nice if you could start from a clean environment again, setting up w2w and just paste your complete unchanged terminal output in here, including a list of all installed packages (ideally using pip freeze). We hope to figure out what is causing this from that point.

Hi @theendlessriver13, sorry if there was too much information there. I only intended to show that creating new environments  works fine and some of my previous environments didn't reproduce the error either. I did all the tests with the sample data, so the error does come from incompatibilities between packages. I'm unable to provide a detailed step by step because I have built this environment in different stages over the last year or so - if I create a new environment with only the necessary packages and the same versions, I don't get the error.

@dargueso all good! What I suspect is, that we should pin a package with >= which we currently do not do. So if the package is already installed, but not with the latest version, it might not be updated. So I'm trying to narrow it down as good as possible. Pinning everything we have will make w2w likely incompatible in every multi purpose environment so I'd like to avoid that.

Sorry, I'm quite new to Python.
So I created a new virtual environment in Python (v3.8.11), activated it and installed w2w there (with dependencies).
I then ran w2w with the sample data successfully. Same with my own data ! :)
Here are the package versions:
(venv) (base) [fbreton@hpc-login1 WRFInputs]$ pip freeze
affine==2.3.1
appdirs==1.4.4
asciitree==0.3.3
attrs==21.4.0
beautifulsoup4==4.11.1
certifi==2022.6.15
cffi==1.15.0
cfgrib==<IP_ADDRESS>
cftime==1.6.0
charset-normalizer==2.0.12
click==8.1.3
click-plugins==1.1.1
cligj==0.7.2
docopt==0.6.2
eccodes==1.4.2
ecmwflibs==0.4.17
fasteners==0.17.3
findlibs==0.0.2
fsspec==2022.5.0
h5netcdf==1.0.0
h5py==3.7.0
idna==3.3
importlib-metadata==4.11.4
importlib-resources==5.8.0
Jinja2==3.1.2
MarkupSafe==2.1.1
netCDF4==1.5.8
numcodecs==0.9.1
numpy==1.22.4
packaging==21.3
pandas==1.4.2
pooch==1.6.0
pycparser==2.21
Pydap==3.2.2
pyparsing==3.0.9
pyproj==3.3.1
python-dateutil==2.8.2
pytz==2022.1
rasterio==1.2.10
requests==2.28.0
rioxarray==0.11.1
scipy==1.8.1
six==1.16.0
snuggs==1.4.7
soupsieve==2.3.2.post1
urllib3==1.26.9
w2w==0.3.0
WebOb==1.8.7
xarray==2022.3.0
zarr==2.11.3
zipp==3.8.0

Thank you a lot for all the quick and detailed feedback!
Cheers,
Florentin

Glad to see this worked out for you @FloBre33!


Code-Snippet | Docs | Testing and Documentation for Code-Snippet Component

Jira
http://vjira2:8080/browse/BDS-950
Summary
Adding Jest Snapshot tests for the code-snippet component and writing an accompanying TESTING.md file.
Details
I have written tests for the basic usage of the component, usage with attributes added, and for each variation of the component, including display type, color theme, and coding language.
How to test
yarn test:js

@adamszalapski Having some trouble on our end reproducing the issue. Looks like both this branch feature/code-snippets and your PR #1224 are in sync with each other.  Can you confirm that the snapshot is still out of date?

Hey @adamszalapski @mikemai2awesome @joekarasek @TashaBasalt -- what's the status on this + what's the next step to keep this moving along?

@sghoweri, @joekarasek i check this PR a few minutes ago and now is everything ok.


Insurance, Parameterized payment types; test skeletons

Opening this in draft status; the tests are not complete. Though @ArjunBhuptani maybe have a look at the way I've reformatted the test skeletons a bit, and add comments? Could perhaps adapt one of these as a generic "here's how to get started with tests" starter template.

@LayneHaber can this be merged?


[New game]:  Tic Tac Toe

🎮 Game Request
🎮 Game Request: Tic Tac Toe
1: Game Logic Description
Tic Tac Toe is a simple, two-player game that is played on a 3x3 grid. The game logic involves the following steps:
2: Initialization:
The game board is represented as a 3x3 grid.
Two players are identified, Player 1 and Player 2, who will take turns to play.
3: Player Turns:
Players take turns placing their symbol (Player 1 uses "X" and Player 2 uses "O") in an empty cell on the grid.
The game starts with Player 1.
4: Winning Condition:
The game checks for a win after each move. A player wins if they have three of their symbols in a row, column, or diagonal.
5:Draw Condition:
The game ends in a draw if all cells are filled and no player has achieved a winning condition.
6: End of Game:
The game announces the winner or a draw and provides an option to start a new game.
Point down the features
Features of the Game
1: Player Name Input:
Players can input their names before starting the game, which will be displayed during their turn.
2: Turn Indicator:
The game displays a message indicating whose turn it is.
3: Dynamic Game Board:
The game board is dynamically rendered, and players can click on cells to place their symbols.
4: Winning and Draw Notification:
A modal pop-up announces the winner or a draw at the end of the game.
5: New Game Option:
Players can start a new game by clicking a "New Game" button after the current game ends.
6: Responsive Design:
The game is designed to be responsive and can be played on various screen sizes, including mobile devices.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @NAVJOT-786 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @NAVJOT-786!
We are already having a similar game request in #3173 👀
Make sure you come up with a cool unique idea 😀
Waiting for your new game idea 💗.

Hey @NAVJOT-786 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Error : [Errno 111] Connection refused

After trying 3 passwords this pop up (Error : [Errno 111] Connection refused)

Yes, I had this issue too, you have to have tor running. What OS are you running? If it is Linux, then type :
service tor start


Kinematic bodies should wakeup rigidbodies/characters on contact

Operating system or device, Godot version, GPU Model and driver (if graphics related):
c846e49a7d3439d9aef5d499ad403304d89a3b3c
Issue description:
Currently when 3D rigid body is sleeping, and kinematic body collide it, the body will not wake up.
Not sure what was the behavior in 2.x.
Opening this issue as a kindly reminder for @AndreaCatania  :)
It was discussed very slightly in https://github.com/godotengine/godot/issues/13140

Fixed #16757