[BUG] Logs disappear in files other than views/init.py

Describe the bug
As part of #97 I created files other than src/python/views/__init__.py such as src/python/views/marlowe.py. Logs from these modules sometimes appear and sometimes disappear. It seems to vary depending on the type of exception. When I've researched the topic, it seems related to the use of importlib to load src/python/views/__init__.py dynamically. Log configurations often get reloaded when importlib imports code. Streamlit also dynamically re-runs code, but I don't know if that is involved.
I iterated through numerous log configurations before settling on this which does produce logs in ./dc up but not ./dc up -d && ./dc logs -f -t --tail=100.
# Make sure logs get through to STDERR
logger = logging.getLogger(__name__)
logger.setLevel(os.getenv("LOG_LEVEL", "DEBUG"))
stream_handler = logging.StreamHandler(stream=sys.stderr)
logger.addHandler(stream_handler)

Expected behavior
I expect my logs to show up when I call util.log.getChild(app_id) from other files. As demos get more complicated, we need to split files into more that __init__.py.
Observed behavior
Logs from marlowe.py don't print, or don't print from the logger given util.log.getChild(app_id). This seems to vary by the type of exception an may be a stochastic process. It behaves strangely.
To Reproduce
I need to work on this...
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
https://github.com/graphistry/graph-app-kit/blob/demo_avr/src/python/views/demo_avr/marlowe.py

OS [e.g., Ubuntu 18.04 LTS] Docker
Streamlit, version 1.22.0
How you installed: git clone; running via docker local mode ./dc up

Additional context
In general, gak behaves... haunted. I think the combination of streamlit reloading things, importlib reloading things and streamlit repeating itself for requests is causing strange side effects. Unsure if this is happening here.

This was confirmed to be a bug in utils.log.getChild() for non views modules.


Update wrapper following 8.0 RC2 release

@bot-gradle test and merge

I've triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

I've triggered a build for you.


Update batchPut to work with timestamps

Summary:
Currently batchPut fails with error Cannot read property 'updateTimestamps' of undefined if a model uses timestamps. The error results from this line, because toDynamo is called without options here.
This PR fixes the issue and adds two options to batchPut: updateTimestamps (defaults to false, because currently batchPut does not update timestamps), and updateExpires (also defaults to false).
Type (select 1):

[x] Bug fix
[x] Feature implementation
[ ] Documentation improvement
[ ] Testing improvement

[ ] Test added to report bug (GitHub issue #--- @---)
[ ] Something not listed here

Is this a breaking change? (select 1):

[ ] 🚨 YES 🚨
[x] No
[ ] I'm not sure

Is this ready to be merged into Dynamoose? (select 1):

[x] Yes
[ ] No

Are all the tests currently passing on this PR? (select 1):

[x] Yes
[ ] No

Other:

[x] I have searched through the GitHub pull requests to ensure this PR has not already been submitted
[x] I have updated the Dynamoose documentation (if required) given the changes I made
[x] I have added/updated the Dynamoose test cases (if required) given the changes I made
[x] I have run npm test from the root of the project directory to ensure all tests continue to pass
[x] I agree that all changes made in this pull request may be distributed and are made available in accordance with the Dynamoose license
[x] All of my commits and commit messages are detailed, explain what changes were made, and are easy to follow and understand
[x] I have confirmed that all my code changes are indented properly using 2 spaces
[x] I have filled out all fields above

Pull Request Test Coverage Report for Build 684

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.04%) to 85.126%

Files with Coverage Reduction
New Missed Lines
%

lib/Table.js
1
77.66%

Totals

Change from base Build 682:
0.04%

Covered Lines:
1879

Relevant Lines:
2137

💛  - Coveralls

Also please note that there are options (overwrite, condition, conditionName, conditionValues) listed in documentation for batchPut, none of which are implemented in code, if I didn't miss anything. I suppose they need to be either removed or implemented. (I should probably create an issue for this.)

@dolsem I’m on my phone currently. But can we figure out why there are so many random changes? The changes to like the package.json version shouldn’t be in here at all. Nor should the change log stuff. Those look like recent changes to Dynamoose that are already in the repo.
Super confused about why that is in the diff of this PR. But on my phone so might be my mistake.

@dolsem I'm not sure how big of an issue it is. But I'm concerned about merging it in without it, and it also makes it a lot harder to review.
I think what I would do to try to fix it is pull down the latest version of this repo's master branch. Then create a new branch off of that version (not your fork master branch), and make your changes there and make a new PR.
It looks like you used your master branch of your fork for this which I'm assuming is why it's having problems, maybe?? I'd try creating a new branch off of the Dynamoose master branch to see if that works. I think if you create the branch off of your fork the same problem will happen.


Question: Can tasks be scheduled in distributed systems with multiple workers on different machines.

Looking at the documentation and blog-post as well as skimming through the code, I wasn't able to answer the question if fang allows scheduling tasks across distributed systems, with multiple workers on different machines.
Is there some synchronization to make this work and to prevent duplicate work across multiple workers, as well as a mechanism for another worker to pick up a task if the worker that started it dies before reporting back the task as finished?

Looking at the documentation and blog-post as well as skimming through the code, I wasn't able to answer the question if fang allows scheduling tasks across distributed systems, with multiple workers on different machines.

Fang uses a PostgreSQL db as a task queue. As long as all workers access the same PostgreSQL instance, workload will be distributed across all running workers
Each worker fetches and locks a task, so tasks are executed only once.

Is there some synchronization to make this work and to prevent duplicate work across multiple workers, as well as a mechanism for another worker to pick up a task if the worker that started it dies before reporting back the task as finished?

The task will stay forever is in progress state. I think it's a developer's responsibility to make sure there are no panics in application logic
If a task returns Err(FangError), it will be retried


btrfs file system unmounts itself after a brief delay

After a short delay from user app start the btrfs file system unmounts for no obvious reason, resulting in all units that depend on the mount exiting, i.e. supervisor, docker, openvpn.
This renders the device 'soft-bricked' and therefore unusable. Additionally, attempts to mount the btrfs partition to /mnt/data result in no error, no dmesg entries but no mounting actually taking place. Attempting to mount the file system to another path succeeds, though any attempt to 'cheat' by symlinking, etc. results in the same issue recurring.
This has been reproduced on production (1.1.0 fido) and tip (1.8.0) resin OS.

This issue was moved to resin-os/resinos#30


JGRP-2286 VERIFY_SUSPECT can return false positives if member is killed and immediately restarted

https://issues.jboss.org/browse/JGRP-2286

@belaban Please review.

@belaban @pferraro I'm not sure this fixes anything... the logs attached in https://issues.jboss.org/browse/ISPN-9517 show that the old node is removed from the view just fine

@danberindei is right. So long as VERIFY_SUSPECT sends ARE_YOU_DEAD messages as unicasts, they should be ignored by the transport of the reincarnated member via TP.unicastDestMismatch(...)  @belaban You can revert this.

Reverted

Hmm, this is not true:
public boolean unicastDestMismatch(Address dest) {         return dest != null && !(Objects.equals(dest, local_addr) || Objects.equals(dest, local_physical_addr));     }
If dest != local_addr, but dest == local_physical_addr, then the message would not get discarded... not sure why I once added the second part of the condition...

@belaban Would that mean this still be an issue when use_ip_addrs is enabled?

@belaban could it be because some protocols (maybe discovery?) need to send messages to a particular physical address? I would expect this kind of usage to be quite limited though, and the protocols that use physical addresses should have some kind of protection against reincarnation themselves.
OTOH I'm not sure VERIFY_SUSPECT.use_icmp could ever work... any time the JVM crashes but the machine stays up, the node is not going to be removed from the view. If another node is started on the same machine, it won't remove the old node from the view either.

@danberindei Yes, you're right: TCPPING needs to send messages to physical addresses when iterating through initial_hosts

OK @pferraro Have you come up with a reproducer?
So the current logic does not discard a message if the UUID is the same as the local address OR the destination is a physical address and the local physical address is the same. This means reincarnation is possible if the destination is a physical address and it equals the local physical address.
However, this should only be possible in TCPPING. That's the only case where we ever send physical addresses rather than UUIDs in a message.


fix compilation problems

As #24 points out, this fix some compilation problems.

Sorry for the late late late late reply....
I've been traveling for a really long time and haven't got the time to maintain this project.
Thank you so much for the fix !!!


Clear display on shutdown

Good OPSEC would be to clear the eInk display on device shutdown.

+1  Was looking for a clear script.

+1 Was looking for a clear script.

In theory, I think main_loop.epd.Clear() should work, around line 368 in display.py -- but I haven't been able to get that to anything.

Or better allow to set custom screen image :) then you can set empty :)

This was brought up before
https://github.com/infinition/Bjorn/issues/60


Image generation fails if image size not set with (Azure) OpenAI

Bug description
The image generation fails if image size not set e.g. via spring.ai.image.options.openai.size with (Azure) OpenAI with the following error.
org.springframework.ai.retry.NonTransientAiException: 400 - {
  "error": {
    "code": null,
    "message": "'nullxnull' is not one of ['256x256', '512x512', '1024x1024', '1024x1792', '1792x1024'] - 'size'",
    "param": null,
    "type": "invalid_request_error"
  }
}

It can be fixed by replacing lines https://github.com/spring-projects/spring-ai/blob/e5410d7e8da170c546a79852c2234c2be5a80b97/models/spring-ai-openai/src/main/java/org/springframework/ai/openai/OpenAiImageOptions.java#L156  and https://github.com/spring-projects/spring-ai/blob/e5410d7e8da170c546a79852c2234c2be5a80b97/models/spring-ai-openai/src/main/java/org/springframework/ai/openai/OpenAiImageOptions.java#L177 with this.size = this.getSize();
Has to be also fixed for AzureOpenAiImageOptions.
Environment
Spring AI M3/M4, OpenAi, Dall-E 3
Steps to reproduce
Use (Azure) OpenAI and Dall-E 3, and execute an image generation request and don't set spring.ai.image.options.openai.size.
Expected behavior
Image generation should work without setting spring.ai.image.options.openai.size.

According to OpenAI documentation, the size can be set to null; in that case, it will fall back to 1024x1024.
However, variations like nullx1024 or 1024xnull are considered invalid dimensions.
I will fix it this week.

Issue reproduced using spring-ai 1.0.0-M4.
`
@SpringBootTest
class ImageGenerationTest {
@Autowired
private ImageModel imageModel;

@Test
void shouldReturnImageUrl() {
    ImagePrompt imagePrompt = new ImagePrompt("A cartoon depicting a parrot on the shoulder of a pirate.");
    ImageResponse imageResponse = imageModel.call(imagePrompt);
    Image image = imageResponse.getResult().getOutput();
    assertThat(image.getUrl()).isNotNull();
}

}
`
Exception:
`
org.springframework.ai.retry.NonTransientAiException:
400 - {
"error": {
"code": null,
"message": "'nullxnull' is not one of ['256x256', '512x512', '1024x1024', '1024x1792', '1792x1024'] - 'size'",
"param": null,
"type": "invalid_request_error"
}
}
`

PR is open at https://github.com/spring-projects/spring-ai/pull/1840
For some reason, I am not able to run all tests locally.

I only ran into this issue after including ImageOptions in my ImagePrompt to specify the style (and nothing else).
It looks like OpenAiImageOptions.mergeOptions will lead to setHeight/setWidth being called with null in that case, which will set the size to "nullxnull" which was previously null.
Maybe size should be set to null in setHeight/setWidth when these are called with null?

I only ran into this issue with M4 after including ImageOptions in my ImagePrompt to specify the style (and nothing else).
It looks like OpenAiImageOptions.mergeOptions will lead to setHeight/setWidth being called with null in that case, which will set the size to "nullxnull" which was previously null.
Maybe size should be set to null in setHeight/setWidth when these are called with null? Or maybe get rid of size and setSize() and have getSize() return null if either width or height are null?

Hi @henningSaulCM  have you seen the pull request #1840?
The size is only updated when width and height are not null.

Hi @dennysfredericci,

Hi @henningSaulCM have you seen the pull request https://github.com/spring-projects/spring-ai/pull/1840?
No, sorry, I must have missed it in the comments. Was wondering if the PR should show up in the right hand sidebar in the Github browser UI for the issue under "Development" which currently says "No branches or pull requests".

Anyway, thanks for the fix!

Hi @dennysfredericci,

Hi @henningSaulCM have you seen the pull request #1840?

No, sorry, I must have missed it in the comments. Was wondering if the PR should show up in the right hand sidebar in the Github browser UI for the issue under "Development" which currently says "No branches or pull requests".
Anyway, thanks for the fix!

Ok, and I guess the maintainers could link the PR with this issue.

@markpollack  since #1840 is closed we can close this issue as well.


Add caput callback support

This requires some research

Isn't this already closed by PR #98?

Yes


Support iPhone XS, iPhone XS Max and iPhone XR

Addresses #235
Basically always toLowerCase device names when comparing, because depending on where the device name comes from there are many different formatting, i.e.:

iPhone Xs Max
iPhone XS Max
iPhone XS MAX

Also normalized the ʀ character (R != ʀ). Comparing is always false otherwise even when toLowerCase().
Note for Cordova users:
Until this is merged / released and Cordova updates its dependencies, you may want to add ios-sim to your devDependencies and replace in your workflow:
cordova run --target=DEVICE_TYPE_ID

by
ios-sim launch platforms/ios/build/emulator/YOUR_APP.app --devicetypeid=DEVICE_TYPE_ID

I just integrated #239 for ES6 support which is failing your changes. Rebase from master, thanks!

No need for rebase, I did it through Github. Now your PR is failing the eslint check, can you do:
npm install
npm run eslint -- --fix

Done 🤘

Thanks @EtienneLem for fixing this!


Clappr won't play HLS stream

Hello,
I've been trying to get my HLS stream to work.  If I upload a .m3u8 file to my server and set Clappr's source to it, I can stream it fine, but when using PHP to stream the file, it fails.
VLC plays it and hls.js plays it, but Clappr does not.
Does Clappr check the filename to see if it's a m3u8 file or ts file?  Or does it check the header?
Headers I am using:
  header("HTTP/1.1 200 OK");
   header("Accept-Ranges: bytes");
   header("Pragma: no-cache");
   header("Expires: 0");
   header("Connection: close");
   header("Cache-Control: private, no-cache, no-store, s-maxage=0, max-age=0, must-revalidate");
   header("Content-Length: $size");
   header("Access-Control-Allow-Origin: *");
   header("Access-Control-Allow-Credentials: true");
   header("Access-Control-Allow-Methods: GET, POST, OPTIONS");

m3u8 file:
header("Content-Type: application/x-mpegURL");
.ts files
header("Content-Type: video/MP2T");
Thanks!

UPDATE:
Clappr apparently does want a .m3u8 or .ts extension instead of checking the header.  That's okay, I just used Apache rewrite to send the filenames to my PHP script.
:-)

Updated


As a user with dietary restrictions, I can exclude meals that does not fulfill my dietary requirements.

So that I only get specific meals with regards to my meal type, and do not choose the wrong meals.

Fixed based on #106


IsBinary determination for console not working perfectly

We're getting too much binary data in the console output...
Specifically it was during a git push command in the context of cribl stream cloud processes.  The console output of git push itself looks fine, but the console of subsequent child processes do not look so great.  Here's one of the child procs that looks wonky /usr/libexec/git-core/git send-pack --stateless-rpc --helper-status --thin --no-progress https://git-blahblah.us-west-2.amazonaws.com/v1/repos/blahblah-leader/ --stdin

For 2. above, something like this might be what's required in doReset() in src/wrap.c:

// set stdout/stderr to unknown
setFSContentType(stdout, FS_CONTENT_UNKNOWN);
setFSContentType(stderr, FS_CONTENT_UNKNOWN);

So I was able to repro the original problem by extending our console integration test with a new test case.   In this test case I use apache as an http frontend to a git repo.  Then in a working sandbox that's configured to use this http origin, when I scope git push it results in a process tree that includes git send-pack as originally observed.
The process tree I see from scoping git push (pid, cmd):
172, git push --set-upstream origin master
173, /usr/lib/git-core/git-remote-http origin http://localhost/git/myrepo.git
178, /usr/lib/git-core/git send-pack --stateless-rpc --helper-status --thin --progress http://localhost/git/myrepo.git/ --stdin
180, /usr/lib/git-core/git pack-objects --all-progress-implied --revs --stdout --thin --delta-base-offset --progress

The console data reported by these processes in time order:
{
  "sourcetype": "console",
  "_time":<PHONE_NUMBER>.052664,
  "source": "stdout",
  "host": "4d654cb84bbc",
  "proc": "git-remote-http",
  "cmd": "/usr/lib/git-core/git-remote-http origin http://localhost/git/myrepo.git",
  "pid": 173,
  "data": {
    "message": "stateless-connect\nfetch\noption\npush\ncheck-connectivity\n\nok\nok\n"
  }
}
{
  "sourcetype": "console",
  "_time":<PHONE_NUMBER>.834833,
  "source": "stdout",
  "host": "4d654cb84bbc",
  "proc": "git",
  "cmd": "/usr/lib/git-core/git pack-objects --all-progress-implied --revs --stdout --thin --delta-base-offset --progress",
  "pid": 180,
  "data": {
    "message": "Binary data detected--- message"
  }
}
{
  "sourcetype": "console",
  "_time":<PHONE_NUMBER>.069224,
  "source": "stderr",
  "host": "4d654cb84bbc",
  "proc": "git",
  "cmd": "/usr/lib/git-core/git pack-objects --all-progress-implied --revs --stdout --thin --delta-base-offset --progress",
  "pid": 180,
  "data": {
    "message": "Enumerating objects: 4, done.\nCounting objects:  25% (1/4)\rCounting objects:  50% (2/4)\rCounting objects:  75% (3/4)\rCounting objects: 100% (4/4)\rCounting objects: 100% (4/4), done.\nDelta compression using up to 8 threads\nCompressing objects:  25% (1/4)\rCompressing objects:  50% (2/4)\rCompressing objects:  75% (3/4)\rCompressing objects: 100% (4/4)\rCompressing objects: 100% (4/4), done.\nWriting objects:  25% (1/4)\rWriting objects:  50% (2/4)\rWriting objects:  75% (3/4)\rWriting objects: 100% (4/4)\rWriting objects: 100% (4/4), 17.16 MiB | 19.81 MiB/s, done.\nTotal 4 (delta 0), reused 0 (delta 0)\n"
  }
}
{
  "sourcetype": "console",
  "_time":<PHONE_NUMBER>.063856,
  "source": "stdout",
  "host": "4d654cb84bbc",
  "proc": "git",
  "cmd": "/usr/lib/git-core/git send-pack --stateless-rpc --helper-status --thin --progress http://localhost/git/myrepo.git/ --stdin",
  "pid": 178,
  "data": {
    "message": "009d00950000000000000000000000000000000000000000 08582e37918792e3d2d1748331b7ff3ef32bc56a refs/heads/master\u0000 report-status side-band-64k agent=git/2.25.100002004PACK\u0000\u0000\u0000\u0002\u0000\u0000\u0000\u0004�\

Leaving out lots of console messages from 178 that contain a bunch of encoded binary data.
02��u�>B���S����\r��b�3OT�-���y�0����\u00142TƧ00000000ok refs/heads/master\n"
  }
}
{
  "sourcetype": "console",
  "_time":<PHONE_NUMBER>.499356,
  "source": "stdout",
  "host": "4d654cb84bbc",
  "proc": "git-remote-http",
  "cmd": "/usr/lib/git-core/git-remote-http origin http://localhost/git/myrepo.git",
  "pid": 173,
  "data": {
    "message": "ok refs/heads/master\n\n"
  }
}
{
  "sourcetype": "console",
  "_time":<PHONE_NUMBER>.501082,
  "source": "stdout",
  "host": "4d654cb84bbc",
  "proc": "git",
  "cmd": "git push --set-upstream origin master",
  "pid": 172,
  "data": {
    "message": "Branch 'master' set up to track remote branch 'master' from 'origin'.\n"
  }
}
{
  "sourcetype": "console",
  "_time":<PHONE_NUMBER>.499689,
  "source": "stderr",
  "host": "4d654cb84bbc",
  "proc": "git",
  "cmd": "git push --set-upstream origin master",
  "pid": 172,
  "data": {
    "message": "To http://localhost/git/myrepo.git\n * [new branch]      master -> master\n"
  }
}

👉  So this console output above shows that our library is doing what it's designed to, but illustrates that the design didn't account for console applications A) starting with text, B) switching to binary, and C) switching back to text.  👈  As it turns out here, our theory about our fork handling is something we should address, but has no part in describing why we're getting all this console data in this case.
Our plan to address this does not include a user-configurable policy for this at this time.  Additional configuration could be useful if users have problems in console data that they need to address, but it's asking more than seems reasonable of the users.  Even if we provided a policy selection for console settings, I think there's no a priori way to know what processes would need what settings.
So the plan is to run the isBinary check on every packet.  If binary data is seen during a packet check, we will output one "Binary data detected" message.  We will not send the message again for that process unless subsequent packets are text and then revert to binary again.  So if five packets arrive and we determine that they're:
(1)text->(2)binary->(3)binary->(4)text->(5)binary
So with this example we plan so produce a Binary data detected on (2), not for (3), and then again on (5).

Ok.  Starting from the 1.0.0 branch, the last couple commits created an AppScope build which implements what I talked about in my last comment above.
It’s not an official release, but can be used to evaluate how removing binary data from console can help.
It’s available here:
https://cdn.cribl.io/dl/scope/bug/869-ongoing-isBinary-determination/linux/x86_64/scope
https://cdn.cribl.io/dl/scope/bug/869-ongoing-isBinary-determination/linux/aarch64/scope
Since it’s not an official release it identifies itself like this:
ubuntu@ip-10-8-107-159:temp$ ./scope version
Version: e0e2cf2
Build Date: 2022-04-09T22:06:23Z
In a as-yet-unpublished integration test we have that executes the same git push
process tree that we’ve been observing, it reduced the volume of console data from
27,958,398 bytes that primarily contains not-so useful data like this:
qӏR??\f?9+??<??PًYa?wL??sP??E?+h=;\u000f`s6Ҙ)???+??\n\t?\u000b5

to 81,816 bytes that primarily contains data like this which should be less disruptive, I hope:
Binary data detected--- message2004Binary data detected--- message0cc6

(the git process in question is alternating between putting text and binary onto the console,
and we’re now replacing the binary with a “Binary data detected---” message.)

The above commit is going to be "redone" on the master branch in the next commit.
Additionally the next commit includes:

unit and integration tests
support for environment setting SCOPE_ALLOW_BINARY_CONSOLE=true which turns off our redaction of binary data
rename of message from "Binary data detected--- message" to "-- binary data ignored --".  This change was made because it seems more appropriate for situations where data is switching back and forth between text and binary.


fix: removed extra apostrophe

...after it's' created. -> ...after it's created.

@approved : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Couple MaxRSS/MaxVSize to Memory updates for Resubmission

Fixes #8293
Performance arguments not provided are not going to be touched.

There is still this problem with the web UI assignment: #8236
but this one will have to wait until the next month.

test this please


Improve Table Payouts per issue #13

See Issue #13 for discussion.
This changes Table.payouts to store all bet information that varies by table on the Table (ex. Field Payouts, Fire Bet Point payouts, etc.) It also makes table an attribute of Bet in order to access those variables when doing the update logic. It also makes Bet.payout_ratio a property of bet instead of an attribute so for bets where the payout ratio varies based on table settings or other logic than a static number.

@skent259 for some reason there was two of each of your comments, so I deleted one of each and replied to the others.

Sorry about the dual comments, not sure why that happened.
I'm happy to merge this and follow-up the requested changes in #19, given that my comments were all minor and there's a lot of good work in this to incorporate.  @amortization let me know if that works for you


KOGITO-6421: Unskip DMN New Expression editor tests

@jomarko Sonar job seems stuck. Do you know what can be happening?

@tiagobento infrastructure for jenkins machine provisioning is broken, I can not fix it. Please merge.

The (build) kie-tools-stunner-editors check has failed. Please check the logs.


nuclei: 3.1.6 -> 3.1.7

Diff: https://github.com/projectdiscovery/nuclei/compare/v3.1.6...v3.1.7
Changelog: https://github.com/projectdiscovery/nuclei/releases/tag/v3.1.7
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 283077 run on x86_64-linux 1

1 package built:

nuclei


deprecated

The official addon doesn't have the hivemq webclient.
In stead of removing the add-on, could you maybe only remove the mqtt broker part?

Nope, the webclient causes quick a few issues and it one of the reasons to deprecate the add-on in the first place.
Other options are: The now builtin available MQTT tools inside the Home Assistant developers tab, MQTTExplorer and the CLI tools available in the SSH & VSCode add-ons.


Please clarify URL recommendations

I am confused with respect to json:api's recommendations for URLs. The recommendation mentions that the type values and  member names (of relationships and attributes) should ripple through to URLs:

It is recommended that the URL for a collection of resources be formed from the resource type.
...
It is recommended that a related resource URL be formed by appending the name of the relationship to the resource’s URL.

In turn, there are explicit recommendations for member names: use camelCase (#1297).  For type values there are no explicit recommendations, but for consistency to me it makes sense to use the same convention here, because else you could end up having an API response that contains both kebab-case and camelCase. The idea of consistency between type vales and member names is supported by the spec:

The values of type members MUST adhere to the same constraints as member names.

So my reading is that if we choose to adhere to the extra camelCase constraint, it should also apply to type values.
So far all of this seems to suggest that urls should be camelCased too (i.e. /myModels/1/relationships/toOneRelationship). However, the async processing example does not seem to follow the outline above because queue-jobs is in kebab-case in both the type value and the URL.
What does this imply? Does it imply that type values can remain in kebab-case but member names should be pascalCase? This would mean we end up having kebab-case and pascalCase in both the api output and URL, which is not desirable? Or is it simply an example that choose to not follow the recommendations and in which kebab-case is used everywhere?
I'm trying to figure out what to do with my URLs. I understand these are just recommendations and I am free to do as I like, but I'm working on a json:api implementation (JsonApiDotNetCore) and I want to stay as close as possible to the specs and recommendations. Basically, the questions posed by @antonkomarev  in https://github.com/json-api/json-api/issues/1255 at the bottem are pretty much the open questions I have too

Personal stance:  I vote for having camelCase everywhere.
Two main arguments: (1) consistency is key and (2) readability/crawlability is not as important
1. Consistency is key
I think json:api should aim at maximizing consistency, which is an argument in favour of having camelCased urls:

query parameter part of url: having kebab-case when filtering on attributes and relationships (?filter[first-name]=x) while these attributes in the document body are camelCase ( attributes: { "firstName": "x" ...) is not consistent. Thus, go for camelCase in query parameters too
path part of url:  Then it follows that relationship member names are camelCase in the body document as well as in the query parameters, so having them kebab-cased in the path part of the url would be inconsistent. So, prefer .../relationships/toOneRelationship?include=toManyRelationship over .../relationships/to-one-relationship?include=toManyRelationship for consistency.
Since a part of the url path is camelCased, all of it should be camelCased: myModels/relationships/toOneRelationship?include=toManyRelationship.

2. Readability/crawlability is not as important

Some people would argue that kebab-case simply looks nicer and is easier to read for humans. I agree with them. But that's the thing with API urls: humans will never have to look at it, except when writing the javascript that will do the reading for them
In this stackoverflow post it is argued that for "public/external" webpages, kebab-case allows for better crawlability, and to keep it simple it is best to just stick with that for "private/internal" webpages. But here we're designing urls to be used for an entirely different content type which wont be crawled by search engines.

Personally I'm using camelCase for everything except resource types. Types in my APIs have UpperCase.

So your routes look like /myModel/1/relationships/toOneRelationship but the payload contains { "type": "MyModel"}?
What is the motivation for having uppercase in the document body?

/articles/1/relationships/exampleRelationship
/articles?filter[exampleRelationship][type]=UpperCaseResourceType
Don't think about articles in URI as about Article type. URI could be like this:
/someRandomName?filter[exampleRelationship][type]=UpperCaseResourceType
Or even like this:
/fsdkfjdskflsdklf?filter[exampleRelationship][type]=UpperCaseResourceType
But it could return Article resources.

There are cases when one endpoint could return different resource types, then you cannot strictly follow this rule. I'm always trying to follow this concept to make API developer friendly, but sometimes it's impossible.
I highly recommend you to read this set of articles: https://blog.michaelhibay.com/2017/03/29/development-guidelines-for-hypermedia-apis/

The specification does not place any normative constraints on the URL-space itself, only how the URLs returned in the various links structures should behave.
This is good, since it avoids misleading API consumers into thinking URLs can be constructed by clients.
It would be better if this separation were more clear (in fact, I thought were was something about this, but I can't find it now). The presence of recommendations about URL structure in the Recommendations page is... unfortunate.

Don't clients need to be able to construct URLs from resource identifier objects?

Actually, no.  Your example of a relationship can provide the URLs required in the links object, and arguably should, especailly if the relevant resources are not included in the response.

Your example of a relationship can provide the URLs required in the links object,

If a relationship listed, say, 10 resource identifier objects, then how would the 10 corresponding URLs be listed within the relationship's links object? How would the correspondence between each object's type/id combination and its URL be represented?
Or are you referring to links objects in the resource identifier objects (which I don't think I've seen in any of the spec's examples)?


api token error

Hi,
After upgrade doltlab, we are now getting below error. What is the reason of this error, it is not understandable. Can you help?
{"query_execution_status":"Error","query_execution_message":"apitoken_db: API Token with matching ID not found","repository_owner":"xxx","repository_name":"yyy","commit_ref":"main","sql_query":"SHOW FULL TABLES WHERE Table_Type = 'BASE TABLE'","schema":[],"rows":[]}

@pirimoglu this bug is fixed in DoltLab v1.0.3, sorry for the inconvenience!


Vector Store polish

general low hanging optimization and polish

refactored the VectorStore implementations so that if they implemented InitializingBean, they now implement ApplicationListener<ApplicationReadyEvent>, instead. The result is that the vector stores now initialize their own state after the boot app has started. this is important because a) nobody wants to wait 2x as long for their app to run SQL statements or create collections or whatever, especially when developing, and nobody wants their Kubernetes health check to fail for stuff that can be done after the application's fully online.
who is the author of ChromaVectorStore? Should we add their author tag? do we need ChromaVectorStore#SIMILARITY_THRESHOLD_ALL and ChromaVectorStore#SIMILARITY_THRESHOLD_ALL
renamed the module/artifact for spring-ai-azure-vector-store to spring-ai-azure-store to match other vector stores
renamed a few directories to match their artifactIds
made sure pom.xml name elements looked consistent  (try running ./mvnw clean and you'll see the output is nicer)

Half of the changes in the PR were applied, however the approach to initializing the vector store though the use of a Spring Boot application event is concerning as ideally we do not want to take a dependency in the vector stores on Spring Boot.  There is perhaps another approach that can be used.  Moving this to M2 to look into it more deeply another time.

I think all topics/feature changes in this PR have been addressed except for the default in the common properties
public class CommonVectorStoreProperties {

	private boolean initializeSchema = true;

     ...
}

Closing this issue and opening up another now to address changing the default initialization from true to false.

https://github.com/spring-projects/spring-ai/issues/907 is the new issue.


Restore failure on recently migrated endpoint

I recently upgraded this endpoint to test migration from 14.04 to 16.04. The backups have doubled in size since before the migration, and (more importantly) the first restore hit the following error:
++ flynn-host bootstrap --peer-ips=<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS> --from-backup /mnt/flynn-restore-source --timeout 3600
+ bootstrap_output='panic: assignment to entry in nil map [recovered]
        panic: assignment to entry in nil map

goroutine 1 [running]:
panic(0xa58280, 0xc4203010d0)
        /tmp/tmp.2C8TIsBXaF/src/github.com/flynn/flynn/util/_toolchain/go/src/runtime/panic.go:500 +0x1a1
github.com/flynn/flynn/pkg/shutdown.(*handler).exit(0xc420017830, 0x0, 0x0, 0x0, 0xa58280, 0xc4203010d0)
        /tmp/tmp.2C8TIsBXaF/src/github.com/flynn/flynn/pkg/shutdown/handler.go:69 +0x222
github.com/flynn/flynn/pkg/shutdown.Exit()
        /tmp/tmp.2C8TIsBXaF/src/github.com/flynn/flynn/pkg/shutdown/handler.go:40 +0x6a
panic(0xa58280, 0xc4203010d0)
        /tmp/tmp.2C8TIsBXaF/src/github.com/flynn/flynn/util/_toolchain/go/src/runtime/panic.go:458 +0x243
github.com/flynn/flynn/host/cli.runBootstrapBackup.func2(0xc4202187e0, 0xc420231740)
        /tmp/tmp.2C8TIsBXaF/src/github.com/flynn/flynn/host/cli/bootstrap.go:247 +0x204
github.com/flynn/flynn/host/cli.runBootstrapBackup(0xc420254000, 0x9deb, 0x9feb, 0x7ffc04bb9860, 0x19, 0xc420218420, 0x0, 0x0, 0xc4202263c0, 0x3, ...)
        /tmp/tmp.2C8TIsBXaF/src/github.com/flynn/flynn/host/cli/bootstrap.go:268 +0xd2ab
github.com/flynn/flynn/host/cli.runBootstrap(0xc4201f55c0, 0x226, 0xc42005f3e0)
        /tmp/tmp.2C8TIsBXaF/src/github.com/flynn/flynn/host/cli/bootstrap.go:120 +0x612
github.com/flynn/flynn/host/cli.Run(0x7ffc04bb9813, 0x9, 0xc42007b480, 0x5, 0x8, 0xc42004bc01, 0xb7f610)
        /tmp/tmp.2C8TIsBXaF/src/github.com/flynn/flynn/host/cli/cli.go:62 +0x4b4
main.main()
        /tmp/tmp.2C8TIsBXaF/src/github.com/flynn/flynn/host/host.go:155 +0x4d4'

https://gist.github.com/3dc460e283b48aca703ef5bd2db3f449 is the debug-info gathered. I am trying again to see if this repeats.

It does repeat: https://gist.github.com/5c4522e7aeadd302a1e00293ac3ae5df

@temujin9 what version of Flynn are you bootstrapping? I can't see how that code would panic unless you are using an old bootstrap manifest.

I'm using FLYNN_VERSION="v20170109.0" here.

Are you still encountering this issue with v20170121.0?

Experiencing the same issue, using v20170116.0p2 with a backup that was created with v20161218.1.

@RobinDaugherty can you post the exact error output?

I don't see anything in the release notes that addresses backup restoration since v20170116.0p2. @titanous are you asking about v20170121.0 because there's something in that release that may fix it? I just haven't wanted to go beyond the latest stable without a good reason.

panic: assignment to entry in nil map [recovered]
    panic: assignment to entry in nil map

goroutine 1 [running]:
panic(0xa58300, 0xc4202ef270)
    /tmp/tmp.225plNbtkw/src/github.com/flynn/flynn/util/_toolchain/go/src/runtime/panic.go:500 +0x1a1
github.com/flynn/flynn/pkg/shutdown.(*handler).exit(0xc420063830, 0x0, 0x0, 0x0, 0xa58300, 0xc4202ef270)
    /tmp/tmp.225plNbtkw/src/github.com/flynn/flynn/pkg/shutdown/handler.go:69 +0x222
github.com/flynn/flynn/pkg/shutdown.Exit()
    /tmp/tmp.225plNbtkw/src/github.com/flynn/flynn/pkg/shutdown/handler.go:40 +0x6a
panic(0xa58300, 0xc4202ef270)
    /tmp/tmp.225plNbtkw/src/github.com/flynn/flynn/util/_toolchain/go/src/runtime/panic.go:458 +0x243
github.com/flynn/flynn/host/cli.runBootstrapBackup.func2(0xc42020a780, 0xc4202254c0)
    /tmp/tmp.225plNbtkw/src/github.com/flynn/flynn/host/cli/bootstrap.go:247 +0x204
github.com/flynn/flynn/host/cli.runBootstrapBackup(0xc420242000, 0x9e33, 0xa033, 0x7ffd5878c84c, 0x17, 0xc42020a3c0, 0x0, 0x0, 0xc42023e240, 0x3, ...)
    /tmp/tmp.225plNbtkw/src/github.com/flynn/flynn/host/cli/bootstrap.go:268 +0xd2b0
github.com/flynn/flynn/host/cli.runBootstrap(0xc4201e3680, 0x226, 0xc42008fb30)
    /tmp/tmp.225plNbtkw/src/github.com/flynn/flynn/host/cli/bootstrap.go:120 +0x612
github.com/flynn/flynn/host/cli.Run(0x7ffd5878c834, 0x9, 0xc4201176c0, 0x4, 0x4, 0xc420045c01, 0xb7fcc0)
    /tmp/tmp.225plNbtkw/src/github.com/flynn/flynn/host/cli/cli.go:62 +0x4b4
main.main()
    /tmp/tmp.225plNbtkw/src/github.com/flynn/flynn/host/host.go:155 +0x4d4

@RobinDaugherty yes, there were a couple fixes that might be related, please try the latest nightly:
https://github.com/flynn/flynn/commit/327da97802f847edf9460bd7874caa16075cc5ee
https://github.com/flynn/flynn/commit/ec7698ca7562df7b71a51b57e388999812aa8b28

On version v20170207.0:
panic: assignment to entry in nil map [recovered]
    panic: assignment to entry in nil map

goroutine 1 [running]:
panic(0xa5ae40, 0xc4203085f0)
    /tmp/tmp.rJNe8qvsER/src/github.com/flynn/flynn/util/_toolchain/go/src/runtime/panic.go:500 +0x1a1
github.com/flynn/flynn/pkg/shutdown.(*handler).exit(0xc420017860, 0x0, 0x0, 0x0, 0xa5ae40, 0xc4203085f0)
    /tmp/tmp.rJNe8qvsER/src/github.com/flynn/flynn/pkg/shutdown/handler.go:69 +0x222
github.com/flynn/flynn/pkg/shutdown.Exit()
    /tmp/tmp.rJNe8qvsER/src/github.com/flynn/flynn/pkg/shutdown/handler.go:40 +0x6a
panic(0xa5ae40, 0xc4203085f0)
    /tmp/tmp.rJNe8qvsER/src/github.com/flynn/flynn/util/_toolchain/go/src/runtime/panic.go:458 +0x243
github.com/flynn/flynn/host/cli.runBootstrapBackup.func2(0xc4200d7f80, 0xc420195e80)
    /tmp/tmp.rJNe8qvsER/src/github.com/flynn/flynn/host/cli/bootstrap.go:247 +0x204
github.com/flynn/flynn/host/cli.runBootstrapBackup(0xc420254000, 0x9deb, 0x9feb, 0x7ffd916e67b3, 0x17, 0xc4200d7bc0, 0x0, 0x0, 0xc420169290, 0x3, ...)
    /tmp/tmp.rJNe8qvsER/src/github.com/flynn/flynn/host/cli/bootstrap.go:268 +0xd2e7
github.com/flynn/flynn/host/cli.runBootstrap(0xc4201fd440, 0x226, 0xc4200e2a50)
    /tmp/tmp.rJNe8qvsER/src/github.com/flynn/flynn/host/cli/bootstrap.go:120 +0x612
github.com/flynn/flynn/host/cli.Run(0x7ffd916e679b, 0x9, 0xc4200dbe40, 0x4, 0x4, 0xc420047c01, 0xb82fb8)
    /tmp/tmp.rJNe8qvsER/src/github.com/flynn/flynn/host/cli/cli.go:62 +0x4b4
main.main()
    /tmp/tmp.rJNe8qvsER/src/github.com/flynn/flynn/host/host.go:156 +0x4d4

@RobinDaugherty Would you please extract flynn.json from the backup (a gzipped tarball) and email it to<EMAIL_ADDRESS>Ideally redact any keys you see in there before sending it.

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


Show current file name and path somewhere

When you have a file open you cannot see the current path anywhere (e.g. status bar, title bar, some info dialog, ...).
Sometimes you want to know where the current file is stored on the file system. It should be possible to see/check this.

We are showing that as part of the tab (mouseover should show the file path). That is a standard behavior for Editors (Netbeans, Sublime Text, ...). Where else should we display that information?

Ah ok - I actually didn't recognize it there. Sorry. I personally would prefer something copy & pastable (to be able to navigate there quickly) - but that is much less urgent - so we can also close this issue.


Replaced the ES File Explorer with Acode Editor

I updated the software preparation page in guide section by replacing ES File Explorer with Acode Editor as a preferred code editor for making add-ons on Android devices and also also updated Addon obfuscator link

Can you motivate this change? Why is it better?

It has directory view, autocompletions, suggestions and also tell where  the syntax error is present and many more features.


How to use

Hello.
I did not understand how to launch and configure Winbar.
Can you explain this in detail?

Hi Andrew - ensure you have winbar and its associated CLI installed. The easiest way is to get off the Releases page, but if you prefer compiling from source, see Compiling from source.
Adding to PATH
If you compiled from source, you can ignore the following.
You need to move the executables into a folder that's available in your PATH environment variable or make a new directory and add that into the PATH variable:

I'm currently on a Windows 11 system, but I assume it'll be the same on Windows 10: in the Start menu, search "Edit the system environment variables" OR simply "path" and click the (typically) first option. This will open up Control Panel.
Click the "Environment Variables..." button at the bottom of the window. This will open up another window showing you all of your set environment variables.
Look for "Path" under System variables - then double click it (or click Edit at the bottom).
Another window will open at this point - from here you can see a list of folders in your Path. You can choose to either move the executables into one of these folders (not recommended), or click "New" and add a new path. If you choose to do the latter, I'd recommend either making the folder under C:\Program Files\ or make a custom bin folder (e.g., C:\Users\<your name>\bin\).

At this point, you should be able to open up a terminal window (Command Prompt, Powershell, etc), and run the winbarc command.
Configuring
You need to generate the config for winbar; either download it from the repo (https://github.com/Sulaxan/winbar/blob/main/winbar.json), or you can generate it from the command line:
winbar --config-path <PATH> --generate-config

(Using winbar here, not winbarc)
A quick note:  can be anything - if you put ./winbar.json it'll be your current directory. I recommend either putting it in C:\Users\<your name>\.config OR in the same directory as the executables above.
There currently isn't a standard config location in winbar as of right now, however, I plan to standardize this in the future. This will effectively eliminate you from passing in the --config-path option every time you run a command, assuming you have it in the standard location. Again, something for the future.
See the docs to see what you can change in the config file to configure winbar.
Running winbar
There are a couple of ways to run winbar, outlined in Usage. I'll note the method using winbarc below.
Run the following:
winbarc start --config-path <PATH>

Note that  is the path to the config file (e.g., if it's in C:\Users\<your name>\.config, then you'd specify something along the lines of C:\Users\<your name>\.config\winbar.json [or whatever else you named the config file]).
This should start winbar in the background, use winbarc stop to stop the process.
A forewarning on winbar
Winbar is very much a work in progress; there are currently only 2 components you can use. I've started working on the next major feature for winbar (plugins) some months ago, but have not had time to get around to finishing it. Once this feature is implemented, a lot more components can be added with relatively easily.
With that being said, hopefully you see potential with this project - as always, let me know if you have any issues or questions.

Ok. I ran winbarc start --config-path <PATH> but didn't see anything. I downloaded the config file from here: https://github.com/Sulaxan/winbar/blob/main/winbar.json
If I write the command winbarc show, then I get  Sending show window payload... Error occurred in the winbar server connection: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение. (os error 10061)

Ok. I ran winbarc start --config-path <PATH> but didn't see anything. I downloaded the config file from here: https://github.com/Sulaxan/winbar/blob/main/winbar.json
If I write the command winbarc show, then I get  Sending show window payload... Error occurred in the winbar server connection: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение. (os error 10061)

If you didn't see any message after running winbarc start ..., it is likely that the process wasn't started (you should see Started winbar! if the process started successfully). Oddly though, you should have seen some sort of output after running this command; either a success message or an error. Has me curious if there's an edge case...
For now, try running the winbar executable directly:
winbar --config-path <PATH>

Let me know if this works and we'll start working through what the issue is. If the above does work, it could be an issue with winbarc.

Oh yeah, I forgot to say I got Started winbar!
I meant that I didn't see any panels...

Ah, makes sense. Have you had a chance to run the command I mentioned above?

This winbar --config-path <PATH>? Yes. I got it

Looks like this was an issue caused by me - I made some changes months ago that made some breaking changes to the config file, but never updated the config in the repo. I just updated the repo, so when you get a chance, if you could download the config file again (https://github.com/Sulaxan/winbar/blob/main/winbar.json) and try running winbar.
Namely, the following changes were made:

Colors are now specified using the function syntax: "Transparent" => "Transparent()"
No more null colors in the config

Oh. Yes. I'll definitely try it tomorrow

I had to enter 2 commands before I saw the panels. But now I get some endlessly repeating output
https://github.com/user-attachments/assets/404f79ee-96a3-40a6-9315-ae169b9cd6e9

I had to enter 2 commands before I saw the panels. But now I get some endlessly repeating output
2024-11-16.143223.mp4

Unfortunately, I can't view the video (corrupted?), but glad you got it working. What were the 2 commands you used?
Just to clarify, using winbar runs the status bar directly, so you'll see all the logging in your terminal. Try running the winbarc command that you originally tried (i.e., winbarc start --config-path <PATH>). This should hopefully start winbar in the background now. Let me know if you get it working.

Unfortunately, I can't view the video (corrupted?)

Yes, it looks like it. Here I uploaded the video again
https://github.com/user-attachments/assets/15b84b93-b1fb-4c40-a680-657a6f0e09e2

Unfortunately, I can't view the video (corrupted?)

Yes, it looks like it. Here I uploaded the video again
2024-11-16.143223.mp4

Still unable to view it


Update opencensus-contrib-log-correlation-log4j2 artifact/package names in readme.

This commit is a continuation of #1411.

Codecov Report

Merging #1416 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1416      +/-   ##
============================================
- Coverage     83.71%   83.69%   -0.02%
  Complexity     1522     1522
============================================
  Files           233      233
  Lines          6993     6993
  Branches        661      661
============================================
- Hits           5854     5853       -1
  Misses          939      939
- Partials        200      201       +1

Impacted Files
Coverage Δ
Complexity Δ

...census/implcore/trace/export/SpanExporterImpl.java
91.78% <0%> (-1.37%)
8% <0%> (ø)

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 18a2bbd...d4c55c1. Read the comment docs.


Bootleg DevKit Introduction

As Deborah the developer, I just found my way into the Bootleg devKit webpage (friend told me about the article and I clicked the link), I need to know within 15 seconds whether this is something I really care enough to continue learning about, so that I can take the next step and start reading the details.
English description of goal in a sentence or two, usually in the form of a user story.
Questions

What does a canonical Deborah really care about?

Will Deborah likely go on to read the stuff in one sitting, or should we anticipate that she might set it aside for a while and we need a way to prompt her back into the devKit...maybe a signup, alert? Something clever we can use for all devKits and other content we want to be sure people don't forget to come back to?

Assumptions

Deborah is

Acceptance

Most Deborahs continue to read into the rest of the devKit

Tasks

[ ] Write draft of Intro (JW)
[ ] Review and compose Intro into web page (?)

Copy of #87


Marker return wrong data when zooming or resizing browser

Hi all
When I drag a marker to somewhere in map, it'll be okay. But issue appears when I resize or zoom my browser, marker lat/lng return wrong data.
Is it a bug?

Can you provide a reproduction and describe exactly what is actual, and what is expected result?


pull request for e2e test at 12/05/2016 21:26:00

:white_check_mark: Validation status: passed
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.


Allow specifying a base directory for relative pathing in pip-compile?

Suppose I have a package structure like this:
.
└── hello
    └── world
        ├── api
        │   └── requirements.in
        ├── shared
        │   └── requirements.in
        ├── tools
        │   └── requirements.in
        └── requirements.in

And suppose that these different requirements.in files are not independent. For instance, under hello/world/api/requirements.in, it may include this line:
-r ../shared/requirements.in

And perhaps hello/world/tools/requirements.in includes these lines:
-r ../shared/requirements.in
-r ../requirements.in

What I'm wondering is if there's any way I can do away with the ..s in the relative paths and instead replace these values with the path relative to where pip-compile was invoked? So for instance, if I'm calling pip-compile from the root, specifying each file as an argument, one by one, could I instead use lines like this one - even from further down the folder chain?
-r hello/world/shared/requirements.in
-r hello/world/requirements.in

As far as I can tell, currently the answer is "no". The reason I want this is because .. is messy; I would contend it is harder to manage if one ever needs to restructure a package (many times you can move one folder around freely without any changes if you're able to use the kind of paths I'm describing). And I'm working on a big Makefile to build up all the different subpackages in a given repo, and it would make gathering of targets a lot easier if I didn't have to deal with paths relative to each file but instead was dealing with paths relative to the root of the repo.
I recognize that pip-compile is using pip internals under the hood so I'm not sure if this is even possible. But I thought I'd ask! If it were possible I imagine it would be done by adding some kind of optional parameter to pip-compile to set the basedir, e.g. pip-compile -d $(pwd) hello/world/requirements.in

Hello @soapergem,
Thank you for the very detailed report!

I recognize that pip-compile is using pip internals under the hood so I'm not sure if this is even possible. But I thought I'd ask! If it were possible I imagine it would be done by adding some kind of optional parameter to pip-compile to set the basedir, e.g. pip-compile -d $(pwd) hello/world/requirements.in

I'm afraid it's not possible to achieve it without hacks, since the base dir for references (-r and the other path related options) has been implemented deep down in pip.

I'll close it for now. Feel free to reopen this issue if you'll have more questions.


zotero_7: init at 7.0.0-beta

Description of changes
I added the beta version of Zotero. I'm not sure how to put the two derivations in a single file, so I could use some help there. Also, there is a warning on the terminal that is shown when I run the binary:
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.720421) [GFX1-]: glxtest: libpci missing
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.720421) |[1][GFX1-]: glxtest: libEGL missing (t=0.720463) [GFX1-]: glxtest: libEGL missing
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.720421) |[1][GFX1-]: glxtest: libEGL missing (t=0.720463) |[2][GFX1-]: glxtest: EGL test failed (t=0.720474) [GFX1-]: glxtest: EGL test failed
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.720421) |[1][GFX1-]: glxtest: libEGL missing (t=0.720463) |[2][GFX1-]: glxtest: EGL test failed (t=0.720474) |[3][GFX1-]: No GPUs detected via PCI (t=0.720492) [GFX1-]: No GPUs detected via PCI

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

1 package built:

zotero_7

Hey, thanks for putting in the work! :sparkling_heart: It is nice to have Zotero 7 beta available to circumvent CVE-2023-5217.
I could replicate that zotero_7 works on x86_64-linux, with the error messages you mentioned.
I see you removed the postPatch (sed -i '/pref("app.update.enabled", true);/c\pref("app.update.enabled", false);' defaults/preferences/prefs.js), as the file no longer exists. However, Zotero 7 still comes with an updater binary — do we need to disable the auto-updating mechanism here, or is it enough to not manually install the updater?
I'm not an active nixpkgs contributor, but maybe it's OK to leave the derivations in two separate files, it's the same for the Julia compiler. I guess the commits should be merged into one before merging though.

Heyy, thx for taking the time to review!
I think it is enough not to install the update script. I oppened zotero and
tried to search for updates and it simply said that there isnt new updates.
I know this isnt enough to make an absolute conclusion, but I think is
enough to know that the program will function properly without the update
script.
I will be squashing the commits now.
On Tue, Nov 21, 2023, 09:49 stega @.***> wrote:

Hey, thanks for putting in the work! 💖 It is nice to have Zotero 7 beta
available to circumvent CVE-2023-5217
https://github.com/advisories/GHSA-qqvq-6xgj-jw8g.
I could replicate that zotero_7 works on x86_64-linux, with the error
messages you mentioned.
I see you removed the postPatch (sed -i '/pref("app.update.enabled",
true);/c\pref("app.update.enabled", false);' defaults/preferences/prefs.js),
as the file no longer exists. However, Zotero 7 still comes with an updater
binary — do we need to disable the auto-updating mechanism here, or is it
enough to not manually install the updater?
I'm not an active nixpkgs contributor, but maybe it's OK to leave the
derivations in two separate files, it's the same for the Julia compiler
https://github.com/NixOS/nixpkgs/blob/e4ad989506ec7d71f7302cc3067abd82730a4beb/pkgs/development/compilers/julia/1.8.nix#L80.
I guess the commits should be merged into one before merging though.
—
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/268612#issuecomment-1821292079,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBHMNIE7AMHIR2J6337FVLYFTLP7AVCNFSM6AAAAAA7SD5EKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRRGI4TEMBXHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Could you also remove me as a maintainer from this package? I'm guessing you copied this from an earlier Nixpkgs revision, but I had myself removed from the stable zotero's maintainers because I'm not able to test the package anymore.
Feel free to add yourself as a maintainer.

Hey! Sure, I will do this.
On Tue, Nov 21, 2023, 12:39 Imran Hossain @.***> wrote:

Could you also remove me as a maintainer from this package? I'm guessing
you copied this from an earlier Nixpkgs revision, but I had myself removed
from the stable zotero's maintainers because I'm not able to test the
package anymore.
Feel free to add yourself as a maintainer.
—
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/268612#issuecomment-1821567885,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBHMNN6KM3C7FGISEE53TTYFT7O5AVCNFSM6AAAAAA7SD5EKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRRGU3DOOBYGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Could you also remove me as a maintainer from this package? I'm guessing you copied this from an earlier Nixpkgs revision, but I'm not able to test this package.
Feel free to add yourself as a maintainer.

I just removed you from zotero_7, do you also want to be removed from stable zotero?

Yes, if you are able to maintain that package as well. Thanks!

Actually Im not haha, I would only put my name on this one. In that case I
think its better for u to open a PR later maybe.
On Wed, Nov 22, 2023, 11:38 Imran Hossain @.***> wrote:

Yes, if you are able to maintain that package as well. Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/268612#issuecomment-1823286346,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBHMNLALOYZ47ULBV673VTYFZBDDAVCNFSM6AAAAAA7SD5EKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRTGI4DMMZUGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi, if you want an updated version of Zotero 7 built from source, check out https://github.com/camillemndn/zotero-nix. By the way, Zotero 7 is still beta, I guess this should be reverted when NixOS 24.05 is released, no?


[bug] Sortable swapping does not work when forceFallback is enabled and a handle or content is a custom element (web component) with a shadowRoot

Describe the bug

When in forceFallback: true, and the handle or list content is a web component with an open shadowRoot items cannot be dragged.
In our usage, our handle element is another custom element with shadowRoot and the content within a sortable element is also a custom element.
The code problem area is seen in this section: https://github.com/SortableJS/Sortable/blob/07708fa1e7d9cf9d4563a7b1a09f7a47771522ed/src/Sortable.js#L756-L759
With this line target = target.shadowRoot.elementFromPoint(touchEvt.clientX, touchEvt.clientY);, its returning elements within our handle custom element or content custom element instead of a child of the Sortable instance.
This only happens when in forceFallback: true or when used by a mobile device which seems to always go into fallback mode.
When using native drag and drop the issue is not seen.

To Reproduce
Steps to reproduce the behavior:

Go to https://codepen.io/driskull/pen/OJqrzVL?editors=1010
Try to drag a handle over another handle and notice it won't swap elements
Drag a handle over a list element textContent and notice it does swap
If there are other custom-elements inside the list-element in place of the text content elements won't swap either.
See sample: https://codepen.io/driskull/pen/xxBmpra?editors=0110

Expected behavior
I would expect sort swapping to work when a handle or content within a list is a custom element.
Information

sortablejs = ^1.15.1
@types/sortablejs = ^1.15.1
Additional context
I have a PR open to fix this but need verification that it is the best approach to fixing the issue.
Reproduction
codesandbox: https://codepen.io/driskull/pen/OJqrzVL?editors=1010 and https://codepen.io/driskull/pen/xxBmpra?editors=0110
Pull Request Fix
https://github.com/SortableJS/Sortable/pull/2347

Thank you, PR has been merged

Thank you @owen-m1 🍻

Thanks, @driskull and @owen-m1! When is the next SortableJS release planned?

@owen-m1 any chance we can get a new release with this fix?

Thank you @driskull it has been released in 1.15,3


Does not use alerts, confirms, or prompts

Does not use alerts, confirms, or prompts
Check for this prior to completing mvp stage

None are used so far


Knives Tag

I've run into a bug involving the electrum knife and the forge:tools/knives tag. This occurred using the 1.18.2 forge latest release as of submitting this report. Discovered while attempting to use Farmer's Delight knives. The screenshot shows Farmer's Delight's tags are filled just fine. The instance's log outputted this error:
Couldn't load tag forge:tools/knives as it is missing following references: oreganized:electrum_knife

Should be fixed in 1.0.4 now that compatibility with Farmer's Delight is completely fixed


Several queries failing

Several queries are failing with the latest nightlies:
q03, q12, q17 are the ones I noticed:
Trace is the same:
17
Encountered Exception while running query
Traceback (most recent call last):
  File "/home/rgelhausen/gpu-bdb/gpu_bdb/bdb_tools/utils.py", line 276, in run_dask
_cudf_query
    results = benchmark(
  File "/home/rgelhausen/gpu-bdb/gpu_bdb/bdb_tools/utils.py", line 61, in benchmark
    result = func(*args, **kwargs)
  File "queries/q17/gpu_bdb_query_17.py", line 185, in main
    grouped_df = grouped_df.compute()
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dask
/base.py", line 285, in compute
    (result,) = compute(self, traverse=False, **kwargs)
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dask
/base.py", line 567, in compute
    results = schedule(dsk, keys, **kwargs)
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dist
ributed/client.py", line 2707, in get
    results = self.gather(packed, asynchronous=asynchronous, direct=direct)
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dist
ributed/client.py", line 2021, in gather
    return self.sync(
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dist
ributed/client.py", line 862, in sync
    return sync(
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dist
ributed/utils.py", line 338, in sync
    raise exc.with_traceback(tb)
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dist
ributed/utils.py", line 321, in f
    result[0] = yield future
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/torn
ado/gen.py", line 762, in run
    value = future.result()
 File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dist
ributed/client.py", line 1886, in _gather
    raise exception.with_traceback(traceback)
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dask
/optimization.py", line 969, in __call__
    return core.get(self.dsk, self.outkey, dict(zip(self.inkeys, args)))
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dask
/core.py", line 151, in get
    result = _execute_task(task, cache)
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dask
/core.py", line 121, in _execute_task
    return func(*(_execute_task(a, cache) for a in args))
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dask
/utils.py", line 35, in apply
    return func(*args, **kwargs)
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/dask
/dataframe/core.py", line 5775, in apply_and_enforce
    df = func(*args, **kwargs)
  File "/home/rgelhausen/gpu-bdb/gpu_bdb/bdb_tools/utils.py", line 919, in <lambda>
    left_merge = lambda df_1, df_2: df_1.merge(
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/contextlib.py", li
ne 75, in inner
    return func(*args, **kwds)
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/cudf
/core/dataframe.py", line 4486, in merge
    gdf_result = super()._merge(
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/cudf
/core/frame.py", line 3206, in _merge
    return merge(
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/cudf
/core/join/join.py", line 40, in merge
    mergeobj = merge_cls(
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/cudf
/core/join/join.py", line 485, in __init__
    super().__init__(*args, **kwargs)
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/cudf
/core/join/join.py", line 128, in __init__
    self._validate_merge_params(
  File "/home/rgelhausen/conda/envs/rapids-gpu-bdb/lib/python3.8/site-packages/cudf
/core/join/join.py", line 416, in _validate_merge_params
    same_named_columns = set(lhs._data) & set(rhs._data)
AttributeError: 'tuple' object has no attribute '_data'

Versions:
conda list | grep dask
dask                      2021.6.2           pyhd8ed1ab_0    conda-forge
dask-core                 2021.6.2           pyhd8ed1ab_0    conda-forge
dask-cuda                 21.08.00a210701         py38_32    rapidsai-nightly
dask-cudf                 21.08.00a210701 py38_g51b1c23b1b_236    rapidsai-nightly
(rapids-gpu-bdb) rgelhausen@rl-dgx2-r11-u7-rapids-dgx202:~/gpu-bdb/gpu_bdb/queries/load_test$ conda list | grep rapids
# packages in environment at /home/rgelhausen/conda/envs/rapids-gpu-bdb:
cudf                      21.08.00a210701 cuda_11.2_py38_g51b1c23b1b_236    rapidsai-nightly

This should be fixed in https://github.com/dask/dask/pull/7838 and https://github.com/dask/dask/pull/7849.
Because of https://github.com/rapidsai/cudf/pull/8581, we now use the new HighLevelGraph code patch in Dask/Distributed, which exposed some unknown bugs. I hope I have fixed all of them.

This has been resolved now that the PRs linked above merged and a new Dask release was cut.


Update kernel version to v4.19.175-cip43

Purpose of pull request
Update kernel version to v4.19.175-cip43

Thanks!


Server: Add support for loongarch64

This PR is for: Server
Add support for loongarch64
The LoongArch architecture (LoongArch) is an Instruction Set Architecture (ISA) that has a RISC style.
Documentations:
ISA:
https://loongson.github.io/LoongArch-Documentation/LoongArch-Vol1-EN.html
ABI:
https://loongson.github.io/LoongArch-Documentation/LoongArch-ELF-ABI-EN.html
More docs can be found at:
https://loongson.github.io/LoongArch-Documentation/README-EN.html

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


Refactor the code to make more things private

Some stuff should be public, e.g. the coinToCompoundMap and the Action struct etc.

Fixed.

Fixed.


license?

hey @arian,
thank you for creating this library! it is very useful and i would really like to use it in one of my projects.
unfortunately, i couldn't find a license in the source code. would you mind adding a license file or a note that clarifies under which conditions i may use + modify the code?
thank you!

I added a license file


Move GC blobs to root and re-generate GC / summary on GC state switch

Fixes #8672 and #8515.
As mentioned in the root-cause for #8672 here, when GC is disabled after it was previously enabled, the summary has to re-regenerate the data for all nodes so that their unreferenced state is cleared.
This PR adds the following changes:

Moved writing the GC data from data stores to the root. This was a pending work item it makes finding out if a summary has GC state simpler and helps having all logic in one place (garbage collector).
When the GarbageCollector loads, it checks if the summary has GC tree or not. If it does and GC is disabled, it sets a flag indicating that the GC state needs to be reset in the next summary.
ContainerRuntime when generating summary, consults the above flag and if true, runs summary with fullTree as true.
The flag is reset when the first summary is ack'd since we only want to regenerate the summary the very first time this happens.

Note that moving the GC blobs to root will have the following consequence:

A forward compat change was made so that older versions can read the GC data at root and write at root here - https://github.com/microsoft/FluidFramework/pull/8389.
But if a summarizer with this change generates a summary which is read by another summarizer running version < 0.53, it will have to regenerate the summary and GC data.

PR that updates the reference snapshots used in snapshot tests - https://github.com/microsoft/FluidFrameworkTestData/pull/35

@pleath Could you please also take a look at the corresponding PR in test repo - https://github.com/microsoft/FluidFrameworkTestData/pull/35. That has to go in before I can merge this one.


Disable the CLA munger in contrib.

Waiting to turn on the CLA plugin in prow for contrib before merging this.

This change is

Awesome! Should we remove the code?

@apelisse I think we can leave it there. One of the repos in incubator is using it IIRC.


How to enable fcitx5-rime single line mode

Fcitx5-rime project has closed this requirement and updated the code.
https://github.com/fcitx/fcitx5-rime/commit/f1c5f5c9f39ea330aff487eb53f49a1fefc4e8b9
So how to add fcitx5-rime single line mode in the configuration.
I tried to configure config, default.custom.yaml, classicui.conf  all have no effect.

you should edit this file ~/.config/fcitx5/conf/rime.conf, and add this code to it:
# 可用时在应用程序中显示预编辑文本
PreeditInApplicaation=True

please exit fcitx5, before you edit ~/.config/fcitx5/conf/rime.conf

@hosxy  Thx. It works.
However, in addition to modifying ~/.config/fcitx5/profile  file need to exit fcitx5 first. You can directly modify other configuration files and then restart fcitx5.
If others have encountered this problem , can use this method to solve it.
If the path is no rime.conf file, you can create it first by yourself.


Instructions for Android

I'm reading this page here http://reapp.io/docs-builds.html and I'm not seeing android instructions. Would instructions be welcome?

Android instructions would be fantastic!

Agreed. The build for android is the same really as iOS, we just haven't built out a theme or specific guides for Android tips.
But basically run through the Cordova instructions but do cordova platform add android and build it from there!

im trying to build android platform but it doesnt seems to load when loading webview source from file:///

@jasonvillalon thanks for commenting.
Can you please provide some context sot that we can help you with your exact problem? In which stage are you, and please show us some code.

hi thank you for your reply. i created startup project using reapp new myapp, im able to run it in my browser using reapp run. then im trying to run it on my android device
here is what i did:

create new cordova project outside my reapp project

cordova create projectname

removed www in my cordova project

rm -rf ww

build reapp project

cd ../my-reapp-project

reapp build android

then link build/android to my cordova project www

cd ../my-cordova-project

ln -s ../my-reapp-project/build/android www

add cordova platform android

cordova platform add android

add cordova plugins

cordova plugin add com.telerik.plugins.wkwebview org.apache.cordova.console org.apache.cordova.device org.apache.cordova.inappbrowser org.apache.cordova.statusbar

run in on my device

cordova run android

when the app launched in my device its just white screen. it looks like when you are browsing the build/android/index.html in browser using file:///path/to/my/build/android/index.html. its just white screen
im trying to upgrade my cordova to 5.0 now. maybe its because im using lower version of cordova. i really dont have idea yet.

Try just using the ios build and linking that. Also I wouldn't use WKWebView. I've just been building to ios and linking that until android support is official.

so WKWebView is a plugin you should only use on ios?

i used WKWebView because i spent hours debugging CORS request on my android device using superagent but after i installed WKWebView it solves my problem about access-control-allow-origin.

Any chance to get an update on what is the situation on android and most importantly get full instructions on how to export for android?

@tom-s it's pretty much the same as ios. Try asking in the gitter.im

I've followed the instructions replcing ios with android. I end up with a white page when lauching the app. Do I need to install cordovas plugin as well, or is that not necessary ? The doc is a bit unclear on that matter.

the plugins are optional afaik

Hi ,
i have followed the instructions replacing ios with android. But getting a white screen

@muralip me too. But I thought it was something wrong with my machine. @natew I think this is something that warrants investigation but it's tough to narrow down.

morenoh149 | any ideas here? https://github.com/reapp/reapp/issues/47#issuecomment-105768674
morenoh149 | I get a white screen when I deploy to the android emulator or device
morenoh149 | where would I start debugging this?
KicStart | morenoh149: probably the permissions in your manifest
morenoh149 | KicStart: interesting. The current instructions have us making symlinks and such. are the manifests different
between ios and android? http://reapp.io/docs-builds.html
KicStart | morenoh149: when I did Android Phonegap debugging I would have weinre running, and set up javascript in my html
file to call it as a server request and debug it remotely
morenoh149 | it's a newish project so having a knowledgeable cordova person review these instructions would be amazing
KicStart | so if you're up and running the index.html properly (yeah I know the app structure changed to app.js) , calling
would let me debug javascript from the weinre console.
KicStart | morenoh149: https://developer.chrome.com/devtools/docs/remote-debugging
morenoh149 | I'll start debugging in few hours. But last time I tackled this I believe index.html would load (via the
console.log plugin) but if I tried to log from deeper in the js logic it wouldn't print
KicStart | The approach on Android has changed a little bit since I last looked.
KicStart | morenoh149: at that time the settings were in the Info.plist, and some in the code, now I'm sure they changed it.
I'll be fiddling around with a new project in a week or so and will revisit the nuances then.

Should we run a tiny web server (like floatinghotpot/cordova-httpd) to serve the compiled assets on Android?

@l4u did that solve things for you? This issue is for getting our reapp apps working on an android device. Currently many of us are getting a white screen when deploying to android.

@morenoh149 I haven't tried. I will have to switch to another framework for now. Hopefully I can revisit reapp some days later.

I was able to fix the Android blank screen issue. The issue is with reapp-routes package. It is fixed in reapp-routes but has not been packaged in the new version. The latest reapp-routes package at this point is 0.10.10. So I manually applied the fix to my reapp-route node package and it works.
See details below:
https://github.com/boazy/reapp-routes/commit/6148226a772c196bd45af86c506eb78c7227c780

@gravi2 I confirm that same worked for me - thanks!

closing this as the blank screen issue is resolved. But we still need better docs for android.


Excellent. This needs to be documented in the official docs.

          Excellent. This needs to be documented in the official docs.

Originally posted by @appetrosyan in https://github.com/hyperledger/iroha/pull/3617#discussion_r1234847310

https://github.com/hyperledger/iroha/pull/3617#discussion_r1235022177


Dashboard for annotation video tiddlers

I have noticed that the annotation video tiddlers don't appear in the mediaplayer dashboard with the annotation template. Can there be a separate dashboard for the annotation tiddlers like the mediaplayer dashboard.

what do you mean by 'dashboard'?

Something similar to the Mediaplayer tiddler with list and sub list of the annotation video tiddlers. Just that I used the term Dashboard

you can have a playlist of annoted videos but not sub lists - I have put an example on
https://mediaplayerava.tiddlyhost.com/

you can have a playlist of annoted videos but not sub lists - I have put an example on
https://mediaplayerava.tiddlyhost.com/

Thank you


rclpy: 1.8.1-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository rclpy to 1.8.1-1:

upstream repository: https://github.com/ros2/rclpy.git
release repository: https://github.com/ros2-gbp/rclpy-release.git
distro file: rolling/distribution.yaml
bloom version: 0.10.6
previous version for package: 1.8.0-1

rclpy
* typo fix. (#768 <https://github.com/ros2/rclpy/issues/768>)
* Restore exceptions for Connext and message timestamps on Windows (#765 <https://github.com/ros2/rclpy/issues/765>)
* Use correct type when creating test publisher (#764 <https://github.com/ros2/rclpy/issues/764>)
* Add a test for destroy_node while spinning (#663 <https://github.com/ros2/rclpy/issues/663>)
* Add __enter__ and __exit__ to Waitable (#761 <https://github.com/ros2/rclpy/issues/761>)
* Check if shutdown callback weak method is valid before calling it (#754 <https://github.com/ros2/rclpy/issues/754>)
* Contributors: Andrea Sorbini, Ivan Santiago Paunovic, Scott K Logan, Shane Loretz, Tomoya Fujita

Please hold for coordinated merge.


Nomad job for PEcAn docker-develop branch, Part 1

[x] Follow Rob's instructions on docker-develop branch from https://github.com/PecanProject/pecan/pull/2610 to get a working setup.

Result:
$ docker ps
CONTAINER ID        IMAGE                                      COMMAND                  CREATED             STATUS                    PORTS                                                        NAMES
7a7ef2a0b4ed        pecan/monitor:develop                      "/bin/sh -c 'python3…"   About an hour ago   Up 27 minutes             <IP_ADDRESS>:9999->9999/tcp                                     pecan_monitor_1
7024939f83f4        traefik:1.7                                "/traefik --loglevel…"   About an hour ago   Up 28 minutes             <IP_ADDRESS>:8000->8000/tcp, 80/tcp, <IP_ADDRESS>:8443->8443/tcp   pecan_traefik_1
9f78ff30b6f3        pecan/executor:develop                     "/bin/sh -c 'python3…"   About an hour ago   Up 27 minutes             8787/tcp                                                     pecan_executor_1
9d5b5555bfb6        pecan/shiny-dbsync:develop                 "/bin/sh -c /srv/shi…"   About an hour ago   Up 28 minutes             3838/tcp                                                     pecan_dbsync_1
63162ac59f00        pecan/bety:latest                          "/home/bety/docker/e…"   About an hour ago   Up 28 minutes             8000/tcp                                                     pecan_bety_1
884fe986ffe0        pecan/model-sipnet-r136:develop            "/bin/sh -c 'python3…"   About an hour ago   Up 27 minutes             8787/tcp                                                     pecan_sipnet_1
0f1204ed2a3a        pecan/model-maespa-git:develop             "/bin/sh -c 'python3…"   About an hour ago   Up 27 minutes             8787/tcp                                                     pecan_maespa_1
ec6d1197aef0        pecan/model-ed2-git:develop                "/bin/sh -c 'python3…"   About an hour ago   Up 27 minutes             8787/tcp                                                     pecan_ed2_1
0c8f3a5e4a78        pecan/web:develop                          "docker-php-entrypoi…"   About an hour ago   Up 28 minutes             80/tcp                                                       pecan_web_1
e164f3b7cfbb        pecan/model-basgra-basgra_n_v1.0:develop   "/bin/sh -c 'python3…"   About an hour ago   Up 27 minutes             8787/tcp                                                     pecan_basgra_1
489c51686494        pecan/docs:develop                         "httpd-foreground"       About an hour ago   Up 28 minutes             80/tcp                                                       pecan_docs_1
3dbc196cd39f        pecan/base:develop                         "/init"                  About an hour ago   Up 28 minutes             8787/tcp                                                     pecan_rstudio_1
9adbc2f5c5b7        pecan/rstudio-nginx:develop                "nginx -g 'daemon of…"   About an hour ago   Up 28 minutes             80/tcp                                                       pecan_rstudio-nginx_1
e0785fc9e2ff        pecan/thredds:develop                      "/entrypoint.sh cata…"   About an hour ago   Up 28 minutes             8080/tcp, 8443/tcp                                           pecan_thredds_1
aff26b2332f6        minio/minio:latest                         "/usr/bin/docker-ent…"   About an hour ago   Up 28 minutes (healthy)   9000/tcp                                                     pecan_minio_1
4ebf7f29623e        rabbitmq:management                        "docker-entrypoint.s…"   3 days ago          Up 28 minutes             4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 25672/tcp          pecan_rabbitmq_1
067085b5728a        mdillon/postgis:9.5                        "docker-entrypoint.s…"    I'm glad you were able to get this Docker stack up and running.

Thank you!
Yes, it took a couple of goes. It failed badly on some services.
@KristinaRiemer You got it working as well, right? Could you develop & test models in it the way it was? I didn't have enough knowledge to be certain whether it ended up in a useful state.
I was able to get all the following endpoints working:

/pecan/: PEcAn web interface, from here you can run different models at different sites.
/rstudio/: RStudio Server, you can edit PEcAn files or run analysis on existing data.
/minio/: Browse the PEcAn data using minio graphicsal interface
/thredds/: Browse the PEcAn generated data using Thredds server
/bety/: BETY Interface to the database with all data used by the PEcAn system.
/pecan/history.php: PEcAn runs done previously.

RStudio seemed to work.
I tried to run a test in RStudio terminal:
cd pecan/tests
../web/workflow.R --settings docker.sipnet.xml

# stuff...
#
# 2020-06-05 21:48:59 ERROR  [PEcAn.data.atmosphere::met.process] :
#    Cannot process met without source information
# Error in paste0("registration/register.", met, ".xml") :
#   object 'met' not found
# Calls: <Anonymous> -> <Anonymous> -> system.file -> file.path -> paste0

I called it quits after that.

So this had been working entirely for me last week. I just tried to spin it up again this morning and I'm getting that same error from trying to run docker.sipnet.xml (which means that sipnet test isn't working). It's because the meteorology data isn't in the database, but I'm not sure why, and I'll let you know when I figure it out.

Follow-up issue: https://github.com/AgPipeline/issues-and-projects/issues/155


Remove indiscriminate outline suppression for tabindex="-1" elements

instead, only apply outline suppression if the browser wouldn't normally apply the focus outline, using the (currently experimental) :focus-visible pseudo-class
Closes https://github.com/twbs/bootstrap/issues/28425

This will add the focus ring back everywhere since this property is not yet supported (https://caniuse.com/#search=focus-visible). Don't know if that's an issue?

This will add the focus ring back everywhere

everywhere there's a tabindex="-1" and the element is then focused programmatically - either because, say, it's an in-page anchor, or because it was invoked via focus() JS method. unless i missed anything, only our modal dialogs (which have an explicit outline: 0 already) fall into the latter category.

but yes, the :focus-visible part is speculative/future-compatible (as per the comment in the scss)


Feature request: Batch files import and export (srt, txt etc)

It would be great that If Buzz can import multiple files (video / mp4 ) and then export / output srt files one by one (sure with same settings) . so you dont have to waiting in front of computer to manually handle it.
Thanks.
P.S Since even the "Quality" setting to "Medium" it takes quite long time ( 5 mins video = 5mins) to process.

I am sorry but the batch import or export function is implemented?
I am using version 0.6.4. still only one by one to import....


Feat: Adjust Font Size for "A Unique Café Experience" to Fit well

Describe the feature
The line "A Unique Café Experience" is currently too large, causing the word "experience" to wrap onto the next line, which affects the overall aesthetic of the design. To improve the visual flow, I would like to decrease the font size so that the entire phrase fits neatly on one line.
Task:

Decrease the font size for the "A Unique Café Experience" text.
Ensure that the phrase fits on one line without breaking.

Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I have starred the repository
[X] I'm a gssoc-24-extd contributor
[X] I want to work on this issue

@neeru24 Go Ahed and also try to give the text a great font style & animation.


Not working in XCode 7.1

MCLog no longer crashing, but filter field no longer present in XCode 7.1 final (7B91b).

Same issue... any solution? Some workaround?

Use xcplugin_update.sh to update UUID of new Xcode. Thanks to @alexlee002

@yuhua-chen after using that MCLog causes crash :(

@yuhua-chen After using that Xcode crashes :cry:

What's your OS version? Can you show me some logs? Still working on it. :dizzy_face:

#34 fixes this.

@yuhua-chen, didn't #34 fix this? The plugin was having set the UUID of the Xcode 7 beta, so Xcode 7.1 was not supported by it, hence it didn't appear.

The UUID of PR is right for Xcode 7.1, by following:
$ defaults read /Applications/Xcode\ 7.1.app/Contents/Info DVTPlugInCompatibilityUUID
7265231C-39B4-402C-89E1-16167C4CC990

I think it crashed by some reasons due to Xcode 7.1.

I understand, for me it didn't crash once, @devxoul, could you clone this project and build the project and tell us if it still crashes?

@revolter, of course, wait for a minute.

@revolter @devxoul  what's your OS version? I found that it only crashed on OS El captain and Xcode 7.1.

I'm on OS X Yosemite 10.10.5

hmm...so weird. but mine is 10.10.5 too. It works fine. Have you tried this before?
sudo xcodebuild -license

I didn't say it crashed for me. So you previous comment might be correct, that it only crashes in El Capitan and Xcode 7.1

master branch causes crash.

@devxoul on what OS version?

OS X 10.11.1 (Yosemite)
Xcode 7.1

I'm able to use it on El Capitain (15B42) and Xcode 7.1 (7B91b) and 7.2 beta (7C46t) with this solution.
But getting this issue in the process =/

I updated the plugin. It works on Xcode 7 right now. Try the newest commit(04c1cc1b) on master.

Hi, @yuhua-chen! I've tried your latest commit, but I'm still getting this issue. Only me?

@lucianoks Have the same issue on Xcode 7.1.1 (7B1005), El Capitan 10.11.1 (15B42).

Let's move to #35 issue since this plugin worked on Xcode 7.1 now.

Not working on El Capitan (10.11.2) and Xcode 7.2 either (filter field not present).

Not working on Yosemite (10.10.5 ) and Version 7.2 (7C68) either (filter field not present). And xcplugin_update.sh works. Thanks @alexlee002 and @yuhua-chen!


Improve PlayCountSorter

Slight changes to PlayCountSorter to improve speed.
Approx. 10 times faster (Tested on a Ryzen 9 3900X with ~10800 maps)
From ~8s to <400ms

Thanks for the PR, I never actually noticed any slowdowns myself, so thanks for bringing it up.
The code looks great, but I have some concerns though with the code written in Prepare() where you added an event to SceneManager.sceneLoaded as the function can be called multiple times in some rare cases, though it is not a big deal since all its doing is setting a bool.
I was thinking either only adding it once, or just use ContextSwitch instead as that is called every time the song list is updated. Could you look into the latter and see if it also improves load times?

Cool, I will test it later and merge it if nothing goes wrong.


[Service Bus] Track rejected messages along with accepted ones

Waiting for #2535 to update the same in azure-sb sample

@HarshaNalluru https://github.com/Azure/azure-sdk-for-js/pull/2535 is merged, can you update this PR?


A suggestion about Factorial

Not an issue - more of a suggestion.  Is it better to start the loop from 2？
export default function factorial(number) {
  let result = 1;

  for (let i = 2; i <= number; i += 1) {
    result *= i;
  }

  return result;
}

Because the factorial of 0 and 1 is always 1 and the function returns 1 if the number is less than 2.
Yes, its better to start the loop from 2 as long as the number is a positive integer.

Thank you for your comment @Jeffrey1029
It is fixed now.


[Integration][Airflow]Add PythonDecoratedExtractor

signed-off-by: Tyler Farris<EMAIL_ADDRESS>Problem

We want to manually set inlets and outlets using the TaskFlow API.
There is no extractor currently for _PythonDecoratedOperator.

Solution

Adds extractor, facet, and schema for PythonDecoratedExtractor.

Note: All schema changes require discussion. Please link the issue for context.

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).
Checklist

[ x] You've signed-off your work
[ x] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[ ] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] You've updated the CHANGELOG.md with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)

Hey @Tylerpfarris, could you rebase your commit on top of main branch?

hey @Tylerpfarris Take a look at: https://github.com/OpenLineage/OpenLineage/blob/main/spec/Naming.md I think the Datasets that are output from this would need to conform to that naming spec.

Hello Tyler. All the reformatting included in the PR makes it hard to review. Could you look at the contributing guidelines and avoid the reformatting?
https://github.com/OpenLineage/OpenLineage/blob/main/CONTRIBUTING.md#creating-pull-requests

hey @Tylerpfarris. generally speaking PythonDecoratedExtractor is implemented as PythonExtractor. Therefore, it should be enough to append PythonDecoratedOperator to the list returned from PythonExtractor's get_operator_classnames classmethod. The other proposal to have inlets/outlets parsed into new facet should be considered separately, an attempt was made in #384.
Also, please refer to above comments, reformatting makes it hard to review.

Hey @JDarDagran, Thanks for the advice and the direction- I'm going to close this PR and work on issue #384.

Hey Julien, thanks for the feedback. Would it be better if I opened a new
PR then?
On Fri, Jun 24, 2022 at 6:00 PM Julien Le Dem @.***>
wrote:

Hello Tyler. All the reformatting included in the PR makes it hard to
review. Could you look at the contributing guidelines and avoid the
reformatting?
https://github.com/OpenLineage/OpenLineage/blob/main/CONTRIBUTING.md#creating-pull-requests
—
Reply to this email directly, view it on GitHub
https://github.com/OpenLineage/OpenLineage/pull/886#issuecomment-1166144169,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASDHOT5BCJR7JBGCPZ7PYATVQZDYHANCNFSM5ZV7EDXA
.
You are receiving this because you were mentioned.Message ID:
@.***>


np.matrix is no longer recommended and may be removed in the future

This PR changes all active np.matrix variables to np.array in latcontrol_indi.py (np.matrix docs message about deprecation). Since the arrays are all no larger than 2D, no change in output should occur.
Here's the comparison of the dot products of K and C both as matrices and as arrays:
>>> np.allclose(np.dot(K, C), np.dot(np.array(K), np.array(C)))
True

I see this is not tested in process replay. Let's get a RAV4 and a Prius in there so both LQR and INDI are verified.

Added Prius and RAV4 routes to process replay in 516da927f9a1f04be4cbc281bc1b3c73092a4a36. Can you rebase?

Let me try


Fix floating-point precision errors

I've carefully reworked this package to only perform a single math operation on all float values. Exponential notation expansion happens without performing any float-math operations, but when we still need to call the power() function on the integer representing the floating value, to convert it to a decimal. This needs to be replaced with something to handle precision errors.

https://github.com/JosephTLyons/lenient_parse/pull/67

Fixed
FloatTestData(
  input: "2.712",
  expected_program_output: Ok(2.712),
  expected_python_output: Ok("2.712"),
),

// Would produce a floating point error in v1.3.1: 7.5776864147000005
FloatTestData(
  input: "7.5776864147",
  expected_program_output: Ok(7.5776864147),
  expected_python_output: Ok("7.5776864147"),
),

Now, we have
// Currently produces :<PHONE_NUMBER>.328557
FloatTestData(
  input: "8556272791.3285562727",
  expected_program_output: Ok(8_556_272_791.328556),
  // Python doesn't output a precise value for this input
  expected_python_output: Ok("8556272791.328556"),
),


:focus-within supported in Edge, but BCD says it isn't

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details
https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-within
In the browser support , table is showing no support on the Edge. However, the support is now available in the Edge too.
https://caniuse.com/#search=focus within
Thank you

This got fixed https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-within#Browser_compatibility