Add OCNE tools 1.9, kubectl 1.29

No helm changes between ocne 1.8 and 1.9. Maybe worth updating helm 3.12 to OCNE 1.9?

I'll defer to you on version choices as you're closer to this than I am.


Street Fighter Alpha Anthology (USA)  ，graphic error while in software render

Running this game, while  switch to the software redner, the graphic shows  vertical cracks on it

This is down to issues with Android's OpenGLES SW implementation. It doesn't work as well as OpenGL SW on the PC and has various issues. There isn't an easy fix since software rendering ignores almost all hacks and hardware fixes, so I suggest using a hardware renderer if it produces better graphics

This is bugged even in PCSX2, so I doubt there's an easy way to fix this. Closing it for now


+⚽[Here's LIVe]* Chelsea vs Arsenal LIVE STreams ON TV Channel 2024 #978

🔴▶ Chelsea vs Arsenal Live 🔴▶
🔴▶ Chelsea vs Arsenal Live 🔴▶
One of the biggest rivalries of the 21st century in England reignites, as Chelsea welcomes Arsenal at Stamford Bridge for the highlight fixture of the weekend in the Premier League.
Chelsea is winless against the Gunners since Aug. 2021 and it's been over six years since the Blues defeated its London rivals at the Bridge. Enzo Maresca will face his fellow Pep Guardiola understudy, Mikel Arteta, for the first time, hoping his team shows a much better face than it did in the 0–5 defeat the last time out against Arsenal.
Both teams come into the game level on points in the Premier League, with the Blues ahead thanks to goal difference. Arsenal ended up with a frustrating loss against Inter Milan midweek in the Champions League whilst Chelsea was merciless and put eight past Noah FC in the Conference League.
Maresca has some injury concerns with the status of Cole Palmer still uncertain following a nasty challenge from Lisandro Martínez a week ago at Old Trafford. Jadon Sancho has also been nursing fitness issues and hasn't featured for Chelsea in its last five games.
There were a lot of standout performances from Chelsea midweek, we'll see if Maresca rewards any of them by giving them a start in this massive London derby.
JOIN SI SOCCER'S CHELSEA WHATSAPP COMMUNITY - GET ALL THE LATEST NEWS AND ANALYSIS STRAIGHT TO YOUR PHONE
Chelsea Predicted Lineup vs. Arsenal: Premier League (4-2-3-1)
GK: Robert Sánchez—The Spaniard's rash challenge gifted Manchester United its only goal of the game a week ago. He continues to be mistake prone and the critics are beginning to get louder.
RB: Reece James—James has given up his preferred spot on the right side of defense in favor or Malo Gusto in recent weeks. In a game of crucial implications in the race for the top four places, James should return to where he plays best.
CB: Wesley Fofana—Fofana can still be prone to taking unnecessary risks that leave Chelsea exposed in defense. However, he's had a very solid season overall in his return to fitness after a year out.
CB: Levi Colwill—Colwill will partner Fofana in what's undoubtedly Chelsea's best center-back pairing.
LB: Marc Cucurella—Having not featured midweek, Cucurella could take over from Malo Gusto thanks to his better defensive quality. He'll be tasked with containing the always dangerous Bukayo Saka as he did in the Euro 2024 Final.
CM: Moisés Caicedo—One of the best midfielders in the Premier League this season. He's been phenomenal defensively and scored a screamer that saved Chelsea a point from its visit to Old Trafford.
CM: Romeo Lavia—Enzo Fernández was brilliant midweek but in a game like this, Maresca seems poised to once again opt for a more balanced and physical midfield, pairing Lavia alongside Caicedo.
RM: Pedro Neto—Noni Madueke's performances have tailed off recently and Neto could switch to the right wing where he featured a lot during the very early days of his Chelsea tenure.
 João Félix would be the emergency alternative.
LW: Mykhaylo Mudryk—Mudryk has been fantastic off late in Chelsea's midweek games. His recent form is worthy of a Premier League start and he could add even more speed and directness to a Chelsea attack that lacked punch at Old Trafford.
ST: Nicolas Jackson—Jackson has his work cut out dealing with arguably the best center-back pairing in world soccer today. He already proved to be a handful for Liverpool's center-backs and he'll look to replicate that performance against Arsenal.
READ THE LATEST CHELSEA NEWS, PREVIEWS, PREDICTIONS, TRANSFER RUMORS AND MORE
•
Chelsea vs Arsenal: Preview, team news, how to watch, kick-off time & prediction
•
Chelsea vs Arsenal: Who is the referee and VAR for the Premier League clash?
•
Chelsea vs. Arsenal Prediction, Odds, and Best Bets for Premier League Week 11
•
Why Enzo Maresca is enjoying Chelsea luck amid Chelsea’s 25 players squad decision

xcxc


need to update 2.0 chart version when changes go in

Signed-off-by: Chris Ahl<EMAIL_ADDRESS>Final piece for https://github.com/open-cluster-management/backlog/issues/12925

/lgtm


[CI] Fix golangci-lint to avoid legacy lint errors

Signed-off-by: Aadhitya A<EMAIL_ADDRESS>Description
This PR fixes #5269
Notes for Reviewers
WIP and requires checks
Signed commits

[x] Yes, I signed my commits.

🤞

Is there any way to disable typecheck linter? I tried all ways, but seems the CI action won't allow it to do so even if done explicitly

Well... I hope this would do the trick..

golanglint-ci may be the death of you... or maybe me. ;)

golanglint-ci may be the death of you... or maybe me. ;)

Well at least we managed to kill the legacy lint errors for now 😂 so that's one less of a problem. You can check the error logs of CI action now, those errors are gone. It's back to usual lint errors

Lint errors still exists

Lint errors still exists

I know, these are already present in the files... if we want to remove them, then we have to lint the go files literally

Lint errors still exists

I know, these are already present in the files... if we want to remove them, then we have to lint the go files literally

Yup that's what I meant

OK it's fixed now :)


v6 TS Missing static properties when component is wrapped by styled-component

TS does not see static properties when component is wrapped by styled-component.
Reproduction
function MyComponent({ className }: { className?: string }) {
  return
My component

}
MyComponent.SomeStaticData = "Foo bar";

const StyledMyComponent = styled(MyComponent)`
  color: blue;
`;

return (
  <>{StyledMyComponent.SomeStaticData}</>
);

Property 'SomeStaticData' does not exist on type 'IStyledComponent<"web", typeof MyComponent, { className?: string | undefined; } & object> & object'.ts(2339)

Example: https://codesandbox.io/s/keen-euler-gxn4zj?file=/src/App.tsx
(CodeSandbox supports styled-components 6.0.0-beta.14 however it works exactly the same for 6.0.5)
Steps to reproduce
Wrap a component that contains static properties.
Expected Behavior
Static properties should remain accessible.
Actual Behavior
TS does not see static properties.

Fixed by @MartinPELCAT in https://github.com/styled-components/styled-components/pull/4141.
Thanks!


CSHARP-420 TypeCodec.GetColumnTypeCodeInfo does not handle IEnumerabl…

…e runtime types well

The code for the other generic types (Nullable, ISet, IDictionary, Tuple) look like they also have this problem.
If my solution here is okay I can take a look at those types also, if you'd like.

TypeCodec got revamped in #194, its now called Serializer (in the serialization namespace) and supports multiple TypeSerializer<T>.
Any feedback on #194 would be greatly appreciated. It's expected to be released in the next version.
See https://github.com/datastax/csharp-driver/blob/CSHARP-402/src/Cassandra/Serialization/Serializer.cs#L186


MackerNews is using libhn http://mackernews.com

Just wanted to give a shout out :)

btw i'm the author of mackernews, opened up the pull request as the readme suggested so that you could add mackernews to the list of apps using it :) thanks again @bennyguitar  :)

Awesome, it's on the readme now!

@bennyguitar thanks :)


Remove SVE from Arm(R) Neoverse(TM) N1 CPU in Makefile

I incorrectly added +sve to the Neoverse(TM) N1 CPU GCC parameters, which doesn't support SVE - this results in failed builds when using a compiler that doesn't support -mtune=neoverse-n1 which appears to hide the mistake.

Oops. I even remember noticing that change but obviously forgot to ask.

Would it be possible to add GCC 8.x testing into CI @martin-frbg ? Unsure where/how we could do this but it would've caught this I think.


project.mk msys path issue on windows (IDFGH-1181)

Yesterday I got a project using arduino components to compile in Eclipse after  implementing the fix suggested in "Eclipse on Windows shows Errors due to failing to find all header paths (build succeeds in background) (IDFGH-1059) #17" by @dsptech.
I created a new project by copying & editing the working project.  I still had some compile warnings but compiling was working well.
Today after rebooting my computer, on the same project I now get:
...
C:/Users/Andreas/eclipse-workspace/WM/build/main\libmain.a(WMLoRa.o):(.data.ssid+0x0): multiple definition of `ssid'
C:/Users/Andreas/eclipse-workspace/WM/build/main\libmain.a(WM.o):(.data.ssid+0x0): first defined here
collect2.exe: error: ld returned 1 exit status
make: *** [C:\msys32\home\Andreas\esp\esp-idf/make/project.mk:461: /c/Users/Andreas/eclipse-workspace/WM/build/WM.elf] Error 1
"make -j4 all" terminated with exit code 2. Build might be incomplete.
It looks like an msys path on my Windows 10, esp-idf 3.2 system. The error occurs in Eclipse as well as running esp-idf in an msys window.
Any help appreciated.
A Kotowski

Hi, as I already said, the fix is not tested on the last esp-idf framework.
Could you try to remove the fix from the project makefile ?

The fix is not the problem, it is still working well.  It must be the structure of my program, I swapped a different version of the source code which has multiple files in the "main" directory.

Hi,
It seems to me that the two variables "ssid" are declared in two differerent sources (WM.c and WMLoRa.c ?) without the "static" qualifier, or "ssid" is declared in a common shared header without the "extern" keyword.
Are you declaring such variable ? Is the project cloned correctly ? Could you try a "make clean" and "make menuconfig" (changing any option)  on the cloned project ?

@dsptech
You are right "extern" declarations were missing.  I just did not know how to decode the error message.
Thank You


files reset when state change

Environment
Package version:
form_builder_file_picker: ^2.3.0

Flutter doctor

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.0, on macOS 13.2 22D49 darwin-arm64, locale en-ID)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.75.0)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

Code sample

if (type == 'filepicker') {
      return FormBuilderFilePicker(
        name: 'filepicker_datum$page',
        validator: FormBuilderValidators.required(errorText: 'Jawaban wajib diisi!'),
        decoration: const InputDecoration(labelText: 'Attachments'),
        maxFiles: 1,
        previewImages: true,
        onChanged: (val) {},
        typeSelectors: [
          TypeSelector(
            type: FileType.any,
            selector: Row(
              children: const <Widget>[
                Icon(Icons.attachment),
                Gap(8),
                Text('Pilih Berkas'),
              ],
            ),
          )
        ],
        onFileLoading: (val) {
          debugPrint(val.toString());
        },
        onSaved: (newValue) {},
        // customFileViewerBuilder: customFileViewerBuilder,
      );
    }

Description
i am using pageview, when finished fetching files, the list of files that have been fetxhed is reset to null.
Expected behavior:
file lists persists
Current behavior:
files reset
Video
https://user-images.githubusercontent.com/111847308/218387741-ac248f22-27d7-434b-8350-d2bc41b6a46b.mp4

@yudomaryanto please fill all info in the template (flutter doctor, minimal code sample and package version)
Thanks

@yudomaryanto please fill all info in the template (flutter doctor, minimal code sample and package version) Thanks

done update, thanks

Hi @yudomaryanto
This happens with other fields of FlutterFormBuilder package? I don't sure if this is related to the field our to your state management implementation

I have same issue , it only occurs with this field


Roadmap

Hi,
I was thinking of getting more involved in this project since I use it so much and it's the best :)
We might have to create a roadmap to create a "wish list" and start implementing them based on their priority. Here's what I have in mind so far:

Configuration file support (yml file would be ideal)
Daemon mode support
Proper logging support (with levels/files/syslog support)
Ability to use base64: syntax for any input file (certificate etc) instead of providing the actual file
Implement more protocols (I have nothing in mind)
Handle SIGKILL etc. better

What do you think? How do you want to prioritize these or do you have anything else in mind.
Cheers,

Hi,
Thanks for your great roadmap for pproxy!
There is more that I have in mind:

Multiple user authentication
Traffic statistics by domain, user, etc
Logging by domain, url, etc with different levels

I would be really appreciated if you can get more involved in developing.
If you are interested in some of these features, just pick one as you wish.
If you have any questions, please feel free to discuss with me


How to set MySQL root password

Description
I am trying to figure out how to set the MySQL root password when creating a new project. No matter how I set things, the root pow is always blank.  I have set the value in docker-compose.yml and have tried various settings in the project .env
I have scoured the docs and can’t seem to find anything?
OS
My OS is:

[x ] MacOS [Mojave]
[x ] Linux

Hi! It will use the password set by DB_PASSWORD env var but only sets the
password the first time the container is created (when mysql bootstraps
itself). After that it keeps the first settings.
You can reset that mysql container  (this erases any data in it!!) by
running “./vessel down -v” and then restarting it: “./vessel start”
However also check the docker-compose.yml file to make sure i’m right - it
has the setting   in the “mysql” environment setting and will tell you for
certain what env var it used to set that root password (and what other user
is created as well, since it creates a secondary user also).
They key point here is once the mysql container is created, the usernames
and passwords are set. Changing the env var doesn’t change the password any
longer.
On Fri, Jun 12, 2020 at 18:55 Mike Erickson<EMAIL_ADDRESS>wrote:

Description
I am trying to figure out how to set the MySQL root password when creating
a new project. No matter how I set things, the root pow is always blank. I
have set the value in docker-compose.yml and have tried various settings
in the project .env
I have scoured the docs and can’t seem to find anything?
OS
My OS is:

[x ] MacOS [Mojave]
[x ] Linux

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/shipping-docker/vessel/issues/146, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADSDU252YQQ24FQ5OOMK5DRWK563ANCNFSM4N4XEYCA
.

Hey @fideloper
Ya, that is what I have set in .env but it doesn’t seem to use it when creating the MySQL container (this is what has me baffled)
I have the default docker-compose.yml and the
...
environment:
  MYSQL_ROOT__PASSWORD: “${DB_PASSWORD}”
...

and in .env
DB_PASSWORD=“test”

If I call ./vessel stop then change the password in .env to blank, then start again, I am able to successfully connect using ./vessel mysql


Simplify initial condition construction

This PR aims to simplify the initial condition construction, as per the discussion in https://github.com/COSIMA/regional-mom6/issues/174.
Closes https://github.com/COSIMA/regional-mom6/issues/174

In this PR you're changing the boundary condition function not the initial condition right? I still think that the boundary and initial conditions should be kept as separate functions. If not, then we'll should rename it so that the "initial condition" function doesn't do the boundary right?

Oh my bad

This PR will require a new tag release as it's not backwards compatible. Also need to update the access om2 example with the changes.

I'm going to approve the PR because it was Navid's originally. Wait on merging until @navidcy is happy and we also fix up the access om2 example to match simultaneously

I'd like to merge this and then we tag a new release -- how does this sound @ashjbarnes?

Great! Need to reflect changes in access om2 example


Service-now Government instance support

Hello,
It's our understanding that automatic provisioning should also work on Service-Now's government instances, hosted on *.servicenowservices.com, with basic authentication. Asking that this tutorial is updated to reflect government support. Thank you.

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

ID: 50436ac6-fc6c-eef9-8cc8-bf05e8c4b997
Version Independent ID: 2bb67494-9b87-b928-91c2-af8af039eb3b
Content: Configure ServiceNow for automatic user provisioning with Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/saas-apps/servicenow-provisioning-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @twimmers
Microsoft Alias: thwimmer

@josuvil
Thanks for your feedback! We will investigate and update as appropriate.

@josuvil
I'm going to assign this to the document author so they can take a look at it accordingly
@twimmers
Can you please check and add your comments on this doc update request as applicable.

@josuvil - Added this notes section to tutorial. It will be live in next 24 hrs

#please-close


fixed import path for App.js test

Issue: [ #20 ]

Welcome, @Croustys! Thank you so much for your first pull request!
It's great having you contribute to this project

@steveWDamesJr completed your suggestions! let me know if I can help with anything else!


"tuple index out of range" error

When I try to run this program, I get the error in this image.
I am still learning python, my apologies if I am unfamiliar with some of the code.
Do you what is causing this error or how to fix it?

Hi, it looks like the HTTP response data cannot be fetched from cache. Either it is not there or the format changed and my code cannot read it. Unfortunately without a sample I do not know what to change, however I added exception for this part of the code so you can run it again but please be aware that none of the response data will be recovered. I will try to do some tests later this week on new Discord data to see if I can get similar error.


New version: Google.FirebaseCLI version 12.4.6

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/114778&drop=dogfoodAlpha

@wingetbot run


PWN-3806 - Add feature toggles in app

Jira Ticket
https://p2pvalidator.atlassian.net/browse/PWN-3806
Description of Work

add feature toggle entity with subclasses that declare concrete types
edit feature toggles settings screen
add RemoteConfig fetch from Firebase

Screenshots (Optional)

check hook


Add compact option for creating single controller file

This PR allows to compress the CRUD operations inside a single controller class by adding the --compact option

Hi @JustSteveKing
Please review. I will wait for your response.


Feature exist ok

Coverage decreased (-1.02%) to 97.818% when pulling 3b0f0f9272adb5792c9ea81f499ee6af643013c8 on feature-exist-ok into dda5c56add4d97b5291a104e2e8acd480ed4edb5 on development.


Segfaults in run_loop

Hey tetsurom,
Thanks for your work on the library!
I don't know if this is an issue report or simply a misuse on my part, but I am getting some segfaults inside the run loop, given a certain threading setup:
It seems to be an interaction between firing a subject from a non-GUI thread, which is being observed on the GUI thread.  This alone doesn't cause issue, until any unrelated subscription makes use of "sample_with_time" on the GUI thread, which all together seems to cause some issues and segfault.
  rxqt::run_loop rxqt_run_loop;
  rxcpp::subjects::subject<bool> test;
  rxcpp::subjects::subject<bool> test2;

  // Subject to be fired subscribes on the GUI loop
  test.get_observable()
    .observe_on(rxqt_run_loop.observe_on_run_loop())
    .subscribe([](bool) { });

  // Unrelated subject samples on the GUI loop
  test2.get_observable()
    .sample_with_time(std::chrono::milliseconds(25), rxqt_run_loop.observe_on_run_loop())
    .subscribe([](bool){ });

  // Fire first subject from another thread.
  rxcpp::observable<>::range(1, 10000)
    .observe_on(rxcpp::synchronize_new_thread())
    .subscribe([=](int) {
      test.get_subscriber().on_next(true);
    });

I have tested another alternative, where I fire the subject on the GUI thread instead, which leads to the same results:
  rxcpp::observable<>::range(1, 10000)
    .observe_on(rxcpp::synchronize_new_thread())
    .tap([=](int) {
      // Some work on the other thread
      std::this_thread::sleep_for(std::chrono::seconds(2));
    })
    .observe_on(rxqt_run_loop.observe_on_run_loop())
    .subscribe([=](int) {
      test.get_subscriber().on_next(true);
    });;

The segfault occurs at this line in the rxqt library: https://github.com/tetsurom/rxqt/blob/7f7029967b880862df31f5936fe0dbd76d89bfb9/include/rxqt_run_loop.hpp#L20
I did wonder if this had to do with the rxcpp bug mentioned here:
https://github.com/ReactiveX/RxCpp/pull/486
but I had the feeling it was more related to the use of QTimer in rxqt_run_loop
Let me know if you have any tips or insight.  Thanks!

One thing I've noticed:  If I just create my own QThread, and fire the test subject with that, everything functions properly.  It's only when trying to fire the test subject off an Rxcpp-spawned thread that it collides, from my experience.

Hi Noggog, I believe now this is fixed.

Test case

Thank you for the report.

Will take a look and report back on monday.  8)  Thanks!

Looks good so far!  Will reopen another case if anything comes up.
Thanks a lot!


jdk 10 support, livecoin NPE fix, mavens formatting fix

this PR makes XChange compile under jdk 10
also fixed one NPE caused by an anomaly in Livecoins API
maven forces some formatting changes on many files I did not edit during the build

related issue: https://github.com/knowm/XChange/issues/2337


Fix Issue with SConsCPPConditionalScanner misinterpreting ifdefs suffixed with L or UL [Alternate Implementation]

This PR is an alternate implementation of PR #4624 based on the discussion in #4623 and #4624.
PR #4624 fails 9 of the tests included in this PR.
This PR also fixes a bug with evaluating hex integer literals.
For example:
#define HEX0 0x0
#if HEX0
#include <file411-yes>   # <=== actual
#else
#include <file411-no>    # <=== expected
#endif

This reason is the int conversion fails and is using string '0x0' which evaluates true (non-empty string) as opposed to an integer literal of 0.  The integer conversion was implemented as int(expansion) rather than int(expansion, 0).
This PR replaces the integer conversion with a method to evaluate a constant expression.
Changes:

Preserve non-integer literals that contain valid integer specifications
Add binary integer specifications
Add octal integer specification
Zero (0) is considered an octal number
Add negative lookbehind/lookahead for number specifications (text is not word/token based)
Add method to evaluate constant expression for define constant expressions
Replace int conversion with constant evaluation expression

int conversion failed for hex numbers due to default base 10 [int(s)] vs unknown base [int(s, 0)]

Two fixes to the existing test suite were applied
Additional tests were added

Contributor Checklist:

[x] I have created a new test or updated the unit tests to cover the new/changed functionality.
[x] I have updated CHANGES.txt and RELEASE.txt (and read the README.rst).
[ ] I have updated the appropriate documentation

Add a blurb to release and changes.txt and we can merge this.

Wouldn't it be sufficient though to test the regex's alone without parsing a file? Simplify?

Wouldn't it be sufficient though to test the regex's alone without parsing a file? Simplify?

Modifying the regex revealed underlying issues with the implementation and the way the tests were written.  The example in the description above has nothing to do with the regexes (i.e., there is no suffix) but is a manifestation of a failure to convert a hex string to integer without specifying the optional base.
There are a number of issues and potential issues with the implementation that I need to write up.  I'm guessing there is a sizable gap between how one thinks the code is working and how it actually works.
The expression evaluation for #if is not recursive so only the first level of replacement is performed which may then yield another string that should be expanded.  Depending on the way the test is written, that could result in the string effectively being considered "True".

Many of the tests are for the eval_constant_expression() replacement for int().

Wouldn't it be sufficient though to test the regex's alone without parsing a file? Simplify?

Modifying the regex revealed underlying issues with the implementation and the way the tests were written. The example in the description above has nothing to do with the regexes (i.e., there is no suffix) but is a manifestation of a failure to convert a hex string to integer without specifying the optional base.
There are a number of issues and potential issues with the implementation that I need to write up. I'm guessing there is a sizable gap between how one thinks the code is working and how it actually works.
The expression evaluation for #if is not recursive so only the first level of replacement is performed which may then yield another string that should be expanded. Depending on the way the test is written, that could result in the string effectively being considered "True".

Since none of these have been detected (or at least not reported) thus far in the wild. It's probably safe to assume that it's existing functionality (when used) has been sufficient for most.
That said, improvements are always welcome, and as usual @jcbrill 's contributions are well thought out and implemented!
Add and CHANGES/RELEASE and we'll get this one merged.

Quick-and-dirty notes concerning implementation so they are not forgotten.
Known/Potential issues and TODO items for cpp.py:

The regex substitution for integer literals strips the optional suffix.  It is possible that a macro argument is a valid integer literal but the macro implementation is using the argument as token pasting/concatenation.  In this case, stripping the suffix is invalid.  This is likely either very difficult or possibly impossible to handle based on the current implementation.
The cpp namespace dictionary may need to add symbols true and false to be compatible with the c/cpp spec (i.e., if true and false are not in the namespace dictionary, add them).
In some contexts, and undefined preprocessor symbol is treated as 0 where in the SCons implementation, an undefined symbol causes eval() to fail.  A UserDict overriding __getitem__ might be necessary.
For a defined symbol whose value is a literal integer, the literal integer string is converted to an integer in the namespace dictionary.  If the same symbol is then used with token pasting/concatenation, the evaluation most likely fails due trying to "add" a string and an integer.
Need to verify if the "stringify" operator (i.e., #) is supported and if not, is there a reasonable implementation.
Unlike include resolution, the expression evaluation for #IF and #IFDEF is not recursive at present (i.e., only one expansion is performed).
Expansion issues (see above) can cause a string to be "evaluated" as the result of the expansion causing the test to be true.  For example, if  '0' is returned, the result would be true; where if 0 is returned the result would be false.  There may examples of this behavior in the current test suite.

Looks good. Thanks!

Thanks for the fix @jcbrill :)


Cookbook to blacklist PreferencePanes.

Pull? last one tonight...time for sleep.

I think in this case, you shouldn't use MC X, but rather the native method Apple provides via profiles. My internal preference pane cookbook uses 'PayloadType' => 'com.apple.systempreferences'

Np. I don't see "internal preference pane cookbook", or has it yet to be added?

I don't work for Facebook. Pinterest has one. :P
On Aug 18, 2016, at 4:17 PM, cgerke <notifications<EMAIL_ADDRESS>wrote:
Np. I don't see "internal preference pane cookbook", or has it yet to be added?

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/IT-CPE/pull/32#issuecomment-240885376, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFa_GIaq__LFR50B_W4-caoEyUkn4lL0ks5qhOgFgaJpZM4JngMY.

Cool. You going to do a pull request to get it in here?

Nope. It won't be here.
Sent from my iPhone
On Aug 18, 2016, at 6:03 PM, cgerke <notifications<EMAIL_ADDRESS>wrote:
Cool. You going to do a pull request to get it in here?

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/IT-CPE/pull/32#issuecomment-240900952, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFa_GGzOcVm3CPxXrsTK1mTocI3VS3y-ks5qhQDBgaJpZM4JngMY.

ok np. will rewrite.


Unread count in narrowed view

Fix #158
Screenshots:

Automated message from Dropbox CLA bot
@krtkmj, it looks like you've already signed the Dropbox CLA. Thanks!

I think we may want to do some tweaks to the look; I pinged @bgilbert as the original reporter for this thoughts.  Also, I think this might make sense to be a setting since I'm not sure everyone wants the same thing here; perhaps we could make it a checkbox under "display settings"?

With the PR as currently implemented, (31) could mean either that the 31 unreads are all in this narrow, or that none of them are in this narrow.  In the latter case I'd suggest (0/31).
Other than that, the UX LGTM.  Since the narrowed and total counts are both shown, is this worth the complication of an additional setting?

I agree with that (0/31) would be better.
Re: setting, I'm not sure.  I worry that this may be too confusing for users new to the product.  Here's a few questions:

Is it OK that this only shows the narrow numbers in the title, and not in the favicons?  It wasn't clear to me in the initial issue whether the intent was to update the favicon images
Is there a way we can fix the fact that the 3 number is redundant between the title and favicon?

I was assuming the favicon behavior would not change, but I'd be okay with switching it to the narrowed unread count instead.  In that case, icons of narrowed tabs should probably be visually distinctive (such as a different color), just as the titles are.
I think the redundancy between the icon and title is actually a good thing, since it might be confusing if they showed two distinct numbers without explanation.  It's also more accessible to include all the information in the title.

Closing this, since while it's a useful reference for doing this feature, there's enough merge conflicts that we'll probably want to type it in again before merging.
Thanks for all your work on this @krtkmj!


Kata 1.3 rc0

Add new fixes found creating Kata release  1.3.0-rc0
Update versions file to new kata version.

lgtm

seeing no WIP or DNM, I think this one was just left over? merging...


Control Icons not displaying

I have everything setup according to the guide. However, I am unable to see the control icons.
Here's how dapui looks like. I'm using the exact configuration you have on the readme.md file.

This could be a config conflict. What version of neovim are you using? Do you have any winbar settings?
Can you try and reproduce with this minimal init.lua
nvim --clean -u minimal.lua
-- ignore default config and plugins
vim.opt.runtimepath:remove(vim.fn.stdpath("config"))
vim.opt.packpath:remove(vim.fn.stdpath("data") .. "/site")
vim.opt.termguicolors = true

-- append test directory
local test_dir = "/tmp/nvim-config"
vim.opt.runtimepath:append(vim.fn.expand(test_dir))
vim.opt.packpath:append(vim.fn.expand(test_dir))

-- install packer
local install_path = test_dir .. "/pack/packer/start/packer.nvim"
local install_plugins = false

if vim.fn.empty(vim.fn.glob(install_path)) > 0 then
  vim.cmd("!git clone https://github.com/wbthomason/packer.nvim " .. install_path)
  vim.cmd("packadd packer.nvim")
  install_plugins = true
end

local packer = require("packer")

packer.init({
  package_root = test_dir .. "/pack",
  compile_path = test_dir .. "/plugin/packer_compiled.lua",
})

packer.startup(function(use)
  -- Packer can manage itself
  use("wbthomason/packer.nvim")

  use("mfussenegger/nvim-dap")
  use({
    "rcarriga/nvim-dap-ui",
    config = function()
      require("dapui").setup()
    end,
  })

  if install_plugins then
    packer.sync()
  end
end)

vim.cmd([[
command! DapUIToggle lua require("dapui").toggle()
]])

With the minimal config, this is what I see:

Oh I thought that 0.7.2 had the winbar feature but apparently not :facepalm: You'll have to use nightly to use it I'm afraid

Oh I thought that 0.7.2 had the winbar feature but apparently not facepalm You'll have to use nightly to use it I'm afraid

I just tried app image of the latest nightly and the icons loaded fine. Thanks for your help!


[Feature] savepoint timeout support #2560

[Feature] savepoint timeout support #2560
What changes were proposed in this pull request
Issue Number: close #2560

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): no

cc @wangsizhu0504 PTAL, thx.


Feature Request: Update tf.image.sample_distorted_bounding_box to use Scalar Tensor Inputs

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Ubuntu 14.04
TensorFlow installed from (source or binary):
binary
TensorFlow version (use command below):
1.1
Bazel version (if compiling from source):
CUDA/cuDNN version:
8.0/5.1
GPU model and memory:
Titan X
Exact command to reproduce:

Can you please update the scalar inputs to tf.image.sample_distorted_bounding_box to also be accepted as Tensors.  I am dynamically creating min_object_covered values (random values) but currently can not input them to the function

This looks like it could be done w/o breaking shape inference, but it would need to be done w/o breaking graphdef compatibility by creating a duplicate of the sample bounding box op as a V2. I am labeling as contributions welcome since this is not likely going to be worked on soon.
One work around would be to make a few discrete values that would be acceptible and use a switch statement to select between several bounding box ops.

Created a PR #10840 for this issue.


Improve documentation

This pull request includes significant updates to the documentation, particularly enhancing the DEVELOPMENT.md guide and the README.md file. The changes aim to provide clearer instructions and a more comprehensive overview of the project's setup, deployment, and functionality.
Documentation Enhancements:

Development Guide:

Renamed the file from # Development to # Development Guide and added a detailed table of contents.
Expanded sections on setting up the development environment, including installing Firebase CLI, project dependencies, and running the project locally.
Added detailed instructions for deploying the project to Firebase, including logging in and deploying specific services.
Included optional setup for Firebase Admin SDK with environment variable configuration for Linux/MacOS and Windows.
Provided a thorough guide on setting up integrations and environment variables for Discord and GitHub.
Added sections on updating configuration variables in Firebase and troubleshooting tips.

README Overview:

Added an overview of the GameCI Versioning Backend, explaining its purpose and integration with GitHub and Discord.
Detailed the backend's functionality for ingesting Unity versions and GameCI Docker versions, including scraping Unity's version archive and scheduling CI build jobs.
Explained the scheduler's role in managing CI jobs and builds, including status tracking and notifications.
Provided instructions for backing up and restoring the Firestore database using the backfire tool.
Linked to the updated DEVELOPMENT.md for further development instructions.

I went forward and tried to improve the docs. I wrote this after seing a user mentionning they couldn't find the docs on how to work with this project after looking at the readme. There is now a link to DEVELOPMENT.md at the end of the ReadMe.
You can see the results here:

DEVELOPMENT.md
README.md

I added some comments which I forgot to hit submit as a self review. I would appreciate if someone can give it a try and confirm if the commands are ok. I will give it a try too shortly

@coderabbitai full review

@coderabbitai full review


fix: update message definition

The message type can only have 3 possible roles: "system" | "assistant" | "user".
Messages can contain an optional name field. This is helpful in some applications, here's an example from OpenAI: https://github.com/openai/openai-cookbook/blob/main/examples/How_to_format_inputs_to_ChatGPT_models.ipynb.

Seems like this got added pretty recent. LGTM.

@ferdousbhai please deno fmt.

@load1n9 please publish a new version after this gets merged

Sure, sorry, my first pull request. 😅


Add tags to the current singleton

Currently, it is not possible to get the current tags from the current singleton. We could add them.

I think this one should be closed by https://github.com/Netflix/metaflow/pull/1019, right?


[bug 1147807] Change the range of years based on the joined program date...

....

Coverage increased (+0.0%) to 91.75% when pulling fa20b2f69498bb12a7da364978475a5406555ec0 on akatsoulas:fix-alumni-date into 88a7013cb426544361ea51bc0de93c273455c951 on mozilla:master.

lgtm r+


Missmatch between charter's initial maintainer list and runC's maintainer list(s)

In #4, I'm proposing we explicitly support per-project TDCs, but the current charter seems to read like it expects a single, OCI-wide TDC.  If #4 doesn't land (or until it lands?), it would be nice to have that TDC be internally consistent.  The current charter reads (§4.e):

The initial leadership of the TDC shall be Michael Crosby (chief maintainer, Docker, @crosbymichael), Rohit Jnagal (google,@rgnagal), Victor Marmol (google, @vmarmol), Mrunal Patel (redhat, @mrunalp), Alexandr Morozov (docker, @LK4D4), Daniel Minh (@dqminh), Tianon Gravi (@tianon), Vincent Batts (redhat, @vbatts), Brandon Philipps (CoreOS, @philips)

The recent press release has:

A draft charter for OCI is available now and the maintainers are sharing the project’s day-to-day technical governance in a Maintainer’s Guide.

Which maps the charter's “governance guidelines” (§4.b.viii)  to that maintainer guide.  So I expect the current runC MAINTAINERS file lists all TDC members.  Howeverv, that file only lists @crosbymichael, @rjnagal, @vmarmol, @mrunalp, @LK4D4, and @dqminh, not @tianon, @vbatts, or @philips.
One possible explanation for the difference is that the maintainer file at some point contained the set listed in the charter, but that the three missing developers have since left the TDC.  Looking through the history of the maintainers file:

@creack was there from the initial opencontainers/runc@6415e8b (2014-02-18) until opencontainers/runc@10597cb9 (2014-06-10)
@tianon was there from opencontaines/runc@e9f44b52d (2014-08-04) until opencontainers/runc@f637539d (2015-06-26)

I don't see @vbatts or @philips in any version of the file.
Poking around some more, I see two other maintainer files.  If those also contain TDC members, then that brings @creack and @tianon back into the TDC set and also adds @cyphar.
So it would be nice to add some clarity on the following questions:

How is runC listing TDC members?  See my GOVERNANCE.md suggestion for one option.
Which maintainer listing (the one in the charter, or the one in runC) is stale?

your investigations is conflating runc and OCI. Also the history of runc is that it comes from libcontainer and nsinit. There is history there that doesn't include maintainers.

Maintainers != TDC Leadership. I am a maintainer of runC, not part of the TDC leadership. AFAIK TDC leadership is an OCI-wide thing (and is based on additional criteria outside of just being a maintainer).

The root MAINTAINERS file lists root-level maintainers (maintainers with the authority to LGTM any patchset). This is not the same as maintainers of different packages within runc. I only maintain libcontainer/user, and I do not take responsibility for the merging of patches outside of that package. I'm sure you'll find most of the other maintainers agree with that sentiment.

On Tue, Aug 11, 2015 at 12:09:33AM -0700, Vincent Batts wrote:

your investigations is conflating runc and OCI.

Right, but I explained that connection in the initial post:

The [recent press release][2] has:

A draft charter for OCI
is available now and the maintainers are sharing the project’s
day-to-day technical governance in a Maintainer’s
Guide.

Which maps the [charter's][1] “governance guidelines” (§4.b.viii) to that
maintainer guide.
…
[1]: https://github.com/opencontainers/web/blob/33bc0b2597cbfd37e4728660d4b74272603b6f97/content/charter.md
[2]: https://github.com/opencontainers/web/blob/33bc0b2597cbfd37e4728660d4b74272603b6f97/content/pressrelease-july-2015.md

Perhaps the intention is that there will eventually be a different set
of governance guidelines for the TDC, independent of the
runC-maintainer documentation?  But if so, I don't see why the press
release would bother linking to the OCI charter and runC maintainer
guide in the same breath.
I'd prefer we explicitly separate “The OCI as a whole” from the
individual projects, with per-project TDCs (#4).  But that's a
separate issue from this one (where I'm trying to understand the
connection between a single OCI-wide TDC and per-project development
rules).

We can use one of those internet pointers <a> to keep things in sync

On Tue, Aug 11, 2015 at 11:06:32AM -0700, Michael Crosby wrote:

We can use one of those internet pointers <a> to keep things in
sync

I like that, so long as the link targets don't require a §11 amendment
with a LF-Board vote to update them.  Shall I take a stab at a
pull-request doing this, or would someone with a more authoritative
understanding of the intended mapping like to handle that?

https://github.com/opencontainers/specs/blob/master/MAINTAINERS is the source of truth for maintainers in OCI and the charter links to this file.

On Mon, Oct 12, 2015 at 05:35:31PM -0700, Michael Crosby wrote:

https://github.com/opencontainers/specs/blob/master/MAINTAINERS is
the source of truth for maintainers in OCI and the charter links to
this file.

Does it?
$ cd ~/src/opencontainers/web
$ git remote -v | grep origin
origin  git://github.com/opencontainers/web.git (fetch)
origin  git://github.com/opencontainers/web.git (push)
$ git fetch origin
$ git show origin/master | head -n1
commit 33bc0b2597cbfd37e4728660d4b74272603b6f97
$ git grep MAINTAINERS origin/master
origin/master:content/pressrelease-july-2015.md:A draft charter for OCI is available now and the maintainers are sharing the project’s day-to-day technical governance in a Maintainer’s Guide. Maintainers have refined the specification, which is available on GitHub, and contributors can comment on specific pull requests today. A formal draft will be published for comments within the month.
So it looks like the only MAINTAINERS reference in this repository is
in a press-release, not the charter, and it's to runC's file, not the
specs'.

The adopted charter links to the opencontainers/specs MAINTAINERS file in §5.e, which is good.  I'm still not clear on the listing for the TDC contributors (as distinct from maintainers) discussed (for example) in the adopted charter's §5.b.viii.2.


Can you add a variable or pulsating light sourse.

Like the title, a variable light source that can ramp up and down its brightness. Maybe something like the creative light block that comes in different strengths and durations or a way to set them with a GUI.

Thanks for your idea!
What about Redstone, maybe light level controlled by Redstone level?


pkg.go.dev: Comments in examples are not always preserved

What version of Go are you using (go version)?

$ go version
go1.14.4

What did you do?
I compared this example on pkg.go.dev, with the source code.
What did you expect to see?
I expected to see the comments in the source code present in the example as well.  The same example on GoDoc has all of the expected comments.
What did you see instead?
The example on pkg.go.dev only has the first comment, which is also the only comment that's on the same line as other code. The rest of the comments in the source code are on separate lines.

Duplicate of #40710


Fix for rounded rect #5540

https://www.dropbox.com/s/zl8yf5te4vo50p3/Screenshot 2019-04-08 20.01.42.png?dl=0

Stroke alignment is still inverted for circles and rounded rects. Is this just the draw orientation?

https://www.dropbox.com/s/wss577uikh4t8lp/Screenshot 2019-04-08 22.21.43.png?dl=0
fixed circle and rounded rect too 👍

@GoodBoyDigital did you push?

do, try now.. :)

There we go!


Hook up EventStore in Sui/Authority

Adds EventStore initialization into AuthorityState
Changes AuthorityState into TypedAuthorityState<EventStore> with default being the SqlEventStore, but making it possible to have different AuthorityStates in the future
Adds event read APIs into AuthorityState
Adds end to end testing
Changes the EventHandler write path to ingest events, including TX digest and checkpoint sequence number

TODO:

Make the write path idempotent, using TX sequence numbers
Sync with main

Sigh, so many files to sync, after just 2 days

@mystenmark @longbowlu most feedback is now addressed, including using enum_dispatch instead of generics.  Please have another look!
I might experiment with a stream-based response for one of the API functions, but maybe not.....

I like enum_dispatch, thanks for exploring to get rid of (potentially many) generics!


Mono fixes

Adds the types Base<T> and Underlying<T> for use in monomorphization, which are wrappers around an Idx<T>. A lot of functions that had Idx types as inputs and outputs now have Base or Underlying.
This does not change any of the functionality of the code, the only purpose is to make the code easier to understand. Previously, looking at comments or carefully reading the code were the only ways to tell what each Idx belonged to, but now with these wrapper types it is in the code itself, in a way that makes it obvious. Ideally, this will make it easier if we ever have to revisit this for debugging or expanding features. The code is a bit more verbose at times, but I don't think there is any way around this if we want to make the distinction obvious.

Once #255 is merged, the tests for this should pass!

Hmm, yeah I was actually thinking that also, but wasn't sure how much we wanted these wrappers to "interact" with the existing IR. But I agree that it would be nice to use get without doing the unwrapping ourselves, so I'll try implementing something like that after I merge this. Thanks!


dead link to https://docs.sciml.ai/stable/modules/DiffEqDocs/basics/integrator/ from https://mtk.sciml.ai/dev/basics/Events/#Continuous-Events

That would be something for the MTK docs?


User Register and Login Implemented

You cannot push your changes directly to the main branch. The pull request has to be to develop.