Fix fpgainfo events power on time stamp

SW should use the information in block with magic number '0x53696CF0' to derive power on event time stamp, and not the timestamp field of magic number '  0x53696C12'. Power on status is logged immediately after power on.  Time of the day information is written by SW into a BMC register. This write will take some time after power on and hence with Power on log there is no timestamp value available. Because of this reason, second block 'time of the day offset' (block with magic number '0x53696CF0' ) is provided from BMC. BMC internally keeps track of time lapse after the power on and first ToD write by Host and provides the correct value by reverse calculation.  Please use this information to print the power on status time
Signed-off-by: anandaravuri<EMAIL_ADDRESS>

Coverage decreased (-0.007%) to 66.073% when pulling c5e4eee4487d37eb59c544f8a587265a98662299 on aravuri/fix_fpgainfo_event_timestamp into 5cb9ac4b0298f8b34440f43f976ea2fdf98e81fa on master.


Make nomad publish ports on 10.83/16 ip addresses

Currently they're published to the public IP address of the server, e.g. <IP_ADDRESS>. This means they can be connected to from the internet without going through the reverse proxy, which is not optimal (but currently not catastrophic).

Solved by 9e79c8ee5c5433b423a3479728d4d1bf49a479e5


Is it possible to run containers manually before starting tests?

Using docker-compose.yml and DockerComposeContainer I managed to start the whole stack and run my tests. (To make it faster, I implemented a singleton instance of DockerComposeContainer). This is fast enough when I run all tests together. But in the middle of development, often, I run one single test. In this case getting  the whole stack up and down is expensive. Now my question is, is it possible to get the whole stack up (using docker-compose up command) and keep developing and running tests? If not, is it possible to add such feature? (I'm willing to work on the feature, though I'm totally new to the library). Thanks.

Will close until in favor of https://github.com/testcontainers/testcontainers-java/pull/1781.


Allow relocatable sandboxes

This cabal feature is somewhat undocumented, but turns out it has been available for some time (since 1.22 was released). Essentially, it means that sandboxes can be copied around! It works by replacing the paths in the sandbox, which are traditionally absolute, by paths relative to a magic ${pkgroot} variable.
I tried it out like this:
/mismi/mismi-s3 $ mafia build
# Much sandboxing occurs, including amazonka
/mismi/mismi-s3 $ cd ../mismi-ec2
/mismi/mismi-ec2 $ cp -r ../mismi-s3/.cabal-sandbox .
/mismi/mismi-ec2 $ mafia build
Cache: Updating mismi-ec2.cabal
Cache: Removing mismi-s3.cabal
Resolving dependencies...
Notice: installing into a sandbox located at
/mismi/mismi-ec2/.cabal-sandbox
Downloading amazonka-ec2-1.3.6...
Configuring amazonka-ec2-1.3.6...
Building amazonka-ec2-1.3.6...
Installed amazonka-ec2-1.3.6
Resolving dependencies...
Configuring ambiata-mismi-ec2-0.0.1...
Building ambiata-mismi-ec2-0.0.1...

As you can see, it didn't build amazonka twice, it was just the additional amazonka-ec2 package.
The downside is that some packages which depend on native libraries don't install properly, for example postgresql-simple:
/test $ cabal install --enable-relocatable postgresql-simple
Resolving dependencies...
Notice: installing into a sandbox located at
/test/.cabal-sandbox
Configuring postgresql-libpq-<IP_ADDRESS>...
Building postgresql-libpq-<IP_ADDRESS>...
Installed postgresql-libpq-<IP_ADDRESS>
Downloading postgresql-simple-<IP_ADDRESS>...
Configuring postgresql-simple-<IP_ADDRESS>...
Failed to install postgresql-simple-<IP_ADDRESS>
Build log ( /test/.cabal-sandbox/logs/postgresql-simple-<IP_ADDRESS>.log ):
Configuring postgresql-simple-<IP_ADDRESS>...
setup-Simple-Cabal-<IP_ADDRESS>-x86_64-osx-ghc-7.8.4: Library directory of a
dependency: "/usr/local/lib"
is not relative to the installation prefix:
"/test/.cabal-sandbox"
cabal: Error: some packages failed to install:
postgresql-simple-<IP_ADDRESS> failed during the configure step. The exception was:
ExitFailure 1

This PR can't be merged until we solve the above issue, but I think this could be a huge win if we work it out.
/cc @markhibberd @nhibberd @charleso

Another good option for alleviating this pain might be sandman.
It turns out that although sandboxes are generally not relocatable, the contents of the *-packages.conf.d directory is, and sandman takes advantage of this.
 Definitely curious to see how this all compares to the new cabal. Feels like it could be a fair amount of work to get something that would be automatic, rather than manually having to mix with sandman.

:+1:

I've been thinking about this and I think I have a better solution in mind which is a bit of work but would essentially allow no-reinstall cabal, even on ghc-7.8


Warn message for package scanning deprecation from pax-logging-api

Hi,
We are currently using pax-logging version 2.1.0 currently and trying to migrate to the latest 2.2.7 version.
When trying to start the server I'm getting the following warning multiple times.
org.ops4j.pax.logging.pax-logging-api [log4j2] WARN : The use of package scanning to locate plugins is deprecated and will be removed in a future release

Further debugging the issue I identified that this is yielding from the line [1] in log4j-core version 2.22.1. This seems to be due to the following packages added from the PluginManager the pax-logging-log4j2 component [2].
Therefore, even there are no packages from our side, the warning messages are logged. Is there a way to work around this or am I missing something?
[1] https://github.com/apache/logging-log4j2/blob/rel/2.22.1/log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/util/PluginManager.java#L128
[2] https://github.com/ops4j/org.ops4j.pax.logging/blob/logging-2.2.7/pax-logging-log4j2/src/main/java/org/ops4j/pax/logging/log4j2/internal/PaxLoggingServiceImpl.java#L79
Thanks in advance!

Thanks for the issue @HeshanSudarshana. #521 was created to prepare for next major Log4j release (3.0) and till then we'll be keeping Pax Logging 2.2.x compatible with Log4j2 2.x. This means upgrading to newer 2.22.0, 2.22.1, ..., etc. releases, but such warnings may appear unfortunately.
There's no way to quite down this message because I don't think we should change the way Pax Logging itself adds its plugin to Log4j2...
So please understand - we'll check this issue at next Pax Logging release (2.3.x).

Thanks for the response @grgrzybek, I understand that this kind of issues can occur when upgrading to the latest versions.
However, shouldn't the changes be done to avoid the usages of deprecated methods such as PluginManager.addPackages in a 2.2.x patch version as well?

deprecation in 2.22.x doesn't mean it'd be removed in any next 2.x (I hope). Anyway - I'm keeping the issue open, so I may review it and think about it. But to be honest I'm quite busy now with completely different issues (React...)

Whew, I have a solution - instead of simple call to (now deprecated) org.apache.logging.log4j.core.config.plugins.util.PluginManager.addPackage(), I've created Pax Logging's own Maven plugin that can be configured like this:
<plugin>
    <groupId>org.ops4j.pax.logging</groupId>
    <artifactId>pax-logging-log4j2-maven-plugin</artifactId>
    <executions>
        <execution>
            <id>generate-pax-logging-log4j2-plugin-descriptor</id>
            <phase>prepare-package</phase>
            <goals>
                <goal>generate-log4j-plugin-descriptor</goal>
            </goals>
            <configuration>
                <plugins>
                    <!-- These are equivalents of deprecated org.apache.logging.log4j.core.config.plugins.util.PluginManager.addPackage() call -->
                    <plugin>org.ops4j.pax.logging.log4j2.internal.bridges.PaxOsgiAppender</plugin>
                    <plugin>org.apache.logging.log4j.layout.template.json.JsonTemplateLayout</plugin>
                    <plugin>org.apache.logging.log4j.layout.template.json.resolver.LoggerResolverFactory</plugin>
                    <plugin>org.apache.logging.log4j.layout.template.json.util.RecyclerFactoryConverter</plugin>
                </plugins>
            </configuration>
        </execution>
    </executions>
</plugin>

This is kind of equivalent of what was done in a static block of org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl class:
PluginManager.addPackage(PaxOsgiAppender.class.getPackage().getName());
PluginManager.addPackage(JsonTemplateLayout.class.getPackage().getName());
PluginManager.addPackage(LoggerResolverFactory.class.getPackage().getName());
PluginManager.addPackage(RecyclerFactoryConverter.class.getPackage().getName());

This plugin generates proper Log4j2Plugins.dat file for the above plugins' packages and puts them into special location: /META-INF/pax-logging-log4j-plugins/META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat.
Log4j2 uses standard java.lang.ClassLoader#getResources() but it usually doesn't work as expected in OSGi. That's why this location is added to pax-logging-log4j2 bundle's Bundle-ClassPath manifest entry:
Bundle-ClassPath: .,META-INF/pax-logging-log4j-plugins

This ensures that one bundle (with two cp entries) can provide two URLs of the location of named /META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat resource. And both core and Pax Logging Log4j2 plugins are loaded this way without problems.


[Event Change Request] codeunit 90  "Purch.-Post" - multiple publishers

Hello, would it be possible to add OnRunOnAfterPostPurchLine2, OnPostPurchLineOnBeforeInsertReceiptLine2, OnAfterPurchCrMemoLineInsert2 event to codeunit 90  "Purch.-Post", like this:
There is an existing event OnRunOnAfterPostPurchLine( that has been updated with additional parameters.
    trigger OnRun()
...
                  PostPurchLine(
                   PurchHeader, TempPurchLineGlobal, TempVATAmountLine, TempVATAmountLineRemainder,
                   TempDropShptPostBuffer, EverythingInvoiced, ICGenJnlLineNo);
                 OnRunOnAfterPostPurchLine(TempPurchLineGlobal);
//Existing->                OnRunOnAfterPostPurchLine(TempPurchLineGlobal);
>                 OnRunOnAfterPostPurchLine2(PurchInvHeader, PurchCrMemoHeader, ReturnShptHeader, PurchRcptHeader);//New Event

                 if RoundingLineInserted then
                     LastLineRetrieved := true
                 else begin

There is an existing event OnPostPurchLineOnBeforeInsertReceiptLine( that has been updated with additional parameters.
    local procedure PostPurchLine(var PurchHeader: Record "Purchase Header"; var PurchLine: Record "Purchase Line"; var TempVATAmountLine: Record "VAT Amount Line" temporary; var TempVATAmountLineRemainder: Record "VAT Amount Line" temporary; var TempDropShptPostBuffer: Record "Drop Shpt. Post. Buffer" temporary; var EverythingInvoiced: Boolean; var ICGenJnlLineNo: Integer)
...
              end;

             IsHandled := false;
             OnPostPurchLineOnBeforeInsertReceiptLine(PurchHeader, PurchLine, IsHandled, PurchRcptHeader, RoundingLineInserted, CostBaseAmount, xPurchLine);
//Existing->            OnPostPurchLineOnBeforeInsertReceiptLine(PurchHeader, PurchLine, IsHandled, PurchRcptHeader, RoundingLineInserted, CostBaseAmount, xPurchLine);
>             OnPostPurchLineOnBeforeInsertReceiptLine2(PurchHeader, PurchLine, IsHandled, PurchRcptHeader, RoundingLineInserted, CostBaseAmount, xPurchLine, ReturnShptHeader, TempTrackingSpecification, ItemLedgShptEntryNo);//New Event
             if not IsHandled then
                 if (PurchRcptHeader."No." <> '') and ("Receipt No." = '') and
                    not RoundingLineInserted and not "Prepayment Line"
                 then

There is an existing event OnAfterPurchCrMemoLineInsert( that has been updated with additional parameters.
    local procedure PostPurchLine(var PurchHeader: Record "Purchase Header"; var PurchLine: Record "Purchase Line"; var TempVATAmountLine: Record "VAT Amount Line" temporary; var TempVATAmountLineRemainder: Record "VAT Amount Line" temporary; var TempDropShptPostBuffer: Record "Drop Shpt. Post. Buffer" temporary; var EverythingInvoiced: Boolean; var ICGenJnlLineNo: Integer)
...
                              PurchCrMemoLine.Insert(true);
                             Session.LogMessage('0000DDB', EmptyIdFoundLbl, Verbosity::Warning, DataClassification::SystemMetadata, TelemetryScope::ExtensionPublisher, 'Category', PurchLinePostCategoryTok);
                         end;
                         OnAfterPurchCrMemoLineInsert(PurchCrMemoLine, PurchCrMemoHeader, PurchLine, SuppressCommit, PurchHeader);
//Existing->                        OnAfterPurchCrMemoLineInsert(PurchCrMemoLine, PurchCrMemoHeader, PurchLine, SuppressCommit, PurchHeader);
>                         OnAfterPurchCrMemoLineInsert2(PurchCrMemoLine, PurchCrMemoHeader, PurchLine, SuppressCommit, PurchHeader, GenJnlLineDocNo, RoundingLineInserted); //New Event
 #if not CLEAN20
                         if UseLegacyInvoicePosting() then
                             CreatePostedDeferralScheduleFromPurchDoc(xPurchLine, PurchCrMemoLine.GetDocumentType(),
                                 PurchCrMemoHeader."No.", PurchCrMemoLine."Line No.", PurchCrMemoHeader."Posting Date")

      [IntegrationEvent(false, false)]
//Existing->    local procedure OnRunOnAfterPostPurchLine(var TempPurchLineGlobal: Record "Purchase Line" temporary)
     local procedure OnRunOnAfterPostPurchLine2(PurchInvHeader: Record "Purch. Inv. Header"; PurchCrMemoHeader: Record "Purch. Cr. Memo Hdr."; ReturnShptHeader: Record "Return Shipment Header"; PurchRcptHeader: Record "Purch. Rcpt. Header")
     begin
     end;

      [IntegrationEvent(false, false)]
//Existing->    local procedure OnPostPurchLineOnBeforeInsertReceiptLine(PurchaseHeader: Record "Purchase Header"; PurchaseLine: Record "Purchase Line"; var IsHandled: Boolean; PurchRcptHeader: Record "Purch. Rcpt. Header"; RoundingLineInserted: Boolean; CostBaseAmount: Decimal; xPurchaseLine: Record "Purchase Line");
     local procedure OnPostPurchLineOnBeforeInsertReceiptLine2(PurchaseHeader: Record "Purchase Header"; PurchaseLine: Record "Purchase Line"; var IsHandled: Boolean; PurchRcptHeader: Record "Purch. Rcpt. Header"; RoundingLineInserted: Boolean; CostBaseAmount: Decimal; xPurchaseLine: Record "Purchase Line"; var ReturnShptHeader: Record "Return Shipment Header"; var TempTrackingSpecification: Record "Tracking Specification"; ItemLedgShptEntryNo: Integer)
     begin
     end;

      [IntegrationEvent(false, false)]
//Existing->    local procedure OnAfterPurchCrMemoLineInsert(var PurchCrMemoLine: Record "Purch. Cr. Memo Line"; var PurchCrMemoHdr: Record "Purch. Cr. Memo Hdr."; var PurchLine: Record "Purchase Line"; CommitIsSupressed: Boolean; var PurchaseHeader: Record "Purchase Header")
     local procedure OnAfterPurchCrMemoLineInsert2(var PurchCrMemoLine: Record "Purch. Cr. Memo Line"; var PurchCrMemoHdr: Record "Purch. Cr. Memo Hdr."; var PurchLine: Record "Purchase Line"; CommitIsSupressed: Boolean; var PurchaseHeader: Record "Purchase Header"; GenJnlLineDocNo: Code[20]; RoundingLineInserted: Boolean)
     begin
     end;

Sorry, we cannot process group requests with so many different event requests. Please create one requests for each event.


Magisk Version

Please update the module to support 27005+ version

What error are you getting?

Fixed for the next release b8339eb

Added a pre release version that adds support for Magisk 27005+


Mesa: build i965 dri drivers

Contributing to homebrew-xorg:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Does your submission pass
brew audit --strict <formula> (where <formula> is the name of the formula you're submitting)?
[x] Have you built your formula locally prior to submission with brew install <formula>?

Here's the failure from git-cola:
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965

Timed out trying to build llvm 😦

Circle CI ran out out of memory.

Test failed on Travis:
Testing linuxbrew/xorg/mesa

==> ldd /home/linuxbrew/.linuxbrew/Cellar/mesa/17.0.0_1/lib/libGL.so

Error: linuxbrew/xorg/mesa: failed

Expected /libxcb\-randr\.so\.0/ to match "\tlinux-vdso.so.1 =>  (0x00007ffe84fdf000)\n\tlibexpat.so.1 => /home/linuxbrew/.linuxbrew/lib/libexpat.so.1 (0x00007f85a0f54000)\n\tlibxcb-dri3.so.0 => /home/linuxbrew/.linuxbrew/lib/libxcb-dri3.so.0 (0x00007f85a0d50000)\n\tlibxcb-present.so.0 => /home/linuxbrew/.linuxbrew/lib/libxcb-present.so.0 (0x00007f85a0b49000)\n\tlibxcb-sync.so.1 => /home/linuxbrew/.linuxbrew/lib/libxcb-sync.so.1 (0x00007f85a0940000)\n\tlibxshmfence.so.1 => /home/linuxbrew/.linuxbrew/lib/libxshmfence.so.1 (0x00007f85a073d000)\n\tlibglapi.so.0 => /home/linuxbrew/.linuxbrew/opt/mesa/lib/libglapi.so.0 (0x00007f85a0509000)\n\tlibXext.so.6 => /home/linuxbrew/.linuxbrew/lib/libXext.so.6 (0x00007f85a02f8000)\n\tlibXdamage.so.1 => /home/linuxbrew/.linuxbrew/lib/libXdamage.so.1 (0x00007f85a00f4000)\n\tlibXfixes.so.3 => /home/linuxbrew/.linuxbrew/lib/libXfixes.so.3 (0x00007f859feec000)\n\tlibX11-xcb.so.1 => /home/linuxbrew/.linuxbrew/lib/libX11-xcb.so.1 (0x00007f859fce9000)\n\tlibX11.so.6 => /home/linuxbrew/.linuxbrew/lib/libX11.so.6 (0x00007f859f9a6000)\n\tlibxcb.so.1 => /home/linuxbrew/.linuxbrew/lib/libxcb.so.1 (0x00007f859f779000)\n\tlibxcb-glx.so.0 => /home/linuxbrew/.linuxbrew/lib/libxcb-glx.so.0 (0x00007f859f55a000)\n\tlibxcb-dri2.so.0 => /home/linuxbrew/.linuxbrew/lib/libxcb-dri2.so.0 (0x00007f859f353000)\n\tlibXxf86vm.so.1 => /home/linuxbrew/.linuxbrew/lib/libXxf86vm.so.1 (0x00007f859f14c000)\n\tlibdrm.so.2 => /home/linuxbrew/.linuxbrew/lib/libdrm.so.2 (0x00007f859ef38000)\n\tlibm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f859ec24000)\n\tlibpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f859ea05000)\n\tlibdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f859e801000)\n\tlibc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f859e438000)\n\tlibbsd.so.0 => /home/linuxbrew/.linuxbrew/lib/libbsd.so.0 (0x00007f859e224000)\n\tlibXau.so.6 => /home/linuxbrew/.linuxbrew/lib/libXau.so.6 (0x00007f859e01f000)\n\tlibXdmcp.so.6 => /home/linuxbrew/.linuxbrew/lib/libXdmcp.so.6 (0x00007f859de18000)\n\t/lib64/ld-linux-x86-64.so.2 (0x00005577bd6d0000)\n\tlibrt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f859dc0f000)".

Circle ran out of memory with 8 threads. Let's try 6.

6 also used too much memory. Trying 4.

Again 4, used too much memory. Trying 2.

Finally resolved this in https://github.com/Linuxbrew/homebrew-xorg/commit/66d2069ab90f2dda5d773ef5c3cb4c5acc6aaed5


The argument type 'TextStyle' can't be assigned to the parameter type 'TextStyle?'.

What happened?
Getting error when using TextPaint and setting TextStyle

What do you expect?
Should accept TextStyle()
pubspecc.yaml
environment:
  sdk: '>=3.3.0 <4.0.0'

dependencies:
  flutter:
    sdk: flutter
  flame: ^1.16.0

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_lints: ^3.0.0
  flame_lint: ^1.1.2

How can we reproduce this?
import 'package:flutter/material.dart';
import 'package:flame/game.dart';
import 'package:flame/components.dart';

void main() {
  runApp(
    GameWidget(
      game: MyGame(),
    ),
  );
}

class MyGame extends FlameGame {
  @override
  Future<void> onLoad() async {
    add(
      TextComponent(
        text: 'Text',
        position: size / 2,
        textRenderer: TextPaint(
          style: TextStyle(
            color: Colors.red
          ),
        ),
      ),
    );
  }
}

What steps should take to fix this?
No response
Do have an example of where the bug occurs?
its working on zapp but not working on my system
https://zapp.run/edit/flame-zzpu06khzpv0?entry=lib/main.dart&file=lib/main.dart:0-485
Execute in a terminal and put output into the code block below
Output of: flutter doctor -v
[✓] Flutter (Channel stable, 3.19.0, on macOS 14.4 23E5196e darwin-arm64, locale en-US)
    • Flutter version 3.19.0 on channel stable at /Users/burhankhanzada/Development/Google/Flutter/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision bae5e49bc2 (7 days ago), 2024-02-13 17:46:18 -0800
    • Engine revision 04817c99c9
    • Dart version 3.3.0
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/burhankhanzada/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C500b
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] VS Code (version 1.86.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.82.0

[✓] Connected device (3 available)
    • iPhone 15 (mobile) • 03DF0ECA-D1C1-4C3C-A954-BBB0D685F7DB • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-17-2 (simulator)
    • macOS (desktop)    • macos                                • darwin-arm64   • macOS 14.4 23E5196e darwin-arm64
    • Chrome (web)       • chrome                               • web-javascript • Google Chrome 121.0.6167.184

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Affected platforms
All
Other information
No response
Are you interested in working on a PR for this?

[ ] I want to work on this

Your reproduction doesn't fail for me, it only gives a warning about TextStyle not being const when it could be, but no type errors:

Closing this issue as issue automatically resolved after my mac update but i don't understand why this happen on the first place. BTW thanks @spydon for trying this.


Yak widget gallery

None of your examples for the widgets were app projects so they couldn't actually run in isolation, so here's a gallery app to show them all off in one spot!
Fixes: https://github.com/iapicca/yak_packages/issues/81

hi, @AlexHartford
I'm not really open to PR at the moment
I apologize if I gave you a different impression
and you when to the trouble of submitting this PR
as you might have noticed the widgets have very little (if any) in terms of ui
and are much more focused in clean code and streamline the state management
I'm not sure there's much to showcase
examples are meant to display how to use the code rather then display the finished result,
more like documentation
beside CI isn't happy, I think the monorepo's bootstrap (melos) is not set
  Failed to load "/home/runner/work/yak_packages/yak_packages/examples/yak_widgets/gallery/test/widget_test.dart": Compilation failed for testPath=/home/runner/work/yak_packages/yak_packages/examples/yak_widgets/gallery/test/widget_test.dart

I'm afraid I'm gonna close this PR for now, while keeping the issue open
I'll tag you if the situation changes


[CI][test/drivers/flash] NXP flash driver is not called on RT10xx seriese

Describe the bug
flash test report flash driver is not initized.
Please also mention any information which could help others to understand
the problem you're facing:
NXP mimxrt1060_evk/mimxrt1015_evk and all RT10xx series platform impacted.
the flash driver init is not called.
To Reproduce
Steps to reproduce the behavior:
cd tests/driver/flash
west build -b mimxrt1060_evk
west flash --runner=pyocd
*** Booting Zephyr OS build zephyr-v3.3.0-853-g419dda3ed72d ***
Running TESTSUITE flash_driver
===================================================================

    Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/flash/src/main.c:59: flash_driver_setup: device_is_ready(flash_dev) is false

START - test_read_unaligned_address
 FAIL - test_read_unaligned_address in 0.001 seconds
===================================================================
TESTSUITE flash_driver failed.

------ TESTSUITE SUMMARY START ------

SUITE FAIL -   0.00% [flash_driver]: pass = 0, fail = 1, skip = 0, total = 1 duration = 0.001 seconds
 - FAIL - [flash_driver.test_read_unaligned_address] duration = 0.001 seconds

------ TESTSUITE SUMMARY END ------

Expected behavior
Test PASS
Impact
flash functions
Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows)
Toolchain (e.g Zephyr SDK, ...)
Commit SHA or Version used: zephyr-v3.3.0-853-g419dda3ed72d

Additional context
bisect found the issues  is introduced by below commit

8c6137d7a794f84ca963d79ed9529f43ff61eee5 is the first bad commit
commit 8c6137d7a794f84ca963d79ed9529f43ff61eee5
Author: Fabio Baltieri<EMAIL_ADDRESS>Date:   Tue Feb 21 19:18:37 2023 +0000

    build: sort and compact drivers and subsys CMakeLists and Kconfig

    There are just list of child files to include, right now there's a hint
    of that trying to be alphabetical but then entries have been added with
    various logic, so one has to figure where stuff has to be added.

    Rewrite these to:
    - keep the list alphabetical, for CMakeLists unconditional first,
      conditional after so one just has to select and sort
    - drop the spaces in the Kconfig
    - use a single space between  target and directory
    - rename from "Sub Systems" to "Subsystems" (single word)

    Signed-off-by: Fabio Baltieri<EMAIL_ADDRESS>
 drivers/CMakeLists.txt |  88 +++++++++++------------
 drivers/Kconfig        | 184 +++++++++++++++----------------------------------
 subsys/CMakeLists.txt  |  47 ++++++-------
 subsys/Kconfig         |  61 ++++------------
 4 files changed, 137 insertions(+), 243 deletions(-)

@dleach02 , @mmahadevan108 , this issue fails all flash fucntions in RT10xx series

Same issue as #55258 , fixed in #55504 yesterday

@decsny in this case below driver will have the same problem
memc_mcux_flexspi_aps6408l.c
memc_mcux_flexspi_s27ks0641.c


(6.3.x) BZ1284782: Full Text search throws exception in special case

See https://bugzilla.redhat.com/show_bug.cgi?id=1284782

I'll ask if this should be on 6.3.x before requesting it's merged.

Not right now. I've proposed this for the first maintenance update.

Ok it's your call I guess - but it means "full text" search is quite broken in 6.2.0 as the chances of a term matching something in Designer's "global" area is, IMO, reasonably high.

https://github.com/droolsjbpm/kie-wb-common/commit/d3a4940359fb936b936fe9069f21c674f2d98f35


Contains Duplicate Problem

Description
You are given an integer array nums and two integers indexDiff and valueDiff.
Find a pair of indices (i, j) such that:
i != j,
abs(i - j) <= indexDiff.
abs(nums[i] - nums[j]) <= valueDiff, and
Return true if such pair exists or false otherwise.
DSA Problem
Find Duplicate Pair with Conditions

@Charan0313 Can u assign me this??

@iamdestinychild please assign this issue to me.


Do not calculate statistics json length as it is already provided by librdkafka

No need to traverse long strings

Cool thing, up!


javac -version outputs to stderr

I am unable to install Dafny because the current installation code expects javac -version to output to stdout (as a way to test that Java is installed). However, in fact javac -version outputs to stderr, at least on my Mac M1.

This is also fixed by #183. Closing.


RadzenDropdown ValueTemplate support when Multiple is true

The ValueTemplate feature of the RadzenDropdown is very nice when working with single selection. The Template or TextProperty will be reflected in the popup options, and the ValueTemplate will show in the input box when a selection is made. When set to multiple selection however, the ValueTemplate has no effect. I have a list of objects with a Name property and a Letter property, and what I'd like to achieve is a multiple, chips dropdown that displays the names as the options, and the letters as the selections.

You can use Template for that:

Here is the same with chips:


"warning: line breaks generate invalid boostbook"

Boostbook generates this warning

warning: line breaks generate invalid boostbook

from this xslt output:
    [Constructor. [br][role silver —][br]Construct from raw bytes. [br][role silver —][br]Construct from an unsigned integer.

I think its the [br]

I am still getting this

We could just comment it out in the source file:
https://github.com/boostorg/quickbook/blob/5f2e8c24cb813b4b0b94d3316e664b971c5b71dd/src/actions.cpp#L265

the fix worked!


Github actions/CI and dev branch

More of a suggestion than anything since it'd make life easier for testing upcoming updates and such, how about moving all new features/bugfixes, etc to a dev branch, have CI on that dev branch so testers can grab the artifact with the executables to test it before merging it into main and pushing a new release?

Like this.
Since now I've treated every main branch as "dev", but I can totally see the advantages of it in the long run.

Yep, looks clean, should be able to use these actions at the bottom to create downloadable artifacts on the actions for so anyone testing doesn't have to setup a local build environment.
   - name: Upload linux binary artifact.
      uses: actions/upload-artifact@v3
      with:
        name: linux
        path: ./target/release/puddler

    - name: Upload windows binary artifact.
      uses: actions/upload-artifact@v3
      with:
        name: windows
        path: ./target/release/puddler.exe

Yep, thats what i had in mind.


API/C: Add the missing header to the pipeline-internal header file

This patch adds a missing internal header, 'nnstreamer.h', which defines data structures and types required by the
'ml-api-inference-pipeline-internal.h' file.
Signed-off-by: Wook Song<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #316. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


Add quotes to etags

This PR fixes etag generation in Propshaft::Server.
In contrast to other headers, etags must be quoted. (See RFC 9110 §8.8.3.)
Before:
etag: fa74dbac
After:
etag: "fa74dbac"

Not sure if we should add a W/ before to make it a weak tag, but we can discuss this later. Merged.

My understanding is that strong etags are appropriate when:
a) the etag is always assured to change if/when the content changes, and
b) the strong etag is only used for a single encoding of the content (identity, gzip, brotli, etc).
In the case of (b), strong etags may still be used with different encodings as long as the etag itself also changes. With digest-based etags, that can be as simple as adding a suffix, like "originalDigest-gzip", although a fresh digest of the compressed content would be valid too (it's just hard to match a fresh digest back to the original if needed).
If an etag is reused across encodings, then it should be weak (or converted to weak). As a general rule, this conversion should be the responsibility of whatever's transforming the encodings.
Strong etags can allow for content to be cached more often or for longer, and are desirable for things like static assets.
Since propshaft doesn't involve itself with compression or any other alternate encodings, and since the digest-sourced etag will definitely change if the content changes, a strong etag seems appropriate.

Your final paragraph addresses the thing I had been wondering: CDNs that automatically serve optimized versions of image files.
I agree that since it’s not Propshaft making that change, then Propshaft can use strong tags and the CDN can handle their part.


feat(tagging): added tagging for removed tracers

:tada: This PR is included in version 1.27.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


There is no appropriate visualization for stopped/aborted builds

(At least) in Jenkins builds can be stopped/aborted midway. The current visualization maps them to "failed" which isn't really the same.

CCMenu uses the cctray feed, and that format doesn't have a stopped/aborted/canceled state. The mapping to failed is implemented by Jenkins, not by CCMenu.


Type union narrowing in callbacks

TypeScript Version:  2.3.1
Code
type Thing = {
  type: 'thing';
  thing: number;
  doStuff(cb: (value: Thing) => void): Thing;
}

type Foo = {
  type: 'foo';
  foo: number;
  doStuff(cb: (value: Foo) => void): Foo;
}

type Bar = {
  type: 'bar';
  bar: number;
  doStuff(cb: (value: Bar) => void): Bar;
}

type Baz = {
  type: 'baz';
  baz: number;
  doStuff(cb: (value: Baz) => void): Baz;
}

type Stuff = Thing | Foo | Bar | Baz;

function main() {
  let stuff: Stuff;
  if (stuff.type !== 'thing' && stuff.type !== 'foo') {
    return;
  }
  stuff = stuff.doStuff((value: Foo | Thing) => {
    value; // value should be Foo | Thing here, but fails with error TS2349: Cannot invoke an expression whose type lacks a call signature....
  });
}

Expected behavior:
It seems like the above snippet should compile.
Actual behavior:
The compiler doesn't see the callback as compatible with the callback required by the remaining types in the union.

Same cause as #1805?

Duplicate of https://github.com/Microsoft/TypeScript/issues/7294

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


DotNet: Add support for nuget-inspector

Please ensure that your pull request adheres to our contribution guidelines. Thank you!

Closed in favour of #6209


Change default file and setting names  from the dotenv names

This is simply a work-in-progress thing as I'm moving away from the original source code of dotenv. Obviously, not real .env files shouldn't be called .env - I think .env.toml is good for a default, that's what https://github.com/zaida04/tomlenv uses as well. Other file names and config names also need to be revised - in particular, they definitely shouldn't be prefixed with "dotenv".

Changed file names to .env.toml and .env.toml.vault respectively - also, all occurrences of "dotenv" has been changed to the appropriate representation of "toml env" (so tomlEnv for camelCase etc).


Test to Create a new experiment

Acceptance Criteria

Given A logged in User selects create new experiment
When They fill in all the required fields
And They hit the submit button
Then The new experiment is created

This test is done and marked as closed with PR https://github.com/timeades/Phrasee_tech_test/pull/11


Yarn fails during setup

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
I'm following along with the setup instructions and I've gotten to the point where it says to run "yarn". This step fails with multiple error messages (see attached). The first error message is an HTTP 404 when trying to download node-canvas, and indeed, the node_modules/canvas/build/config.gypi file contains a "node_napi_label" value of "node-v127", but there is no file at the full URL:
https://github.com/Automattic/node-canvas/releases/download/v2.11.2/canvas-v2.11.2-node-v127-linux-glibc-x64.tar.gz
v120 seems to be the latest version available on the releases page under v2.11.2, so I'm not sure why we're trying to select v127 and failing to download it. On the other hand, I can't even be confident that this is the root cause of the larger build failure, since I'm not a yarn expert at all. Editing the config file to replace v127 with v120 doesn't help; that config file says it's generated by gyp and shouldn't be edited. It's possible that something entirely different in the output I'm seeing is the cause.
The complicated part of this issue is that I'm on WSL. I'm following the Linux install instructions since there aren't right now dedicated WSL instructions, but all the steps have worked up to this point. My system is running Arch Linux under WSL2, on an x86_64 CPU. I'm on a fork on commit  98788e00c3093aa7b86a1c9541f36c7e38dace75, but I haven't yet made any changes to the code (trying to get the build process working first!
I did see a mention of asking about setup issues in slack, but the slack link is dead (and was last updated in 2023).
yarnout.txt
Steps To Reproduce
Follow the Linux setup guide through step #3: run 'yarn'.
Expected Behavior
Yarn should succeed in installing stuff.
Screenshots
No response
Device Information [optional]
- OS: WSL2 on Windows, running Arch Linux (64-bit)
- Browser: Not relevant, but Firefox
- version: commit 98788e00c3093aa7b86a1c9541f36c7e38dace75 (latest as of 2024-10-2)

Additional context
No response
Are you working on this issue?
No

Hi! @solsword seems like the issue stems from an incompatible Node.js version. The error you're seeing is because node-canvas is trying to use a version of Node.js that doesn't have the appropriate pre-built binaries available. Here's what you can try:

Install Node.js 16.x (as it's the version recommended for this setup):

curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash -
sudo apt install -y nodejs

Install the necessary build tools for node-canvas:
sudo apt-get install build-essential libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-dev
yarn add canvas

Once you've done that, delete your node_modules folder and yarn.lock file, and try running yarn again.

Thanks for the help! That's something I should have checked on...
After upgrading nodejs, I was able to proceed a bit further. The database commands failed due to permissions, and it's hacky and possibly going to be an issue later, but proceeding with sudo (after doing a sudo gem install, which gem warned me about but I'm not using Ruby for anything else on this system) lets me actually run the app, which is good. I had to delete the node_modules folder in cv-frontend-vue after getting repeated ENOTEMPTY errors for renaming folders there, but that actually let the thing run and respond to a request on localhost:3000. Unfortunately, I'm now getting an error in the browser about a missing asset (obviously, possibly due to my hacking around a few steps).
My new error looks like this, but I'll try to poke around a bit more before actually asking for help with this. I'm just posting this response now in case I don't get to that soon and others trying to get it up and running on WSL find what I'm doing useful or run into the same sorts of errors.
Sprockets::Rails::Helper::AssetNotFound in Circuitverse#index

Showing /home/pmwh/teaching/240/src/CircuitVerse/app/views/layouts/application.html.erb where line #18 raised:

The asset "application.js" is not present in the asset pipeline.

Extracted source (around line #18):

16
17
18
19
20
21

    <%= javascript_include_tag "application_sprockets", "data-turbolinks-track": "reload" %>
    <%= javascript_include_tag "application", "data-turbolinks-track": "reload", defer: true %>

    <!-- Global site tag (gtag.js) - Google Analytics -->
    <%= render partial: "layouts/google_analytics" if Rails.env.production? %>

Rails.root: /home/pmwh/teaching/240/src/CircuitVerse
Application Trace | Framework Trace | Full Trace
app/views/layouts/application.html.erb:18
app/controllers/application_controller.rb:34:in `switch_locale'
Request

Parameters:

None

I was able to solve this error.

This app was previously a Rails 6 but as you upgraded to Rails 7, the application.html.erb was no longer recognizing my application.js file. I just made a minor change and now it is working fine. I will create a pull request to solve this issue.

Hey! For some reason, I am unable to commit my code to git. So all you have to do is change the "application" part in the below code with " /assets/application.js"

Then it should work

It is documented here


chng inpatient signals aren't documented

They are named 7dav_inpatient_covid and  7dav_outpatient_covid. They should be added to the chng page

Are these signals actually in the DB? Maybe they are at different geo levels, because when I try pulling at county level, I don't get any results. Need to check on that first.

They are only available at the state level.  Some documentation went in with https://github.com/cmu-delphi/delphi-epidata/pull/1534

Gotcha, thanks for clarifying!


Fix remove hidden data to support list binding and hiddenRow

Description

This updates the removeHiddenData functionality to support hiddenRow in repeating groups as well as fixing the implementation of AddIndicesRecursive to not crash when encountering a list-binding which can be found in a file-upload component with multiple files allowed.
Related Issue(s)

https://github.com/Altinn/app-frontend-react/issues/726

Verification

[x] Your code builds clean without any errors or warnings
[x] Manual testing done (required)
[x] Relevant automated test added (if you find this hard, leave it and we'll help out)
[x] All tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Looks good, this code has a lot of loops and conditions so I think we should stive to have good testcoverage. Should we take a pair programming session and add som tests for hiddenrows?

Checking in here to ask some questions... I believe me and @ivarne discussed the hiddenRows functionality at one point when thinking about removing hidden data, and I've talked to SSB about it as well. There are multiple use-cases for hiddenRows, and for SSB (at least) they said they would not expect hidden rows to cause deletions from the data model upon submitting. That's because they would like to use hiddenRows to filter the (prefill) data in ways to show only the relevant parts for the user - but at the same time they had systems on the receiving end that required all the data to be present in the data model even if some of it was hidden for the user.
Another use-case I've heard of is having two repeating groups on two different pages, bound to the same structure in the data model, but showing different sets of rows (typically using hiddenRow with inverse logic on one of them). We should make sure no data is deleted in those cases, as all data is shown to the user.
So, are we sure this is what users want? Maybe we should have flags for it?

If I remember correctly the removal is implemented with aggregation of two lists, one of the keys to remove and one of visible fields. Before removing anything I check that the relevant fields are not visible anywhere else. HiddenRows should obviously follow the same pattern.
Generally I think it makes most sense to remove all data not visible to the end user when submitting, but the current implementation preserves fields that isn’t mapped in any component (as a way to implement hidden fields that probably will be ignored or manipulated by machine integrations and cause bugs in validation or backend systems).
If there is a use case for not removing fields that are actively hidden by a component, I think the most sensible approach would be a "hiddenNotRemove": true just under the hidden expression. Modifying the expression just seems way too syntax heavy.

For now I suggest we just split the removehiddendata into to flags (so we don't make upgrade of apps relying on hiddenRows not being removed impossible). If we down the road see that we need hiddenNotRemoved functionality i like @ivarne approach

Hmm, I agree with the principle that no data should be hidden from the user while also requiring them to submit it. It goes against the whole point of having a receipt that shows the user what they submitted, and we've discussed before that from the users perspective it's the receipt they confirm as being their valid submission and not the data model itself. So I'm all for keeping the functionality as implemented here - but we should make sure it's visible in the v8 release notes and/or docs that the data removal functionality now removes more data than it used to. No service owner should find out by surprise, at least.
And when it comes to "hiddenNotRemove": true I would prefer it being named "removeDataWhenHidden": false as to avoid a double-negative. Also, configuring it on the component-level might not be optimal, as each component can have one or many bindings to the data model, and we may not want all of them to be kept/removed. The data modelling tools in Studio can probably add some custom configuration for this, but it might not be easy to read metadata like that from C#. In app-frontend we can now easily read metadata from the data model, at least in v4.

Trying a small summary:
We should revert the changes in this PR that removes hiddenRows from the datamodel if RemoveHiddenDataPreview is set to true to keep the functionality unchanged for v7.
For v8 we need to make a clear decision on what will happen if data is hidden for a user.
When the developer should use shadowfields and where they should use hidden on the component. Introducing yet another hidden/remove param seems like a bad idea.


⚠ Bofrost.lu has degraded performance

In 8a86d2c, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2132 ms

Resolved: Bofrost.lu performance has improved in 4cec7b3 after 13 minutes.


Is it ud?

Have I change sth or just use it safety?
And one question. Is the author polish?

Yes he is Polish I believe.
You should change stuff to make it UD, eventho I think this is UD anyways

Probably undetected by VAC.
And yes, I am Polish.


test: placate Clang's --Wbitwise-instead-of-logical

Back port to 3.0 because it fixes an error in test-test.
test: placate Clang's --Wbitwise-instead-of-logical
test/test_test.c:58:9: note: cast one or both operands to int to silence this warning
test/test_test.c:58:9: error: use of bitwise '|' with boolean operands [-Werror,-Wbitwise-instead-of-logical]
    if (!TEST(1, TEST_uint_eq(3u, 3u))
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
test/test_test.c:58:9: note: cast one or both operands to int to silence this warning

Originally the fix for #18639
Fixes #19024

[ ] documentation is added or updated
[x] tests are added or updated

This pull request is ready to merge

Merged to 3.0 branch. Thank you.


packaging: correctly select flavor when initializing with a remote

See: http://tracker.ceph.com/issues/13030
Signed-off-by: Andrew Schoen<EMAIL_ADDRESS>

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/teuthology-pull-requests/1847/
Test PASSed.


Recipe for locking initial state attribute ?

I need to lock initial state attribute so that other developers are unable to overwrite it. How could i do that?
Lets say i have state like this:
defaultState = {
  isLoading: false,
  data: undefined,
  actions: {
    getData: ()
  }
}

Im using immer middleware and modified redux middleware that binds dispatch to every action on initialization .
When other devs want to reset state then they will do something like this:
case 'RESET':
  return defaultState;

But now dispatch is not bind to actions anymore
Locking is probably impossible? But can someone give me an hint how to write middleware or edit redux or immer middleware to check if 'actions' belongs to modified set attributes so i could bind dispatch again ?
Edit: Can close this issue. Solution was just not to keep actions in state.
const [useStore, actions ] = ....

Yeah I can close this. I'm glad you found a solution.


Added stock name to success response

Added stock name on a successfull response as it's an easy implementation and quite nice to have in a stock api.

hi, thanks for your PR. I think because both of these blocks look similar, should we create a function so the codebase doesn't get duplicated too much? Thank you

Moved the name tidying code to a function named getTidyName in the same class

LGTM! Thanks for your PR

@all-contributors please add @twhtanghk for code

@all-contributors please add @shykeiichi for code

my bad lol


fix #8414 follow poetry source constraint

Context

fix #8414

Package source constraints are strongly suggested for all packages that are expected to be provided only by one specific source to avoid dependency confusion attacks.

https://python-poetry.org/docs/repositories/#package-source-constraint
Summary

Update the index_finder.rb script to ensure that if a dependency has a package source configuration in pyproject.toml, it won't utilize any other sources as its :main source.
Please note that the behavior may not completely align with Poetry's behavior.

For example, if a package points to a source that is not defined in pyproject.toml, Poetry will raise an exception, but Dependabot will continue to check the default source.
Should we consider aligning dependabot behavior with Poetry's in this regard?

User-facing changes

dependabot bot won't check default source if a package defined its source correctly.

Testing Instructions
[dependabot-core-dev] ~ $ ./bin/dry-run.rb pip lucemia/dependabot-source-constraint --cache=files
Before modification

dependabot will check https://pypi.org/simple/requests/

=> reading cloned repo from /home/dependabot/tmp/lucemia/dependabot-source-constraint
=> parsing dependency files
=> updating 1 dependencies: requests

=== requests ()
 => checking for updates 1/1
🌍 --> GET https://pypi.org/simple/requests/
🌍 <-- 200 https://pypi.org/simple/requests/
🌍 --> GET https://some.internal.registry.com/pypi/requests/
 => handled error whilst updating requests: private_source_timed_out {:source=>"https://some.internal.registry.com/pypi/"}
🌍 Total requests made: '2'
🎈 Ecosystem Versions log: {:languages=>{:python=>{"raw"=>"^3.7", "max"=>"3.11"}}}

After modification

dependabot won't check https://pypi.org/simple/requests/

=> reading cloned repo from /home/dependabot/tmp/lucemia/dependabot-source-constraint
=> parsing dependency files
=> updating 1 dependencies: requests

=== requests ()
 => checking for updates 1/1
🌍 --> GET https://some.internal.registry.com/pypi/requests/
 => handled error whilst updating requests: private_source_timed_out {:source=>"https://some.internal.registry.com/pypi/"}
🌍 Total requests made: '1'
🎈 Ecosystem Versions log: {:languages=>{:python=>{"raw"=>"^3.7", "max"=>"3.11"}}}

Regarding your question, yes, it makes to me to align with poetry. If poetry fails to run that kind of project, since we run poetry ourselves, we're already running into an unknown error anyways. So it makes sense to raise a proper user error instead. Maybe DependencyFileNotEvaluatable or MisconfiguredTool error.

Regarding your question, yes, it makes to me to align with poetry. If poetry fails to run that kind of project, since we run poetry ourselves, we're already running into an unknown error anyways. So it makes sense to raise a proper user error instead. Maybe DependencyFileNotEvaluatable or MisconfiguredTool error.

I've squashed the commits, and I think the PR may be also to merged first.
To align with Poetry, it will require more time as I want to clarify Poetry's behavior. I have raised an issue there to discuss further: https://github.com/python-poetry/poetry/issues/8704."

Thank you! Yes, I will merge this PR independently of any other improvements. Hopefully next week!

Thanks for the improvement @lucemia, it's now merged and deployed 🎉


Create branch to resolve test cases

fixing and additions of testcases looks good, will merge once last 2 test cases are resolved

fixing and additions of testcases looks good, will merge once last 2 test cases are resolved

also merge conflicts should be settled, im not as familiar with what needs to be added so leaving this to @yezkez10 to do

Merged to continue fixing test cases from @yezkez10


htop added

htop was missing from the brew.sh

Thanks, but I personally don’t use htop often enough to warrant adding it to my brew.sh.


Как добавить кириллицу?

Ask your question
Как добавить кириллицу?
Как получить из '#imports'  объект jsPDF?
Additional information
No response

I also want to know know how could we create pdf not only latin but also in cyrillic language?

Hi everyone, please check out #10 for more information on to to:

Currently do this
My plan to improve DX in the future to make this even easier!


maximumRateDescription not Displaying

maximumRateDescription for the survey is not displaying correctly. The issue is evident on the example page as well.
http://surveyjs.org/examples/react/real-productfeedback.html
Note that for the "satisfied" question, the minimumRateDescription shows, but the maximumRateDescription does not show.

@AndehWong this is bug. Thank you for reporting it!

@AndehWong it is fixed in master branch

Awesome, thanks a lot!


implement module release command

Implement the inmanta module release command with the following semantics:

without arguments, it expects a dev version x.y.z.devx and converts it to a stable version x.y.z. It commits, adds a release tag, then calls inmanta module release --dev --patch (described below).
with the --dev argument it converts the current version to a dev version. It optionally accepts --patch, --minor or --major, defaulting to --patch. The command results in a dev version that is at least the requested bump ahead of the last version tag. The changelog should be updated accordingly (either add a new section or rename the current one depending on the type of bump that was done). The command should commit the changes.

Similar logic for dev bumping with respect to a bump specifier and the latest tag is currently implemented in irt.release.release, which might be of use.
Make sure to take the following into account:

It should be compatible with both v1 and v2 modules. In particular, v1 modules have tags directly in the version field while v2 modules have it in the egg_info.tag_version field in setup.cfg. The metadata objects in inmanta.module likely already contain all abstractions to interact with tagged versions for both module generations.
It should not break for modules that have never been released yet (have no last version tag)

I also think dev versions should not get a git tag?

I'll add that explicitly.


Discount amount with actual amount on cart summery.

Issue Reference
#6378

@jitendra-webkul
As we discuss, the issue is invalid for which @papnoisanjeev  create this PR, so I am closing this PR.


Can't compile with GCC 8.4.0

Using Hyperbola GNU/Linux-Libre
the testing version
followed the commands after downloading and unzipping the master:
cmake -G"Unix Makefiles" -Bbuild .
then
cmake  --build build -j2
and this happens:
[  1%] Generating src/generated/ntsc-final/lang/ame.h
Traceback (most recent call last):
File "/home/user/perfect_dark-port/tools/assetmgr/mklang", line 3, in
import assetmgr
File "/home/user/perfect_dark-port/tools/assetmgr/assetmgr.py", line 163, in
os.environ['ROMID'] = arg.removeprefix('--romid=')
AttributeError: 'str' object has no attribute 'removeprefix'
make[2]: *** [CMakeFiles/pd_headers.dir/build.make:267: src/generated/ntsc-final/lang/ame.h] Error 1
make[1]: *** [CMakeFiles/Makefile2:85: CMakeFiles/pd_headers.dir/all] Error 2
make: *** [Makefile:91: all] Error 2

Looks like you don't have Python 3.9. I changed the script in question, so it should work with lower versions now.

Looks like you don't have Python 3.9. I changed the script in question, so it should work with lower versions now.

Ran into other problem
/home/user/perfect_dark/port/src/preprocess/filemodel.c: In function ‘populateMarkers’:
/home/user/perfect_dark/port/src/preprocess/filemodel.c:266:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modeldef *src_modeldef = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:267:4: error: expected expression before ‘int’
int num_texconfigs = PD_BE16(src_modeldef->numtexconfigs);
^~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:272:24: error: ‘num_texconfigs’ undeclared (first use in this function); did you mean ‘texconfigpos’?
for (int i = 0; i < num_texconfigs; i++) {
^~~~~~~~~~~~~~
texconfigpos
/home/user/perfect_dark/port/src/preprocess/filemodel.c:272:24: note: each undeclared identifier is reported only once for each function it appears in
/home/user/perfect_dark/port/src/preprocess/filemodel.c:277:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelnode *src_node = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:278:4: error: expected expression before ‘u32’
u32 node_type = PD_BE16(src_node->type) & 0xff;
^~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:279:67: error: ‘node_type’ undeclared (first use in this function); did you mean ‘hovtype’?
setMarker(PD_BE32(src_node->ptr_rodata), nodeTypeToContentType[node_type], marker->src_offset);
^~~~~~~~~
hovtype
/home/user/perfect_dark/port/src/preprocess/filemodel.c:286:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_textureconfig *src_texconfig = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:292:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modeldef *src_modeldef2 = (struct n64_modeldef *) src;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:293:4: error: expected expression before ‘u32’
u32 *src_parts = (u32 *) src_thing;
^~~
In file included from /home/user/perfect_dark/include/PR/R4300.h:25,
from /home/user/perfect_dark/include/PR/rcp.h:27,
from /home/user/perfect_dark/include/ultra64.h:26,
from /home/user/perfect_dark/src/include/types.h:3,
from /home/user/perfect_dark/port/src/preprocess/filemodel.c:5:
/home/user/perfect_dark/port/src/preprocess/filemodel.c:297:23: error: ‘src_parts’ undeclared (first use in this function); did you mean ‘num_parts’?
setMarker(PD_BE32(src_parts[i]), CT_NODE, marker->src_offset);
^~~~~~~~~
/home/user/perfect_dark/src/include/platform.h:52:42: note: in definition of macro ‘PD_BSWAP32’
#define PD_BSWAP32(x) __builtin_bswap32(x)
^
/home/user/perfect_dark/port/src/preprocess/filemodel.c:297:15: note: in expansion of macro ‘PD_BE32’
setMarker(PD_BE32(src_parts[i]), CT_NODE, marker->src_offset);
^~~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:305:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_gundl *src_gundl = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:311:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_distance *src_dist = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:315:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_reorder *src_reorder = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:320:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_chrgunfire *src_chrgunfire = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:324:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_toggle *src_toggle = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:328:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_stargunfire *src_stargunfire = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:341:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_dl *src_dl = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c: In function ‘convertContent’:
/home/user/perfect_dark/port/src/preprocess/filemodel.c:400:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modeldef *src_modeldef = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:401:4: error: expected expression before ‘struct’
struct modeldef *dst_modeldef = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:402:4: error: ‘dst_modeldef’ undeclared (first use in this function); did you mean ‘src_modeldef’?
dst_modeldef->skel = (void *)(uintptr_t)PD_BE32(src_modeldef->ptr_skel);
^~~~~~~~~~~~
src_modeldef
/home/user/perfect_dark/port/src/preprocess/filemodel.c:411:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelnode *src_node = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:412:4: error: expected expression before ‘struct’
struct modelnode *dst_node = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:413:4: error: ‘dst_node’ undeclared (first use in this function); did you mean ‘src_node’?
dst_node->type = PD_BE16(src_node->type);
^~~~~~~~
src_node
/home/user/perfect_dark/port/src/preprocess/filemodel.c:417:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_textureconfig *src_texconfig = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:418:4: error: expected expression before ‘struct’
struct textureconfig *dst_texconfig = dst_thing;
^~~~~~
[ 37%] Building C object CMakeFiles/pd.dir/port/src/preprocess/segfonts.c.o
[ 37%] Building C object CMakeFiles/pd.dir/port/src/romdata.c.o
/home/user/perfect_dark/port/src/preprocess/filemodel.c:422:6: error: ‘dst_texconfig’ undeclared (first use in this function); did you mean ‘src_texconfig’?
dst_texconfig->textureptr = (void *)(uintptr_t)PD_BE32(src_texconfig->ptr);
^~~~~~~~~~~~~
src_texconfig
/home/user/perfect_dark/port/src/preprocess/filemodel.c:445:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modeldef *src_modeldef2 = (struct n64_modeldef *) src;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:446:4: error: expected expression before ‘u32’
u32 *src_parts = (u32 *) src_thing;
^~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:449:29: error: ‘src_parts’ undeclared (first use in this function); did you mean ‘num_parts’?
u16 *src_nums = (u16 *) &src_parts[num_parts];
^~~~~~~~~
num_parts
/home/user/perfect_dark/port/src/preprocess/filemodel.c:466:4: error: a label can only be part of a statement and a declaration is not a statement
struct marker *parent = findMarker(marker->parent_src_offset);
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:467:4: error: expected expression before ‘u32’
u32 src_vtx;
^~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:473:5: error: ‘src_vtx’ undeclared (first use in this function); did you mean ‘dst_vtx’?
src_vtx = PD_BE32(src_rodata->ptr_vertices) & 0x00ffffff;
^~~~~~~
dst_vtx
/home/user/perfect_dark/port/src/preprocess/filemodel.c:490:4: error: a label can only be part of a statement and a declaration is not a statement
struct modelrodata_chrinfo *src_chrinfo = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:491:4: error: expected expression before ‘struct’
struct modelrodata_chrinfo *dst_chrinfo = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:492:4: error: ‘dst_chrinfo’ undeclared (first use in this function); did you mean ‘src_chrinfo’?
dst_chrinfo->animpart = PD_BE16(src_chrinfo->animpart);
^~~~~~~~~~~
src_chrinfo
/home/user/perfect_dark/port/src/preprocess/filemodel.c:499:4: error: a label can only be part of a statement and a declaration is not a statement
struct modelrodata_position *src_position = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:500:4: error: expected expression before ‘struct’
struct modelrodata_position *dst_position = dst_thing;
^~~~~~
[ 37%] Building C object CMakeFiles/pd.dir/port/src/system.c.o
/home/user/perfect_dark/port/src/preprocess/filemodel.c:501:4: error: ‘dst_position’ undeclared (first use in this function); did you mean ‘src_position’?
dst_position->pos = PD_SWAPPED_VAL(src_position->pos);
^~~~~~~~~~~~
src_position
/home/user/perfect_dark/port/src/preprocess/filemodel.c:510:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_gundl *src_gundl = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:511:4: error: expected expression before ‘struct’
struct modelrodata_gundl *dst_gundl = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:512:4: error: ‘dst_gundl’ undeclared (first use in this function); did you mean ‘src_gundl’?
dst_gundl->vertices = NULL;
^~~~~~~~~
src_gundl
/home/user/perfect_dark/port/src/preprocess/filemodel.c:518:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_distance *src_dist = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:519:4: error: expected expression before ‘struct’
struct modelrodata_distance *dst_dist = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:520:4: error: ‘dst_dist’ undeclared (first use in this function); did you mean ‘src_dist’?
dst_dist->near = PD_SWAPPED_VAL(src_dist->near);
^~~~~~~~
src_dist
/home/user/perfect_dark/port/src/preprocess/filemodel.c:526:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_reorder *src_reorder = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:527:4: error: expected expression before ‘struct’
struct modelrodata_reorder *dst_reorder = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:528:4: error: ‘dst_reorder’ undeclared (first use in this function); did you mean ‘src_reorder’?
dst_reorder->unk00 = PD_SWAPPED_VAL(src_reorder->unk00);
^~~~~~~~~~~
src_reorder
/home/user/perfect_dark/port/src/preprocess/filemodel.c:539:4: error: a label can only be part of a statement and a declaration is not a statement
struct modelrodata_bbox *src_bbox = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:540:4: error: expected expression before ‘struct’
struct modelrodata_bbox *dst_bbox = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:541:4: error: ‘dst_bbox’ undeclared (first use in this function); did you mean ‘src_bbox’?
dst_bbox->hitpart = PD_BE32(src_bbox->hitpart);
^~~~~~~~
src_bbox
/home/user/perfect_dark/port/src/preprocess/filemodel.c:551:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_chrgunfire *src_chrgunfire = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:552:4: error: expected expression before ‘struct’
struct modelrodata_chrgunfire *dst_chrgunfire = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:553:4: error: ‘dst_chrgunfire’ undeclared (first use in this function); did you mean ‘src_chrgunfire’?
dst_chrgunfire->pos = PD_SWAPPED_VAL(src_chrgunfire->pos);
^~~~~~~~~~~~~~
src_chrgunfire
/home/user/perfect_dark/port/src/preprocess/filemodel.c:561:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_type11 *src_type11 = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:562:4: error: expected expression before ‘struct’
struct modelrodata_type11 *dst_type11 = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:563:4: error: ‘dst_type11’ undeclared (first use in this function); did you mean ‘src_type11’?
dst_type11->unk00 = PD_BE32(src_type11->unk00);
^~~~~~~~~~
src_type11
/home/user/perfect_dark/port/src/preprocess/filemodel.c:574:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_toggle *src_toggle = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:575:4: error: expected expression before ‘struct’
struct modelrodata_toggle *dst_toggle = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:576:4: error: ‘dst_toggle’ undeclared (first use in this function); did you mean ‘src_toggle’?
dst_toggle->rwdataindex = PD_BE16(src_toggle->rwdataindex);
^~~~~~~~~~
src_toggle
/home/user/perfect_dark/port/src/preprocess/filemodel.c:580:4: error: a label can only be part of a statement and a declaration is not a statement
struct modelrodata_positionheld *src_posheld = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:581:4: error: expected expression before ‘struct’
struct modelrodata_positionheld *dst_posheld = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:582:4: error: ‘dst_posheld’ undeclared (first use in this function); did you mean ‘src_posheld’?
dst_posheld->pos = PD_SWAPPED_VAL(src_posheld->pos);
^~~~~~~~~~~
src_posheld
/home/user/perfect_dark/port/src/preprocess/filemodel.c:588:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_stargunfire *src_stargunfire = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:589:4: error: expected expression before ‘struct’
struct modelrodata_stargunfire *dst_stargunfire = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:590:4: error: ‘dst_stargunfire’ undeclared (first use in this function); did you mean ‘src_stargunfire’?
dst_stargunfire->unk00 = PD_BE32(src_stargunfire->unk00);
^~~~~~~~~~~~~~~
src_stargunfire
/home/user/perfect_dark/port/src/preprocess/filemodel.c:594:4: error: a label can only be part of a statement and a declaration is not a statement
struct modelrodata_headspot *src_headspot = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:595:4: error: expected expression before ‘struct’
struct modelrodata_headspot *dst_headspot = dst_thing;
^~~~~~
[ 37%] Building C object CMakeFiles/pd.dir/port/src/utils.c.o
/home/user/perfect_dark/port/src/preprocess/filemodel.c:596:4: error: ‘dst_headspot’ undeclared (first use in this function); did you mean ‘src_headspot’?
dst_headspot->rwdataindex = PD_BE16(src_headspot->rwdataindex);
^~~~~~~~~~~~
src_headspot
/home/user/perfect_dark/port/src/preprocess/filemodel.c:600:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_dl *src_dl = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:601:4: error: expected expression before ‘struct’
struct modelrodata_dl *dst_dl = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:602:4: error: ‘dst_dl’ undeclared (first use in this function); did you mean ‘src_dl’?
dst_dl->numvertices = PD_BE16(src_dl->numvertices);
^~~~~~
src_dl
/home/user/perfect_dark/port/src/preprocess/filemodel.c:609:4: error: a label can only be part of a statement and a declaration is not a statement
struct modelrodata_type19 *src_type19 = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:610:4: error: expected expression before ‘struct’
struct modelrodata_type19 *dst_type19 = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:615:4: error: ‘dst_type19’ undeclared (first use in this function); did you mean ‘src_type19’?
dst_type19->numvertices = (num_vertices);
^~~~~~~~~~
src_type19
/home/user/perfect_dark/port/src/preprocess/filemodel.c: In function ‘relinkPointers’:
/home/user/perfect_dark/port/src/preprocess/filemodel.c:658:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modeldef *src_modeldef = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:659:4: error: expected expression before ‘struct’
struct modeldef *dst_modeldef = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:660:4: error: ‘dst_modeldef’ undeclared (first use in this function); did you mean ‘src_modeldef’?
dst_modeldef->rootnode = (void *)(uintptr_t)resolvePointer(PD_BE32(src_modeldef->ptr_rootnode));
^~~~~~~~~~~~
src_modeldef
/home/user/perfect_dark/port/src/preprocess/filemodel.c:665:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelnode *src_node = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:666:4: error: expected expression before ‘struct’
struct modelnode *dst_node = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:667:4: error: ‘dst_node’ undeclared (first use in this function); did you mean ‘src_node’?
dst_node->rodata = (void *)(uintptr_t)resolvePointer(PD_BE32(src_node->ptr_rodata));
^~~~~~~~
src_node
/home/user/perfect_dark/port/src/preprocess/filemodel.c:676:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_textureconfig *src_texconfig = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:677:4: error: expected expression before ‘struct’
struct textureconfig *dst_texconfig = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:679:5: error: ‘dst_texconfig’ undeclared (first use in this function); did you mean ‘src_texconfig’?
dst_texconfig->textureptr = (void *)(uintptr_t)resolvePointer(PD_BE32(src_texconfig->ptr));
^~~~~~~~~~~~~
src_texconfig
/home/user/perfect_dark/port/src/preprocess/filemodel.c:684:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modeldef *src_modeldef2 = (struct n64_modeldef *) src;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:685:4: error: expected expression before ‘u32’
u32 *src_parts = (u32 *) src_thing;
^~~
In file included from /home/user/perfect_dark/include/PR/R4300.h:25,
from /home/user/perfect_dark/include/PR/rcp.h:27,
from /home/user/perfect_dark/include/ultra64.h:26,
from /home/user/perfect_dark/src/include/types.h:3,
from /home/user/perfect_dark/port/src/preprocess/filemodel.c:5:
/home/user/perfect_dark/port/src/preprocess/filemodel.c:690:44: error: ‘src_parts’ undeclared (first use in this function); did you mean ‘num_parts’?
dst_parts[i] = (resolvePointer(PD_BE32(src_parts[i])));
^~~~~~~~~
/home/user/perfect_dark/src/include/platform.h:52:42: note: in definition of macro ‘PD_BSWAP32’
#define PD_BSWAP32(x) __builtin_bswap32(x)
^
/home/user/perfect_dark/port/src/preprocess/filemodel.c:690:36: note: in expansion of macro ‘PD_BE32’
dst_parts[i] = (resolvePointer(PD_BE32(src_parts[i])));
^~~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:698:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_gundl *src_gundl = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:699:4: error: expected expression before ‘struct’
struct modelrodata_gundl *dst_gundl = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:700:4: error: ‘dst_gundl’ undeclared (first use in this function); did you mean ‘src_gundl’?
dst_gundl->opagdl = (void *)(uintptr_t)resolvePointer(PD_BE32(src_gundl->ptr_opagdl));
^~~~~~~~~
src_gundl
/home/user/perfect_dark/port/src/preprocess/filemodel.c:718:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_distance *src_dist = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:719:4: error: expected expression before ‘struct’
struct modelrodata_distance *dst_dist = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:720:4: error: ‘dst_dist’ undeclared (first use in this function); did you mean ‘src_dist’?
dst_dist->target = (void *)(uintptr_t)resolvePointer(PD_BE32(src_dist->ptr_target));
^~~~~~~~
src_dist
/home/user/perfect_dark/port/src/preprocess/filemodel.c:723:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_reorder *src_reorder = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:724:4: error: expected expression before ‘struct’
struct modelrodata_reorder *dst_reorder = dst_thing;
^~~~~~
[ 38%] Building C object CMakeFiles/pd.dir/port/src/video.c.o
/home/user/perfect_dark/port/src/preprocess/filemodel.c:725:4: error: ‘dst_reorder’ undeclared (first use in this function); did you mean ‘src_reorder’?
dst_reorder->unk18 = (void *)(uintptr_t)resolvePointer(PD_BE32(src_reorder->ptr_node_unk18));
^~~~~~~~~~~
src_reorder
/home/user/perfect_dark/port/src/preprocess/filemodel.c:729:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_chrgunfire *src_chrgunfire = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:730:4: error: expected expression before ‘struct’
struct modelrodata_chrgunfire *dst_chrgunfire = dst_thing;
^~~~~~
[ 38%] Building CXX object CMakeFiles/pd.dir/port/fast3d/gfx_cc.cpp.o
/home/user/perfect_dark/port/src/preprocess/filemodel.c:731:4: error: ‘dst_chrgunfire’ undeclared (first use in this function); did you mean ‘src_chrgunfire’?
dst_chrgunfire->texture = (void *)(uintptr_t)resolvePointer(PD_BE32(src_chrgunfire->ptr_texture));
^~~~~~~~~~~~~~
src_chrgunfire
/home/user/perfect_dark/port/src/preprocess/filemodel.c:737:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_toggle *src_toggle = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:738:4: error: expected expression before ‘struct’
struct modelrodata_toggle *dst_toggle = dst_thing;
^~~~~~
In file included from /home/user/perfect_dark/port/fast3d/gfx_cc.cpp:1:
/home/user/perfect_dark/port/fast3d/gfx_cc.h:8:10: fatal error: compare: No such file or directory
#include
^~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/pd.dir/build.make:3674: CMakeFiles/pd.dir/port/fast3d/gfx_cc.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/home/user/perfect_dark/port/src/preprocess/filemodel.c:739:4: error: ‘dst_toggle’ undeclared (first use in this function); did you mean ‘src_toggle’?
dst_toggle->target = (void *)(uintptr_t)resolvePointer(PD_BE32(src_toggle->ptr_target));
^~~~~~~~~~
src_toggle
/home/user/perfect_dark/port/src/preprocess/filemodel.c:742:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_stargunfire *src_stargunfire = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:743:4: error: expected expression before ‘struct’
struct modelrodata_stargunfire *dst_stargunfire = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:744:4: error: ‘dst_stargunfire’ undeclared (first use in this function); did you mean ‘src_stargunfire’?
dst_stargunfire->vertices = (void *)(uintptr_t)resolvePointer(PD_BE32(src_stargunfire->ptr_vertices));
^~~~~~~~~~~~~~~
src_stargunfire
/home/user/perfect_dark/port/src/preprocess/filemodel.c:757:4: error: a label can only be part of a statement and a declaration is not a statement
struct n64_modelrodata_dl *src_dl = src_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:758:4: error: expected expression before ‘struct’
struct modelrodata_dl *dst_dl = dst_thing;
^~~~~~
/home/user/perfect_dark/port/src/preprocess/filemodel.c:759:4: error: ‘dst_dl’ undeclared (first use in this function); did you mean ‘src_dl’?
dst_dl->opagdl = (void *)(uintptr_t)resolvePointer(PD_BE32(src_dl->ptr_opagdl));
^~~~~~
src_dl
make[2]: *** [CMakeFiles/pd.dir/build.make:3506: CMakeFiles/pd.dir/port/src/preprocess/filemodel.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:111: CMakeFiles/pd.dir/all] Error 2
make: *** [Makefile:91: all] Error 2

What version of gcc do you have? Use gcc -v to check. This is also not the full log.

What version of gcc do you have? Use gcc -v to check. This is also not the full log.

It actually broke at 78%
I tried  to do the command again and it stopped at 38% this time.
I have 8.4.0 version.

That's pretty old. The game requires a couple C++20 features, which have only started appearing in 8. I committed a change that might at least partially fix this. Can you try again?

Yeah you don't have <compare>. Means your compiler is too old.

Yeah you don't have <compare>. Means your compiler is too old.

My bad, I guess will have to wait for the devs of my os to fix this problem.
I  assume its too much trouble, hence I say this. Let me know if this is indeed correct.

This is unfortunately not easily fixable. You could maybe build gcc9 or 10 yourself from source, though that's kind of time consuming and I probably can't help you with it.

This is unfortunately not easily fixable. You could maybe build gcc9 or 10 yourself from source, though that's kind of time consuming and I probably can't help you with it.

No problem, you tried. Do you think you can support clang though if nothing else?

No problem, you tried. Do you think you can support clang though if nothing else?

I plan to. What version do you have available?

No problem, you tried. Do you think you can support clang though if nothing else?

I plan to. What version do you have available?

Got 11 actually, is that a problem or no.

I don't know. I think one thing that the code uses might've only been added in 14, but I'm not sure. We'll see when someone gets around to build it for OSX or something.

I don't know. I think one thing that the code uses might've only been added in 14, but I'm not sure. We'll see when someone gets around to build it for OSX or something.

Ill see if I can build clang 14 or newer then. I have to update my cmake first tho

You should probably close this, if you don't have a path forward for this. I don't wish to waste your time with this.
I am wondering if this installs on any BSDs without the linux compatibility layer tho


Add source files and .gitignore

i added the .gitignore file.

closes #28
Fixes  medsuet/Xcelerium-IC-Design-Training#28

Added first 5 assembly tasks

Added Booth.py and Non_restoring.py

Tasks upto Sequential Multiplier


Add Parametric Soft Exponential Unit (PSEU) activation layer

- What I did
See above
- How I did it
- How you can verify it
I added unit tests

This pull request fixes #issue_number_here

@gabrieldemarmiesse I have added the Parametric Soft Exponential Unit (PSEU) activation layer. Here is the research paper on arXiv. The build is passing now. Do you know someone who can review this ?

@SriRangaTarun We're currently focused on getting the design of this repo right to have a v1.0. So there might be delays to reviews PRs which add new features.

@SriRangaTarun Thanks for the contribution! I've left some comments. Also, as soon as https://github.com/keras-team/keras-contrib/pull/441 gets merged, you can rebase on it and add yourself as the code owner for this feature. Nice work!

@RaphaelMeudec I have made all the changes you suggested and the CI build is still passing.

@gabrieldemarmiesse PR looks good to me. You might want to add @SriRangaTarun in your current codeowner PR?

@RaphaelMeudec and @gabrieldemarmiesse Everything is working fine. I have added important parameters and handled all possible input cases. But, since the codeowners PR has been merged, it is failing the codeowners test.

@RaphaelMeudec and @gabrieldemarmiesse Today I tried to add initializer and trainable options, instead of only having a constant alpha initializer. But, I removed them because they cause numerical instability in the function (it is a piecewise function in alpha, so it becomes unstable when the negative formula is used for positive alpha weights and the other way round). A custom initializer or trainability can cause the signs of the weights to mismatch the function and result in NaNs.  So, I am sticking to constant initial alpha weights which can not be trained.

@RaphaelMeudec and @gabrieldemarmiesse Everything seems to work fine. But, ever since the codeowners PR has been merged, it is failing the codeowners test.

@RaphaelMeudec and @gabrieldemarmiesse Today I tried to add initializer and trainable options, instead of only having a constant alpha initializer. But, I removed them because they cause numerical instability in the function (it is a piecewise function in alpha, so it becomes unstable when the negative formula is used for positive alpha weights and the other way round). A custom initializer or trainability can cause the signs of the weights to mismatch the function and result in NaNs. So, I am sticking to constant initial alpha weights which can not be trained.

@RaphaelMeudec and @gabrieldemarmiesse Today I tried to add initializer and trainable options, instead of only having a constant alpha initializer. But, I removed them because they cause numerical instability in the function (it is a piecewise function in alpha, so it becomes unstable when the negative formula is used for positive alpha weights and the other way round). A custom initializer or trainability can cause the signs of the weights to mismatch the function and result in NaNs. So, I am sticking to constant initial alpha weights which can not be trained.

Now the build is passing after adding pseu.py to CODEOWNERS.

@RaphaelMeudec and @gabrieldemarmiesse Today I tried to add initializer and trainable options, instead of only having a constant alpha initializer. But, I removed them and reverted to the previous version because they cause numerical instability in the function (it is a piecewise function in alpha, so it becomes unstable when the negative formula is used for positive alpha weights and the other way round). A custom initializer or trainability can cause the signs of the weights to mismatch the function and result in NaNs. So, I am sticking to constant initial alpha weights which can not be trained.

@RaphaelMeudec Do you suggest any other changes ?

@RaphaelMeudec Do you suggest any other changes ? The most recent build failed because the instancenormalization test suddenly failed for some reason.

@SriRangaTarun All good, nothing to add IMO!
@gabrieldemarmiesse Failing test doesn't seem linked to this PR, code looks good to me!

Somehow, the build is passing now.

@gabrieldemarmiesse I think we can merge this!

We'll merge this after I merge the tf.keras PR. It's getting quite painful to resolve conflicts every two days.

@SriRangaTarun Please merge master into your branches to make sure that it's compatible with tf.keras

@RaphaelMeudec and @gabrieldemarmiesse I am closing this PR and have created an alias here. There, I have merged master into my branch.
Any other changes ?


add DQN example

Related to #5

Hello,
Could you make this into a pure python script instead of a notebook (consistently with the other example)? Also could you name the new file simple_dqn.py and rename catch.py to online_qlearning.py?

Also, please update in README.md the requirements listed under Installation where it says In order to run the examples/...

Thank you very much for the contribution,
we will merge the PR internally and push a commit with you as author.


Update to upstream version 0.1.5

Also add zip dependency as suggested by conda skeleton cran, see also
https://github.com/conda/conda-build/pull/3030
Checklist

[*] Used a fork of the feedstock to propose changes
[*] Reset the build number to 0 (if the version changed)
[*] Re-rendered with the latest conda-smithy
[*] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


combine order: bug?

combine returns values in the order of how widgets are displayed, while following the definition order would probably be more sensible:
@bind tmp PlutoUI.combine() do Child
	w1 = Child(Slider(0:10))
	w2 = Child(Scrubbable(5))
	@htl("$w1 $w2")
end

# tmp == (0, 5): slider is first, scrubbable is second

@bind tmp PlutoUI.combine() do Child
	w1 = Child(Slider(0:10))
	w2 = Child(Scrubbable(5))
	@htl("$w2 $w1")  # only changed order here
end

# tmp == (5, 0): scrubbable is first, slider is second
# I didn't expect that order changes

I would say that it's by design just to have a simple API. Otherwise, we would track both orders and union them (and track duplicates).
But in your case, it sounds like you should specify a name for each child, so that you get a named tuple. I added this option so that you don't have to depend on rendering order.
For your matrix case, also check out the CSS flex styling options to change between grid orders.


merge package from arlac77/npm-package-template-esm-only

README.md

docs(README): update from template

Codecov Report

Merging #485 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #485   +/-   ##
=======================================
  Coverage   74.36%   74.36%
=======================================
  Files           2        2
  Lines         476      476
=======================================
  Hits          354      354
  Misses        122      122

Continue to review full report at Codecov.

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

Coverage remained the same at 71.972% when pulling e192960ada56bd1fb79b8ea0957aac97a83cd6f0 on template-sync-1 into 30c1b3eb7090378f4efcc9f5a69d29934de7289a on master.

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


NL Translation proposal

Gitea version (or commit ref): 1.4.2 & master
Operating system: All operating systems

Description
In the nl_NLl translation ther is a confusing statement.
file
gitea/options/locale/locale_nl-NL.ini
settings.update_settings=Instellingen bewerken
should be
settings.update_settings=Instellingen opslaan
Reason is that in the settings interface is already about changing settings.
The button is meant to save them, now it tells met to change them instead of save them.

Thank you for discovering this. If you'd like to contribute a fix all the translations are done on crowdin. For instructions please see: https://github.com/go-gitea/gitea/blob/master/CONTRIBUTING.md#translation

Maybe someday, i am trying to learn al the fun stuff, an again discovered something new :-)

@T100D I've just submitted a translation on your behalf.

Closing this as the translation has been submitted, and now it is just waiting for review from another translator.


Fix LineData sample generator

I missed the use of pointers and that cause the CI of #11 failed, I think.

And it inherits #10 .


Deprecate all S3 functions

Deprecates all the things in S3 and removes most of the tests in preparation for dropping the module.
Part of https://github.com/JuliaCloud/AWSTools.jl/issues/12.

bors try

bors try

Removed the docs block. Tests should pass next time.

bors try

bors r+


Introduce an API for referring to types available in a particular semantic context

Description:
type ErrorDetail1 record {|
    string cause;
    int errorCode;
|};

type MyErr error<ErrorDetail1>;

public function main() {
    MyErr myerr = error(<cursor>)
}

An error constructor requires a mandatory positional arg (error message). Currently, there is not a way to get the type descriptor of this parameter. Following is a capture of the error symbol of the above source code.

We need to capture the expected type at the cursor position in order to check for the assignability to  provide a sorted completion items list.

The more generic problem here is that there is no way in the Semantic API to refer to builtin types. e.g., referring to string, int etc. type symbols
This ability to reference these types is vital to do queries like "is T a sub type of string?". We need to come up with an API for this.

So something like the following is what I had in mind.

The main requirement is one should be able to refer to the types available in a particular semantic context in order to be able to do various analysis tasks. This came up a lot in compiler plugin development related stuff. For now, what they have done is manually verify types using name, module ID etc. Instead, they should be able to use the subtypeOf() API in TypeSymbol. To do that, they need access to the types.
A next step in this API would be to provide support for creating type symbols.

The design doc for this: https://docs.google.com/document/d/15I164NKdPX0xu40Nxiy6wL_eJg2rvG2YFtUNDdcKgZ8/edit?usp=sharing

Initial implementation is merged with https://github.com/ballerina-platform/ballerina-lang/pull/35353 . Next set of improvements is in progress.

Initial implementation is merged with #35353 . Next set of improvements are in progress.

The improvements are tracked as subtasks of #35415.
Closing this since the initial requirement was resolved by #35353.


Razor syntax highlighting not occurring for most of my .razor files

Greetings all. Running 17.5.0 Preview 3, also tried updating to preview 4 this morning. Most of my razor files do not have color coding. IE, in dark mode, all the text is white, in light mode, all the text is black.

Doesn't matter if the file has a code behind (file.razor.cs) or not
Doesn't affect all files
Started out of the blue a week or so ago with no system changes
Doesn't seem to affect "newly created" razor components, just existing ones.

Not sure where to start with this one. Screenshot attached.
I have tried resetting all settings to default as well as a full reinstall of VS2022.
This is .net core 7.0.2.
Thanks.

This is likely a duplicate of https://github.com/dotnet/razor/issues/7966. If you temporarily comment out your ValidationMessage tags do you get coloration back?

no, but strangely if I comment out all of the DevExpress components, the color comes back. I will try removing and reinstalling their stuff and report back.

It is not an issue with their components (no component should be able to break colorization, it should at worst not be recognized), it's a bug in the tooling which should be fixed by this PR (likely the DevExpress component in question use Generic Type parameters under the covers). We just got that fix into the upcoming preview release, so once that's available updating Visual Studio should resolve the issue.

Thank you! Yeah I played with commenting various parts out, and realized it was just really weird patterns that made it work. Thanks for the fix! I'll look very forward to it :D