[Android] Let npm take care of versioning

From build.gradle:
dependencies {
    compile "com.facebook.react:react-native:0.20.+"
}

This means that when adding the react-native-code-push module to an app and building it, Gradle will fetch React Native 0.19 from Maven, even if the app is using say RN 0.34. We stopped releasing the React Native Android artifacts to Maven - they are distributed via npm along with the JS code.  For example I installed RN 0.34 from npm, it will have the 0.34 Android artifacts in node_modules and Gradle will use those to build the app.
Would you consider using compile 'com.facebook.react:react-native:+' instead, as for example react-native-push-notification do react-native-maps do?
If this doesn't make sense for some reason feel free to close this pull request. Just noticed this and thought explicitly depending on a very old RN version looked wrong.

Thanks for merging!

Thanks!


Document basebox build process and upload

Make it easy for others to help out here.

basebox/README.md and ./build.sh updated in new Zonama/ZonamaDev repo to make this clearer and easier.


Update tcl-tk.rb

Fixes #490.

It seems like https one Sourceforge is no longer working and causes issues when trying to install tcl-tk.

The https url is working for me:
🐙  curl -IL https://downloads.sourceforge.net/project/tcl/Tcl/8.6.4/tk8.6.4-src.tar.gz
HTTP/1.1 302 Found
Server: nginx
Date: Tue, 21 Jul 2015 19:43:04 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
content-disposition: attachment; filename="tk8.6.4-src.tar.gz"
Set-Cookie: sf_mirror_attempt="tcl:iweb:Tcl/8.6.4/tk8.6.4-src.tar.gz"; expires=120; Path=/
Location: http://iweb.dl.sourceforge.net/project/tcl/Tcl/8.6.4/tk8.6.4-src.tar.gz

HTTP/1.1 200 OK
Date: Tue, 21 Jul 2015 19:43:04 GMT
Server: Apache
Last-Modified: Thu, 12 Mar 2015 14:14:06 GMT
ETag: "142582e-4119ba-51117ff23a780"
Accept-Ranges: bytes
Content-Length: 4266426
Connection: close
Content-Type: application/x-gzip

While you've got the PR open, though, would you like to fix these audit warnings?
 * A top-level "man" directory was found
Homebrew requires that man pages live under share.
This can often be fixed by passing "--mandir=#{man}" to configure.
 * Non-libraries were installed to "/usr/local/Cellar/tcl-tk/8.6.4/lib"
Installing non-libraries to "lib" is discouraged.
The offending files are:
  /usr/local/Cellar/tcl-tk/8.6.4/lib/Tk.icns
  /usr/local/Cellar/tcl-tk/8.6.4/lib/Tk.tiff

Mmm might be doing this wrong. I've included a photo of what is happening.

Seems to be a local issue for you. I can't reproduce here. It may be that the particular mirror you hit is having issues; Can you try a fresh brew fetch tcl-tk -fs -v?

It seems to be working now. Not sure what was causing it though. Must of been a problem reaching a mirror like you said.

Cool. I suspect either SF or the mirror was having some sort of issue, we seem to hit temporarily "dud" mirrors from time to time. Closing here but feel free to flag it up if it happens again, Thanks!


Real Log levels

Introduce log levels depending on an environment variable

Default log level should be 'development' (equaling 'warnings/info')

Should be able to switch to 'only errors', 'production' (none)

test it in Linux (bash, sh) and Windows

DONE - although default log level is now 'production' - works in Linux & Windows!


Fetching and rendering of AreWeHeadlessYetTopicPage

There is a topics section in the homepage where is listed all the topics relevant to headless builds with Wagtail. We also have a dedicated topic page which provides more details about each topic.
The goal of this PR is to fetch the topic pages from the backend in wagtail.org and render them (Ticket 19 on CodeBase) i.e build the dedicated topic page.
The work done here is based on what have been done in the sections branch hence the target. That also explains why the CI fails; fixing it in that branch will get it resolved here too.

@Tijani-Dia I don’t think this is reviewable at this stage – as I said in #1, please make sure to always describe the changes you’re making in the pull request description. Here I’d expect you to say:

What the PR is trying to achieve overall
Which tickets it’s for
How you’ve tested it
Why it’s pointing at the sections branch (what is it for?) rather than main? What’s the plan to merge what is inside section?
Why the CI builds are failing / should we ignore this or raise it with you / what’s your plan to get them passing.

@thibaudcolas I've added a description to this PR. Let me know if you want more details.
I've tested it locally and in the preview environment.


Any idea what causes this error:

PHP Fatal error:  Uncaught exception 'Swift_TransportException' with
message 'Expected response code 250 but got code "550", with message "550
5.7.1 Command rejected
It's triggered from a cron script.
The site moved to a new server about one month ago but the cron email was all ok up till now.
Other emails got sent correctly from the same cron, directly after this error message, so PHP cannot have suffered a "fatal errror".
Any ideas what this might indicate?
Thanks

Update to latest SM version and provide code piece witch sends email.


Default value in reactive form

How can I put a default value on reactive forms when the form initializes ?

There is an example in wiki pages. Example app example.
Both of those examples use javascript date object to initialize the date. It is also possible to initialize with the IMyDate object.
Example to initialize with IMyDate object.
ngOnInit() {
  // Initialize to yesterday date
  let d: Date = new Date();
  d.setDate(d.getDate() - 1);

  let model: IMyDateModel = {isRange: false, singleDate: {
     date: { year: d.getFullYear(), month: d.getMonth() + 1, day: d.getDate() }
  }};

  this.myForm = this.formBuilder.group({
    myDate: [model, Validators.required]
    // other controls are here...
  });
}


Add a default case for LEM's MatchTag

It should behave similarly to MatchSymbol.
synthesize will need to accommodate the new design. The constraint at play is that either one of the cases path was followed or the default path was followed.
We had this implementation on a very early version of LEM.

I think that for generality, LEM should support both an 'unprovable default' and an actual default case for both/all kinds of match. But if we have to have only one, we should make sure to support an explicit default so we can handle explicit errors of unknown/bad input.

Ah, now I remember our talk. Let me modify the issue title


Better detection of Server app

Existing Server app does not indicate a running server, but launchctl knows.

now it's a good pull request. ;)

PR is fine! Did you test this on  10.6 and up?  I don't have Mac OS X server before 10.9

Currently not. But the old one doesn't support 10.6 too...
On Monday I can test this with a 10.6 Srv VM. :)

Not sure what the requirements should be.. I'm not using it due to not having OSX servers

The path of the Server app is different from the script. The services are also different.


Update terragrunt.hcl

Ran Plan for dir: . workspace: default
Plan Error
running "/usr/local/bin/terraform plan -input=false -refresh -out \"/atlantis-data/repos/italorafaeltavares/Atlantis/37/default/default.tfplan\"" in "/atlantis-data/repos/italorafaeltavares/Atlantis/37/default": exit status 1
╷
│ Error: No configuration files
│
│ Plan requires configuration to be present. Planning without a configuration
│ would mark everything for destruction, which is normally not what is
│ desired. If you would like to destroy everything, run plan with the
│ -destroy option. Otherwise, create a Terraform configuration file (.tf
│ file) and try again.
╵

atlantis plan

atlantis plan

Ran Plan for dir: . workspace: default
Plan Error
running "/usr/local/bin/terraform plan -input=false -refresh -out \"/atlantis-data/repos/italorafaeltavares/Atlantis/37/default/default.tfplan\"" in "/atlantis-data/repos/italorafaeltavares/Atlantis/37/default": exit status 1
╷
│ Error: No configuration files
│
│ Plan requires configuration to be present. Planning without a configuration
│ would mark everything for destruction, which is normally not what is
│ desired. If you would like to destroy everything, run plan with the
│ -destroy option. Otherwise, create a Terraform configuration file (.tf
│ file) and try again.
╵


Upgrade database in DBFlow Android

We released a version of the application in Play Store which implemented DBFlow, now we wants to update the app into next version, in that we should add two new tables to the existing database using DBFlow. Can anyone help me on this?

If it is only new tables you can just increment the version number on the database class annotation.

https://github.com/Raizlabs/DBFlow/blob/master/usage2/Migrations.md

Thank you for the answer. But I have new columns for the existing tables also, how to upgrade for this?

following the usage guide posted above create a migration for version two.
Keep in mind the new tables are created before the migration steps are run

Hi, i have the same question,too. I need update the app into next version,and i modify some data in some tables,what should i do for this update,and let users use new data?Thank you.


JUnit v4.13.1

Upgrade to JUnit v4.13.1

Coverage remained the same at 96.358% when pulling 3289f56f4ebb5a323aa8227b65f37bd97ff702e9 on nhojpatrick:junit-4.13.1 into c9c7295f04a6b632bb212de7f0e73ad0a2e463e2 on apache:master.

You don't need to submit PRs for version changes, Dependabot already does this.


 Master nodes should not handle this traffic.

We'll be going forward with using the presence of the following label as an indicator that the node is a master node.
node-role.kubernetes.io/master

With this, we'll be taking the approach made in https://github.com/coreos/alb-ingress-controller/pull/94 (thanks @owenhaynes) but going forward with slightly different code due to how the ingress library has changed and this difference in the labeling mentioned above.


expecting variable (T_VARIABLE)

We are using an older version of WHMCS for one of our installs, version 7.4.2
We get this error when testing the mollie creditcard gateway.
ParseError: syntax error, unexpected '?', expecting variable (T_VARIABLE) in /modules/gateways/mollie/vendor/guzzlehttp/guzzle/src/Client.php:202

Please read the release docs to check with PHP version is supported. This is as expected.


i18n(es): update i18n & plugins

Description

What does this PR change? Give us a brief description.
Updates i18n & plugins based on this commit 5269aad928773ae08b35ba8e19c0f2832d0d2c89

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

es
guides/i18n.mdx
Localization changed, will be marked as complete.

es
reference/plugins.md
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Thank you for the code review @HiDeoo


Deselect the View Web Version row after tapping

Fixes #210
Deselects the row for "View Web Version" after the select action happens.
Good catch @aerych!

I considered whether it would be nicer to check statsSection != StatsSectionGraph at the beginning of tableView:didSelectRowAtIndexPath: and then only deselect a row in one place, but honestly I really can't see that it gains much.
:shipit: yo :)

Thanks for the review @aerych!


ld: warning: object file (...) was built for newer OSX version (10.12) than being linked (10.10)

On a fresh project with LLVM installed through homebrew and pkg-config file added I get the following warnings when running swift build:
$ swift build
Cloning https://github.com/harlanhaskins/LLVMSwift.git
HEAD is now at 0a03385 Added handy function for creating a global string constant
Resolved version: 0.0.3
Cloning https://github.com/harlanhaskins/cllvm.git
HEAD is now at 092074b Initial commit
Resolved version: 0.0.1
Compile Swift Module 'LLVMSwift' (13 sources)
Compile Swift Module 'MyLanguage' (1 sources)
Linking ./.build/debug/MyLanguage
ld: warning: object file (/usr/local/opt/llvm/lib/libLLVMScalarOpts.a(Scalar.cpp.o)) was built for newer OSX version (10.12) than being linked (10.10)
...
ld: warning: object file (/usr/local/opt/llvm/lib/libLLVMSupport.a(regstrlcpy.c.o)) was built for newer OSX version (10.12) than being linked (10.10)

Is this normal?  Or can I do something to resolve the warnings?

Unfortunately, this is an artifact of statically linking the LLVM binaries. I talked with @aciidbomb3r about what to do for this, and basically we can't do much until LLVM fixes their dylib file and we can use that instead.

If you want an easy way to silence this (assuming you're running on 10.12+) just set your deployment targets to 10.12.

Just to update you on this.  The Swift 5.0 version of package manifests allows us to impose deployment target constraints.  We are beginning to do so in #207, and will continue to update our deployment target to follow the LLVM binaries built through homebrew.

tl;dr No more warnings.

Unfortunately, it seems SPM's deployment target customization only changes the build settings for each target, not for the product. The result is that packages using something like LLVMSwift as a dependency still need to manually change the deployment target for the product in Xcode, even if the deployment target is overridden in the client package manifest.

Unfortunately, it seems SPM's deployment target customization only changes the build settings for each target, not for the product.

That sounds like a bug.  I just tried it with silt, and the generated Xcode project had all the right settings and I was able to build the thing just fine.
If we are used as a dependency in a situation where deployment targets aren't set forward far enough, the result should be a linker error.  I suspect there's some deeper shenanigans going on.  You could try to regenerate your project file with
$ swift package update
$ swift package generate-xcodeproj


Free R&D accounts

Please mention possibility to get free R&D account at this link:
https://earth.esa.int/aos/OSEO
This should be added somewhere here:
In order to run the example you'll need a Sentinel Hub account. You can get a trial version here.

This was added a while ago here.
In the future we might instead of this paragraph just add link to sentinelhub-py documentation chapter with the same content. But for now I am closing the issue.


FR: override setEnabled and disable the ripple on Button

Great library, would appreciate being able to turn it off for disabled buttons.
Thanks!

+1


NodeRopeServer not found on mac

res://addons/ropesim/Rope.gd:125 - Parse Error: Identifier "NativeRopeServer" not declared in the current scope.

Please provide information about your system, how you installed the addon and provide a minimal reproduction project.

Im on Mac Os and and godot 4.2.2 stable-version  I downloaded the extension from the assetLib

There was recently an issue related to Mac version incompatibilities (#3).
Apparently I forgot to create a new release after updating the build.
Since you didn't specify which MacOS version you are using, I can only guess that you might have run into the same issue.
Please try this version from the recent GH Actions build and report back if it works for you.

Im on mac Os sonoma 14.4.1 and it didn't work , thank for your help i hope it will work and that we can find a solution

when im trying to open the project i have this notification Unable to open “libropesim.macos.template_debug” as developer cannot be verified. I think it could be linked ?

Thank you it worked

Great, then I'll create a release and the update will be on the asset store in the next few days. Until then, you can simply use these libs that worked.
Regardless of this issue, here are some friendly tips for the future:

Please put a reasonable amount of effort when posting on Github or when asking for help in general.
People can't read your mind and also can't tell you why something is not working without having various types of information about your system and environment.
Hence, if you want people to help you, provide as much information about your issue as possible. This includes:

Version numbers of all involved software, including the OS.
Full logs as far as applicable, not just single lines.
A description of what you are trying to do
Code to reproduce the issue or a minimal reproduction project (MRP). An MRP is an empty project which contains just enough code to reproduce the issue and nothing more. In this case, for example, it would be a default project with the plugin installed and a single scene that contains one Rope node. You can then upload the project and make the life of people trying to reproduce and debug the issue much easier. An MRP becomes increasingly helpful the more complex the issue gets.

Finally, Github issues are not a chatroom. Please do not spam messages and try to respect basic punctuation and grammar as far as possible. It's perfectly fine if you are not fluent in english, just try your best. That means, try what people suggest, provide information that was asked for (as far as possible) and write up your stuff in a single post when you're done. If you have questions or are unsure about something, just ask. Before submitting, take a moment to proof read your text. You can also edit messages when you notice you have forgot something.


Return policy

@Stanislaw-bnk Thank you for adding this aspect of refund, including unpaid customs duties.

@Stanislaw-bnk please fix pre-commit.

@Stanislaw-bnk please fix pre-commit.

fixed


Add SystemSetup state to allow dump collection

This commit adds SystemSetup state as valid state to allow host dump collection

Can one of the admins verify this patch?

add to approvelist


Authentication issue Ubuntu

I upgraded to
kitchen-docker (2.6.0)
test-kitchen (1.13.0)

When i try to converge I keep getting
 Waiting for SSH service on localhost:32829, retrying in 3 seconds
 Waiting for SSH service on localhost:32829, retrying in 3 seconds
 Waiting for SSH service on localhost:32829, retrying in 3 seconds

With debug
D      [SSH] opening connection to kitchen@localhost<{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>32830, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/Users/ahelal/test_kitchen/.kitchen/docker_id_rsa"], :auth_methods=>["publickey"], :user=>"kitchen"}>
D      [SSH] connection failed (#<Net::SSH::AuthenticationFailed: Authentication failed for user kitchen@localhost>)
       Waiting for SSH service on localhost:32830, retrying in 3 seconds

Digging in deeper loggin into the container  I get this in the sshd log
 User kitchen not allowed because account is locked

Further tests revealed if i generate a password for kitchen user the ssh authentication works.
My current work around is to add the following to driver_config
provision_command     : echo "kitchen:$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)" | chpasswd

Which Ubuntu platform string is this with?

its based on https://github.com/phusion/baseimage-docker

Hmm, can you paste in what you have in your kitchen config?

It's a config issue. thank you for your support

@ahelal I know we're closed out, here— but could you expand on what your config issue was?  I'm struggling with a similar problem here.


Loading issue with "Load scene from URL" plugin

Apparent on this graph:
http://create.vizor.io/fthr/twisty-gradient-robots-3/edit
Load that, press play, and you're supposed to see a bunch of robots. Instead you only see the backround cube. Navigate to "Root" of the graph, and the robots appear.
This graph uses loops, and is quite CPU/GPU heavy. On graphs that are less heavy the problem isn't present, for example: http://create.vizor.io/kschzt/robot-in-a-castle/edit

fixed, it was an async loading issue


Bump smithay-clipboard dependency version

Fixes https://github.com/jwilm/alacritty/issues/2529.

Tested OK!


Fix {use_parent_signal()} and {get_parent_signal()} to work properly

Investigate why those functions are not working and fix it.
You can find they being used in parent.fyre file.
Screenshot of parent.fyre

They are working now.


insufficient memory for the Java Runtime Environment - CPU

Are you sure this is a bug?
Not sure
Describe the bug
CPU version juicer.sh gets java memory options set like so:
Picked up _JAVA_OPTIONS: -Xmx150000m -Xms150000m
Seems to be no way to override this as it is hard coded in the script:
export _JAVA_OPTIONS="-Xmx150000m -Xms150000m"
Running CPU version on the small test data set  MiSeq GM12878.
Centos 7.9, java 1.8 , 32G memory

Hi! Could you let me know if you have any solution?


Right configuration

Who can share with me his configuration file where in standalone usage it will return correct link and thumbnails will show OK.
in my case I have

'user_field'            => 'id',
'shared_folder_name'    => 'shares',
'thumb_folder_name'     => 'thumb',

'images_dir'            => 'public/photos/',
'images_url'            => '/photos',

'files_dir'             => 'public/files/',
'files_url'             => '/files',

I have returned link is http://sandra.dev/photos/shares/Events/58836aa9c5018.jpg
but in filemanager I have

======================
if I add '/shares' thumbnails are OK, but the link to image will be http://sandra.dev/photos//shares/Events/58836aa9c5018.jpg

config/lfm.php has been refactored. Please run php artisan vendor:publish --tag=lfm-config --force. Upgrade guide will be noted in readme, and then stable version of v1.7 will be released.

OK, forgot to mention, I have made some settings in scripts.blade
var image_url     = "{{ Config::get('lfm.images_url') }}";
var file_url      = "{{ Config::get('lfm.files_url') }}";
and because of this I get this double slashes.
CAN WE have configuration in lfm.php that will help us to configure use url or path to files.
SHOW FULL PATH = FALSE

Sorry I forgot to mention that, script.blade.php is also refactored and replaced with with script.js, run php artisan vendor:publish --tag=lfm_public to get that.

Great looking foreword for 1.7 and action there :)

after upgrade double slashes problem still exists for 'allow_multi_user' => false

v1.7.0 has released. Closing issue now.


merge ssb-server/plugins/plugins

lets just have one plugins plugin that supports both types.
this just copies files across from ssb-server/plugins/plugins (including the tests)
next is to support both kinds... then there will be support for out of process plugins in the default ssb-server release. I'm thinking you just have something in the package.json which says it should be run as a out-of-process plugin.

/cc @cryptix

Hmm, I made it check ssb.outOfProcess in the module package.json
not sure if I like that, though.
other ideas: check for module_path/bin & module_path/manifest.json (and treat as process plugin)
Also: I never really liked that sbot wrapped npm. then it became a permanent-temporary solution... I'd like to remove that, you can install plugins manually. Lets just document it clearly.

oh oops, I didn't actually mean to merge this.


Deploy latest STAC Browser to test and prod

UDS Stac Browser bundled with v7.10.1 has been deployed to test and prod and configured with HTTPD proxy.


Shaders auto-completion has been broken

Godot version:
550f436f8
Issue description:

Expected:

Possibly related to @Geequlim's changes?

Broken by this commit https://github.com/godotengine/godot/commit/2293c612e6c0913b6999080c9f2fa77227348818 .

I'll check it.


Add way to copy builds between loadouts

There exists a situation where on support characters you can have multiple loadouts created that have different conditionals based on which team they are supporting, such as anemo/vv users. But their actual artifacts or tc builds do not change - only conditionals.
You can easily duplicate a full loadout + all builds within that loadout and modify that to suit, but if you create new builds / tc builds AFTER you've setup your seperate loadouts, there is currently no easy way to copy build data between loadouts.
It's awkward and slow; but you can at least export multi-targets and import them into other loadouts.

Van already brought up it being good to export/import just the tc builds: #1849

Can be fulfilled by https://github.com/frzyc/genshin-optimizer/issues/2035


feat: add useFocus hook

Description
Adds useFocus hook. The hook returns an element and a boolean control variable.
Also, it's my first contribution here, even after reading the Contributing Guidelines I might have missed something, sorry in advance!
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

Checklist

[x] Read the Contributing Guide
[x] Perform a code self-review
[x] Comment the code, particularly in hard-to-understand areas
[x] Add documentation
[x] Add hook's story at Storybook
[x] Cover changes with tests
[x] Ensure the test suite passes (yarn test)
[x] Provide 100% tests coverage
[x] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
[x] Make sure types are fine (yarn lint:types).

I have recently done something close to you. I did it in a different way, so I wanted to share my approach as I think it's does the same but in a more natural way.
// Merging custom onFocus/onBlur function with useFocus own function.
type UseFocusProps = {
  onFocus?: () => void;
  onBlur?: () => void;
};
type UseFocusHandle= {
  ref: React.Ref;
  onFocus: () => void;
  onBlur: () => void;
};
const [isFocused, focusHandle]: [boolean, UseFocusHandle] = useFocus(props?:UseFocusProps);
return (

    <input {...focusHandle}/>

{isFocused? 'Input is on focus!' : ''}

);


⚠ Samsung has degraded performance

In 924e0b9, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2671 ms

Resolved: Samsung performance has improved in 0b761b0.


79 export select

This pull request has been deployed to Vercel.

✅ Preview:
https://matou-technologies-purrfect-ui-storybook-80.vercel.app

🔍 Inspect:
https://vercel.com/matou-technologies/purrfect-ui/4MfmmsbAWqzUB8wVXF1prAjviPZ7


Update GoogleEarthPro.pkg.recipe

The current recipe is broken and just copies the .dmg as a .pkg which then won't open.  Tweaked the PkgCopier processor to find the pkg inside the dmg and copy that.

@rickokid Thanks for the catch and the fix! :-)


brew rm <URL> downcases the URL when fetching it

(note: I’m using Linuxbrew here but others have been able to reproduce the issue on macOS)
Steps to reproduce:
$ brew rm -v https://raw.githubusercontent.com/teoljungberg/homebrew-core/4f08fc94bd35aecebe16e6c1b59c423a772df4e6/Formula/pick.rb
/usr/bin/curl --fail --remote-time --location --user-agent Linuxbrew/1.0.6-2-gcdb9b18 (Linux; x86_64 Ubuntu 14.04.5 LTS) curl/7.35.0 https://raw.githubusercontent.com/teoljungberg/homebrew-core/4f08fc94bd35aecebe16e6c1b59c423a772df4e6/formula/pick.rb -o /home/baptiste/.cache/Homebrew/Formula/pick.rb
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
Error: Failure while executing: /usr/bin/curl --fail --remote-time --location --user-agent Linuxbrew/1.0.6-2-gcdb9b18\ (Linux;\ x86_64\ Ubuntu\ 14.04.5\ LTS)\ curl/7.35.0 https://raw.githubusercontent.com/teoljungberg/homebrew-core/4f08fc94bd35aecebe16e6c1b59c423a772df4e6/formula/pick.rb -o /home/baptiste/.cache/Homebrew/Formula/pick.rb

It may fail later in the process if you don’t have pick installed but it shouldn’t fail when fetching the formula. It’s because it tries to fetch a downcased URL: see the …/Formula/… that becomes …/formula/… in the curl command.

brew rm calls ARGV.kegs, which itself calls downcased_unique_named (see here). The downcased URL is then passed to Formulary.to_keg which passes it to Formulary.factory (here), which retrieves the formula using FromUrlLoader.
The problem is thus that we want to preserve the argument’s casing when it’s an URL. I don’t have a fix ready for that; hence an issue instead of a PR.

Honestly I'd probably rather we scoped back the places we accept URLs. They don't work well and there's rarely a good argument for one over a tap or brew pull.

Gonna close this out just because it's not something users are hitting. Will accept a fix, though.


Numpy 2.0

There are changes that are needed to support numpy 2.0.

What things I have noticed np.float_ has been deprecated.

I believe this has been fixed in Gigaanalysis 0.5.0


Chip click event should bubble

Expected Behavior
Allow event to bubble up
In your chip component https://github.com/angular/components/blob/master/src/material/chips/chip.ts#L387
  _handleClick(event: Event) {
    if (this.disabled) {
      event.preventDefault();
    } else {
      event.stopPropagation();
    }
  }

If this component is wrapped by another component, the event will not be caught. It's even more confusing that it does bubble when it is disabled.
It doesn't make sense to write extra code to catch the event and emit it in the wrapper. The native element should bubble. Please see Polymer components for reference.
Also, please keep in mind that webcomponent specs/best practices are downward data through data bindings and upward data through events. If your using the mediator pattern then it's a must that the events bubble.

Duplicate of #19759


Fix storybook preview

-Add missing React import.
-Import Notifications instead of the old NotificationsProvider.

Thanks!


ar.js

I couldnt get the ar.js to work on iOS11, and I saw that yours work.
I am not sure if the ar.js you use is any different from the official AR.js so I use your ar.js file, and i still received the same error in iOS 11  with "WebCam Error: NotAllowedError".
My code is very simple and only works on PC with webcam:
<!doctype HTML>
<html>
<script src="https://aframe.io/releases/0.7.0/aframe.min.js"></script>

<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>

<script src="https://prashant-andani.github.io/AR.js/aframe/build/aframe-ar.js"></script>

<body style='margin : 0px; overflow: hidden;'>
    <a-scene stats embedded arjs artoolkit='sourceType: webcam;'>

        <a-assets>
            <a-asset-item id="model" src="models/mymodel.gltf" />
        </a-assets>
        <a-gltf-model src="#model" scale="0.01 0.01 0.01"></a-gltf-model>
        <!--<a-box material='color: black;'></a-box>-->
        <a-marker-camera preset='custom' type='pattern' patterUrl='ar.patt' url='ar.patt'>

        </a-marker-camera>
    </a-scene>
</body>

</html>

any reason why I cant get it working?

Hey @ultradyran it works fine for me...
Can you share your link where you hosted this code ?


Add notification UI when something succeeds

Currently the user has no feedback (other than some prints) when the action they performed succeeds.
It would be helpful to display a notification when an action is successfully completed, such as registering or updating a prefab.
Will this finally be the introduction of Roact?

This exists with toasts now


A new helper "applyConfig" that ensures that all addon config methods return config

When writing volto-slate, which has an extensible architecture based on plugins and configuration insertion modeled after Volto's, I've noticed that it's very easy to do mistakes and create configuration methods that don't return the config object. So I've tweaked the addon loader code to use this safeWrapper and I've also added a helper called applyConfig that loads configuration methods.
See the modifications in addons.md file in this PR for more details.

This is ready to be merged


sound volume not doing anything?

ev3dev version: 4.4.19-15-ev3dev-ev3
ev3dev-lang-python version: 0.8.0

from ev3dev import ev3
for v in range(0,100,10):
  ev3.Sound.volume = v
  ev3.Sound.tone(400, 50)

https://github.com/ev3dev/ev3dev/wiki/Using-Sound#sysfs-attributes-and-module-parameters
This probably came from the transition to use the beep command, which does not have a volume parameter.
Should we shell out the same way and call, e.g.
amixer -q set Playback 50%

Currently Sound is just a convenience class that wraps espeak, aplay and beep utilities. It does not inherit from Device, so Sound.volume = v does nothing except for creating a class level field named volume.
Did you try writing to /sys/devices/platform/snd-legoev3/volume directly? Does that work? In case it does, we could easily introduce the volume attribute to the Sound class.

FYI, I don't intend to keep /sys/devices/platform/snd-legoev3/volume around forever, so I would not suggest becoming reliant on it. Better to use the ALSA mixer instead.

yep, this works too:
 echo "10" | sudo tee /sys/devices/platform/snd-legoev3/volume

I thought using amixer would be more portable to e.g. brickpi. But on the other hand writing to the sysfs is probably faster than spawning a binary.
I am bringing this up, because this worked in the past before we switched to the beep command.

There is also python-pyalsa and python-alsaaudio but these don't have python3 packages.

See #259


FRAME: General storage-usage system

Fixes #13529

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2563396

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2563395

Maybe worth to use it in one pallet to see that the abstractions all work?

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2567122

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2567125

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2567121


Migrate Pack2 Features

A number of great features have been added to Pack2 since POP was forked. These include the work on unit testing and mocking the hub.

Dave got this


Nrf5340 cpu app fix ram partitioning

Reason for this patch:
For nrf5340 builds without support for Trusted Execution (ARM TrustZone) we would like to use all available SRAM for the single (default secure) image. Right now the SRAM for the secure image is limited to the lowest 64 kB, regardless of whether we build with TrustZone support.
In addition to the above: the shared SRAM with the Network MCU has been moved to the upper part of the Application MCU SRAM. So for builds without TrustZone, the whole SRAM below the shared partition can be given to the single image.

CC @koffes

Have tested this briefly and it looks good. 64 kB RAM with CONFIG_TRUSTED_EXECUTION_SECURE=y and 448 otherwise.


if an event is an error, pass the exception object

Upstream PR https://github.com/JustinTulloss/zeromq.node/pull/578 has not been responded to at this time.  I propose to merge this to our fork for now.

Still a little bothered by having a separate upstream PR, esp since we don't know the state of it.
I believe the last changes to storage to produce better error messages for already bound zmq ports will be a good enough test to make sure nothings broken between node/npm-zmq and nsolid - make sure you run the storage integration tests w/nsolid to make sure nothings b0rken ...
Other than that, LGTM, but not really familiar with the NAN usage in the natives ...

The NAN usage was copied from neighboring code, so it should be ok
I'll ping upstream one more time...

In general LGTM

Upstream accepted a modified version of this but it's not merged yet.  Keeping this open for a few more days to see how that shakes out and when it lands

Upstream fix merged and landed, closing this


Running the Periodic Hill case

Hello @ashwinvis
I have tried to run the Periodic Hill case. I followed the guidance on this page. The !ls {sim.path_run} command, gives the following:
build.log  info_solver.xml  makefile nek5000  params_simul.xml  phill.box  phill.log  phill.par  phill.usr SIZE templates etc	logs		    makefile_usr.inc  obj params.xml  phill.f    phill.ma2  phill.re2  SESSION.NAMESnakefile  toolbox
Which means it does not give me the result of simulation (rs6phill0.f00001 ...). I tried sim.make.exec('test') ..., it gives
 Changing to shadow directory: ../Sim_data/phill_run_2021-01-25_12-12-27
Building DAG of jobs...
MissingRuleException:
No rule to produce e (if you use input functions make sure that they don't raise unexpected exceptions).
Out[9]: False
I do not know if it is related. I wonder if you could help me with this issue.

Hi @akhoubani, the sim.make.exec(rules=...) method would only respond to the rules specified in the Snakefile. You can see that test is not a rule.  If you executed sim.make.list() you would see all the available rules. Hope that helps.

Hi @akhoubani, the sim.make.exec(rules=...) method would only respond to the rules specified in the Snakefile. You can see that test is not a rule.  If you executed sim.make.list() you would see all the available rules. Hope that helps.

Also @akhoubani, it is important to have Nek5000 in your machine and the following environment variables set before executing snek5000
export NEK_SOURCE_ROOT="/path/to/Nek5000"
export PATH="$PATH:$NEK_SOURCE_ROOT/bin"

Also @akhoubani, it is important to have Nek5000 in your machine and the following environment variables set before executing snek5000
export NEK_SOURCE_ROOT="/path/to/Nek5000"
export PATH="$PATH:$NEK_SOURCE_ROOT/bin"

Since the mesh was generated and nek5000 executable was produced, I see you have the necessary dependencies. Maybe attach phill.log here so that we can look at any runtime error messages. You could also try `sim.make.exec(['srun'])' instead.

Since the mesh was generated and nek5000 executable was produced, I see you have the necessary dependencies. Maybe attach phill.log here so that we can look at any runtime error messages. You could also try `sim.make.exec(['srun'])' instead.

Thank you very much @ashwinvis for your fast reply. Included you will find the phill.log of sim.make.exec(['srun']).
phill.log
Also the .log that is saved in nek5000 directory.
2021-01-25T133739.773720.snakemake.log
Thank you for your time.

Thank you very much @ashwinvis for your fast reply. Included you will find the phill.log of sim.make.exec(['srun']).
phill.log
Also the .log that is saved in nek5000 directory.
2021-01-25T133739.773720.snakemake.log
Thank you for your time.

Here is the error:
  Error: Nek has has been compiled for
         number of elements/proc  (lelt):         128
         total number of elements (lelg):        1024

  This run requires:
     lelt >=          960  for np =            1
     lelg >=          960

an error occured: dying ...

The number of processors are detected using a standard Python here. Not sure why that did not work. Can you open a Python console and try the following:
In [1]: import os

In [2]: os.cpu_count()
Out[2]: 4

In [3]: import multiprocessing

In [4]: multiprocessing.cpu_count()
Out[4]: 4

In [5]: import psutil

In [6]: psutil.cpu_count()
Out[6]: 4

Here is the error:
  Error: Nek has has been compiled for
         number of elements/proc  (lelt):         128
         total number of elements (lelg):        1024

  This run requires:
     lelt >=          960  for np =            1
     lelg >=          960

an error occured: dying ...

The number of processors are detected using a standard Python here. Not sure why that did not work. Can you open a Python console and try the following:
In [1]: import os

In [2]: os.cpu_count()
Out[2]: 4

In [3]: import multiprocessing

In [4]: multiprocessing.cpu_count()
Out[4]: 4

In [5]: import psutil

In [6]: psutil.cpu_count()
Out[6]: 4

Here it is:
In [1]: import os

In [2]: os.cpu_count()
Out[2]: 8

In [3]: import multiprocessing

In [4]: multiprocessing.cpu_count()
Out[4]: 8

In [5]: import psutil

In [6]: psutil.cpu_count()
Out[6]: 8

Here it is:
In [1]: import os

In [2]: os.cpu_count()
Out[2]: 8

In [3]: import multiprocessing

In [4]: multiprocessing.cpu_count()
Out[4]: 8

In [5]: import psutil

In [6]: psutil.cpu_count()
Out[6]: 8

Dear @ashwinvis,
I upgraded to Ubuntu 20.04 and now it works. Thank you for your time.

Dear @ashwinvis,
I upgraded to Ubuntu 20.04 and now it works. Thank you for your time.

Thank you for trying snek5000 out, and do not hesistate if you have any questions / requests.

Thank you for trying snek5000 out, and do not hesistate if you have any questions / requests.


Add support for accepting values defined as runtime parameters

I have a parameter and a task that uses it:
parameters:
  - name: aws_region
    displayName: AWS region
    default: eu-central-1
...
          - task: AWSShellScript@1
            displayName: Get AWS short-term credentials
            inputs:
              inlineScript: |
                echo "Hello"
              regionName: ${{ parameters.aws_region }}
              failOnStandardError: true
              awsCredentials: $(aws_service_connection)
              scriptType: inline

The extension reports the following problem for regionName:
Value is not accepted. Valid values: "af-south-1", "ap-east-1", "ap-northeast-1", "ap-northeast-2", "ap-northeast-3", "ap-south-1", "ap-south-2", "ap-southeast-1", "ap-southeast-2", "ap-southeast-3", "ap-southeast-4", "ap-southeast-5", "ca-central-1", "ca-west-1", "eu-central-1", "eu-central-2", "eu-north-1", "eu-south-1", "eu-south-2", "eu-west-1", "eu-west-2", "eu-west-3", "il-central-1", "me-central-1", "me-south-1", "sa-east-1", "us-east-1", "us-east-2", "us-west-1", "us-west-2", "cn-north-1", "cn-northwest-1", "us-gov-east-1", "us-gov-west-1".
Can the extension use the default value of the parameter to validate the property?

Going to track this under #420


Unable to build on Windows 10

I get the following when attempting to run build simpleDemo:
....\flutter\flutter.go:177: cannot use C.uintptr_t(len(strMessage)) (type C.uintptr_t) as type C.size_t in field value

I've managed to get it working by changing it to the expected C.size_t, however, unsure if this is the proper fix.

@Syleron thanks for the issue :smile:
This is the proper fix! ref: embedder.h
Do you think you could submit a quick PR for this?

Awesome :) Yes, It's awaiting your confirmation.


No ability to have a non-sandboxed preload with web renderer target

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
7.1.0
Electron version
25.8.4
Operating system
macOS Sonoma 14.1.1
Last known working Electron Forge version
6.3.0
Expected behavior
The Electron team recommends to sandbox renderer processes as much as possible, which is a good attitude. However, the current configuration of Electron forge prevents the proper usage of the contextBridge to safely expose modules without disabling the sandbox for the entire renderer process.
The expected behavior is that I can create my BrowserWindows with the following settings:

nodeIntegration: false (or omitted, since that's default behavior)
contextIsolation: true (or omitted, since that's default behavior)
sandbox: false

… and be able to use my main renderer code with the target web (i.e., set nodeIntegration: false) while still allowing my preload script to be not sandboxed.
Doing so will allow me to do this:
contextBridge.exposeInMainWorld('path', path)

The path module is safe to use in renderers and my use-case requires me to have the exact same path module in both my main process and my renderers. I would like to do so while still enabling context isolation.
Actual behavior
Disabling nodeIntegration in the forge configuration for my renderers will automatically sandbox my preload scripts, preventing me from exposing specifically the path module (contextBridge.exposeInMainWorld('path', path)) to my renderers.
There is currently no configuration that would allow this without both enabling nodeIntegration and disabling the sandboxing, which is discouraged.
Steps to reproduce
Set up browser windows with the above mentioned settings: Node integration off, context isolation on, sandbox off. Then, keep the nodeIntegration setting at default (false) in the forge config.
Observe that the line contextBridge.exposeInMainWorld('path', path) will only expose an empty object ({}) to the renderer context, instead of transferring the functions of the path module.
Additional information
Proposed Fix
I managed to pinpoint the exact cause of this and believe to have a simple fix. Specifically, this issue was introduced in the following commit and file: https://github.com/electron/forge/blob/3e6fe255395f96e0a28bd1a487ae33eea86465a7/packages/plugin/webpack/src/WebpackConfig.ts
Specifically, observe these lines:
https://github.com/electron/forge/blob/3e6fe255395f96e0a28bd1a487ae33eea86465a7/packages/plugin/webpack/src/WebpackConfig.ts#L200-L201
As you can see, the nodeIntegration option of Forge's configuration controls both the target for the actual renderer process and its preload script.
There is no way to achieve a renderer target web with a simultaneous preload target electron-preload.
Indeed, I could confirm that, by turning these lines:
function rendererTargetToWebpackTarget(target: RendererTarget): WebpackTarget {
  switch (target) {
    case RendererTarget.Web:
    case RendererTarget.SandboxedPreload: // <-- This line will move ...
      return WebpackTarget.Web;
    case RendererTarget.ElectronPreload:
      return WebpackTarget.ElectronPreload;
    case RendererTarget.ElectronRenderer:
      return WebpackTarget.ElectronRenderer;
  }
}

Into these:
function rendererTargetToWebpackTarget(target: RendererTarget): WebpackTarget {
  switch (target) {
    case RendererTarget.Web:
      return WebpackTarget.Web;
    case RendererTarget.SandboxedPreload: // <-- ... here
    case RendererTarget.ElectronPreload:
      return WebpackTarget.ElectronPreload;
    case RendererTarget.ElectronRenderer:
      return WebpackTarget.ElectronRenderer;
  }
}

I was able to successfully run my application as it had been before.
Therefore, my proposal would be to add another configuration option that allows me to control the preload's target independent of the renderer's target, such as sandboxPreload: true|false.
Would this be possible?

Quick update; after a few days of digging around, I have found that we can provide a custom webpack config just for the preloads. Trying to set electron-preload as the target there, however, blows up the webpack hot module replacement server and floods my terminal with error messages.
Interestingly, the target appears to be overridden by Electron Forge (i.e., my custom config has zero bearing on the actual config being used) – I tried various targets, but to no avail.
So I am still stuck to 6.3.0 with no way to make Electron Forge do what I need it to. I tried already plugging in the necessary change myself, but that made a few unit tests fail, so there is no news on this side as well. I still don't understand why moving the RendererTarget.SandboxedPreload switch case one line down fixes the issue completely, but that I have so many difficulties simply adding a new config option …
I would greatly appreciate if someone with more experience of the code base could chime in, I feel a bit lost here.

Can i work on this issue ?

There may be a potential "fix" here to support your usecase in that the forge entry config should probably have separate nodeIntegration preferences for the top level entry and the nested prelaod entry so that here we can assign the preload a different target setting.

That was basically my plan, yes. I am also currently looking into getting rid of any Node modules across all renderers to follow the recommended security practices more closely, but I must say this breaking change was very confusing for me because somehow Forge simply stopped working properly with no indication as to why …


Suggestions?

I loved the name overreact (overlay + react) ;)
Or reactbox.

I like over-react.

Almost anything is better than react-modal2 though. ;)

Now that react-modal2 works universally, it could be renamed react-universal-modal.


/typescript command

Complete the following REQUIRED checkboxes:

[x] I have thoroughly read and understand The Odin Project Contributing Guide

[x] The title of this issue follows the command name: brief description of request format, e.g. /help: add optional @user parameter

The following checkbox is OPTIONAL:

[x] I would like to be assigned this issue to work on it

1. Description of the Feature Request:

There are a lot of questions about typescript, so I think there should be a command that will use Mao's reponse on if typescript will be covered in the course.
2. Acceptance Criteria:

[ ] /typescript command is added to the bot

3. Additional Information:

Valuable input added by carlos

@TheOdinProject/odin-bot Can someone review please

+1 for Carlos's comment. I also would want a more generalized command and not a Typescript-specific command.  There are a lot of adjacent tech that people either think they 'need to learn'/'want to learn' while doing TOP.


Calling this[fn].bind requires extra check

It is not valid to assume that Sortable's prototype contains what you expect it to.
In my environment, Sortable is loaded by requirejs, and the prototype is modified in requirejs's loader callback by injecting a special __moduleId__ property into the prototype, in a fashion like this:
        requirejs.onResourceLoad = function(context, map, depArray) {
            context.defined[map.id].prototype.__moduleId__ = map.id;
        };

At Sortable.js#L232 this effectively leads to trying to call .bind on a String object, resulting in this[fn].bind is not a function error.
There should be a smarter way to copy functions from the prototype, so far I can suggest an extra check for object type before calling .bind:
if (fn.charAt(0) === '_' && typeof(this[fn].bind) === 'function') {
	this[fn] = this[fn].bind(this);
}

I cannot accept it. If everyone will add similar things for yourself, the library will be similar to mess.

Or not...

Note it was not my idea to modify the prototype this way, it's a popular framework that does this as part of its module management engine.
requirejs.onResourceLoad exists there for a reason - module tracking, measuring timing of module loading etc. You can't predict what would happen to your class so it's better to be secured against such modifications.

Hmm ... well, okay, check on typeof this [fn] === 'function' will be sufficient, correct this PR  and I accept.

PR updated.

Brackets removed.

:v:


Update remark@9

This PR fixed #513 but it has breaking changes about markdown parsing.

entities-advanced.text match AST
frontmatter-empty.text match AST
frontmatter-extra-dashes.text match AST
frontmatter-initial-lines.text match AST
frontmatter-normal.text match AST
frontmatter-only.text match AST
links-inline-style.text match AST
links-title-empty-parentheses.text match AST
links-title-parentheses.text match AST
links-url-new-line.text match AST
links-url-white-space.text match AST
title-attributes.text match AST

You can update test fixtures by running node tools/update-fixtures.js

tools/update-fixtures.js

@azu Thank you for information.
I just thinking about that.

Thanks for update.
it looks like that remark<EMAIL_ADDRESS>is almost bug fix.
I think that most existing rules does not affected by this changes, but should we publish it as major release?
If we does major update, I want to consider about label:"Type: Breaking Change" like #443 #489

I think that most existing rules does not affected by this changes

Well, I think this PR released as not major release.

@Leko OK. I'll release new version #516


Help on similar project

Im trying to get my app ported to Discord. My frontend is showing up but i cant get my backend to bypass the CSP. My system is running on docker containers like yours. Do you think nginx is causing these problems? Ive spent all weekend trying to get this to work so any help would be greatly appreciated. H
Heres my stack: Django, Create React APP, Ngnix, Docker
Docker compose file:
version: '3.8'

services:
  db:
    container_name: database
    image: postgis/postgis:12-3.3
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U myuser -d mydb"]
      interval: 10s
      timeout: 10s
      retries: 5
    volumes:
      - ./postgres-data:/var/lib/postgresql/data
      #- postgres_data:/var/lib/postgresql/data
    environment:
      - POSTGRES_USER=myuser
      - POSTGRES_PASSWORD=mypassword
      - POSTGRES_DB=mydb
    networks:
      - mynetwork
  backend:
    container_name: backend
    image: backend-image
    build:
      context: ./backend
      dockerfile: DockerFile.dev.backend
    ports:
      - "8000:8000"
    depends_on:
      db:
        condition: service_healthy
    environment:
      - DEBUG=True # Change in production
      - DB_HOST=db
      - DB_PORT=5432
      # Add other environment variables needed for your Django app
    volumes:
      - ./backend:/app
    networks:
      - mynetwork

  frontend:
    container_name: frontend
    image: frontend-image
    build:
      context: ./frontend
      dockerfile: DockerFile.frontend
    ports:
      - "3000:3000"
    depends_on:
      - backend
    volumes:
      - ./frontend:/app
      - /app/node_modules
    networks:
      - mynetwork

  nginx:
    container_name: reverse-proxy-nginx
    image: nginx-image
    build:
      context: ./Nginx/
      dockerfile: DockerFile.dev.nginx
    ports:
      - "80:80"
    depends_on:
      - frontend
    networks:
      - mynetwork

volumes:
  postgres_data:

networks:
  mynetwork:
    driver: bridge`

NGINX
http {
    upstream frontend {
        server frontend:3000;
    }

    upstream backend {
        server backend:8000;
    }

    server {
        listen 80;

        location / {
            # Assuming the frontend handles routing and all URIs should be sent to the frontend
            proxy_pass http://frontend;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        }

        location /api/ {
            # Assuming all backend requests start with /api/
            proxy_pass http://backend;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        }
    }
}

events {
    worker_connections 1024;
}

index.js
import React, { useState, useEffect } from 'react';
import ReactDOM from 'react-dom/client';
import { BrowserRouter as Router } from 'react-router-dom';
import { DiscordSDK, patchUrlMappings } from "@discord/embedded-app-sdk";
import './index.css';
import * as serviceWorker from './serviceWorker';
import 'bootstrap/dist/css/bootstrap.min.css';
import { AuthProvider } from './AuthContext';
import { GoogleOAuthProvider } from '@react-oauth/google';
import App from './app';
import { getApiUrl } from './config/config';

const isProd = process.env.NODE_ENV === 'production';

const DiscordApp = () => {
  const [isSDKReady, setIsSDKReady] = useState(false);
  const [auth, setAuth] = useState(null);
  const [isDiscordEnvironment, setIsDiscordEnvironment] = useState(false);

  useEffect(() => {
    const setupEnvironment = async () => {
      const urlParams = new URLSearchParams(window.location.search);
      const frameId = urlParams.get('frame_id');
      setIsDiscordEnvironment(!!frameId);

      if (isProd && isDiscordEnvironment) {
        await patchUrlMappings([
          { prefix: '/api', target: 'tunnel.clearedgear.com/api' }
        ]);
      }

      if (frameId) {
        const discordSdk = new DiscordSDK(process.env.REACT_APP_DISCORD_CLIENT_ID);

        try {
          await discordSdk.ready();
          console.log("Discord SDK is ready");

          const { code } = await discordSdk.commands.authorize({
            client_id: process.env.REACT_APP_DISCORD_CLIENT_ID,
            response_type: "code",
            state: "",
            prompt: "none",
            scope: ["identify", "guilds"],
          });

          const tokenExchangeUrl = getApiUrl('/discord/token');

          const response = await fetch(tokenExchangeUrl, {
            method: "POST",
            headers: {
              "Content-Type": "application/json",
            },
            body: JSON.stringify({ code }),
          });

          if (!response.ok) {
            throw new Error(`HTTP error! status: ${response.status}`);
          }

          const { access_token } = await response.json();

          const authResult = await discordSdk.commands.authenticate({ access_token });

          if (authResult == null) {
            throw new Error("Authenticate command failed");
          }

          setAuth(authResult);
          console.log("Discord SDK is authenticated");
        } catch (error) {
          console.error("Error setting up Discord SDK:", error);
        }
      }

      setIsSDKReady(true);
    };

    setupEnvironment();
  }, []);

  if (!isSDKReady) {
    return
Loading...
;
  }

  return (
    <Router>
      <React.StrictMode>
        <GoogleOAuthProvider clientId={process.env.REACT_APP_GOOGLE_CLIENT_ID}>
          <AuthProvider>
            <App discordAuth={auth} isDiscordEnvironment={isDiscordEnvironment} />
          </AuthProvider>
        </GoogleOAuthProvider>
      </React.StrictMode>
    </Router>
  );
};

const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(<DiscordApp />);

serviceWorker.unregister();

Hi @erikthe-viking, your issue may have several origins, which is complicated to spot on.
What happen when you try to reach http://localhost:80/ and http://localhost:80/api does the request reach the frontend and the backend ?
With react I'm using vite that is proxying correctly API requests to my backend server running on a different port (you will probably need a configuration like this somewhere), see:
https://github.com/PaulMarisOUMary/Discord-Activity/blob/22818a2009d57753663ae41b77bc0ddc14038507/client/vite.config.ts#L14-L20
About NGINX, be careful about which port you use, you can find my configuration here:
https://github.com/PaulMarisOUMary/Discord-Activity/blob/22818a2009d57753663ae41b77bc0ddc14038507/client/nginx/nginx.conf#L1-L23
Depending on your requirements, you could also consider merging your nginx and client(frontend) in the same container, see:
https://github.com/PaulMarisOUMary/Discord-Activity/blob/22818a2009d57753663ae41b77bc0ddc14038507/Dockerfile.client#L1-L43

http://localhost:80/ and http://localhost:80/api route to the frontend and the backend!


Multi Table Example?

Could someone post a working multiple table example zip file?

You can grab it from the yadcf-showcase repo' , here is the relevant html , here its in action in the showcase


Outdated analyzer dependency on ferry_generator

Analyzer dependency on the generator is outdated:
https://github.com/gql-dart/ferry/blob/master/packages/ferry_generator/pubspec.yaml#L18
Starting to get conflicts with other packages.
Is there a reason it hasnt been updated in a while?

Theres a dependency on gql_code_builder.

How are others working around this issue? I'm reluctant to do a dependency_override in case that breaks it just wondering if anyone else has found a workaround for this

Did you end up doing it? If so, did you face any issues?

How are others working around this issue? I'm reluctant to do a dependency_override in case that breaks it just wondering if anyone else has found a workaround for this

Did you end up doing it? If so, did you face any issues?

Yea I ended up adding the following to my pubspec and everything has been working from what I can tell
dependency_overrides:
  ### Required due to https://github.com/gql-dart/ferry/issues/291
  analyzer: ^2.7.0

I'm curious if this repo is going will continue actively maintained going forward? Reason I ask is that the repo was receiving nearly daily commits up until September 9th then nothing since. Is there a dev branch or new project I'm not aware of?
Hope that my question doesn't come across the wrong way I'm genuinely curious what the future of the repository is going to be. I really appreciate all of the hard work everyone has put into this repo

duplicate of https://github.com/gql-dart/ferry/issues/282

I'm curious if this repo is going will continue to be actively maintained going forward?
I plan to continue to maintain ferry on a best-effort basis.


Polyglot Notebook: [DevExE2E] If Markdown in Edit status -> collapse the markdown, the tip "1 cell hidden" doesn't show.

Describe the bug
Using extension Polyglot Notebook in VS Code
If Markdown in Edit status -> collapse the markdown, the tip "1 cell hidden" doesn't show.
Detailed Repro Build info: VSCode 1.77.3 + dotnet-interactive-vscode-1.0.4227011.vsix
VS Code Version: 1.77.3 (user setup)
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
Date: 2023-04-12T09:16:02.548Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No
dotnet-interactive-vscode-1.0.4227011.vsix
build link: https://dev.azure.com/dnceng/internal/_build/results?buildId=2168897&view=artifacts&pathAsName=false&type=publishedArtifacts
sdk info: dotnet-sdk-7.0.203-win-x64.exe
Note:
1.It's a not a regression issue. It also repro on VSCode 1.77.3 + dotnet-interactive-vscode-1.0.4219021.vsix.
2.Repro VM: <IP_ADDRESS>
Steps:
1.Open the notebook from https://github.com/dotnet/interactive/blob/main/NotebookTestScript.dib
2.Click the > icon in markdown left field - check UI
3.Double click in markdown(ensure it's in edit status) -> Click the > icon in markdown left field -> check UI
Expected Results:
The tip "1 cell hidden" will show in page.

Actual Results:
If Markdown in Edit status -> collapse the markdown, the tip "1 cell hidden" doesn't show.

Please complete the following:
Which version of .NET Interactive are you using? (In a notebook, run the #!about magic command. ):

OS

[ √] Windows 11
[ ] Windows 10
[ ] macOS
[ ] Linux (Please specify distro)
[ ] iOS
[ ] Android

Browser

[ ] Chrome
[ ] Edge
[ ] Firefox
[ ] Safari

Frontend

[ ] Jupyter Notebook
[ ] Jupyter Lab
[ ] nteract
[√ ] Visual Studio Code
[ ] Visual Studio Code Insiders
[ ] Visual Studio
[ ] Other (please specify)

This is a bug ;(

This issue still repro on VS Code 1.93.1 + dotnet-interactive-vscode-1.0.5468011.vsix + dotnet-sdk-8.0.401-win-x64.


Use goimports for gofmt if available

Goimports is gofmt in steroids; automatically adding and removing imports for
you. It is API-compatible with gofmt, but better.

lgtm


bigamist, cryptopin (logical-conflict)

This pull request was generated by the 'mq' tool

/trunk merge


Hive 25945: Upgrade H2 database version to 2.1.214

What changes were proposed in this pull request?
version upgrade for h2
Why are the changes needed?
To address some CVEs
Does this PR introduce any user-facing change?
No
How was this patch tested?
not tested

@nrg4878 The JIRA id used here is wrong; please use the correct one (HIVE-26566) when you merge this to master.

Thank you @zabetak for the review and catching the incorrect the jira number. Should be fixed. Thanks again


Time picker: resolve cropped type inside time containers

In Safari and Chrome:
https://www.carbondesignsystem.com/components/date-picker/code
@jeanservaas   @joshblack

this should be resolved with the work Vince is doing on the component demos


cherry-pick: commits from main to v0.3.0

git cherry-pick -x -s 7639637d1573bb0c0fc215794653f818d5d6668b^..5b316b43ac00168aae100ca6d8b9e2aecd2bfcda
git cherry-pick -x -s 7639637d1573bb0c0fc215794653f818d5d6668b^..5b316b43ac00168aae100ca6d8b9e2aecd2bfcda

Codecov Report

Merging #1027 (e09db42) into release/v0.3 (ffa4bad) will increase coverage by 0.06%.
The diff coverage is 46.05%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@               Coverage Diff                @@
##           release/v0.3    #1027      +/-   ##
================================================
+ Coverage         62.09%   62.15%   +0.06%
================================================
  Files                55       55
  Lines              8779     8801      +22
================================================
+ Hits               5451     5470      +19
- Misses             2958     2959       +1
- Partials            370      372       +2

Impacted Files
Coverage Δ

internal/gatewayapi/filters.go
79.57% <0.00%> (-0.79%)
:arrow_down:

internal/gatewayapi/runner/runner.go
28.26% <0.00%> (-0.32%)
:arrow_down:

internal/gatewayapi/translator.go
97.10% <ø> (ø)

internal/infrastructure/kubernetes/deployment.go
54.97% <0.00%> (ø)

internal/infrastructure/kubernetes/infra.go
27.63% <0.00%> (ø)

internal/infrastructure/kubernetes/service.go
40.81% <0.00%> (-0.57%)
:arrow_down:

internal/xds/translator/route.go
81.08% <37.50%> (-1.53%)
:arrow_down:

internal/xds/translator/runner/runner.go
75.67% <44.44%> (-10.54%)
:arrow_down:

internal/xds/translator/translator.go
76.12% <60.00%> (ø)

internal/xds/translator/ratelimit.go
93.33% <66.66%> (-2.78%)
:arrow_down:

... and 8 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


E2 Editor improvement

Hello,
Would it be possible to disable tab from switching between function suggestions in the e2 editor?

I feel this would help when manually indenting or during correction of indentation.
or if not disable it, add an opt-out check box in the editor's settings in the 'Expression 2' tab?
Best Regards,
Sam.

I recall that you can customize tab-completion style in the options menu, from Visual Studio-style to Eclipse-style.

Ah, you are indeed correct, Thank you very much!


Feature request: functionality to download detailed question info in batches

Current behavior
Functionality does not exist
Expected/desired behavior
I need to achieve the following:

Download

individual user predictions
CP
individual user comments
scores

for all questions belonging to the Q3 and Q4 AI benchmark tournaments
as a batch
preferably as a csv file, alternatively as json
preferably via the API, alternatively via the admin panel

Also needed is to add the ability to downlaod user-level forecasts from the download-csv endpoint.

The ability to do this is now added to the admin panel.
For individual questions, if full resolution data is required, it's available from www.metaculus.com/api/posts/<post_id>/download-csv/?minimize=false
This does not include user-level data, so I'll add that soon.


Update the Integration Tests to wait for dev mode to start completely

In the dev-it bucket the tests wait for dev mode to start using the line:
verifyLogMessageExists("Liberty is running in dev mode."

Unfortunately after dev mode prints this message it continues to compile the app and test source and also registers directories to detect file changes. Tests which depend on compilation or file changes must wait for this extra work to complete.
The tests should add a line to wait for "Source compilation was successful" and also a bit longer for the directory registration to complete. Potentially dev mode could give an additional indication directory registration is complete.
BaseDevTest and DevTest are affected by this issue.
This change may cause some of the existing tests to be modified.

Related, getLogTail(logFile) logic runs before the log exist, while dev mode is just starting up. See https://github.com/OpenLiberty/ci.maven/pull/1570#issuecomment-1209746739


isort configuration added to pyproject.toml

I thought hugs would do that, but I will add it

Are hugs different to cuddles ?
Sorry its been a long week and its only Thursday!!!
-Ian.

On Feb 10, 2022, at 3:16 PM, Paulo Nuin @.***> wrote:
I thought hugs would do that, but I will add it
—
Reply to this email directly, view it on GitHub https://github.com/alliance-genome/agr_literature_service/pull/56#issuecomment-1035453597, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7X4RT3L4BE5SGDENEPLT3U2QMIPANCNFSM5OB3KE7A.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because your review was requested.

It depends on where on the commonwealth you are, I guess


Fixes #85: Added back option in battle move selection menu

I have implemented the back option in the battle move selection menu to prevent the player getting stuck after changing their mind to move. See Issue 85.

I've changed the Back key to e because that's closer to the other options on the keyboard, making for a better user experience.

Ok, that makes more sense


Update babel plugin dependencies

Babel 7.1 and babel-loader 8 are now both stable.

I'm going to close this PR for now, I need to take a deeper look at this.

This was a duplicate of #2642, my mistake.


How to produce results in Table 3

Hello,
To produce the IoU results by class in Table 3, are there any changes I need to make to the yaml files? After running the pretrained model the iou value comes out to be a mean constant instead of a nine-value IoU array by class.
Also, is there a reason the transformer block only uses key and value vectors but not a query vector?
Thanks!

This issue relates to the repo https://github.com/romainloiseau/Helix4D
Please open a new issue in the good repository so that I can answer


Get image source (library/camera)

I need to know if the image comes from the camera or from the library. Am I correct that this information is not available at the moment? Would someone add this?

@Palando, You're right, this is not available at the moment but this should be fairly simple to implement so we'll try to it have it in the next version :)

That would be great. Thank you.


Couldn't Find the Node

Hi , I Install the custom node, but i couldnt find it , can u help me fix this?

I am also having this problem.


Think about architecture for supporting different neuron/synapse types, and interdependencies between them

Right now, we attach attributes such as "excitatory" or "inhibitory", etc. to the synapse, which is the "correct" way to do things. However, this doesn't work for the Izhikevich model, because there are some neuron parameters that vary by type. Right now, we encode this information in the Layout. We should think through how to deal with this in the long run.
See segundo86, figure 22 for starting point for many different synapse (actually, PSP) types. Need to do a little research about whether neurons can actually have different synapse types.

See issue #139 for in-depth information about synapse type lookups and threads.

Merging in issue #195 and closing it. Here was the info from it:
Synapses can have a variety of parameters, such as time constant (PSP decay), delay, etc. Right now, this is partially hard-coded (for example in AllSpikingSynapses::createSynapse()). All of this should be pulled into the parameter files.

Continuing to merge more minor synapse issues that would all be solved by this issue, which seems to be at least a mini-project. Here's from issue #184:

Our LIF/DSSynapse model determines synapse type from both pre and postsynaptic neuron. Izhikevich does from presynaptic. We need to develop some abstract way of specifying how synapse type is determined in the parameter file.
Synapses can have a variety of parameters, such as time constant (PSP decay), delay, etc. Right now, this is partially hard-coded (for example in AllSpikingSynapses::createSynapse()). All of this should be pulled into the parameter files.
There likely is more complexity here. We need to spend some time thinking about this.

And from issue #205:
Issues #173 and #195 are connected to this. It appears there are common device-side functions that are shared among different synapse classes; these functions have assumptions that aren't always valid. Need to look at the requirements for dynamic spiking synapses and for Izhikevich synapses and come up with a more general solution, or refactor this code so they each have their own functions.


Synthesis failed for python-datacatalog

Hello! Autosynth couldn't regenerate python-datacatalog. :broken_heart:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the python-datacatalog API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
nts sha256 = "fe995def6873fcbdc2a8764ef4bce96eb971a9d1950fe9db9be442f3c64fb3b6"
DEBUG: Call stack for the definition of repository 'gapic_generator_python' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:278:1
INFO: SHA256 (https://github.com/googleapis/gapic-generator-go/archive/v0.18.6.tar.gz) = c0d0efba86429cee5e52baf838165b0ed7cafae1748d025abec109d25e006628
DEBUG: Rule 'com_googleapis_gapic_generator_go' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "c0d0efba86429cee5e52baf838165b0ed7cafae1748d025abec109d25e006628"
DEBUG: Call stack for the definition of repository 'com_googleapis_gapic_generator_go' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:300:1
Loading: 0 packages loaded
Loading: 0 packages loaded
INFO: SHA256 (https://github.com/googleapis/gapic-generator-php/archive/v0.1.0.zip) = 3dffc5c34a5f35666843df04b42d6ce1c545b992f9c093a777ec40833b548d86
DEBUG: Rule 'gapic_generator_php' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "3dffc5c34a5f35666843df04b42d6ce1c545b992f9c093a777ec40833b548d86"
DEBUG: Call stack for the definition of repository 'gapic_generator_php' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:364:1
INFO: SHA256 (https://github.com/googleapis/gapic-generator-csharp/archive/4304b1ae8684d28c92458155cd2d39e2eedc4ac7.zip) = 4db430cfb9293e4521ec8e8138f8095faf035d8e752cf332d227710d749939eb
DEBUG: Rule 'gapic_generator_csharp' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "4db430cfb9293e4521ec8e8138f8095faf035d8e752cf332d227710d749939eb"
DEBUG: Call stack for the definition of repository 'gapic_generator_csharp' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:386:1
Loading: 0 packages loaded
INFO: SHA256 (https://github.com/googleapis/gapic-generator-ruby/archive/cc272f0905e45950873e04d3cd8df77a63f215ca.zip) = a14ec475388542f2ea70d16d75579065758acc4b99fdd6d59463d54e1a9e4499
DEBUG: Rule 'gapic_generator_ruby' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "a14ec475388542f2ea70d16d75579065758acc4b99fdd6d59463d54e1a9e4499"
DEBUG: Call stack for the definition of repository 'gapic_generator_ruby' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:400:1
DEBUG: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/rules_python/python/pip.bzl:61:5: DEPRECATED: the pip_repositories rule has been replaced with pip_install, please see rules_python 0.1 release notes
INFO: SHA256 (https://github.com/bazelbuild/bazel-skylib/releases/download/0.9.0/bazel_skylib-0.9.0.tar.gz) = 1dde365491125a3db70731e25658dfdd3bc5dbdfd11b840b3e987ecf043c7ca0
DEBUG: Rule 'bazel_skylib' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "1dde365491125a3db70731e25658dfdd3bc5dbdfd11b840b3e987ecf043c7ca0"
DEBUG: Call stack for the definition of repository 'bazel_skylib' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:35:1
Analyzing: target //google/cloud/datacatalog/v1:datacatalog-v1-py (1 packages loaded, 0 targets configured)
Analyzing: target //google/cloud/datacatalog/v1:datacatalog-v1-py (5 packages loaded, 5 targets configured)
Analyzing: target //google/cloud/datacatalog/v1:datacatalog-v1-py (15 packages loaded, 41 targets configured)
Analyzing: target //google/cloud/datacatalog/v1:datacatalog-v1-py (16 packages loaded, 41 targets configured)
ERROR: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/upb/bazel/upb_proto_library.bzl:257:29: aspect() got unexpected keyword argument 'incompatible_use_toolchain_transition'
INFO: Call stack for the definition of repository 'pandoc_linux' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/protoc_docs_plugin/repositories.bzl:62:5
 - /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/protoc_docs_plugin/repositories.bzl:34:5
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:270:1
ERROR: Analysis of target '//google/cloud/datacatalog/v1:datacatalog-v1-py' failed; build aborted: error loading package '@com_github_grpc_grpc//': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors
INFO: Elapsed time: 36.248s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (57 packages loaded, 2677 targets configured)
FAILED: Build did NOT complete successfully (57 packages loaded, 2677 targets configured)

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/python-datacatalog/synth.py", line 34, in <module>
    include_protos=True,
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 52, in py_library
    return self._generate_code(service, version, "python", False, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 204, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', '--max_idle_secs=240', 'build', '//google/cloud/datacatalog/v1:datacatalog-v1-py']' returned non-zero exit status 1.
2021-04-27 02:13:37,464 autosynth [ERROR] > Synthesis failed
2021-04-27 02:13:37,464 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 87826f7 chore: prevent normalization of semver versioning (#141)
2021-04-27 02:13:37,470 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2021-04-27 02:13:37,476 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 356, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 191, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 336, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 68, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Obsolete. This repo has migrated to owl bot.


After submitting the form, I get the error "Could not connect" or right to the "GRAWL" button

After submitting the form, I get the error "Could not connect" or right to the "GRAWL" button
App Screenshot:

XAMP Screenshot:

Are you connected to the internet ?

yes


Add initial support for hcl

Description
Allows HCL to be used for input files in datacenters. This is the first milestone so the goal is to be able to write the V1 datacenter spec in HCL and not use any of the new HCL really yet.
Any file that ends in .arc will be considered HCL.
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
I converted the local datacenter to HCL and applied it.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

@mueschm can this be closed now that you have the modules branch open?


Add join button to schedule

Allows attendees to join calls. However, button is public so anyone can join. @Chasbob is there some sort of authentication we could do here to prevent this? Maybe Sign In with Slack or some "put the code word in the box"?

So the options I see at first:

make the calendar private
distribute the zoom details on slack
setup the call so you have to approve each person

Also just to be clear, the calendar event is currently completely public regardless of the button on the site. Is that ideal?

The calendar is currently set to public yup in the calendar settings

I guess my point is I don't think we can keep the call details private and in the calendar.
Maybe either having a second private calendar feed / a slack bot to schedule the meetings.
Having someone approving people joining the calls might solve it and let you keep the details on the calendar.

You can totally do a code word to get the link, it would be a lot like what I did with the CTF for PwC, could send off the code word to a cloud function and then the function responds with the link in a JS alert if it’s correct?

Ah neat hadn't really thought of it like that.
I guess I wonder if that's just starting to overcomplicate it when everyone will already be on slack.

It would probably be the fastest thing to set up, but there will definitely be more elegant solutions

@jac0bwilson would you be able to set this up? I’ll invite you to the GCP project

Yeah I can take a look tomorrow probably

If you did want to go that route it could probably be dropped behind the same oauth application instead of using a password?

That would be ideal, otherwise do the cloud function option

In that case, all that's needed is a simple key value loopkup which returns the call details.
I think got Justin's interest, so we can see what he comes up with after work 😆

@Chasbob what's the status on the secure meeting links


Update README.md

Update it

Update this

Thank you for noticing my mistake.

As a passionate GP trainee with a keen interest in technology and healthcare, I am keen to start project  to enhance the learning experience for GP (General Practitioner) trainees in NHS UK. I am seeking a talented developer to join me in integrating the Fourteenfish (e-portfolio) and RCGP (Royal College of General Practitioner) websites.
The goal is to create a seamless platform where trainees can access educational materials from the RCGP website directly through their FourteenFish e-portfolio. By bridging these two platforms, we can provide trainees with easy access to valuable study resources and enhance their learning journey.
I am looking for a developer who shares my enthusiasm for GP training and technology, and who has experience in API integration and web development. Together, we can build a platform that streamlines the learning process for trainees and empowers them to make the most of these incredible resources.
If you are passionate about healthcare technology, API integration, and improving the educational experience for GP trainees, just respond to me here.


Indistinguishable properties and attributes

Currently, the patch() function treats every JSX attribute simultaneously as a property and an attribute - it initializes both, which means you have no ability to update them individually.
Blindly treating every JSX attribute as both a property and an attribute means that most updates are unnecessarily being done twice - one of them generating either a meaningless property or a meaningless DOM attribute. The DOM accumulates a lot of garbage this way.
For example, <div innerHTML={content}> will inject literal HTML via the innerHTML property, but will also create a useless innerHTML attribute - or in some cases, such as <input value={value}>, will initialize the value twice, first using the value property, then again using setAttribute('value', ...).
I don't have a lot of references, but snabbdom for one separates properties from attributes - which seems sort of inevitable, at the VDOM level, if we want to solve this problem?

@mindplay-dk I don't use innerHTML and I can't recommend using it. But if I really had to, I would not do it declaratively, using h or JSX, but inside a lifecycle event.
What about Preact/React, I don't recall they having any special syntax for distinguishing attributes and props and I think that's great, because it makes it easier to reason about my user interface. I don't want to think about separation of attributes and props really.

What about Preact/React, I don't recall they having any special syntax for distinguishing attributes and props and I think that's great, because it makes it easier to reason about my user interface

Yes, but I think this is one of the reasons why these frameworks are considerably larger and more complex - they make distinctions between different element-types and their attributes.
For example, React use code like this to detect specific element types:
https://github.com/facebook/react/blob/45c1ff348e1c7d03567f5bba6cb32cffa9222972/packages/shared/isTextInputElement.js
They have to make distinctions and run-time, and that requires knowledge of every element type, it's properties and attributes - in fact, they make numerous distinctions beyond just properties and attributes, here:
https://github.com/facebook/react/blob/94f44aeba72eacb04443974c2c6c91a050d61b1c/packages/react-dom/src/shared/DOMProperty.js#L43

Properties: object mapping DOM property name to one of the
DOMPropertyInjection constants or null. If your attribute isn't in here,
it won't get written to the DOM.

It's not unthinkable that we can find a much simpler way to deal with this, but it most likely will need to include either a blacklist or whitelist of some sort?

@mindplay-dk I don't think Preact can afford that.

@mindplay-dk You already gave one good example, innerHTML. I already expressed my opinion on that property and here is something I wrote about sanitation.
What are other props/attributes examples that you think should be treated differently?

There are interesting edge-cases - for example, if you do readOnly={true}, that's the property, whereas readonly={true} is the attribute, which needs a string cast. They're not even the same type.
Custom properties don't map to attributes:
document.querySelector("input").foo = "bar"
> "bar"
document.querySelector("input").setAttribute("foo", "qux")
document.querySelector("input").foo
> "bar"

But many built-in properties do map to an attribute:
document.querySelector("input").id = "aaa"
> "aaa"
document.querySelector("input").setAttribute("id", "bbb")
document.querySelector("input").id
> "bbb"

So, some properties update their attribute counterpart as a side-effect, and vice-versa. Fun times.
I wonder if we can exploit this somehow?

I don't think Preact could afford that

Sure - it can do everything at compile-time.

Here's the relevant portion of the Preact sources for reference:
        if (name!=='list' && name!=='type' && !isSvg && name in node) {
		setProperty(node, name, value==null ? '' : value);
		if (value==null || value===false) node.removeAttribute(name);
	}
	else {
		let ns = isSvg && (name !== (name = name.replace(/^xlink\:?/, '')));
		if (value==null || value===false) {
			if (ns) node.removeAttributeNS('http://www.w3.org/1999/xlink', name.toLowerCase());
			else node.removeAttribute(name);
		}
		else if (typeof value!=='function') {
			if (ns) node.setAttributeNS('http://www.w3.org/1999/xlink', name.toLowerCase(), value);
			else node.setAttribute(name, value);
		}
	}

It's doing something like what I suggested - it's checking for name in node (with some more criteria) and doesn't update the attribute if it finds that this is a property. But to deal with id and other edge-cases (as I explained above) they also removeAttribute() if the value is null (ish) to avoid accumulating garbage like id="" in the document model itself.
I'm experimenting with something similar, I'll let you know what I find...

I'm close to a solution, but the test-framework seems to contain an inconsistency with real browsers.
In a real brower, setting the element.value property also updates the attribute.
In seems, in the test framework, that's not the case.
In fact, there's a passing test in the current test-suite, which I think should actually fail:
testTrees("update element with dynamic props", [
  {
    node: h("input", {
      type: "text",
      oncreate(element) {
        element.value = "bar"
      },
      value: "foo"
    }),
    html: `<input type="text" value="foo">`
  },

Here, the test says that the initialization via props value: "foo" should win - but oncreate gets called last, and if I change the test to use setAttribute instead, it fails:
testTrees("update element with dynamic props", [
  {
    node: h("input", {
      type: "text",
      oncreate(element) {
        //element.value = "bar"
        element.setAttribute("value", "bar")
      },
      value: "foo"
    }),
    html: `<input type="text" value="foo">`
  },

oncreate executes after property initializations, so the value should be "bar", right?
But setting the value property doesn't update the attribute.
Try setting element.value in the property and then getAttribute("value") - it works, but with the test-framework, it doesn't appear to.
I'm reluctant to change the test before checking this with you, but I think the test is wrong, and it's passing because of a bug in the test-framework?
So I have two failing tests as of right now:
  ● update element with dynamic props

    expect(received).toBe(expected)

    Expected value to be (using ===):
      "<input type=\"text\" value=\"foo\">"
    Received:
      "<input type=\"text\">"

      at test/vdom.test.js:9:39
      at Array.forEach (native)
      at Object.<anonymous> (test/vdom.test.js:7:11)
      at process._tickCallback (internal/process/next_tick.js:109:7)

  ● elements with falsy values

    expect(received).toBe(expected)

    Expected value to be (using ===):
      "<input type=\"text\" value=\"\">"
    Received:
      "<input type=\"text\">"

      at test/vdom.test.js:9:39
      at Array.forEach (native)
      at Object.<anonymous> (test/vdom.test.js:7:11)
      at process._tickCallback (internal/process/next_tick.js:109:7)

The first is what I just explained.
The second one, I think, is actually correctly omitting the value="" attribute, since it's empty, and we've decided we don't want empty attributes such as id="" per another part of the spec. But I wanted to check this with you as well before changing the spec.

@mindplay-dk Please don't worry so much about tests for now. If you have a working PR addressing the issues you were having, I'd like to see it first. That way I can understand what this issue is really about, because I have to confess I am still confused. Or perhaps I am just not that interested in 100% accuracy as long as it works. Show me the code! 💸 😄

It's on this branch :-)

@mindplay-dk Do you think it would be possible to refactor this part:
if (null == value || false === value) {
  element.removeAttribute(name)
}

Yes, though this requires the introduction of a var empty for the test result.

What do you think about the failing tests?
Do you agree that this might be a bug in the test-framework? From what I could find, this is not how a real browser behaves - but I honestly have very little experience with testing in JS, and I'm not even sure which package or component is at fault.

@mindplay-dk Sorry, I was not aware of any failing tests. If you can send me a PR with these changes so we can review it.

There are two failing tests, as explained above - the first seems like it should have failed all along (before I changed anything) but may be passing due to a bug in the test-framework. I'm really not confident enough to say that with certainty.
And as explained, because of the same bug, I can't make the other test pass - although I'm fairly certain it would pass in a real browser.
As said, I don't know enough about this test-framework to even say which package is at fault.
So I'm kind of stuck with both of these :-/

@mindplay-dk I have a question: are you treating values as properties only if the key is name, or am I reading the code wrong?

I'm treating values as properties if they map to properties ;-)
let foo = { bar: "baz" }
let name = "bar"
name in foo // true

@mindplay-dk I was reading it wrong. Thanks! This looks good, could you make a PR?

Yeah, but... I have two failing tests and no idea how to fix either of them.

Well, in that case I guess I'll help myself with your fork and try to come up with a solution myself! 💪😄

Bingo, the tests are passing 😄
I've opened a PR which I think is ready for review now.


Missing ehtereumjs-vm dependency

Describe the bug
Direct installation of smock thats not work out of the box. When running my tests an error Error: Cannot find module '@nomiclabs/ethereumjs-vm/dist/exceptions' is thrown.
This is fixable by installing that dependency on the project, but its a pretty weird behaviour, honestly.
Reproduction steps

Start a project
Install smock
Try to use it (at least Im using fake)

Expected behavior
Work out of the box.
Screenshots
Can't show without doxing myself - approach via DM if necessary.
System Specs:

OS: Ubuntu
Package Version (or commit hash): 2.0.3

Additional context
n/a

Ah okay I see the problem. Will see if I can work out a quick fix.