rx: allow overwrite with --output-file= #73

first time contributing to open source - let me know if anything's off :)

Wow, nice patch! And the tests are excellent.. great job!
One thought I had, maybe we should refactor _decide_destname() and _ask_permission() a bit, to make this cleaner. The case I'm thinking about is if you use --output-file=, and the file already exists, but you don't use --accept-file, and you say "no" when asked for permission. In that case, wormhole receive will delete the old file, but won't write anything into its place, which seem less than ideal (leaving you with less than you started).
I haven't figured out the best way to do this yet, but I'm wondering if we move the already-exists/overwrite checks into _ask_permission(), to make it easier to leave the file in place if permission is not granted. The tricky part is that the "Receiving file ..." message probably shouldn't print until we're really going to receive the file (so after permission is granted), but we need the filename and sizes to be displayed before asking permission.
Let me think about this. It might be easiest to just land your patch now, and then think about cleanups, especially since the denied-permission case isn't really that common.
thanks!

@warner thanks!
for the denied-permission case, I have it only calling _remove_existing() from _decide_destname() if the --accept-file flag is present - otherwise it gets called after the permission check is successful in _ask_permission(). it's not the cleanest, cause it does the os.path.exists() check twice, but it should prevent the scenario you described - testing locally, when I use --output-file= but deny permission, the old file/dir isn't deleted
let me know if it works differently for you, or if you have ideas for a better way to handle it!

I did some manual testing.. looks like the old/new behavior is:

--output-file
--accept-file
os.path.exists
old
PR139

no
no
no
ask
ask

no
no
yes
reject
reject

no
yes
no
write
write

no
yes
yes
reject
reject

yes
no
no
ask
ask

yes
no
yes
reject
ask (1)

yes
yes
no
write
write

yes
yes
yes
reject
write

That looks great. And the "(1)" case I was wondering about does indeed leave the existing file alone if you say "no" when prompted.
In the future, we might simplify this a bit, by letting --output-file= imply --accept-file. But not today.
Landing momentarily. Thanks!

Codecov Report

Merging #139 into master will increase coverage by 0.05%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##           master     #139      +/-   ##
==========================================
+ Coverage   79.33%   79.38%   +0.05%
==========================================
  Files          26       26
  Lines        3479     3488       +9
  Branches      513      516       +3
==========================================
+ Hits         2760     2769       +9
+ Misses        619      617       -2
- Partials      100      102       +2

Impacted Files
Coverage Δ

src/wormhole/cli/cmd_receive.py
84.29% <91.66%> (+1.46%)
:white_check_mark:

src/wormhole/wormhole.py
90.51% <ø> (-0.34%)
:x:

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 20619bc...ffefb5e. Read the comment docs.


java.lang.Thread issues (not in Processing)

hi folks
In order to support some students on a project, I had to write a class extending Thread so they could run it when an event occurred (serial message).
I don't mean a Processing thread(String) but a proper Java Thread.
While in Processing the Thread.sleep(ms) function gets called and the thread sleeps, when in Sublime I get this error
Thread.pde:49:0:49:0: The function sleep(int) does not exist.

anyone else bumped into this?
I have tried import java.lang.Thread (which in Processing gives me no issue) but I get what looks like a duplicate import error:
The import java.lang.Thread conflicts with a type defined in the same file

Hope someone can shine a light on this.
here's a Class I'm using to test this behaviour
class SpeakThread extends Thread {
  public boolean isRunning;
  private int counter;
  public void stopRunning() {
    this.isRunning = false;
  }

  public void run() {
    this.isRunning = true;
    this.counter = 0;
    println("running");
    while (this.isRunning) {
      println("Sleeping...");
      try {
        counter++;
        Thread.sleep(100);
      }
      catch(Exception ie) {
        println("trouble sleeping");
      }
      if (counter > 30) {
        this.isRunning = false;
      }

      println("counter: " + counter);
    }
    println("done");
    return;
  }
}

Please post the entire contents of Thread.pde, since the error is being reported on line 49, and your snippet doesn't reflect this.

@ybakos the whole program is not relevant to the specific error, but here it is.
as I said, this works inside Processing but not in Processing Sublime
//import java.lang.Thread;
SpeakThread runningThread;
void setup() {
  runningThread = new SpeakThread();

  // thread("readKeys");
}
void draw() {
}
void checkKeys() {
  println("checkKeys");
  if (keyPressed) {
    if (key == 'q') {

      println("QQQ");
      runningThread.isRunning = false;
      ;
    }
  }
}
void keyPressed() {

  println("Key");
  if (key == 'q') {
    runningThread.isRunning = false;
  }
  if (key == 't') {
  	runningThread.start();
    //runningThread.run();
  }
}

class SpeakThread extends Thread {
  public boolean isRunning;
  private int counter;
  public void stopRunning() {
    this.isRunning = false;
  }

  public void run() {
    this.isRunning = true;
    this.counter = 0;
    println("running");
    while (this.isRunning) {
      checkKeys();
      println("Sleeping...");
      try {
        counter++;
        Thread.sleep(100);
      }
      catch(InterruptException ie) {
        println("trouble sleeping");
      }
      if (counter > 30) {
        this.isRunning = false;
      }

      println("counter: " + counter);
    }
    println("done");
    return;
  }
}

@ubidefeo Runs just fine for me in both Processing and from Sublime - assuming I fix the syntax error of InterruptException to InterruptedException.

@ybakos even after fixing that I get the same error.
Thread.pde:49:0:49:0: The function sleep(int) does not exist.

I added "Interrupt" at a later time, the compiler won't complain about it being just an Exception, thinking it would help but it didn't.
On which OS are you?
Java version?
maybe it can help me figure out why I have this issue.
I'd much rather write my processing code in ST than the Processing editor :)

@ybakos I found my issue, and I think it's relevant to everyone using Processing-Sublime
The compiler is not able to find imports/definitions for source which is not in the standard Processing documents folder.
On Mac, I keep my original Processing sketches in my Documents folder (same for Arduino), but when I use ST I tend to keep my projects in another folder.
I think the processing-java command fails to fully recognise things outside of its designated document folder (not sure why).
Now that I know I'll work in the standard sketch folder, but it would be great if a project could reside everywhere.
Thank you for your test

@ubidefeo What operating system do you use?
We have never had a problem using the Processing Sublime plugin for projects that are not in the default sketches directory.
For example, I created an empty sketch on my Desktop (MacOS), pasted your code, ran it with the sublime plugin, and do not receive any error.

I'm on Mac OS 10.12.6 (Sierra).
Java 8 (1.8.0_162)
same exact code works in Processing 3.3.6 and ST as long as the project resides in the ~/Documents/Processing folder.
If I move it anywhere else then imports fail and some classes are not found.
Not sure what to make of it.
I don't use Processing that often and never tried creating a Thread in Processing-Sublime before so it worked great for me so far.
I don't mind keeping the projects in the Documents folder now that I know, but I still wonder what causes this


Add ConfigV2 Validator

Add util to validate a ConfigProto object as valid under the V2 schema.
This util is currently not used, but it is planned to be used very soon.

PTAL

asking protobuf team to make a java release too https://github.com/protocolbuffers/protobuf/issues/5972

renamed things
PTAL

PTAL


Update to Dart 2.5.0

I'm seeing the following error when I attempt to direct traffic to the Dart 2.5 backend:
Error compiling to JavaScript:
Failed to decode request with internal error: type 'Utf8Decoder' is not a subtype of type 'StreamTransformer<Uint8List, String>' of 'streamTransformer'

Something has changed. No idea what.
/cc @devoncarew @johnpryan @RedBrogdon

Do you have a stacktrace?

We may be hitting some aspect of https://github.com/dart-lang/sdk/issues/36900.

I’m currently in transit, but the Dart 2.5 dart-services version is still provisioned on gae, just not receiving traffic.

I've spent several hours attempting to replicate this issue. Turns out, dart-services works fine locally, it works fine inside of a docker container when I change the serving endpoint to bin/server_dev.dart on both my mac laptop and on a GCE hosted debian drawfork docker host. I even rebuilt the GAE Flex image, but no.

Hmm, perhaps you're using slightly different package versions than the remote instance? You could try running pub upgrade to see if you hit the issue; or, delete thee pubspec.lock file entry from the gitignore file, commit the lock file, re-deploy, and see if the problem is solved.

Yeah, if your remote container is tied to an older package, it may not have picked up a fix for dart-lang/sdk#36900

I've started looking into this, since Brett's on Australian time and dealing with an OOO situation on top of it.

Underlying cause is a break in the rpc package. I've created a fix here, but have no idea how to land it:
https://github.com/dart-archive/rpc/pull/140

Is it worrisome that we're depending in something in dart-archive?

I tried to land an update to RPC a while back, but Mit said no. I had been moving in the direction of migrating from RPC to gRPC, but other things got in the way. I'd say the best way at this point is to vendor RPC into dart-services and dart-pad. We obviously need to migrate off of rpc.
/cc @mit-mit

Is it worrisome that we're depending in something in dart-archive?

Yes.
There are trade-offs being made here in terms of infrastructure updates vs. new feature development, though. We need to move away from the discoveryapis/rpc setup currently in use, but unforking flutter_web in the backend and getting the new playground done have so far taken precedence.
@domesticmouse Pulling rpc into the repos is an option, but it's also (at least at little) more work for what is essentially a patch job we want to replace anyway (be it with gRPC or OpenAPI). If we can make this one update to get back on track, that's likely to be a quicker way to get where we're going.

OpenAPI is not a replacement for RPC, it is a way describing the API exposed by RPC. gRPC likewise is not a clean replacement for RPC as it is less expressive and the web browser usage is still in development. In short, the current approach is hard deprecated, the new approach is still in development.

grpc-web is supported as of a few weeks ago

Sounds like the best approach is to vendor in rpc while we migrate to grpc-web


net::ERR_ACCESS_DENIED When Rendering Local HTML

Bug description:

I am trying to display a local PDF in base64. I have assigned all the correct permissions to view the document. When I try to render it I get the error net::ERR_ACCESS_DENIED. This only happens on Android.
To Reproduce:

Create a WebView
Use a path in the local system
Try to view the WebView
https://github.com/ALEEF02/Bulletin-Magazine-Mobile-App/blob/da41ff504d1ad2a5463b2d062adaa66fb54c61c2/rn-pdf-reader-js/index.js#L200
Expected behavior:

The WebView should be able to render to specified PDF in the local files
Screenshots/Videos:

Environment:

OS: Android
OS version: Unknown
react-native version: 34.0.2
react-native-webview version: 7.5.1

Alright, so I was able to find a temporary fix to the solution, seen here: https://github.com/react-native-community/react-native-webview/issues/656#issuecomment-551312436

@ALEEF02, I'm having the same issue loading a static HTML, it apparently happens when loading the file right after or during webview being de-instantiated by the runtime from a previous load.
Both your links aren't working. Would you kindly provide your workaround?
Thanks!

I fixed the links :D

Doesn't work to me
Encountered an error loading page {description: "net::ERR_ACCESS_DENIED"
name: "Screenshot_20200330-002215.png"
type: "image/png"
uri: "content://com.android.providers.media.documents/document/image%3A1318"
const handleAndroidSource = useCallback(() => {
setSource({uri: params.file.uri});
}, [params]);
<WebView
    style={styles.container}
    pagingEnabled
    javaScriptEnabled
    domStorageEnabled
    startInLoadingState={true}
    // automaticallyAdjustContentInsets={false}
    source={source}
    originWhitelist={[`*`]}
    allowFileAccess={true}
    allowFileAccessFromFileURLs={true}
    allowingReadAccessToURL={true}
    onLoad={Platform.select({
      android: onAndroidLoad,
      ios: onIOSLoad,
    })}
  />

Any solution?

I faced the same problem. It happened randomly on first load. I found that if the WebView source was initially null, then it won't happen. Hope this could provide some insight to debug the problem.
This temporary fix is not quite desirable as it would leave a blank page in the WebView's history stack.

Facing the same issue. Anyone found the solution?

Same issue with react-native 0.63.3, react-native-webview ^10.10.0, tried everything with all flags and the state.renderedOnce solution above:
<WebView
  allowFileAccess={true}
  originWhitelist={['*']}
  javaScriptEnabled={true}
  domStorageEnabled={true}
  source={this.state.renderedOnce ? {uri: this.state.cachedItemPath} : undefined}
  allowFileAccess={true}
  allowUniversalAccessFromFileURLs={true} />

I'm trying to render some html that was saved to local storage.

Here is the fix:
const [uri, setUri] = useState(null);

useEffect(() => {
  setUri('blahblah');
  return () => {
    setUri(null);
  };
}, []);

Here is the fix:
const [uri, setUri] = useState(null);

useEffect(() => {
  setUri('blahblah');
  return () => {
    setUri(null);
  };
}, []);

Solution by vgort here: https://github.com/react-native-webview/react-native-webview/issues/656#issuecomment-561067913 worked for me !
As he explained, you have to define source after webview onLoad():
const [renderedOnce, setRenderedOnce] = useState(false);

const updateSource = () => {
    setRenderedOnce(true);
 };

return(
   <WebView
       originWhitelist={['*']}
       source={renderedOnce ? {uri: localHTML} : undefined}
       style={{flex: 1}}
       allowFileAccess={true}
       allowUniversalAccessFromFileURLs={true}
       onLoad={updateSource}
   />)

Solution by vgort here: #656 (comment) worked for me ! As he explained, you have to define source after webview onLoad():
const [renderedOnce, setRenderedOnce] = useState(false);

const updateSource = () => {
    setRenderedOnce(true);
 };

return(
   <WebView
       originWhitelist={['*']}
       source={renderedOnce ? {uri: localHTML} : undefined}
       style={{flex: 1}}
       allowFileAccess={true}
       allowUniversalAccessFromFileURLs={true}
       onLoad={updateSource}
   />)

This worked for me but I agree this issue shouldn't be closed.

@alancwoo allowFileAccess={true} saved me 🙏


Switch to pixi and some directory renaming and clean-up.

Adds pixi as default dependency manager for the project.
Rename scratchpad to sandbox.
Add raw_data, processed_data, and results directories to the template. They are excluded by the .gitignore.
Rename ipa to source.
Add install.sh and source.sh for easy setup on Linux machines.
Remove example scripts and example notebooks.

Closes #16.


[WIP] Integrate intra-prediction assembly from dav1d

Notably, dav1d has mostly AVX2 low-bitdepth assembly at present.

[ ] pred_dc
[x] pred_dc_128
[ ] pred_dc_left
[ ] pred_dc_top
[ ] pred_h
[ ] pred_v
[ ] pred_paeth
[ ] pred_smooth
[ ] pred_smooth_h
[ ] pred_smooth_v
[ ] pred_cfl

Alternatively someone might help having cc-rs address this directly (I opened https://github.com/alexcrichton/cc-rs/issues/356 to see if upstream is fine with this approach).


Webstorm - Cannot resolve symbol '' after installing styled components

Environment
Environment:
  OS: macOS High Sierra 10.13.4
  Node: 8.11.1
  Yarn: 1.6.0
  npm: 5.8.0
  Watchman: 4.6.0
  WebStorm: 2018.1
  Xcode: Xcode 9.3.1 Build version 9E501
  Android Studio: 2.3 AI-162.3764568

Reproduction
yarn add styled-components

Steps to reproduce

When I install styled components, Webstorm 2018.1 fails to recognise react native imports

e.g:
Before installing styled components I can do this:

Install styled-components (you don't need to import it).
# Simply installing this will cause the auto complete in webstorm to stop working
yarn add styled-components

"Cannot resolve symbol 'Component Name'"

# Remove it and it comes back like normal with auto complete
yarn remove styled-components

Expected Behaviour
It shouldn't do this. I don't understand why it breaks the auto complete of existing libraries.

No idea. If WebStorm uses typescript typings to do its thing, it's possible that the @types/react-native dependency styled-components has doesn't list that export or something?


az storage blob move 'move' is misspelled or not recognized by the system.

https://docs.microsoft.com/en-us/cli/azure/storage/blob?view=azure-cli-latest#az_storage_blob_move
while running
$ az storage blob move --account-name $ACCOUNT --container-name $CONTAINER -s $SOURCE -d $DEST --sas-token $TOKEN

i get
'move' is misspelled or not recognized by the system.

$ az --version
azure-cli                         2.27.2

core                              2.27.2
telemetry                          1.0.6

Python location '/opt/az/bin/python3'
Extensions directory '/home/zhukov/.azure/cliextensions'

Python (Linux) 3.6.10 (default, Aug 23 2021, 03:36:00)
[GCC 9.3.0]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Please let us know how we are doing: https://aka.ms/azureclihats
and let us know if you're interested in trying out our newest features: https://aka.ms/CLIUXstudy

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

Thanks for bringing this to our attention. We are actively investigating and will get back to you soon.


Panic when trying to ask for the connections between two chains

Summary of Bug
Panic when trying to ask for the connections between two chains

Version
Hermes v1.4.1+45b5c29

Steps to Reproduce
./hermes query connections  --counterparty-chain cosmoshub-4 --chain bitcanna-1
2023-05-30T10:40:20.515009Z  INFO ThreadId(01) using default configuration from '/home/raul/.hermes/config.toml'
2023-05-30T10:40:20.515134Z  INFO ThreadId(01) running Hermes v1.4.1+45b5c29
thread 'main' panicked at 'removal index (is 36) should be < len (is 35)', crates/relayer-cli/src/commands/query/connections.rs:73:36
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Acceptance Criteria

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Detailed reproduction steps
First of all, create 3 connections between ibc-0 and ibc-1:
$ hermes create connection --a-chain ibc-0 --b-chain ibc-1
$ hermes create connection --a-chain ibc-0 --b-chain ibc-1
$ hermes create connection --a-chain ibc-0 --b-chain ibc-1

These connections are identified on ibc-0 as connection-0, connection-1 and connection-2.
Then create 3 connections between ibc-0 and ibc-2:
$ hermes create connection --a-chain ibc-0 --b-chain ibc-2
$ hermes create connection --a-chain ibc-0 --b-chain ibc-2
$ hermes create connection --a-chain ibc-0 --b-chain ibc-2

These connections are identified on ibc-0 as connection-3, connection-4 and connection-5.
Then, query all the connections on ibc-1:
$ hermes query connections --chain-id ibc-0
SUCCESS [
    ConnectionId(
        "connection-0",
    ),
    ConnectionId(
        "connection-1",
    ),
    ConnectionId(
        "connection-2",
    ),
    ConnectionId(
        "connection-3",
    ),
    ConnectionId(
        "connection-4",
    ),
    ConnectionId(
        "connection-5",
    ),
]

Then filter the connections to only include the ones who point to ibc-1:
❯ hermes query connections --chain ibc-0 --counterparty-chain ibc-1                                                                                 50% at 14:24:36
thread 'main' panicked at 'removal index (is 5) should be < len (is 4)', crates/relayer-cli/src/commands/query/connections.rs:73:36
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Let's do the same for the connections pointing to ibc-2:
$ hermes query connections --chain ibc-0 --counterparty-chain ibc-2
SUCCESS [
    ConnectionId(
        "connection-1",
    ),
    ConnectionId(
        "connection-3",
    ),
    ConnectionId(
        "connection-5",
    ),
]

While this does not crash like the command above, we see that the results are wrong.


Using model's $table property (if available) as table name in foreignIdFor methods

Hello,
I'm new at "pull requesting". I hope I'm doing things right.
Currently, the $table->foreignIdFor always uses the plural version of table part of the foreign key to determines the foreign table name. So if the name is changed in the model, the name will be wrong.
I made small changes to account for the $table property. Hope that will be helpful (it is for me).
P.S.: Since getTable() returns the plural version of the model and getForeignKey() is also based on the model, I think we could get rid of the Str::plural(...) part, but I didn't dare to.
Best regards.
Martin Boudreau

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

@taylorotwell Hello, As a Laravel user, I would really need the method foreignIdFor to use the $table property. Please, help me make the right things to help you fix this bug. The changes are not intrusive. I'm new to submitting pull request. Sorry if I do anything wrong. Thnak you very much.


Basic Melody Editor

This is the initial version of the melody editor. You should hear the notes as you select them. Pressing play will play the entire melody continuously. Pressing stop will stop the melody and clear the rest of the notes that are queued to play. The tempo input updates the tempo in the editor but does not currently update the tempo played by the simulator when the block is collapsed. The editor allows only one note to be selected per column.
There is still a lot more functionality to add and styling to do:

The gallery button will show a list of built-in melodies and populate the editor when selected (just like the sprite editor)
The grid will be updated to look like the led matrix
There will be a vertical line animation moving from left to right to indicate what note is being played
The editor will support multiple notes and instruments played at a time
The tempo parameter on the block and in the editor will be synced
May reverse the order of the notes (currently lower notes are at the top)

This is what it should look like:

Is there a particular reason that the higher notes are on the bottom and the lower notes are on the top? Should be the other way around in my opinion.

Is there a particular reason that the higher notes are on the bottom and the lower notes are on the top? Should be the other way around in my opinion.

Yea I wasn't sure. I just looked at some other melody editors and they all have the higher notes at the top. I can change it.

Could you grab the test build that travis generates (deep in the logs) and add it to the bug description?

@pelikhan that doesn't work for PRs on pxt. I'll make a build

Here's the new build: https://arcade.makecode.com/app/e2239055ecad044a720eccceae769985159211c4-332210e3db#editor

Overall, it feels that we should be reusing the svg framework built for the sprite editor in here. Lots of duplication work to get accessilibyt, keyboard navigation, etc... right.

Overall, it feels that we should be reusing the svg framework built for the sprite editor in here. Lots of duplication work to get accessilibyt, keyboard navigation, etc... right.

Yea. @riknoll mentioned he could create a shell for this and future editors based off the sprite editor, which will also keep the look and feel consistent. We can definitely bring this to the forefront to avoid unnecessary work.


Fix: Prevent UnionTransformer type ambiguity in combination with PyTorchTypeTransformer

Why are the changes needed?
@task
def foo() -> Union[list[torch.Tensor], torch.Tensor]:
    return [torch.tensor([1, 2, 3])]

@workflow
def wf():
    foo()

This example fails with:
TypeError: Failed to convert outputs of task 'wf.foo' at position 0.
Failed to convert type <class 'list'> to type typing.Union[list[torch.Tensor], torch.Tensor].
Error Message: Ambiguous choice of variant for union type.

The type transformer choice should, however, not be ambiguous.
The problem arises as follows:
Here in the UnionTransformer we test all union variants and raise the observed error if more than one of the union variants work.
In this case, the two union working variants are:

Call the ListTransformer for a list of tensors and then the PyTorchTensorTransformer for each element in the list. This is the expected behaviour and does work.
Call the PyTorchTensorTransformer for the list of tensors. This, however, works as well as torch.save([some_tensor], ...) works. This is not intended and hence causes the ambiguity.

What changes were proposed in this pull request?
We need to prevent the pytorch type transformers from serializing lists of tensors or modules since the type engine (i.e. the UnionTransformer expects these cases to be handled by the ListTransformer).
How was this patch tested?
Tested with the snippet above and added a unit test that would have caught this.

[ ] I updated the documentation accordingly.
[x] All new and existing tests passed.
[x] All commits are signed-off.

@workflow
def wf():
    foo()

Absolutely https://github.com/flyteorg/flytekit/pull/2726/commits/99df4fe20dd8b9042c876f444eba4f3f83eec6e5


The strangeness of editor themes

Godot 2.0.3
Everything on the attached image:

Duplicate of #728, I'll add your image there.


Couchbase module not compatible with Docker Hub _/couchbase image

For the latest Couchbase 6.6, we can use couchbase:communtiy and couchbase:enterprise to get the latest Couchbase, but  I tried to use this as DockerImageName, it will complain the docker name is not compatible with couchbase/server.
Check: https://hub.docker.com/_/couchbase

This should be easy to resolve - will create a PR.

Actually, while testing, I'm finding that couchbase:community-6.5.1 is not a drop-in replacement for couchbase/server:6.5.1 - startup fails with an error which I don't have the couchbase knowledge to diagnose: The value must be one of the following: [forestdb]".
Because of this, I'd say that the compatibility check is working correctly: it's designed to prevent the wrong image being used, but give the user a chance to override.
If you really do want to use the couchbase:community images, please follow the instructions in the error message and use DockerImageName.parse("couchbase:community-YOURVERSION").asCompatibleSubstituteFor("couchbase/server") as the image. This tells Testcontainers that you're declaring compatibility between the image you're using and the image that the CouchbaseContainer class was designed/tested with.
I'm not sure this community image will work though, due to the error I mentioned.
The good news is that couchbase:enterprise-* does seem to function as a drop-in replacement for couchbase/server:*. Unfortunately our compatibility checks only look at the image name, not at the tag part, so for now it will still be necessary to use `asCompatibleSubstituteFor I'm afraid.
@daschl is it expected that the Couchbase module is not compatible with the couchbase:community-* images from Docker Hub's official library?

@rnorth  there is no 6.6 under naming couchbase/server

@rnorth I'll come up with a PR to make sure community  edition also works. Right now we did not test with  community, and community  only allows for a different index engine (forestdb). The fix shouldn't be hard, working  on it.

@rnorth @hantsy provided a PR in #3428
Note that this helps to work around the issue and provides more flexibility in general, but I still wonder if we should do two more things:

change the default image name to couchbase:enterprise-6.5.1, since I'm not sure when but it looks like the naming has changed to a format like this?
add a "withCommunityEdition" which would 1) swap it tocouchbase:community-6.5.1 and 2) apply the storage setting automatically?

@daschl  I think the default couchbase(couchbase:latest) should be the enterprise.

@hantsy I'm not sure I would want that personally, since I'd rather want the server version to be the same I currently use in prod

I would like to use the latest product when starting a new project, but the versions used in testcontainers are up to date requently.

Let's leave that  final call to @rnorth, since I assume there is a established best practice with other modules and couchbase should just follow that.

After updated to couchbase:community as you suggested, got the store error, which could be resolved in your prs.
I will test it again when it is merged.

I think this is good to go now?

@rnorth @bsideup  trying again :) I think this is good to be merged.


[popover] accessibility tab documentation

Accessibility tab

Add accessibility documentation for the Popover component. Use our current accessibility docs template.

Possible sections:

[ ] How it works
[ ] Accessibility considerations
[ ] Resources
[ ] Accessibility testing
[ ] Automated test
[ ] macOS Screen reader tests
[ ] Windows screen reader tests
[ ] Android screen reader tests
[ ] iOS screen reader tests

When tackling this, it seems like this content was more appropriate in other pages (like tooltip or disclosure specifically) as there wasn't much related to popover specifically. Going to close this out as a result 👀


Add simple click event using the “on” method

When user clicks on the donut chart it will enlarge. The panel container isn't enlarging yet...We need to discuss this further, but just wanted to get us started on this.

Added "path.on" and removed "chart.on"


JCL-422: perf test

Added a perf test in UMA on GET resource with grant on localhost.

Would it be possible to have the perf tests run in a separate GH Action step (i.e. in parallel) rather than after the e2e tests? That would shorten the wallclock time of the tests and make it easier to re-run, if necessary

Would it be possible to have the perf tests run in a separate GH Action step (i.e. in parallel) rather than after the e2e tests? That would shorten the wallclock time of the tests and make it easier to re-run, if necessary

Absolutely. And we don't nee dot run them on Java 11 also.


[security] Upgrades to address known vulnerabilities

What
Fixing the following vulnerabilities

All vulnerabilities were fixed in the latest update but I had to upgrade transitive dependencies directly to do that. If that's not ok, I'll revert some of these changes. cc: @marcelosalloum @reecexlm
https://socket.dev/dashboard/org/stellar/sbom/272acc90-915e-4236-984a-6a3f1b3452f1?tab=alerts
Checklist
PR Structure

[ ] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR title and description are clear enough for anyone to review it.
[ ] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[ ] This PR adds tests for the new functionality or fixes.
[ ] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[ ] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[ ] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[ ] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[ ] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[ ] This is not a breaking change.
[ ] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[ ] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr310.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr310.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr310.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr310.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr310.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr310.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr310.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr310.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr310.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr310.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr310.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr310.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr310.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr310.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr310.previews.kube001.services.stellar-ops.com


image filenames containing & -> crash

Step 1. Modify the inner loop from default cmd handler to only include this single line echo '{%It&.png% t|t}'
Step 2. Point lighthouses config at this modified handler
Step 3. Run lighthous
Step 4. Type anything
Step 5. Segfault :)
This crash occurs regardless of whether the referenced image file actually exists.

that is an illegal filename, right? shouldn't the & be escaped?

.. Why would the & be escaped? This isn't shell script and as far as I know, & has no special meaning to lighthouse, correct me if I'm wrong.
(On a Ext2/3/4 filesystem or BTRFS filesystem, all characters except NUL and / are valid. I easily created a file t&,png ,just by saving an image normally in GIMP)

Ah, I understand.  I was going off of the restrictions on wordexp.  I'll add that escaping is necessary to address files with special characters in the README.  You can test your example file with t&.png

This now works without escaping, BTW, so the mention in the README of & as a character that needs to be escaped seems to be outdated (at least for cmd output)

Ah, nvm. I wasn't reading closely enough; it causes errors only as a filename, which is consistent with the readme.
(not that this stops the 'problematic' image from loading!)


Render placeholders in menu_name

Description

I had forgotten to render placeholders found in the menu_name key. This fixes that behavior so folks can things like do "menu_name": "{{ DISTRIBUTION_NAME }} shortcuts" to customize the Start Menu directory.
Checklist - did you ...

[x] Add a file to the news directory (using the template) for the next release's release notes?

[x] Add / update necessary tests?
[ ] Add / update outdated documentation?

cc @marcoesters


Add support for Alpine linux platform

I wanted to add support for Alpine Linux as it's quite a useful distro with a small footprint around 5MB. This way it will be available as a platform when defining a platform in the .kitchen.yml
At the moment this fails as Alpine is not a supported platform:
# kitchen create sculpin-alpine
-----> Starting Kitchen (v1.5.0.rc.1)
-----> Creating <sculpin-alpine>...
>>>>>> Create failed on instance <sculpin-alpine>.
>>>>>> Please see .kitchen/logs/sculpin-alpine.log for more details
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Unknown platform 'alpine'
>>>>>> ----------------------

This PR is for:

apk --update
apk add openssh curl

Output within Container:
https://gist.github.com/timani/03cd67a9a287c0337bdc
Are there some additional tests that would need to be run to make sure it meets the requirements? If so I can gladly add those.
Links

http://www.alpinelinux.org/
https://hub.docker.com/_/alpine/

Yes please. I really need this.
I'll install you're fork and see what happens.

Here's a failure for you to fix:
STDOUT: Sending build context to Docker daemon 3.072 kB
Step 1 : FROM drifter-api/base:latest
 ---> f9b822311c35
Step 2 : RUN apk update
 ---> Running in 419d65e2ed97
fetch http://nl.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
fetch http://dl-2.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
fetch http://dl-3.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
fetch http://dl-4.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
fetch http://dl-5.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
v3.3.1-54-g542892a [http://nl.alpinelinux.org/alpine/v3.3/main]
v3.3.1-54-g542892a [http://dl-2.alpinelinux.org/alpine/v3.3/main]
v3.3.1-54-g542892a [http://dl-3.alpinelinux.org/alpine/v3.3/main]
v3.3.1-54-g542892a [http://dl-4.alpinelinux.org/alpine/v3.3/main]
v3.3.1-54-g542892a [http://dl-5.alpinelinux.org/alpine/v3.3/main]
OK: 5318 distinct packages available
 ---> 2b61f4d029f3
Removing intermediate container 419d65e2ed97
Step 3 : RUN apk add openssh curl
 ---> Running in 0b49f88bf472
(1/7) Installing openssl (1.0.2f-r0)
(2/7) Installing ca-certificates (20160104-r2)
(3/7) Installing libssh2 (1.6.0-r0)
(4/7) Installing curl (7.47.0-r0)
(5/7) Installing openssh-client (7.1_p2-r0)
(6/7) Installing openssh-sftp-server (7.1_p2-r0)
(7/7) Installing openssh (7.1_p2-r0)
Executing busybox-1.24.1-r7.trigger
Executing ca-certificates-20160104-r2.trigger
OK: 10 MiB in 18 packages
 ---> db1a4471bdf6
Removing intermediate container 0b49f88bf472
Step 4 : RUN ssh-keygen -A -t rsa -f /etc/ssh/ssh_host_rsa_key
 ---> Running in 4136b63e09aa
ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519
 ---> c07e79742aff
Removing intermediate container 4136b63e09aa
Step 5 : RUN ssh-keygen -A -t dsa -f /etc/ssh/ssh_host_dsa_key
 ---> Running in 833e94e952a0
 ---> 0a81683c5f64
Removing intermediate container 833e94e952a0
Step 6 : RUN if ! getent passwd kitchen; then                 useradd -d /home/kitchen -m -s /bin/bash kitchen;               fi
 ---> Running in a6a8e7a5834d
/bin/sh: useradd: not found

STDERR: The command '/bin/sh -c if ! getent passwd kitchen; then                 useradd -d /home/kitchen -m -s /bin/bash kitchen;               fi' returned a non-zero code: 127
---- End output of docker -H tcp://<IP_ADDRESS>:2376 build -f /Users/omer.katz/Documents/drifter/drifter-api/distribution/dependencies/Dockerfile-kitchen20160210-84186-gz7fs9 - ----
Ran docker -H tcp://<IP_ADDRESS>:2376 build -f /Users/omer.katz/Documents/drifter/drifter-api/distribution/dependencies/Dockerfile-kitchen20160210-84186-gz7fs9 - returned 1]
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

The command to add a user in alpine is adduser. not useradd.

You can find the code here that executes the addition of the user: https://github.com/portertech/kitchen-docker/blob/014b9aa24623d375a3a0c0595585f0d7519c8909/lib/kitchen/driver/docker.rb#L226

Right now I'm stuck with:
[SSH] Established
       Finished creating <default-drifter-base> (0m24.11s).
-----> Converging <default-drifter-base>...
$$$$$$ Running legacy converge for 'Docker' Driver
       Preparing files for transfer
       Preparing dna.json
       Berksfile, Cheffile, cookbooks/, or metadata.rb not found so Chef will run with effectively no cookbooks. Is this intended?
       Removing non-cookbook files before transfer
       Preparing solo.rb
-----> Installing Chef Omnibus (install only if missing)
       Downloading https://www.chef.io/chef/install.sh to file /tmp/install.sh
       Trying wget...
       Download complete.
       Unable to determine platform version!
       Version:

       Please file a Bug Report at https://github.com/chef/omnitruck/issues/new
       Alternatively, feel free to open a Support Ticket at https://www.chef.io/support/tickets
       More Chef support resources can be found at https://www.chef.io/support

       Please include as many details about the problem as possible i.e., how to reproduce
       the problem (if possible), type of the Operating System and its version, etc.,
       and any other relevant details that might help us with troubleshooting.

See https://github.com/thedrow/kitchen-docker/tree/apl

It does work with the dummy provider though.

@timani Should I just open a new pull request?

Chef does not support Alpine at this time so I'm not sure what would pass for "official support" in kitchen-docker. I think for the moment the best approach would be to use the dockerfile configuration option to fully specify your own config. Even with that, I don't know how you would effectively install Chef though.

People use Test Kitchen for other provisioners as well.
I'd like to be able to run the tests without chef.

Even with the other provisioners Test Kitchen has a dependency on Chef as it uses some of the features bundled with it during the verify phase. It is a Test Kitchen thing not something the docker driver is doing.
Does your setup work without using Chef for thr converge? You might have to install Chef manually (if possible) as part of the setup phase using the custom provision config

I'm going to use the shell verifier with serverspec on ssh mode.
I still think there's no value to reject this feature request.
More and more people will want smaller containers and Alpine can provide that.

That's fair, but if you aren't using Chef you'll probably want a fairly different setup than the standard dockerfile too, maybe? A broader description of what you are trying to do with TK+Alpine would help.

I'm trying to test docker images I built from the alpine base image. That's about it.

Hmm, what kind of tests are you planning to run? I wouldn't normally assume that you would install sshd in an Alpine image.

To check if packages are installed. Verify that they do what they declare they do etc.

@thedrow If you can get this to a working state with a non-Chef provisioner, let me know. I would be cool with merging this explicitly for non-Chef use if there was an explicit check for one of the known chef-related provisioners (either by name or preferably by is_a?(ChefBase)) so there is a better UX than an omnibus installer error.

My branch works with the none chef provider but see #194.
The shell verifier cannot work if that issue will not be resolved.

I think kitchen only uses chef because it uses the ruby and gem bundled within chef, to install busser which is the default verifier for kitchen.
While chef does not support alpine, if people do not use chef as provisioner, but something else, like kitchen-ansible, I think alpine would make sense. You can choose not to install chef but only ruby and gem.

I think kitchen only uses chef because it uses the ruby and gem bundled within chef, to install busser which is the default verifier for kitchen.
If you don't use chef provisioner, and busser is not required (or preinstalled in the docker, or just have ruby and gem in the docker and still can install busser), alpine works and it is a small and fast way to do local test.
For example, kitchen, kitchen-docker as driver, kitchen-ansible as provisioner, and alpine as container. Image size could be under 200MB even with sshd, busybox, git, ansible preinstalled.
I have already tested this locally, but with dockerfile option, to bypass the version check. I hope in the following days/weeks I can contribute a PR on this issue to add support for alpine and mention in the doc that you can only use this when you don't use chef as provisioner.
Weird that only me and @thedrow had this issue or requirement, although I think it makes a great sense for faster CI.

@IronCore864 You're not the only two who would find Alpine platform support useful, I'd also benefit from it. Some of our apps which we dev/test using Test Kitchen have Alpine-based Docker images as dependencies, and it would be nice to be able to use them directly as a platform without having to write a Dockerfile to support them.

@ultrafez I got a PR regarding supporting alpine:
https://github.com/test-kitchen/kitchen-docker/pull/288
It's not reviewed nor merged, because CI is failing, but according to the log, I think master branch is failing too. If you want to have something that works now you can check it out.


Chng controller api

Please check it

When running featurecloud controller start I am getting this error:
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url:
http+docker://localnpipe/v1.35/images/create?fromImage=featurecloud.ai%2Fcontrol
ler

I investigated it further, and the problem is in this line: client.api.pull(repository='featurecloud.ai/controller', stream=True)
This works though: client.api.pull(repository='ubuntu', stream=True)
It seems to be somehow related to the registry. I am testing on Windows.
Does it work for you?

When running featurecloud controller start I am getting this error:
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url:
http+docker://localnpipe/v1.35/images/create?fromImage=featurecloud.ai%2Fcontrol
ler

I investigated it further, and the problem is in this line: client.api.pull(repository='featurecloud.ai/controller', stream=True)
This works though: client.api.pull(repository='ubuntu', stream=True)
It seems to be somehow related to the registry. I am testing on Windows.
Does it work for you?

I don't have any problem on Mac. I think it is an OS issue


[BUG] Report range of all dates stay current

Is your feature request related to a problem? Please describe.
When swapping to the toolkit reports, if I've previously selected the date range of 'All Dates' but it is now a new calendar month, the end date range stays with the prior month. This happens even if I have not viewed a report since, eg, November it will be November on the date range today on March 1st until I again click 'All dates'.
Describe the solution you'd like
I'd like the 'All Dates' selection range to stay current when swapping to the toolkit reports. When using the out of the box reports, the All Dates range constantly updates to the current budget month based on the current actual date.
Describe alternatives you've considered
I manually click 'All Dates' again upon load to force the dates to become current again, but this feels like an unnecessary step.

I'm actually going to consider this one a bug. It will require a bit of work to fix but shouldn't be too hard.

All filter options should be relative to the current date. Ie: if user selected past 3 months and comes back on the next calendar month, they should see the past three months from the current date. Not from the previous month.

This may be related, but when I'm using the toolkit (Chrome & Firefox), the filter for transactions reverts to "All Dates." Therefore, I have to go in each time and reset the dates. I usually look at current and next month. I have many monthly scheduled transactions and seeing all of the future dates just takes up screen space. So, this is almost the opposite of undaunt's issue.


More cleanup based on API review

Working through items in https://github.com/dotnet/corefxlab/issues/1714
cc @ahsonkhan, @shiftylogic, @joshfree

Thank you @KrzysztofCwalina for picking this up off the backlog


Update code gen default value ignore filters for new method names

Code generation relies on default values set in the config items. Some things should be ignored like local paths that are specific to the developer's workstation.
Updated the filters to include the new name alias actions.

Can we add all GitHub tokens and AWS tokens as well?

@KrauseFx which ones are missing?

GitHub and AWS tokens, you can find all of them by searching for GITHUB_API_ for all GitHub related actions, and s3.rb for the AWS credentials


Mistyped named arguments interpreted as positional arguments

Hi,
Many times I have encountered a problem with wrongly spelled named arguments being interpreted as position arguments. Especially when the casing/spelling of arguments change (are changed by colleagues). Here is an example:

*** Test Cases ***
TC
    KW
    KW  named1=1
    KW  named_1=1
    KW  Named2=1

*** Keywords ***
KW
    [Arguments]    ${named1}=1  ${named2}=2
    Log To Console    ${\n}Got named1: "${named1}"
    Log To Console    Got named2: "${named2}"

And the output below. Problematic are the last and second to last case.
Got named1: "1"
Got named2: "2"

Got named1: "1"
Got named2: "2"

Got named1: "named_1=1"
Got named2: "2"

Got named1: "Named2=1"
Got named2: "2"

I propose the following solution: Log/print a warning if

a positional argument contains a "=", and
the part that is left of the "=" symbol is similar to the name of a named argument.

Similarity could be determined, for example, using simplified/modified levenshtein distance.
I think this is the location where such a check could be implemented, although I'm not sure whether warnings can be logged by this class (using import warnings?): https://github.com/robotframework/robotframework/blob/d32baeaa4541784e7584cd4b16cb513d029e0ebe/src/robot/running/arguments/argumentvalidator.py#L21

This is a real problem, but hard to solve without breaking backwards compatibility massively. The main problem is that = is a pretty commonly used in normal arguments. If we'd always interpret xxx=yyy to mean named argument usage with xxx as the name, that would be massively backwards incompatible and even reporting a warning would be very annoying. If we were to do something like that, it would need to be controlled with a command line option.
I believe we need to return to this at some point.


Path variable being concatenated after resetting

The "path" variable is being concatenated, even after resetting, when using a "helper" feature and calling that feature from inside a scenario.
In version 1.1.0 you could essentially re-use the path variable without problems.  The main feature file would setup as follows:
Feature: Main feature
Background:
* url url
* header Authorization = token
* path 'care/v1.1/account/'
Scenario: call helper feature then do test
* def fullResponse = call read('init/movein_ADD.feature') { payloadFilename: 'data/account_id_call_ADD_MOVEIN_No_GovtId.json'}
* def updatePayload = read('data/account_id_call_add_MOVEIN_Both_GovtId.json')
* header Accept = json
* header Content-Type = json
Given path ENCODE('16382-8') + '/call/update'
And request updatePayload
When method POST
Then status 200
feature files.zip
Then the helper feature would be setup like:
@ignore
Feature: Helper feature file
Scenario: do some helping
 * url url
 * path 'care/v1.1/account/'
* def payload = read(payloadFilename)
* header Accept = json
* header Content-Type = json
 Given path 'MTYzODJAQDg=/call/add'
  And request payload
 When method POST
 Then status 200

Everything worked fine.  But now on version 1.2.0.RC6 the helper feature file will fail.  Removing the path from the helper feature file scenario will work, however that causes the main feature file scenario to fail, as the path variable becomes concatenated, like "care/v1.1/account/MTYzODJAQDg=/call/add/care/v1.1/account/MTYzODJAQDg=/call/update".  I've tried resetting path in the main scenario right after it does the call to the helper feature, * path 'care/v1.1/account/', no luck as same result.  I've tried using another variable, like * def myPath = 'care/v1.1/account/' and doing Given url myPath ENCODE('16382-8') + '/call/update', but that doesn't work either, still comes out concatenated.
Something must have changed between versions and introduced this unexpected behaviour.

@snow23man I took a quick look at the zip file but am closing this ticket. it is important that you follow the instructions exactly as described: https://github.com/karatelabs/karate/wiki/How-to-Submit-an-Issue


[BUG][WEBJS] - Issue in posting to /api/sendVideo

Hello,
I'm having issue on the endpoint sendVideo

Version
{
"version": "2029.10.29",
"engine": "WEBJS",
"tier": "PLUS",
"browser": "/usr/path/to/bin/google-chrome"
}
this the request i'm sending {
"chatId"<EMAIL_ADDRESS>"file": {
"mimetype": "video/mp4",
"filename": "funnyfastvideo.mp4",
"url": "https://generator-pipeline-api-test.azurewebsites.net/media/fCN9yyJ9a3cj0_yBUW90EIAXL4c232JTnRBbH4i2_eRgz9XzDVmIuEII6Q98cycafUiky0ZvuVQ_3RKSRS3A==.mp4"
},
"caption": "",
"session": "newuser"
}
and there is no response
it stays like that , i tried with many different video links and to send to different users

and then after waiting long the response
499Undocumented | Error: response status is 499

please advice as soon as possible ,
Thank you so much

Fixed in 2024.5.6!
Try first the example payload from https://waha.devlike.pro/docs/how-to/send-messages/#send-video-imagesversionspluspng
{
  "session": "default",
  "chatId"<EMAIL_ADDRESS>  "caption": "Watch this video!",
  "file": {
    "mimetype": "video/mp4",
    "filename": "video.mp4",
    "url": "https://github.com/devlikeapro/whatsapp-http-api/raw/core/examples/video.mp4"
  }
}

Personal TY for such detailed report! :heart:

Hi @devlikepro , Still getting same error. I am using latest version of devlikeapro/whatsapp-http-api-plus:arm

Sorry, we had to revert the solution, it causes sometime "scan qr" issues. Looking for a way to fix it!

Sure @devlikepro  ,
Thanks for quick reply. Please update here once you fixed.

Please fix this problem to send videos using this API. I really need this feature again

Please fix this problem to send videos using this API. I really need this feature again

Please fix that problem :( Really need it...

Please fix that problem :( Really need it...

if you could fix this issue so that i could send videos through api it will really be helpful for me and a lot of people

Could you fix the video API? I'm having problems when I try to send a video.

I need to send videos via API. could you please fix this issue?

Fine, fine, just stop spamming :D
Added a temporary solution in WAHA Plus 2024.5.9

https://waha.devlike.pro/docs/how-to/send-messages/#send-video-imagesversionspluspng
⚠ WEBJS (default) engine notes for sending videos ⚠

💡 If you're experiencing "forever loading" issue (#321, #328) - set up WAHA_WEBJS_WEB_VERSION=2.2412.54-videofix environment variable:

docker run -it -p 3000:3000/tcp -e WAHA_WEBJS_WEB_VERSION=2.2412.54-videofix devlikeapro/whatsapp-http-api-plus:chrome

I don't close the issue, because it requires additional actions right now. When we added "by default" for all session - we'll close the issue and remove the note

:point_up:
@Thiagomleite
@willpexero
@joseamonteironeto
@cadduroleta
@Lucasvico1
@brunoskiner
@ANACAROLINA1089
@rafaelboav

☝ @Thiagomleite @willpexero @joseamonteironeto @cadduroleta @Lucasvico1 @brunoskiner @ANACAROLINA1089 @rafaelboav

Fine, fine, just stop spamming :D
Added a temporary solution in WAHA Plus 2024.5.9
https://waha.devlike.pro/docs/how-to/send-messages/#send-video-imagesversionspluspng
⚠ WEBJS (default) engine notes for sending videos ⚠

💡 If you're experiencing "forever loading" issue (#321, #328) - set up WAHA_WEBJS_WEB_VERSION=2.2412.54-videofix environment variable:

docker run -it -p 3000:3000/tcp -e WAHA_WEBJS_WEB_VERSION=2.2412.54-videofix devlikeapro/whatsapp-http-api-plus:chrome

I don't close the issue, because it requires additional actions right now. When we added "by default" for all session - we'll close the issue and remove the note

It works! Thanks :)

Let's close the issue because it has a workaround. When we moved to new whatsapp (when they released it) - it'll work by default

Im facing the same problem. Version: 2024.6.7 no workaround applied.
I updated to the latest version a few weeks ago to resolve the random session crashes. If I apply this workaround, will I have any downside?

If I apply this workaround, will I have any downside?
Nope, it's regular version, but with the fix!

We're working on fixiing it completely, hopefully soon :crossed_fingers:


Is it possible to use it with non-react project?

Sure, something like this should work.
// my-inject-style.js
import Styletron from 'styletron-client'
import {injectStyle} from 'styletron-utils'

const styletron = new Styletron();
export default style => injectStyle(styletron, style);

import myInjectStyle from './my-inject-style'
const classNames = myInjectStyle({
  color: 'yellow',
  background: 'blue',
});
console.log(classNames); // -> 'a b'

I use grunt and angular one. How to use it with them?

I think a modular approach is pretty much a requirement here.
Use browserify with grunt / gulp, or webpack.
Those would still work just fine with Angular.

Closing unless there are more questions. Thanks!


Add a header to override grpc::string when needed

@gwvo is this going to be a problem for flatbuffer?

Yes, that's a problem since config.h pulls in a whole bunch of other grpc headers. cpp_generator.h is meant to be self-contained so it can be compiled into flatc without needing grpc.

@gwvo Could you somehow override the config.h or remove that line when making the copy? The cpp_generator.h uses grpc::string and it would be hard for me to override it without the header. Thanks.

test this please

I guess easiest if in FlatBuffers we just provide an empty config.h, right?

@gwvo That is what I had in mind :) and it is the reason I did not remove the section about the custom string.

@nicolasnoble ping~


Add support for using TIM2 as a PWM output

This adds support for the PWM output of TIM2 on supported devices. It is simply a matter of providing the corresponding implementations for the correct Pins and a pwm_4_channels implementation for TIM2.

Sorry for the typos, this has been fixed with fd36360 and is building correctly now.
Also this has been tested and is working on a STM32F042G6


Checking for non-zero size of x-matrix

This should fix #2 by emitting a better Rhai error type instead of panicking outright.

@schungx A question on best practice that is related to this PR. In rhai-sci I have some functions for checking size and number of elements in arrays. It would be nice to re-use those to check for this case in rhai-ml. Any thoughts on how to do that in a way that makes the most sense?

Just export them and pull in rhai-sci?


First attempt. Successful, but not very programmatic.

This solution literally maps each character to its translation through a dictionary. I'll keep working to make it more programmatic.

I added a couple lines to program the capital letter translation, but I'd be interested to know if anyone else has ideas on how to make it more programmatic.


Add refresh tilemap block

Implement proposed fix for #15

Hi, @megabyte6 !
Thanks for your new PR, it looks nice, and have been merge.
Thanks again for your contribution.

@AqeeAqee thanks for merging my changes.
How do updates and versioning work for MakeCode Arcade extensions? I noticed it has been a while since the merge and MakeCode Arcade still uses the old code. I briefly looked into it and found some documentation on MakeCode with GitHub releases. Since I don't have permission to the main repository for ptx-raycasting, could you publish a release so MakeCode Arcade detects the updates?
On a side note, I noticed that in your commits for updating the version that you update pxt.json, assets/version.txt, and assets/js/binary.js. I assume assets/js/binary.js is done automatically. As for pxt.json and assets/version.txt, which ones need to be updated manually or are they both updated automatically? I had previously manually updated pxt.json but not assets/version.txt.


Silently connecting to metadata service in constructor is dangerous behavior

I noticed in 147469373c9fec1037bd2d75d7cd949250c6f7c5, it introduced a behavior where, if the region was not specified, it tried to infer it from the EC2 metadata service.  I think this is dangerous behavior because

A user not using S3 probably doesn't care about this field.  A user who additionally isn't using EC2 will incur a several second wait (as this person did https://stackoverflow.com/questions/63725308/awss3s3client-constructor-very-slow).
More importantly, if you are using EC2 but not US-EAST-1 and relying on this, and for some reason one day it fails to connect to the metadata service during the constructor, you have accidentally created a cross-region S3Client without knowing about it.  Since cross region traffic is billed by the byte, this could be a very expensive mistake!

Its easy to work around this by just setting the region explicitly, but it isn't clear that this is a requirement from anything I've seen.
Thanks!

Hi @jvictor0 ,
Yea this is a good point, but it's kind of "known" thing/topic(?)
This was a conscious decision, and that is not to say your points are not valid... but yea let me kind of justify why that's there.
So the first thing to note is that this is meant to only be "default" behavior, the option is there in case you want to avoid it, I wouldn't even say it's a workaround, it is expected that you are able to customize this in whatever way you prefer, so you can explicitly tell the SDK where to look, or have a custom chain of places to look for that don't include the EC2 metadata... But yea it's not a requirement, it's an option.
The idea was to have the sdk run with as little configuration necessary, so we made the default credentials provider chain check for region in all the expected places.
Dunno if this makes sense but let me know what you think.


Tweak path to gdeval

see #1416 - changes to path need to be propagated to rest of documentation.

I think that's just weirdness in how the diffs are displayed?

I think that's just weirdness in how the diffs are displayed?

Ah, sorry, you are right!


needs a model.eval()

Thanks for the minimal VICReg implementation!
eval.py is missing a model.eval() or model.encoder.eval() call prior to the linear layer training loop. Without it, the BatchNorm moving statistics are still being updated in the encoder network with each forward pass and it's not doing linear probing.
As expected, using eval mode and linear probing only brings performance down from 86.99% to 85.50%.
Best,
Neel

Hi Neel,
Good catch! Thanks for letting me know. Will update the code and readme later today.

Fixed in 89eab04.


feat(api-gateway): implement Mock, AWS and Proxy integrations for API Gateway

Fixes #23
Continuation of https://github.com/functionless/functionless/pull/178
Implements support for API Gateway:

[x] Mock
[x] AWS Integrations
[x] Lambda Proxy

Merge error on the build?


bump dependencies to latest versions

issue #286
test are ok
todo example is ok
lens is ok (references and images are not working but it's not related i think, at least no errors)

:+1:

Tested and works fine for me too.


[AIRFLOW-40] add DAGs' filtering over ldap groups

Dear Airflow Maintainers,
Please accept this PR that addresses the following issues:

https://issues.apache.org/jira/browse/AIRFLOW-40

Already better. Can you extend the tests to cover this?

Please rebase and squash your commits. Don't forget to adhere to the commit guidelines.

[Current coverage][cc-pull] is 67.99%

Merging [#1479][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.04%

@@             master      #1479   diff @@
==========================================
  Files           116        116
  Lines          8310       8323    +13
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           5654       5659     +5
- Misses         2656       2664     +8
  Partials          0          0

Powered by Codecov. Last updated by [5963ac8...5b9da86][cc-compare]
[cc-base-branch]: https://codecov.io/gh/apache/incubator-airflow/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/apache/incubator-airflow/compare/5963ac8b7b7c0b3470ce6171b1cd928485bc9884...5b9da86c494eca284e7f777ab366444a22973d3b
[cc-pull]: https://codecov.io/gh/apache/incubator-airflow/pull/1479?src=pr

Hi @bolkedebruin,
Do you see anything that can still be improved to have this PR merged into master?
Thanks for your help.

@bolkedebruin , thanks a lot for your useful comments that definitely helped improving the code quality. If you do not have any other comments, this PR can be considered finished from my side.
Cheers


Messages need to support url links.

Contact Details
<EMAIL_ADDRESS>What happened?
Sending an adventure in a message doesn’t send an openable link. Links should be able to be opened
Version
1.1.5
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Done


Support retries to push to a registry

Description of the issue:
On laggy registries - which means you often get a 504 timeout issue - it is not possible to push images with jib whereas it works with docker with a retry (it retries not yet uploaded layers).
Expected behavior:
A retry would happen on layers (default to 3 maybe?).

We should also investigate using chunked uploads since some layers may be rather huge.  The only worrisome aspect is that it's unclear what should be our minimum chunk size:

There is no enforcement on layer chunk splits other than that the server must receive them in order. The server may enforce a minimum chunk size. If the server cannot accept the chunk, a 416 Requested Range Not Satisfiable response will be returned and will include a Range header indicating the current status:

It appears that chunks must be provided in sequence.  The documentation describing the 416 result says:

Out of order chunk: the range of the next chunk must start immediately after the “last valid range” from the previous response

up? on openshift we easily get SSL issues (indeed without any modification a relaunch works) when pushing concurrently layers so a proper retry would help on client side.

One form retry is implemented in #3351. There can be other ways of retrying, but #3351 should already be very helpful. Closing the issue.


WebGl support on windows?

hey guys!
I was trying to embed a webgl content in the brackets, for game editting.
It's ok on Mac OSX, but failed on Windows.
I have tried to add --enable-webgl --ignore-gpu-blacklist to start command, but still can't get a webgl context on Windows in brackets.
I have tested webgl with http://threejs.org/examples/#webgl_animation_cloth in chrome and node-webkit, it's ok.
So i think my windows supports webgl.
Is there a way to make it right?
Thanks for readding!

The CEF version integrated with brackets should have support for WebGl.
But it may be not initialized or enabled or worse, the DLLs may not be part of brackets.
Angle and Direct3D support
d3dcompiler_43.dll (required for Windows XP)
d3dcompiler_46.dll (required for Windows Vista and newer)
libEGL.dll
libGLESv2.dll
Note: Without these components HTML5 accelerated content like 2D canvas, 3D
CSS and WebGL will not function.

You could build brackets shell from source
https://github.com/adobe/brackets-shell/wiki/Building-brackets-shell
The built version has all the D3D and webgl DLL's.

I rebuild brackets for windows, and it works well ! ^_^
Thanks for your answer, @abose.

:+1: Moving to backlog, confirm if we should have integrated the DLL's in windows natively as mac/linux builds already ships with the bins.

@2youyouo2 If you need brackets to integrate the DLL's in the windows end for writing extensions feel free to reopen this issue.

It's important for me, but i don't know anyone else need  webgl in brackets.
So i reopen this issue to see whether anyone else need it.

Yes, please! I vote for WebGL in bracket-shell by default! :+1:

Are you able to run webgl content on mac builds?

Yes, in official Bracket, out out the box.

Including the DLL's would add around 4 MB to the installer footprint.
@zaggino @nethip @MarcelGerber @petetnt

If there are no technical reasons why WebGL support absolutely shouldn't be added :+1: from me.
It opens the world of possibilities for creative stuff in the future and it seems to be already possible on Mac builds so I am willing to take the 4 MB footprint hit.

Yeah, I also don't think 4 MB is anything to be worried about. If is as simple as adding a DLL to the build, lets do it.

Yes, please! I vote for WebGL in Bracket! :+1:


Added support for yandex browser via opera driver

@Zarom did you test images with the following tests? http://github.com/aerokube/selenoid-container-tests

@vania-pooh not yet. Will come back with results.

@vania-pooh got some troubles while getting tests running on our machines... All tests passes, except "TestProxy":
Results :

Failed tests:
  TestProxy.testProxy:46
Expected: is not an empty collection
     but: was <[]>

Tests run: 22, Failures: 1, Errors: 0, Skipped: 1

Because it fails even on selenoid/opera image, I think this is driver or container test issue.

@Zarom ok, please squash your commits and I'll merge.

@vania-pooh done!

@zarom thank you for contribution!


"Zipline: Show the Local Weather" Issue

Challenge http://www.freecodecamp.com/challenges/zipline-show-the-local-weather has an issue.
When I try to open the Local Weather App on CodePen all I see are three empty boxes.
http://codepen.io/AdventureBear/full/yNBJRj

This is an error due to amount of times the example has been loaded.

There's no real fix for this I'm afraid but if you're to use this API in your own app it should still work.

Generally this happens when your browser prevents any site to load external data from different websites.
If you're using Chrome as your browser, Click the Shield icon on right side of the address bar and select "Load unsafe scripts".

This will refresh the tab and load the scripts for that tab (only).
This is a default setting on browsers due to security reasons.
But as we can see the code on codepen.io and know where it is calling its requests (here openweathermap.org and ipinfo.io), so we can explicitly allow the permissions.

Closing as stale/fixed


Support following vehicles only in Walk-Through mode

Request from therealGN on Steam

Feature Description
In Walk-Through mode, add an option to allow following only vehicles/citizens
Proposed Solutions
A simple solution would be to draw random follow targets out of the pool of all vehicles instead of the pool of all citizens.

added by 905f767126bf75310f3a02aa56a033890aa5be14


inference with custom weights

Hello,
I have successfully trained a custom model.
Now I have some .th files in my train folder but I am not sure how to load the models and do an inference.
Can you give me a hint how to load the model?
This is the content of my folder in total:

@icklerly1 Hello, I think the instructions for exporting your model will help you. https://github.com/facebookresearch/audiocraft/blob/main/docs/MUSICGEN.md#importing--exporting-models

@Elizahub how can one get the SIG of a pretrained model?

Yeah, I am wondering exactly the same thing :)
What does the "SIG_OF_LM" mean?

The SIG is just the hash created to represent the dora experiment, such as 71bdb194.
But the concept of SIG vs XP are still kind of loose on me.

@icklerly1 in your case the SIG is ea5ff7e7


While Guthix Sleeps

Has development for While Guthix Sleeps started?
I'm considering setting up a lot of the framework for the quest but don't want to do double work.
Thanks!

Yup, it's currently being worked on by Zoinkwiz in this branch: https://github.com/Zoinkwiz/quest-helper/tree/while-guthix-sleeps


Fix the URL

As same with PR3050

NOTE: Please check the “Allow edits from maintainers” box below to allow
reviewers fix problems on your patch and speed up the review process.
Please delete this note before submitting the pull request.

This change is

@chenopis Similar to PR #3050


Change Plugin Name

The repo for this plugin is called Manifold Cordova, and the plugin itself is called cordova-plugin-hostedwebapp. This plugin is pretty useful for a general cordova app to detect network issues and display an offline page.
Please consider re-naming this plugin to cordova-plugin-offlinepage to better reflect its purpose.

While the plugin is capable of detecting network connectivity changes and showing an offline page, as I explained in your other issue (https://github.com/manifoldjs/ManifoldCordova/issues/35), its main purpose is to create hosted web apps.
If you only need to show an offline page, then using the standard network-information plugin might be enough.

The network status plugin alone cannot display a page, especially when using in a Cordova hosted app created using the CLI.
The plugin uses a second webview, and has native code to display the offline page - if I wanted as similar functionality, i would simply end up rewriting this plugin.


go test -race fails

Build log:
==================
WARNING: DATA RACE
Read at 0x00c0004100c0 by goroutine 52:
  github.com/tetratelabs/getenvoy/pkg/binary/envoy.(*Runtime).GetPid()
      /home/circleci/project/pkg/binary/envoy/runtime.go:99 +0x169
  github.com/tetratelabs/getenvoy/pkg/binary/envoy/debug.retrieveOpenFilesData()
      /home/circleci/project/pkg/binary/envoy/debug/lsof.go:60 +0x7f
  github.com/tetratelabs/getenvoy/pkg/binary/envoy.(*Runtime).handleTermination()
      /home/circleci/project/pkg/binary/envoy/termination.go:36 +0x17a
  github.com/tetratelabs/getenvoy/pkg/binary/envoy.(*Runtime).RunPath()
      /home/circleci/project/pkg/binary/envoy/run.go:60 +0x484
  github.com/tetratelabs/getenvoy/pkg/binary/envoy.(*Runtime).Run()
      /home/circleci/project/pkg/binary/envoy/run.go:38 +0x106

Previous write at 0x00c0004100c0 by goroutine 50:
  os.startProcess()
      /usr/local/go/src/os/exec.go:25 +0x602
  os.StartProcess()
      /usr/local/go/src/os/exec.go:102 +0x92
  os/exec.(*Cmd).Start()
      /usr/local/go/src/os/exec/exec.go:416 +0x897
  github.com/tetratelabs/getenvoy/pkg/binary/envoy.(*Runtime).runEnvoy()
      /home/circleci/project/pkg/binary/envoy/run.go:133 +0x2be

Goroutine 52 (running) created at:
  github.com/tetratelabs/getenvoy/pkg/binary/envoytest.Run()
      /home/circleci/project/pkg/binary/envoytest/util.go:57 +0x12a
  github.com/tetratelabs/getenvoy/pkg/binary/envoytest.RunKill()
      /home/circleci/project/pkg/binary/envoytest/util.go:81 +0x15a
  github.com/tetratelabs/getenvoy/pkg/binary/envoy/debug.TestGetOpenFileStats.func1()
      /home/circleci/project/pkg/binary/envoy/debug/lsof_test.go:35 +0x25c
  testing.tRunner()
      /usr/local/go/src/testing/testing.go:909 +0x199

Goroutine 50 (running) created at:
  github.com/tetratelabs/getenvoy/pkg/binary/envoy.(*Runtime).RunPath()
      /home/circleci/project/pkg/binary/envoy/run.go:57 +0x462
  github.com/tetratelabs/getenvoy/pkg/binary/envoy.(*Runtime).Run()
      /home/circleci/project/pkg/binary/envoy/run.go:38 +0x106
==================

this will fail until the e2e tests in the debug directory are moved to test/e2e and backfilled with unit tests
there are also some signal tests that fail, but should go away with #172

go test -race ./pkg/util/exec also fails

still an issue

still an issue


45 3.11 mark as accepted rejected

Fixes #45

Coverage remained the same at 100.0% when pulling fae319849cc97d8a5125c2e3c28f54dc9b1c67bf on 45_3.11_markAsAcceptedRejected into e3fafe2307cda347839d77d810ac7615aa3d229c on dev.

Coverage remained the same at 100.0% when pulling c8efdbad4b173cc2e8e462926a1697f3fc76d710 on 45_3.11_markAsAcceptedRejected into e3fafe2307cda347839d77d810ac7615aa3d229c on dev.

Coverage remained the same at 100.0% when pulling 757527d26f31c87052b2bdbb7d50f4c4ae1291ea on 45_3.11_markAsAcceptedRejected into e3fafe2307cda347839d77d810ac7615aa3d229c on dev.

Coverage remained the same at 100.0% when pulling 1cc987d3904ee63d80158bb63d40a03c1be37126 on 45_3.11_markAsAcceptedRejected into 3463c01dea296792ca8013f8a3fd65ff3576d821 on dev.

The PR currently not completes the US it refers to.
It is currently possible to change the status of an application even after the email is send. This should not be possible, after the Acceptance Criteria of the US.

Coverage remained the same at 100.0% when pulling 0c59115c375b5aff85ffc71210b2c4abba0c077d on 45_3.11_markAsAcceptedRejected into ea62eb1af4661d9f9bb0aa009419918d19b88e5e on dev.


Connot interpret 'torch.float32' as a data type

projects/img2llm-vqa/img2llm_vqa.py
resized_img = raw_image.resize((int(w * scaling_factor), int(h * scaling_factor)))
norm_img = np.float32(resized_img) / 255
gradcam = samples['gradcams'].reshape(24,24)
avg_gradcam = getAttMap(norm_img, gradcam, blur=True)
fig, ax = plt.subplots(1, 1, figsize=(5, 5))
The error report points here，Could you please take a look at what the problem is?

pyplot is using numpy datatypes to work, you are passing torch datatypes, so you are getting errors.


WARN  Slow module @nuxtjs/apollo took 209076.58ms to setup.

Environment

Operating System: Linux
Node Version:     v16.18.0
Nuxt Version:     3.6.1
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Describe the bug
Slow build / dev server
Expected behaviour
regular speed
Reproduction

remove yarn.lock
add package.json

{
    "scripts": {
        "build": "nuxt build",
        "dev": "nuxt dev",
        "generate": "nuxt generate",
        "preview": "nuxt preview",
        "postinstall": "nuxt prepare"
    },
    "devDependencies": {
        "@nuxt/devtools": "latest",
        "@pinia/nuxt": "^0.4.11",
        "@types/node": "^18",
        "nuxt": "^3.6.1"
    },
    "dependencies": {
        "@nuxtjs/apollo": "5.0.0-alpha.6"
    }
}

run yarn

Additional context
No response
Logs
No response

Here is a yarn.lock which is not slow
I know, it's bloated. sorry

@Artem-Schander are you adding apollo as a dependency, not as a dev dependency?

apollo itself is not in my package.json
@nuxtjs/apollo is a dev dependency


bug:TypeError: Fetch argument

hi , I got the following issues, when I running the program. Please help fix it :) thanks.
Traceback (most recent call last):
File "/home/amo2/git/prog_nn/prog_nn.py", line 195, in
test_ProgNN()
File "/home/amo2/git/prog_nn/prog_nn.py", line 154, in test_ProgNN
feed_dict={col_0.o_n:fake1})
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 340, in run
run_metadata_ptr)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 523, in _run
processed_fetches = self._process_fetches(fetches)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 493, in _process_fetches
% (subfetch, fetch, type(subfetch), str(e)))
TypeError: Fetch argument [<tf.Tensor 'Placeholder:0' shape=(?, 128) dtype=float64>, <tf.Tensor 'Relu:0' shape=(?, 100) dtype=float64>, <tf.Tensor 'Relu_1:0' shape=(?, 64) dtype=float64>, <tf.Tensor 'Relu_2:0' shape=(?, 25) dtype=float64>, <tf.Tensor 'Softmax:0' shape=(?, 9) dtype=float64>] of [<tf.Tensor 'Placeholder:0' shape=(?, 128) dtype=float64>, <tf.Tensor 'Relu:0' shape=(?, 100) dtype=float64>, <tf.Tensor 'Relu_1:0' shape=(?, 64) dtype=float64>, <tf.Tensor 'Relu_2:0' shape=(?, 25) dtype=float64>, <tf.Tensor 'Softmax:0' shape=(?, 9) dtype=float64>] has invalid type <type 'list'>, must be a string or Tensor. (Can not convert a list into a Tensor or Operation.)

It looks like your copy of tensorflow doesn't want a list as input for the fetch argument to session.run.
What version of tensorflow are you using? To find out run
python -c "import tensorflow;print(tf.__version__)"
Right now I'm not planning to support versions of tensorflow older than 0.11 since the code is mostly a learning exercise.
Try swapping
h_0 = col_0.session.run(col_0.h, feed_dict={col_0.o_n:fake1})
for
h_0 = col_0.session.run([col_0.h], feed_dict={col_0.o_n:fake1})
on line 154 since your version of TF is asking for a Tensor. If that works you'll need to do the same for all the fetch arguments.

thanks very much for quickly replying.
after upgrading  the tf from 0.8  to 11.0, the issue have gone .
@YingHuoChong:~/git/prog_nn$ python -c "import tensorflow as tf;print(tf.version)"
0.8.0

You're most welcome!


Color-Flags are not saved

After setting any of the color flags 'bluemap-color' or 'bluemap-color-outline' there is nothing changing on the map itself.
I can set the color directly in the marker file but after changing any other flag like 'bluemap-render-height' for example, the color is set back again to the default value and not to the value defined in the region flag. The value in the region flag itself is never overriden by the way, so it appears that its just not setting the values in the marker file.
Using the latest version of all involved plugins:
BlueBridge (v1.3.1-alpha)
BlueMap (1.5.5)
WorldGuard (7.0.5)
Paper 1.16.5 (Build #779)

Hmm, I did specifically test custom color flags and they worked on my test server... I will investigate this and if I find something, a fix will be included in the next release (I won't release this fix on its own like your previous issues, because it seems pretty minor and I don't want to annoy Spigot users with a new update notification every day :D)

Okay after booting up my testserver real quick it still works without any issues for me, but I have an idea why it might not work for you:
The worldguard flags have to be hexadecimal numbers that match these formats:

"AARRGGBB" for bluemap-color.
"RRGGBB" for bluemap-color-outline
(AA would be the alpha channel)

Note that there is no "#" in front like you would put it in html tags. So if you want a red outline with a transparent blue fill color you would use:

bluemap-color-outline = "ff0000"
bluemap-color = "960000ff"

It's also case-sensitive and expects lower case characters. so "FF0000" for red would default back to the color set in the config.
If you're not sure, you can send me exactly what you tried to set your flags to, so I can take a look at it and see if something's wrong.

Ahh thanks a lot, it was because of case sensitive.
Had no idea it must be lower case, because some plugins I use are using upper case letters.
Thanks :D

Yeah I will probably make it accept both upper- and lowercase in the next update. It's a simple change and will avoid a lot of confusion in the future. Glad you got it working and thanks for all your feedback!


Angular 19

Fix #11386
Waiting some lib releases:

[ ] angular-builders https://github.com/just-jeb/angular-builders/issues/1869 (19.0.0-beta.1 available)
[x] jest-preset-angular https://github.com/thymikee/jest-preset-angular/releases

@pascalgrimaud PR ready ("@angular-builders/jest": "19.0.0-beta.1" with this beta so we can wait a release or merge)


Create USB-Support doc

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/learn-about-hardware/USB-Support
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

windows-iotcore/learn-about-hardware/USB-Support.md
:warning:Warning

Details

windows-iotcore/learn-about-hardware/USB-Support.md

Line 28: [Warning] Invalid file link:(~/../media/USB-Support/OEM-Components.png).
Line 34: [Warning] Invalid file link:(~/../media/USB-Support/OEM-suppies.png).
Line 86: [Warning] Invalid file link:(~/../media/USB-Support/config-screenshot.png).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

windows-iotcore/learn-about-hardware/USB-Support.md
:warning:Warning

Details

windows-iotcore/TOC.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/USB-Support.md

Line 28: [Warning] Invalid file link:(~/../media/USB-Support/OEM-Components.png).
Line 34: [Warning] Invalid file link:(~/../media/USB-Support/OEM-suppies.png).
Line 86: [Warning] Invalid file link:(~/../media/USB-Support/config-screenshot.png).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


bundle check issue causes ruby-lsp Gemfile dependencies to attach to wrong gem source in Gemfile.lock

Sorry for skipping the bug templates here, but this is not a problem specific to an editor, I can replicate this just by starting the LSP by hand in the appropriate project directory.
The LSP runs correctly but I cannot perform a ruby-lsp bundle update (BUNDLE_GEMFILE=.ruby-lsp/Gemfile bundle update ruby-lsp) because the contents of the generated .ruby-lsp/Gemfile.lock are not valid, as dependencies of ruby-lsp are being assigned to a gemserver which does not contain those gems.
My reproduction for the bundler issue is here:
https://github.com/rubygems/rubygems/issues/5339#issuecomment-2406116947
The bottom line is that bundle check, in whatever specific scenario ruby-lsp is using it (or at least as it occurs on my machine) is resulting in a change to Gemfile.lock which moves the transitive dependencies of ruby-lsp into the wrong rubygems source, rendering the Gemfile.lock invalid (from a dependency resolution perspective) and not able to update.
This issue impacts Bundler versions 2.2.26 to (currently, the latest) 2.5.21.
I think it's worth opening an issue here (even if it's closed immediately) as it's pretty hard to tell where the issue is coming from. I was investigating ruby-lsp source for a while before I went up to the bundler level to see if the issue was there.

Looks like they aren't able to reproduce so I'm going to have to try to write an appropriate bundler spec.

Is there anything we can do from our side or is this a Bundler bug?
The Ruby LSP invokes BUNDLE_GEMFILE=.ruby-lsp/Gemfile bundle check so that we can verify if we need to install gems before booting. I'm surprised that bundle check would modify the lockfile though. Could we pass the --frozen option to bundle check or is that only for install?

Since the PR was merged, I'll close this issue. Thanks for reporting it!


Keybase: Possibly revoked data detected

After several times resetting my key and start from scratch, when trying to open my public folder, I'm receiving this error message:

Keybase: Possibly revoked data detected. /keybase/public/{{my_id}} was modified by a revoked or bad device. Use 'keybase log send' to file an issue with the Keybase admins.

my log id: 52200e8520a5dac96a7abf1c
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5wcIkHbrxINrDl qJF8L7914KWKG7I yFhP9lYYt5fU7hW iVTVJ7RFGz3IIcm EhcRiHqJPU6PzMA 5oYv746NOUVFy8r fxax9KHYc4cMsE9 CjR6Rglknaca2b5 lUGvnVywSrn27dO Hk6uJMl23SD0ZQ3 HhmcU8KtU5lsLr5 a4AsYFQ7S6YWwGy MXVlUGBbd1daCdX kRiqmJ4OQO97AIn scTIR5IIImNULc4 ZNzE3Pdni09N1Gy SA4BFALhhW2kpUx Zl5HWoag4Lgq4bk lcll88SZQtn7WpE XRMYKMgV9T24fCM zXbHIvxv3TazJhs AWamNjHnn17pLJS ioDOXQR0baoJXC9 U03UDGSwH6PsWje rmLDggjtfTdEDlA bisBVSyRC1IroYq GkPERFRlotuxih4 H89UsAi5nPFGJC3 K1IbZ0qw8HAu3XV EQAMpcMcXU8. END KEYBASE SALTPACK SIGNED MESSAGE.

I reset your public folder.  Looks like your private folder was created recently and doesn't need a reset.  Please try them out and close this issue if things look ok.

Amazing! Works like a charm! Thanks @strib


env_*: log command output

There are two instances where we forget to check the output of a command
when it fails. This commit ensures that we log STDOUT/STDERR in the same
way that we do whenever we capture CombinedOutput. Specifically, this
commit adds logging for the output when we fail to recursively chmod
the shared directory as part of the cleanup process.
One note here: recursively chmod-ing the shared directory could easily
fail if a container saves a file as root and the CI user is not root. We
might want to forget about chmod-ing and instead do a rm -rf, which
will delete files not owned by the user executing the command.
Signed-off-by: Lucas Servén Marín<EMAIL_ADDRESS>

Yeah! It looks like the Mac tests can't pull Quay images, or so being able to pull after some time, but only with Kind! This could be some kind of ordering issue, since the Kind tests on Mac are going to be the ones that start the latest.