After upgrading to 0.71.11 Xcode build fails with 'butter/map.h' file not found

Description
After upgrading to 0.71.11 Xcode build fails with 'butter/map.h' file not found
Error is related to an include: #include <butter/map.h>. XCode can't compile React-Codegen pod.
▸ Running script 'Copy generated compatibility header'
▸ Running script 'Copy generated compatibility header'
▸ Compiling FBReactNativeSpec-generated.mm
▸ Compiling FBReactNativeSpecJSI-generated.cpp

❌  /Users/projects/alle-frontend/mobile/consumer-mobile/ios/Pods/Headers/Public/ReactCommon/react/bridging/Object.h:13:10: 'butter/map.h' file not found

#include <butter/map.h>

This issue was also reported in reanimated repo - https://github.com/software-mansion/react-native-reanimated/issues/3823
It was suggested to delete Pods folder and /ios/build before each build, but it's not an acceptable solution
React Native Version
0.71.11
Output of npx react-native info
System:
OS: macOS 12.6.5
CPU: (10) arm64 Apple M1 Pro
Memory: 256.14 MB / 32.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.20.1 - ~/.nvm/versions/node/v16.20.1/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.20.1/bin/yarn
npm: 8.19.4 - ~/.nvm/versions/node/v16.20.1/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.1
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK:
API Levels: 25, 28, 29, 30, 31, 32, 33
Build Tools: 28.0.3, 29.0.2, 30.0.0, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 33.0.0, 33.0.2
System Images: android-28 | Google ARM64-V8a Play ARM 64 v8a, android-29 | Google APIs ARM 64 v8a, android-30 | Google APIs ARM 64 v8a, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play ARM 64 v8a, android-30 | Google Play Intel x86 Atom, android-31 | Google APIs ARM 64 v8a, android-31 | Google APIs Intel x86_64 Atom, android-33 | Google APIs ARM 64 v8a, android-33 | Google Play ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2022.2 AI-222.4459.24.2221.10121639
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 11.0.19 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce

npx react-native init TestApp --version 0.71.11
yarn add react-native-reanimated + babel config
npm run ios or build via Xcode in ios/

Snack, code example, screenshot, or link to a repository
https://github.com/mgcrea/react-native-sandbox/tree/reanimated-bug

It seems that only React-Fabric pod has a butter subspec
https://github.com/facebook/react-native/blob/a6b49a15a0eb9a968631e7c724f5fc318162802f/packages/react-native/ReactCommon/React-Fabric.podspec#L83
By default, Fabric is disabled and butter isn't included. Why the project sometimes compiles if I remove Pods folder and build again, it's a mystery.

Disabling new architecture in the Podfile seems to solve the issue.

+1 to this issue

rm -rf ~/Library/Caches/CocoaPods
rm -rf Pods
rm -rf ~/Library/Developer/Xcode/DerivedData/*
pod deintegrate
pod setup
pod install
Do these steps and check

rm -rf ~/Library/Caches/CocoaPods rm -rf Pods rm -rf ~/Library/Developer/Xcode/DerivedData/* pod deintegrate pod setup pod install
Do these steps and check

It helps if I do it before every build, but it's not acceptable. I didn't have to do it before the upgrade.

+1 to this issue

Also experiencing this, cleaning the build doesn't seem to help for me

rm -rf ~/Library/Caches/CocoaPods rm -rf Pods rm -rf ~/Library/Developer/Xcode/DerivedData/* pod deintegrate pod setup pod install
Do these steps and check

The Path to iphoneos is not set. Run this on CLI to set it: sudo xcode-select --switch /Applications/Xcode.app
reference > https://stackoverflow.com/a/54072304/10317833

still facing the issue

lets try this
https://stackoverflow.com/a/76072343/10317833

+1 with this issue with RN 0.72.3. Only works after run:
cd ios && rm -rf Pods && rm -rf Podfile.lock && rm -rf build && pod cache clean --all && pod install

Is this going to be resolved anytime soon? Still happening in 0.72.7
@cipolleschi Any idea around this? (Sorry for tagging you but this is a very weird issue)

I got this error two. In a very simple macOS popover demo.
Here is how I config my project:
npx react-native@latest init MenuBarApp --template<EMAIL_ADDRESS>npx react-native-macos-init
yarn add react-native-menubar-extra

AppDelegate.h
@interface AppDelegate : RCTAppDelegate

@property(nonatomic, strong) NSPopover *popover;
@property(nonatomic, strong) NSStatusItem *statusItem;

@end

AppDelegate.mm
- (void)applicationDidFinishLaunching:(NSNotification *)notification
{
/* ... some default code */
// Create React Native rootView
  RCTPlatformView *rootView = [self createRootViewWithBridge:self.bridge moduleName:self.moduleName initProps:self.initialProps];
  NSViewController *viewController = [[NSViewController alloc] init];
  viewController.view = rootView;

  _popover = [[NSPopover alloc] init];
  _popover.contentSize = NSMakeSize(400, 600);
  // Set popover content view as React Native rootView
  _popover.contentViewController = viewController;

  // Expands rootView to Popover arrow.
  if (@available(macOS 14.0, *)) {
    _popover.hasFullSizeContent = YES;
  }
  _statusItem = [[NSStatusBar systemStatusBar] statusItemWithLength:NSVariableStatusItemLength];

  [_statusItem.button setTitle:@"Menubar app"];
  [_statusItem.button setAction:@selector(toggleMenu:)];
}

And when I click build button in Xcode, it fails with this error: butter/function.h file not found.
Here is how I solve it:
# if you're using ios, then ios/build
rm -rf macos/build
rm -rf Pods
pod install

Hello there, sorry for the late reply, I was off the past days.
@keerthika-priya is this issue happening to you in a MacOS app, as it is happening to @tempest2023? If yes, I suggest that you open an issue in the MacOS repo as our CI is working correctly in React Native Core and it could be some specific setup of MacOS.
Otherwise, can you provide a reproducer using this template so I can look into it?

Hi @cipolleschi It is happening in iOS app for me. This is easily reproducible.
Just upgrade to react: 18.2.0, react-native: 0.72.7 and do a pod install.
Again do a pod install. Basically, do the pod install 2 times and you should face this issue.

@keerthika-priya thanks for reporting.

Again do a pod install. Basically, do the pod install 2 times and you should face this issue.

Is this happening also for a newly created project?
Can you try with
npx<EMAIL_ADDRESS>init New072App --version 0.72 --skip-install
cd New072App
yarn install
cd ios
bundle install
bundle exec pod install
bundle exec pod install

And try to build?
If not, I suspect that there is something wrong in your Podfile.

We faced the same issue, and it turned out we were using react-native-linear-gradient. If you are using the same dependency, try removing it and reinstalling again. In our case, FBReactNativeSpecJSI-generated.cpp no longer shows up.

Closing, as this was due to libraries or stale pods

This solved the problem.
https://github.com/software-mansion/react-native-reanimated/issues/3823#issuecomment-1346687536

In our project we do not use the new arch, so we've made a temporary fix to remove the file that fails to compile from the source files of the pod.
installer.pods_project.targets.each do |target|
  if target.name == 'React-Codegen'
    source_files = target.source_build_phase.files
    source_files.each do |source_file|
      if source_file.display_name == "FBReactNativeSpecJSI-generated.cpp"
        source_files.delete(source_file)
      end
    end
  end
end


There is no description for exercises. Warm Up/Hello World!/First Words

There is no description or instruction on how to do exercises in the description window. I have to guess what the exercise asks me to do since I cannot see any of the instructions.

Hello,
I can't reproduce the problem. Please clarify what IDE and OS you are using.


Fix Auto Catalyze instantly spending a lot of potions

Fixes the most recent bug report in the discord server. If the autopotion timer is at, for example, 20/100 seconds and auto catalyze gets turned on, it will instantly spend 400 potions; this fixes that.

Thanks!


Publisher resolution impact

Hello,
Using CustomPublisher example, I am trying to understand what is the Publisher resolution impact if camera settings are different than Publisher settings.
For example, what happens if we set

Publisher: Publisher.CameraCaptureResolution.HIGH
but in camera parameters we configure

//-- function startCapture() code -------
 Camera.Parameters parameters = mCamera.getParameters();
        parameters.setPreviewSize(320, 240);
//------------------
//------------------
//------------------

@Override
    public void onPreviewFrame(byte[] data, Camera camera) {
        mPreviewBufferLock.lock();
        if (isCaptureRunning) {
            if (data.length == mExpectedFrameSize) {
                // Get the rotation of the camera
                int currentRotation = compensateCameraRotation(mCurrentDisplay
                        .getRotation());

                // Send frame to OpenTok
                provideByteArrayFrame(data, NV21, 320, 240, currentRotation, isFrontCamera());

                // Reuse the video buffer
                camera.addCallbackBuffer(data);
            }
        }
        mPreviewBufferLock.unlock();
    }

For example, what happens if we setup a 1024p video resolution from the camera settings when tokbox only accepts 720p?
We have seen some crashes if we setup 1024p on a OTG camera with ublisher.CameraCaptureResolution.LOW (or medium), but don't know if it is related.
Same questions with FPS. It is hard to understand what does FPS tokbox publisher/subscriber params if we manually setup a lower or higher number on camera params.
Thanks a lot

tokbox only supports up to 720p video streaming, however what you feed to the sdk in terms of resolution and frame rate is not always what we stream.
The sdk will adapt to network and cpu conditions so that it will send the best resolution and fps given those constraints.
Let's say you capture in 720p/30fps and you feed with those frames to the sdk, if you are in a bad network, we will downscale the frames to 640x480 or even 320x240 with 10 or 15fps if necessary.
Also, that the sdk is not doing is upscaling the frames, if you capture at 320x240, sdk won't never send above that.
Hope this help with your question.
I'm going to close this since it does not look like an issue with the samples or the sdk, but please don't hesitate to continue the conversation here.


Decide what to do about standard name modifiers units

In #3393 we included support for standard name modifiers. However, that PR, for simplicity, did not include in any special handling of the units.
In the CF Conventions Appendix C it lists the accepted Standard Name modifiers including the associated units.

Standard name modifier
unit

detection minimum
u

number_of_observations
1

standard_error
u

status_flag

u means that the unit it is equivalent to the unit of the unmodified standard_name (e.g. northward_wind has units of m s-1 so northward_wind standard_error would also have units of m s-1).
Note only status_flag and number_of_observations have specified units. Also note that both these are deprecated (See this trac ticket), although only the deprecation of status_flag appears in the actual documentation. I think number_of_observations has been missed off?
The question is how to handle the units?
Should we enforce the behaviour such that if someone renames the cube from
air_temperature -> air_temperature number_of_observations
that it would also change the units?
I'm concerned this may trip some people up:
Currently with standard_name, if some renames the cube, it doesn't have any impact on the units. Below we take a wind cube and rename the cube to air_temperature but the units stay as m s-1 rather than converting to the canonical units of air_temperature
>>> c
<iris 'Cube' of northward_wind / (m s-1) (-- : 1)>
>>> c.rename('air_temperature')
>>> c
<iris 'Cube' of air_temperature / (m s-1) (-- : 1)>

Currently with standard_name, if some renames the cube, it doesn't have any impact on the units. Below we take a wind cube and rename the cube to air_temperature but the units stay as m s-1 rather than converting to the canonical units of air_temperature

From a practical point of view, the most likely usage is when a cube is copied and modified to form a template for a new cube.
So I don't think we shouldn't assign the canonical units, the correct units could be just anything compatible with the canonical unit.
How about making rename check the old + new canonical units, and if they are not compatible that set the units to None (aka 'unknown').
so for example (as possible future behaviour) ....
>>> cube = Cube([0.], standard_name='air_temperature', units='K')
>>> cube.rename('x_wind')
>>> cube
<iris 'Cube' of x_wind / (unknown) (-- : 1)>
>>>
>>> cube.units = 'ms-1'
>>> cube.rename('y_wind_gust')
>>> cube
<iris 'Cube' of y_wind_gust / (ms-1) (-- : 1)>
>>>

On the other hand we do have a bit of an inconsistency in current behaviour because we dont' currently check that units are compatible with a standard name.
For example (current actual behaviour) ...
>>> Cube([0.], standard_name='air_temperature', units='s-1')
<iris 'Cube' of air_temperature / (s-1) (-- : 1)>
>>>

Frankly, that could just be changed :  I can't see any good argument for allowing it, as it is non-CF -compliant.
That change would actually require us to clear units on an (incompatible) rename, for consistency.

On the other hand we do have a bit of an inconsistency in current behaviour because we dont' currently check that units are compatible with a standard name (as you pointed out).
Frankly, that could just be changed : I can't see any good argument for allowing it, as it is non-CF -compliant.

Agreed, but I don't think it is a simple change. I would argue that it is a breaking change and so needs to wait for Iris 3.

How about making rename check the old + new canonical units, and if they are not compatible then set the units to None (aka 'unknown').

I've thought a little more about this and I'm leaning more against it. As it is only possible to do this for cube's with standard_names I think it could lead to confusion if you are a user that works with both standard_names and long_names and (not necessarily aware of it).
This change would result in the following with you may be suprised by this:
>>> cube = Cube([0.], standard_name='air_temperature', units='K')
>>> cube.rename('x_wind')
>>> cube
<iris 'Cube' of x_wind / (unknown) (-- : 1)>
>>>
>>> cube = Cube([0.], standard_name='air_temperature', units='K')
>>> cube.rename('east wind') #AKA not a standard_name so no available name-units to check
>>> cube
<iris 'Cube' of east wind / (K) (-- : 1)>
>>>

Whichever way we decide to go I think this should be dropped from the 2.3 milestone due to:

I would argue that it is a breaking change and so needs to wait for Iris 3.

Personally, I'd err on the side of iris being open and flexible, rather than being rigid and strict.
Could we incorporate such runtime compliance checks? Yes. However I think it would be a rather large effort and maintenance overhead, and given the general wooliness of the conventions, it would lead to a lot of inevitable debate and general angst e.g., climatological time coordinates... just sayin' 😅
Naively, I say let the user do what they want, when they want with their data. Perhaps at the very least we could allow them to opt in to a form of strictness for compliance checking on save. We've always strived to have CF compliant netCDF files generated from iris (hence the CF-1.5 version attribute) but why not allow the user to save a cube "as is" to file, CF compliant of not - they may actually have a need for that freedom.

As far as I can tell, the only cases where this would be relevant are for deprecated standard name modifiers so I think we can close this.


WFLY-12855 Fix UnsupportedOperationException on undeploy

... due to change in AttachmentList backing collection type introduced by WFCORE-3948
https://issues.redhat.com/browse/WFLY-12855

@pferraro I'm going to merge this but we can revert it once the next WF Core beta is out. I'm going to revert the WFCORE-3948 fix and replace it with a SynchronizedList-backed AttachmentList. The one DUP where it's known we need to deal with concurrent writes while iterating, that DUP will synchronize on the list while iterating. Any other bugs we find with the same problem (only found one so far in 10 years) can be also synchronize while iterating.
I don't want external projects that build on WF to need to do what you did here.


operator-sdk_sync: provide versionless symlinks

This is necessary for creating reliable download links on
cloud.redhat.com/openshift/downloads.
Please verify this works as intended, as I am not an ARTist.

@vfreex last week's upload didn't seem to have this take affect, any idea why?  https://mirror.openshift.com/pub/openshift-v4/clients/operator-sdk/4.7.23/


Fixed #5078 to support Inserts in non-interactive mode.

Changed non-interactive mode to send everything through the CLI's parser the same way the interactive mode works as per suggestion from gunnaraasen.
Added multiline support for -execute flag.

[x] CHANGELOG.md updated
[X] Rebased/mergable
[X] Tests pass
[X] Signed CLA

Just a thought, but does it make sense to be able to expose all of the interactive commands to the execute flag, since it allows things like the following, which don't make a lot of sense in non-interactive mode.
⇒  influx -execute 'use mydb'
Using database mydb

Adding special cases to the code to reject certain commands seems hardly
worth the maintenance in this case.  While it doesn't make much sense, it
doesn't do anything either.
On Thursday, December 17, 2015, Edd Robinson<EMAIL_ADDRESS>wrote:

Just a thought, but does it make sense to be able to expose all of the
interactive commands to the execute flag, since it allows things like the
following, which don't make a lot of sense in non-interactive mode.
⇒  influx -execute 'use mydb'
Using database mydb
—
Reply to this email directly or view it on GitHub
https://github.com/influxdb/influxdb/pull/5151#issuecomment-165535870.

+1
@corylanou ?

I agree some commands like 'use' don't make sense to be run by themselves but they do if you want to run multiple commands either directly from the command line or read in from a file.
$ influx -execute 'use metrics
select * from sensor'

$ influx -execute "$(< test.influx)"

where test.influx contains:
create database metrics
use metrics
INSERT sensor,floor=1 value=2
select * from sensor
INSERT sensor,floor=10 value=20
select * from sensor

Although i guess you can also achieve the same using the interactive mode but you just have to add exit to your script.
$ influx -database metrics < test.influx

That is a good example @grange74

This looks good.  I think there is room for a future PR to evolve the ParseCommand to return an error instead of a bool and then add another program argument like continue-on-error that would signal if we should continue running the script or not on error.
+1.

OK, thanks @corylanou
Thanks for the contribution @grange74

@grange74, ah yes nice use-case 🙂

@otoolep thanks for the quick feedback and making my first contribution an enjoyable process.
I would love an InfluxDB t-shirt if i qualify and there are still some left.
@corylanou thanks, i agree it is not good to ignore the returned value. Currently the returned bool only seems to indicate if it ran a command or not, regardless if it succeeded or not. Like you said it would be much better to refactor ParseCommand to return any errors from methods like Insert and ExecuteQuery.  I like your idea of having a way to indicate if you want it to continue on errors or not, as there is no obvious default.

@grange74 -- please email me your postal address.


Result summary messages need to be improved

The message that is above the results need to be adjusted to reflect the new gene list search behavior.
The Gene View contains now only the provided user genes (not top 1000 genes).

TODO - also ensure results messages factor in wildcards like TPS* in genelist (pending)

fixed now


PDF Export encoding

Checklist

[X] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
[X] I have taken the time to fill in all the required details. I understand that the question will be dismissed otherwise.

What is/are your question(s)?
Is there a simple way to change the encoding format in PDF export? Adding EncodingConfigComponent to PdfFormat does not work.
Thanks for the answer.
Additional information
No response

Currently there is no built-in way to do this as we never had this situation before.
AFAIK PDFs have no classic "encoding" as have text files: https://stackoverflow.com/a/42118616
According to the PDF spec there can be certain string encodings.
In JasperReports you can do it like this, but it's recommended to use Fonts with the correct encoding instead.


Weights and Biases support

🚀 Feature Request
Add WandB support for logging.
Motivation

WandB is cloud-based - you can access your logs without a direct ssh connection, just using the website
WandB interface is better suited for many experiments, it also can log model weights, configs, and source code
WandB is prettier

Pitch
Tensorboard is slow a buggy - sometimes I wait about a minute for it to load all the logs, sometimes it just doesn't show them.
There is no reason not to allow fairseq users to use wandb.
It is also very simple to add a new progress bar wrapper (and I already did that).
Alternatives
Logger extension interface (plug-in) which can allow users to use any logging method.
Additional context
I already coded this feature for myself. Currently, I am using it for my experiments and it looks pretty good. You can see PR draft  #1781 for more information.
I'll be happy if you can help me to understand why Windows build is failing, I did not write any platform-specific code and I have no windows computer to test it.

Anybody? =(

@Guitaricet - I can help with this and I have a Windows computer for testing =)

Awesome! You can look into this ci log. Tests are failing for windows-latest, 3.6. Everything is looking good for Ubuntu and MacOS. I also double-checked MacOS tests locally on my machine.
Also, what kind of tests does wandb integration require (if any)? I did not find any tests for tensorboard.

@CSP197 thank you for offering help, but I just noticed that this test is failing on all PRs, including documentation improvements. So this is not a problem of this one.

@Guitaricet - Yeah, I think its a permissions issue with the Windows system.
I can run the tests successfully on my local machine...
Ran 116 tests in 166.650s OK (skipped=17)
...but run into the same issues when running on the Github Actions workflow.

@CSP197 thank you!
Now I hope somebody from fairseq will find this feature useful.

PR is ready for review

@myleott sorry that I am asking you directly, but could you please comment if you want this feature in fairseq and accept the PR if so.

Would love to see this feature added :) Although maybe exposing a logging extension interface might be more appropriate. It would avoid core fairseq from having many cutom logging progress bars.

@BadrYoubiIdrissi I improved my implementation a bit - now it also logs the model architecture, gradient norms, and the logger output before the training. The fork is also updated. Hope you'll find it useful.

Would be really nice to see this merged!

Merged in 1a709b2a401ac8bd6d805c8a6a5f4d7f03b923ff

Can wandb be used in distributed training?


Randomly stops working

Hello 👋🏼
I tried your node works really well in general but it always stops randomly and says "unavailable" although the inverter is only. The only way to reset the node is to restart node red.

Hello.
I have to jump in - similar problem. Sometimes the inverters stay on state updating or unavailable and after that no injection helps, only a restart of the flow by changing something, saving and then it works again. I do have 12 inverters I want to check, the bug occurs randomly on these.
It is a great node, so it would be really incredibly helpful for me if there is a possibility to have a reset of the node without manually interaction, or an error correction.
@binsoul do you think you can find a solution?

So the node enters a state where the inverter is permanently marked as unavailable? Is there anything visible in the log files of Node-RED? Maybe an uncaught exception happens and Node-RED deactivates the node or something.

Hello. Thanks for the answer, yes mostly half of the inverters are going unavailable, always different ones. With a node change = flow restart it begins working with the same problem. I did not check the logs. Meanwhile I did help myselft with a github solution deye to mqtt container which works perfectly without any unavailability.

Hello I have the same problem and one more.
sometimes the node stay in updating for ever in loop, I need to reploy the flow to restart.
Forgive my English mistakes.


Add an option to remove the shadows of a flutter window on desktop [linux]

I believe that such a feature would allow for better window customisation on desktop and increase the range of possibilities UI wise.
I have been trying to add custom rounded corners to my flutter desktop window on Linux and one way I was thinking about the problem is by making the GTK window transparent and letting flutter itself draw the rounded corner. However, this effect doesn't look good on Linux because there are shadows expanding from the original window
Corner radius was increased to make the shadow more noticeable:

@scotch-hub
I think your issue is similar to https://github.com/flutter/flutter/issues/31373. Once the desktop client side support is implemented, you'll be able to customize the shadows.  Please follow-up in linked issue for further updates.
If you disagree, write in comments and I'll reopen it.

I'm aware of the present P5 label, I was just wondering if tackling this feature is something that is on the flutter team's radar for the foreseeable future?


ftxvalidator install instructions steer towards Apple Font Tools v9. Should it (can it?) be 11?

Font Bakery can call Apple’s ftxvalidator, if present. This can be installed from Apple’s "Font Tools for Xcode."
Observed behaviour
Current Font Bakery instructions at https://font-bakery.readthedocs.io/en/latest/user/installation/install-macos.html say to install "Font_Tools_for_Xcode_9.dmg"
However, the latest version seen at https://developer.apple.com/download/more/?=font is "Font Tools for Xcode 11", released Oct 1, 2019.
Expected behaviour
I would love to know whether:

Font Bakery specifically requires the the Xcode 9 version
Font Bakery works fine with the Xcode 11 version
the answer is unknown; FB is known to be good with 9, but 11 is uncertain

I would like to see it clarified in the docs.

I suspect that version 9 was the only one available when this instruction was placed in the documentation. I do not remeber any kind of comment about a specific version requirement. So I really think it means "9 or later"
As far as I know, there's no reason to believe that 11 is worse than 9, unless we have explicit evidence to conclude that.

"Should it (can it?) be 11?"

yes, it can, unless stated otherwise.
I will update the documentation now.

I am using XCode 11 version in fontbakery without issues.


Error: No available formula for

Hi,
after tapping, a formula can't be found:
❯ brew tap eugenk/hets
==> Tapping eugenk/hets
Cloning into '/home/eugen/.linuxbrew/Library/Taps/eugenk/homebrew-hets'...
remote: Counting objects: 216, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 216 (delta 0), reused 0 (delta 0), pack-reused 213
Receiving objects: 100% (216/216), 36.10 KiB | 0 bytes/s, done.
Resolving deltas: 100% (121/121), done.
Checking connectivity... done.
Tapped 8 formulae (31 files, 240K)

❯ brew doctor
Your system is ready to brew.

❯ brew install hets
==> Installing hets from eugenk/homebrew-hets
Error: No available formula for uDrawGraph (dependency of hets)
Searching formulae...
uDrawGraph
Searching taps...

❯ brew doctor
Error: Failed to import: uDrawGraph
No available formula for uDrawGraph
Your system is ready to brew.

❯ brew search udrawgraph
uDrawGraph

❯ brew info udrawgraph
Error: No available formula for udrawgraph

interestingly, brew search finds the formula, but brew info and brew install don't.
System information (Ubuntu 14.04):
❯ uname -a
Linux ubuntu 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

❯ gcc --version
gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2

❯ ruby --version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]

The same happens on an up-to-date archlinux box. It seems like linuxbrew has only a problem with the formula of udrawgraph, but I have no idea why.

Try brew install uDrawGraph.  Most formula are all lowercase due to capitalization quirks

Oh yes, I forgot to give the output if brew install:
❯ brew install uDrawGraph
Error: No available formula for udrawgraph
Searching formulae...
uDrawGraph
Searching taps...

I just found out: If I rename the formula from uDrawGraph.rb to udrawgraph.rb, linuxbrew finds it. Note that homebrew on OSX has no problems finding it without the renaming.

Maybe the filesystem plays a role in this. As far as I know, HFS+ is case insensitive by default, while btrfs (on my arch machine) and ext4 (on ubuntu) are case sensitive, but I'm not 100% sure if this is correct.

@eugenk You might want to send a PR to the offending tap... capitals in formula names are really discouraged.

Alright, will do. Just out of curiosity: Does linuxbrew/homebrew plan to support capitals some day? I can definitely understand if not, but it's always nice to know.

No, Homebrew/Linuxbrew has no plans to support capital letters in formula names.


zphysics: Added a few missing API elements.

I'll likely add more later on, but wanted to get this pushed.
Added functions:
JPC_BodyInterface_GetPosition
JPC_BodyInterface_GetRotation
Also added the JPC_PhysicsUpdateError return value to JPC_PhysicsSystem_Update.

@Srekel I did minor tweaks to the PR.


Disable website's mobile view completely

From @leonstafford on May 31, 2017 8:50
Background
Current Bootstrap mobile view rendering was an afterthought and hasn't been actively designed for in recent changes. We want to disable that altogether and just render desktop view for all users.
An alternative approach for a mobile design may come in the future, but for now, only targeting the desktop will also reduce complexity in current development process.
Acceptance criteria

[ ] Desktop and mobile/tablet users all see the same, desktop targeted site

Copied from original issue: sleepbusorg/sleepbus_org#17

From @guitarino on June 8, 2017 5:32
@leonstafford, looking at the number of @media queries in the CSS file, as well as markup for things like mobile menu, I'd say that it'll be less effort to actually maintain the mobile version rather than try to disable it. I think we're more likely to introduce bugs if we were to go ahead and try to remove all mobile site adaptations. Not to mention other benefits that go along with the mobile version... Let me know your thoughts.

@guitarino - good points, let's do that

@guitarino, sorry, I was a bit premature in confirming that. Spoke to the director and he's pretty firm on disabling all mobile rendering for now

@guitarino - just want to make sure you're not demotivated re the mobile site direction. I don't want to discourage you. I think we're both aligned in wanting a mobile version of the site, it's just the way we need to work to make it a reality. ie, it gets disabled now, then we prepare one or more alternative options to show to the director when the time is right (after some other successes). Cheers

@guitarino - would you be able to take this one on next?
FYI, this repo is now on GitHub, so will need to update your .git config to point to it. Also, could you open a new branch for your windows scripts? I separated them out from the banner story, but I think we can merge them into master, better to have them easily available for any other Windows devs joining.

too much effort to disable within Bootstrap. looking at redoing theme and frontend framework together.


Fixes small typos and compilation issue in 117.1.

Ah sorry @jasdev! Missed this PR 😅 Thanks for taking the time, though!

All good and no problemo! 👊🏽


[jmxfetch] Add agent5-like JMXFetch helper commands

What does this PR do?
Adds agent5-like JMXFetch helper commands.
https://docs.datadoghq.com/integrations/java/#troubleshooting
Motivation
Help with jmx troubleshooting.
Additional Notes
I would advice to review the second commit (https://github.com/DataDog/datadog-agent/pull/1208/commits/656bb20e2b64c2b176cf5e52064184aa02331ca9) separately since it's a refactoring and could be merged separately from the rest.

discussed this IRL: this would make the helpers work only if for example the foo check's config is defined in a file located at conf.d/foo.d/conf.yaml, which is not always the case (and, actually, in most cases it's not the only file where the config would be located).
Let's generalize this to at least pull the configs from the FileProvider config provider (and ideally all valid config providers, depending on the amount of work needed on JMXFetch's side)

Removing the 6.1 milestone on this, we have to agree on an general implementation design and the 6.1 freeze is coming soon


[Merge] --squash doesn't acutally squash

I just merged a pull request with the --squash option but still the commits were retained as-is, nothing was squashed.
Not sure if this a bug in Hubkit or the GitHub API end-point.

@sstok I've just hit the same bug while merging a PR. I was just checking the code, but isn't the bug here that the --squash option is not passed to the mergePullRequest method? (The parameter after the sha indicates a squash.
https://github.com/park-manager/hubkit/blob/master/src/Cli/Handler/MergeHandler.php#L89

I've created a PR with a possible fix, see #74


Improve performance monitoring

This PR introduces enhancements to performance monitoring:

Adds dedicated distro rhel90-dbx-perf-large for performance testing.
Uses patch-pinned v6 server (6.0.6) as v6.0-perf alias.

JAVA-5065

Performance trend charts can be found here: link

Actually, it is neither. It is the perf.send command and Performance Plugin which enable Trend Chart.
I have removed it from the PR  description:

Allows viewing performance results in Trend Charts Tab


Run Kube-Bench as Part of K2 CI

We should add Kube-Bench to our K2 CI to evaluate for any security issues.
(If we feel that Kube-Bench is adequate enough).

Can you explain what the difference between this ticket and https://github.com/samsung-cnct/k2/issues/647 is?

Disregard above question...I see how it is different. Do we need to do #647 first, then this ticket?

I don't think so...   checking our setup for security/best practices doesn't require it to be listed


fix inbox measuring

[x] add new local debug flag virtualListMarks which when turned on does some more visual debugging help for inbox rows
[x] modernize some styling in rows
[x] fix an off by one error in inbox row measuring. fix for mixup of index vs i
[x] fix an error if you leave a channel not forcing a remeasure

@keybase/react-hackers


compiler: add vimdoc

https://github.com/google/vimdoc generates vim help files from vimscript files

This looks useful. Maybe also https://github.com/FooSoft/md2vim for those that write a README in (Github) markdown and then add a Vim help file as an afterthought?

i am curious to ask anyone really ever try this vimdoc, even regardless this 'compiler' which just the cmd vimdoc
// no offense if you were the author, but seems that project had been Not updated over 2 years;
i tried a bit, but seems would Not generate some useful doc,
besides now vim9 script it still recognized?
// again, no offense, but it maybe need to confirm it was useful before putting it into official vim code base...
--
shane.xb.qian

i am curious to ask anyone really ever try this vimdoc

I use it on my vim plugin.

now vim9 script it still recognized?

I think the answer is no. @dbarnett Am I right?

i am curious to ask anyone really ever try this vimdoc

I use it on my vim plugin.

have you ever try any some others popular plugins?
what's that doc looked like?
and it mentioned 'pip install' or on its distr, but seems it only worked build from its source code
--
shane.xb.qian

and it mentioned 'pip install' or on its distr, but seems it only worked build from its source code

You can install it by pre-commit or AUR.

have you ever try any some others popular plugins?

You said md2vim? I haven't use it.

what's that doc looked like?

Official example:
https://github.com/google/vim-maktaba/blob/fe95bb10f6bb250943a44632107f6a3d76ce5f28/examples/helloworld/doc/helloworld.txt

and it mentioned 'pip install' or on its distr, but seems it only worked build from its source code
You can install it by pre-commit or AUR.

it's not in 'pip' store, and not in most others distr regular stores i guess so.

have you ever try any some others popular plugins?
You said md2vim? I haven't use it.

what's that doc looked like?
Official example:
https://github.com/google/vim-maktaba/blob/fe95bb10f6bb250943a44632107f6a3d76ce5f28/examples/helloworld/doc/helloworld.txt

no, i think it's been out-date long time, not even saying vim9 script, so this commit perhaps just some burden vs/but not useful.
--
shane.xb.qian

donot understand what you mean, but 'vimdoc' now it is the default compiler of vim ft.

Yes and where before you would get
make: *** No targets specified and no makefile found.  Stop.

Press ENTER or type command to continue

you will now get:
bash: vimdoc: command not found

Press ENTER or type command to continue

I fail to see why this is a problem now?

I'd probably expect a linter to be the default compiler for the vim filetype, if there was going to be one. It's rare to specify a compiler in an ftplugin.

so far, i think there probably no good option ones, supposed no one good fit vim9 script, so perhaps just back out.
// meanwhile, recently tens of runtime update, maybe need more care about the 'usability' before putting into vim code base.

This is vint:
$ vint runtime/bugreport.vim
"runtime/bugreport.vim:20:9: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:41:9: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:47:47: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:47:55: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:48:38: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:49:38: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:50:38: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:53:9: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:60:9: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:64:9: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:68:9: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:72:9: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"
"runtime/bugreport.vim:76:9: warning! " "Prefer single quoted strings(Google VimScript Style Guide (Strings))"


removed trimspace in write method

This fixes #37
Trimspace causes number of bytes wirtten to be not equal to number of bytes requested to write - this causes an error in multiwriter
Happy to help with other tests if needed

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@mariussturm i've just noticed that somehow this PR also will update README.md - this was not my intent, please ignore commit #8a6a140bfa5cdfce8768648e8a7ddf3c13b04be9

@Bobby-88 under what conditions exactly do you have problems with the trimspace?
Messages starting with whitespaces look odd in the Graylog web interface so we trim them usually.

@Bobby-88 under what conditions exactly do you have problems with the trimspace?
Messages starting with whitespaces look odd in the Graylog web interface so we trim them usually.

Sorry for delay.
Here is a piece of code which gives me warnings if i don't trim whitespaces
gelfWriter, err := gelf.NewWriter("<IP_ADDRESS>:12201") 	if err != nil { 		log.Error().Msgf("gelf.NewWriter: %s", err) 	} 	log.Logger = zerolog.New(os.Stdout).With().Timestamp().Logger().Output(zerolog.MultiLevelWriter(zerolog.ConsoleWriter{Out: os.Stderr, NoColor: true}, gelfWriter))

@Bobby-88 under what conditions exactly do you have problems with the trimspace?
Messages starting with whitespaces look odd in the Graylog web interface so we trim them usually.

I think the writer should respect provided data to send it as is. Even with leading white spaces. Problem with odd UI should be resolved in the Graylog web interface logic, not log writer.

This seems sensible. Especially if the only reason to trim it is to fix the UI. As thaod pointed out, it's more sensible to do this in the UI logic.


Output format

How can I structure the query output response to JSON?

Hello,
The LightRAG class already has a basic convert_response_to_json as a param, may be you can refactor according to your need by creating a fork.  It implements as follows in .utils.py

Hope it helps.


Issue with Pkg.build("Mosek")

Hi,
I'm having a build issue with Pkg.add("Mosek"). Please see printout below
Mosek bin/ directory is in my PATH as well as the MOSEKBINDIR environment variable. I can launch Mosek from a terminal just fine. It seems to be failing at line 81 in the build.jl file:
@BinDeps.install [ :libmosek => :libmosek ]
Any ideas? Please see below.
Ubuntu 12.04 (64)
gcc 4.6
Thanks
Pkg.build("Mosek")
INFO: Building Mosek
==========================================[ ERROR: Mosek ]===========================================
None of the selected providers can install dependency libmosek.
Use BinDeps.debug(package_name) to see available providers
while loading /home/dehann/.julia/Mosek/deps/build.jl, in expression starting on line 81
=====================================================================================================
==========================================[ BUILD ERRORS ]===========================================
WARNING: Mosek had build errors.

packages with build errors remain installed in /home/dehann/.julia
build a package and all its dependencies with Pkg.build(pkg)
build a single package by running its deps/build.jl script

=====================================================================================================

See issue #41 .


Continuously asking the same question, langflow will automatically use the cached results to return

Continuously asking the same question, Langflow will automatically use the cache result to return, which is very unfriendly to some tools that add, delete, or modify types. How to close this cache? Every time a question is asked, the tool will be called

@ogabrielluiz @anovazzi1 @lucaseduoli

hey, @zhengxiang5965
This will be in our next release, possibly later today.


Add GCP Deployment infrastructure

Describe your changes
Adds GCP deployment infrastructure.
Links
Poetry docker: https://medium.com/@harpalsahota/dockerizing-python-poetry-applications-1aa3acb76287
Deploy docker image to GCP container registry: https://github.com/marketplace/actions/push-to-gcr-github-action
Checklist before requesting a review

[ ] The code runs successfully.

HERE IS SOME COMMAND LINE OUTPUT

Oh, I might also recommend adding the following container optimizations for python:
# Save startup time if you're only running one thread
ENV PYTHONDONTWRITEBYTECODE=1
# Ensure that `print` statements get flushed to the stdout buffer immediately
ENV PYTHONUNBUFFERED=1
# Don't cache pip packages locally (no need)
ENV PIP_NO_CACHE_DIR=1

These comments are incredibly useful! Thank you, @AetherUnbound! 😄


[Uncaught in Promise] Invalid Basetexture

I was playing with the cover calculation and once finished I removed the player token from the canvas, moved monster tokens back to their rooms and then reset fog of war. Everytime I open the scene now I get these errors:

Oh an I just noticed that one of the monster tokens isn't accessible anymore. Looks like part of the backdrop.
I can't even select it. o.O
Disabling 5ehelper didn't resolve the issue either. It still tries to load that image.

Ok - I was able to open the scene in another browser (Firefox was broken, Chrome worked). The token has this cover status indicator:

I believe this is addressed by #176 . Please re-open if you still experience issues related to this.


korganizer wrongly shows up as a QT library

For this search query, the following is shown:

... however, the correct attribute is actually just korganizer in the root of nixpkgs, which isn't shown in the search results at all.

This is another consequence of https://github.com/NixOS/nixos-search/issues/345#issuecomment-1079286996. Closing as duplicate of that issue.

To clarify, this is because korganizer and libsForQt5.korganizer are the same derivation, so only one of them is shown. korganizer isn't any more correct than libsForQt5.korganizer as far as nixpkgs is concerned, but it might be more convenient (and it should definitely be shown).


Refactor and bump deps

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 147 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tls.go
0
63
0.0%

certs.go
0
84
0.0%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
0

Relevant Lines:
289

💛  - Coveralls


Value Error when user enters location

@tronicdata  Check this out
We should probably have the address that Google Maps be read-only. And then we can have another field where they user can add their own.
I am thinking of moving this field all the way to the top. And adding another address field below the date input fields. Thoughts?

Found out that this issue is related to the new file structure that I will push up in a few.

Related #19


Enable keyboard shortcuts increase and decrease speed

I believe that a new implementation to the project's shortcuts would be the possibility to be able to increase and decrease the speed. Something like:
'shift + >' = increase
'shift + <' = decrease

Is this a welcome addition?

While waiting them to adding the shortcut, you can use this very simple eventListener
document.querySelector(".player").onkeydown = () => {
  if (event.shiftKey && event.keyCode == "190") player.speed += 0.5
  if (event.shiftKey && event.keyCode == "188") player.speed -= 0.5
};


api search missing result

Hi,
There is this snipt: https://snipt.net/dudebxl/fighter3dcamera-1573b38d/
But if you search for "fighter" it doesn't return it, even tho it's in the class name.
Is it because snipt searches whole words only?
Bye,
Jean

Hmm, searching for fighter returns that snipt as the first result: https://snipt.net/search/?q=fighter

?! Ok... that's odd, I waited two days before mentioning it here to double it was not some caching or some other potential issue, and yes it works now... Should have recorded a screencast :)
Thanks anyway for your time.


Explicit interface members don't work.

Expected
Compile.
Actual
Doesn't compile.
Steps To Reproduce
Example
public interface I {
    void Foo ();
}

public class A : I {
    public void Foo () {
        Console.WriteLine("A");
    }
}

public class B : A, I {
    void I.Foo () {
        Console.WriteLine("B");
    }
}

public static class Program {
    [Ready]
    public static void Main (string[] args) {
        I i;

        var a = new A();
        i = a;
        a.Foo(); // expected: "A"
        i.Foo(); // expected: "A"

        var b = new B();
        i = b;
        b.Foo(); // expected: "A"
        i.Foo(); // expected: "B"

    }
}

Confirmed, and thanks for the great test.
We will try our best to fix this as quickly as possible.

It is the same issue as
https://github.com/bridgedotnet/Bridge/issues/1025
See comment https://github.com/bridgedotnet/Bridge/issues/1025#issuecomment-191752216

Duplicate. See #1025.
This issue is being worked on, but will not make it into the 1.14 release.

#1025 has been fixed.


Add 'setroot' wallpaper fetching

Description
Adds fetching wallpaper set with setroot.
I added it with higher priority than feh, since it can be used only as wallpaper setter, while feh could still be used as image viewer. even tho there is probably zero overlap between users.

Put this after feh.
Also, lines need to be below 100 chars long:
elif type -p setroot >/dev/null && \
     [[ -f "${XDG_CONFIG_HOME}/setroot/.setroot-restore" ]]; then
    image="$(awk -F\' '/setroot/ {printf $(NF-1)}'
             "${XDG_CONFIG_HOME}/setroot/.setroot-restore")"

done

Thanks :+1:


Gareth update UG

Codecov Report

Merging #208 (a3c47cf) into master (1fe8e4c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #208   +/-   ##
=========================================
  Coverage     70.92%   70.92%
  Complexity      851      851
=========================================
  Files           103      103
  Lines          2879     2879
  Branches        408      408
=========================================
  Hits           2042     2042
  Misses          680      680
  Partials        157      157

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


Add parameters for HTTP loader and safe URLs

This adds the same parameters as in https://github.com/awslabs/serverless-image-handler/pull/15 but for v3. I've deployed this successfully but there are a few issues even after I've verified the correct ENV vars get added to the lambda (see attached image below).
I think the changes in this PR are good to merge as it adds the correct env vars, but the below issues need to be addressed separately to get the expected functionally actually working.

The unsafe URLs still work even with ALLOW_UNSAFE_URL="No". This was a problem even with ver 2 and this env var. Never been able to disable the unsafe url.
The signed URLs are broken. They worked correctly with version 2.2 and the template from https://github.com/awslabs/serverless-image-handler/pull/15 which created identical env vars. The error I'm getting now is new.[ERROR] 2018-09-27T20:52:26.207Z 3c728b24-c297-11e8-97e9-65b5097a44b9 generating signed url error: unsupported operand type(s) for +: 'NoneType' and 'str'

The above suggests to me that the ENV vars are either ignored or incorrectly named.

Could really use some help from others trying to get this working as documented.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

the release has been pushed v3.1.0, please note you should provide ONLY one of the environment variables

either ALLOW_UNSAFE_URL=true: when you want to allow unsafe URLs
or SECURITY_KEY=mysecuritykey: when you want to implement safe URLs
resolving the issue

We have created a backlog item for your request to have security key as an input parameter for the template and will try to address it with future releases. Closing the PR.

Updated with v3.1