Compatibility with 133.0b3

Hi, may I ask for version bump to be compatible with TB 133.0b3?

Bump'd and awaiting review on ATN.

@lkosson
Above worked in few hours for 133.0b3, but today my TB automatically updated to 134.0b3 and here we go again...
Is there any way to wildcard compatibility in any way to support future versions?
I suspect that TB is not allowing that. If that the case I will consider disabling autoupdates.

IIRC ATN rejected submissions with wildcard strict_max_version and submissions with version higher than current daily build. There is a separate compatibility settings in ATN but I was told not to change it there for reasons I can't really remember.
I have now removed restriction on max version directly in ATN settings anyway. The addon can now be installed on TB 134 and hopefully next versions too. I hope it doesn't break anything.


[Bug] [clickhouse source] Unsupported data type data type in array is not supported

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
I want to synchronize clickhouse data to hive.
Some fields in the clickhouse table are Array (Date),
and an error is reported after running 。data type in array is not supported.
By looking up the source code, I found that an exception
thrownew ClickhouseConnectorException (CommonErrorCode.UNSUPPORTED_DATA_TYPE, "data type in array is not supported:"+subArrayDataType. getDataType())
was directly thrown in the TypeConvertUtil class;
Can you support this type？Thanks
SeaTunnel Version
2.3.0release
SeaTunnel Config
env {
  execution.parallelism = 1
  job.mode = "STREAMING"
}

source {

   Clickhouse {
    host = "<IP_ADDRESS>:8123"
    database = "dist"
    sql = "select soon_appl_date,'2022-03-21' as partitions from dist.ics_ln_loan  limit 10"
    username = "default"
    password = "6lYaUiFi"
    result_table_name = "test"
  }
}

transform {

}
sink {
  # choose stdout output plugin to output data to console

  Hive {
    kerberos.enable="N"
    table_name = "ods_tmp.test_seatunnel_sink"
    metastore_uri = "thrift://p71368v.hulk.bjmd.qihoo.net:9083"
    partition_by = ["partitions"]
    sink_columns = ["soon_appl_date", "partitions"]
  }
}

Running Command
bin/start-seatunnel-flink-connector-v2.sh --config ./config/flink.ck2hive.batch.conf.template

Error Exception
data type in array is not supported.

Flink or Spark Version
Flink1.13.6release
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

please assign to me; thx。


npx create-turbo@latest installs beta/release candidate version of the dependencies

Verify canary release

[X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue
https://github.com/Aloneduckling/turborepo-issue
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Windows
Which canary version will you have in your reproduction?
2.0.6-canary.0
Describe the Bug
npx create-turbo@latest installs beta/release candidate version of dependencies. Below is the package.json for apps/docs next app

Expected Behavior
The version of the installed dependencies should be stable and not the beta/RC ones.
To Reproduce

npx create-turbo@latest
Check the dependencies installed in apps/docs

Additional context
No response

Thanks for the issue! This is intended since these Next.js dependencies will be stable in the coming weeks.
If you prefer, you can downgrade them. 👍


Improve and fix decrypt command

Improve and fix "decrypt" command:

The option and default for the private key should be the same as in the "download" command.
The default output dir can be the same as the input dir since encrypted files have an additional extension. Maybe better than using the working directory. But we can discuss that point.
This PR also fixes the determination of the output file name (should be derived only form input file name, not from input file path).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 3 (33.33%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 73.62%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ghga_connector/cli.py
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
720

Relevant Lines:
978

💛  - Coveralls


Error: 'Network.setCookies' wasn't found

I'm trying to set cookies and I have some code like this:
Promise.all([
  client.send('Network.enable', {}),
  client.send('Network.setCookies', { cookies: [{ acookie: true }]})
]).then(function() {
  return client.send('Page.navigate', { url });
}).catch(function(err) {
  console.error(err);
});

I get this error though: Error: 'Network.setCookies' wasn't found
When I try this (or some example code they have) with Puppeteer, it seems to work.
Am I doing maybe something wrong or is the headless_shell binary perhaps not supporting this?

Hi @ile Hm.. It might be that Network.setCookies does not yet exist in the Chrome Debugging Protocol version that ships with the latest Stable-channel version of Chromium. It's difficult to tell when Network.setCookies was introduced looking at the documentation. You could try specifying another binary (dev or beta channels) for serverless-chrome to use. Alternatively you could loop over Network.setCookie (singular). Something along the lines of:
for (const cookie of cookies) {
    await Network.setCookie({
      ...cookie,
      url: getUrlFromCookie(cookie),
    })
}

source

Hi @adieuadieu and thanks for the tip & reply. Network.setCookie seems to work.
Closing this for now.


Examples makefiles: align /usr/local with /src Makefile

In the /src Makefile, /usr/local can be overriden by the user.
Align the /example Makefile & Makefile.Web with that.

@Tchan0 thanks for the review!


Support editing already existing ink-/stamp-annotations

Disclaimer: This is more or less a clone of issue #15403 with an expanded scope
Attach (recommended) or Link to PDF file here:
dummy.pdf
Configuration:

Web browser and its version: Firefox 116.0.3
Operating system and its version: Windows 10 (22H2)
PDF.js version: 3.8.110
Is a browser extension: No

Steps to reproduce the problem:

Add an ink or stamp annotation
Save the pdf under a different name
Reload the saved pdf
The added ink-/stamp-annotations are "burnt in" and can't be edited anymore

What is the expected behavior? (add screenshot)
I would have expected to be able to edit/remove the added annotations.
What went wrong? (add screenshot)
The annotations are "burnt in" after saving. Subsequent reloads of the pdf won't let me edit or remove them

Are there any plans to move on this issue in an upcoming release?

Yes, we are planning to work on this soon. However, if you're up for it, we'd happily accept contributions to make it happen faster.

#18834 did this for stamp annotations.
#18972 is the first step to do this for ink annotations too.


Update Composer dependencies (2021-09-14-00-13)

Visual regression test passed!
View the visual regression test report


Vertical and Surface Swimming

Implemented smooth character rotations while swimming vertically. 90deg when ascending on SPACE and -90deg when descending on C. Combined with WSAD results in 45deg or -45deg respectively.
Implemented surface swimming: Once reaching the surface, the character will swim at surface until C is pressed to dive.

Ported to studios: https://github.com/webaverse-studios/app/pull/58


Add parser for /proc/[pid]/maps

Hi!
This adds support for parsing process memory mappings information from /proc/[pid]/maps.

Hi Dan!
Thanks a lot for taking the time to review this patch! (and sorry for the delay in answering, I have been sick for a couple of weeks).
I have incorporated most of your suggested changes in the update to the PR (thanks for the feedback, the code looks much better now).
The only pending point is the MapType {File, Anonymous} enum change to the API (see my comment above). Could you comment on my proposal, please? (I'd rather have your feedback before changing the API).

Sounds good!  No worries about the delay, I'm not always the quickest myself :)

Hi Dan!
I finally got around to change the API as per your suggestions. I have added a new MemoryMapKind enum that encodes the mapping type (file-backed, generic anonymous, vDSO, etc.).
I have also moved all fields that only make sense for file-backed mappings to a new FileMap struct, which is used by the MemoryMapKind::File enum variant.
I have added a file() -> Option<&FileMap> method to the MemoryMap struct to make client code that is only interested in file-backed mappings somewhat simpler (it avoids the necessity of using pattern matching in some use cases).
Apart from that, I have also extracted device number parsing onto its own function parse_dev() and the code now uses the device number to determine whether the mapping is file-backed (the previous approach used the inode number, which should also work, but comparing to the null device number will definitely work).
Let me know if there are any other changes that might improve the code. If not, I can rebase and squash the pull request branch (so it can be merged as a single logical commit).

Any update?


chore: unify error usage

@mcansh Thanks for catching that!  Yeah that router directory is gone in the release branch which should merge down to dev today.  We should probably avoid too many unnecessary changes in remix-server-runtime and remix-react until we get this RR 6.4 work merged into dev (hopefully soon!)


Remove month information out of vic_run()

There are still a few instances in which the current month is used (mainly as an array index) in vic_run() to determine parameter values.  Ideally we can move all references to the current month (or date or record) outside of vic_run().

:+1:

@jhamman I think I can fix this issue very quickly.  Only 3 offending lines remain, and one of them only requires a simple substitution of one variable for another.  The other 2 are the displacement and roughness variables you and I discussed before.  I'd be happy to set up veg_var versions of these, along the lines of LAI and albedo, which would solve this whole thing.

Note: dmy is used in a few other places in vic_run, and getting rid of those will take more effort since the use of dmy penetrates pretty far down.  dmy->month is used in canopy_evap() to access various veg_lib array elements and dmy->day_of_year is used in solve_snow() to determine if the the snowpack is in accumulation or ablation phase.  Many functions therefore have dmy in the argument list to pass it all the way down to canopy_evap().

Another thing dmy->day_in_year is used for is in the call to compute_coszen().  This happens in 2 places, one in vic_run()->calc_Nscale_factors() and the other in vic_run()->surface_fluxes() in prep for the call to faparl().  These two instances are (a) redundant and (b) only invoked if CARBON is true.  I could create a veg_var or atmos element for coszen, compute it outside vic_run(), and pass to the functions that need it via vic_run().  Let me know if you would like me to do this.

@tbohn -
I think we follow the ideas you've suggested here. Specifically for the main occurrences of dmy in vic_run().
I don't think it is worth the effort at this point to remove the dmy strcut from solve_snow or canopy_evap. It seems like we're not going to completely get rid of dmy in vic_run before we release 5.0.
However, I think calculating cozen in vic_force and adding it to the atmos_struct makes since.  I don't think we need to worry about the memory usage for forcing variables (especially in the classic driver).

OK, will do.

@tbohn - I'm going to leave this open and will move the Milestone to somday.  Thanks for taking care of the majority of this issue.

Not clear what the remaining issue is. Can we close this one (since it was addressed at least in part) and open a new one that clearly states what the remaining issue is?

I can open a new issue if you'd like.  The remaining unfixed issue is:
dmy is used in a few other places in vic_run, and getting rid of those will take more effort since the use of dmy penetrates pretty far down. dmy->month is used in canopy_evap() to access various veg_lib array elements and dmy->day_of_year is used in solve_snow() to determine if the the snowpack is in accumulation or ablation phase. Many functions therefore have dmy in the argument list to pass it all the way down to canopy_evap().

I've opened a new issue to deal with remaining instances of dmy in vic_run() and subsidiary functions: #510

Thanks @tbohn.


bazel build of tensorflow fails

Issue description
I just did a nix-shell -p python36Packages.tensowflow and got this error:
Loading:
Loading: 0 packages loaded
Analyzing: target //tensorflow/tools/pip_package:build_pip_package (2 packages loaded)
Analyzing: target //tensorflow/tools/pip_package:build_pip_package (29 packages loaded)
Analyzing: target //tensorflow/tools/pip_package:build_pip_package (123 packages loaded)
ERROR: /build/output/external/jpeg/BUILD:122:12: Illegal ambiguous match on configurable attribute "deps" in @jpeg//:jpeg:
@jpeg//:k8
@jpeg//:armeabi-v7a
Multiple matches are not allowed unless one is unambiguously more specialized.
ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted:

Technical details

system: "x86_64-linux"
host os: Linux 4.14.51, NixOS, 18.09pre143771.a8c71037e04 (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.0.4
channels(philipp): "nixpkgs-18.09pre140731.c29d2fde74d"
channels(root): "nixos-18.09pre143771.a8c71037e04"
nixpkgs: /home/philipp/.nix-defexpr/channels/nixpkgs

@abbradar @FRidh @jyp looks like upstream breakage due to tensorflow having used the value of android_cpu instead of cpu and bazel having changed the default value of android_cpu.
From what I've read, I believe you have to either downgrade bazel to 0.11, upgrade tensorflow, or manually incorporate the android_cpu to cpu fix into tensorflow

@pmiddend Master now uses a wheel-based build. So the title should be changed to "bazel build of tensorflow fails".

@jyp: fixed.

Fixed by #64716


test: replace puppeteer with playwright

Firefox and WebKit have troubles running at the moment 🤦♂

hey @FezVrasta, looking at https://github.com/popperjs/popper-core/runs/444293247
it seems that webkit is not launching. can you add { dumpio: true } in the launch args for webkit? it would help us debug what's going wrong there.
 TimeoutError: waiting for firstPageProxy failed: timeout 30000ms exceeded

      at Function.waitWithTimeout (node_modules/playwright-core/lib/helper.js:120:30)
      at WKBrowser._waitForFirstPageTarget (node_modules/playwright-core/lib/webkit/wkBrowser.js:74:31)
      at Function.connect (node_modules/playwright-core/lib/webkit/wkBrowser.js:47:23)

Added! Thanks for the help!

So.. WebKit is failing because of Protocol error (Playwright.createContext): Browser has been closed., and I don't know what to do to fix it.
Firefox and Chrome instead are failing because of some cross-platform difference in the way tables are rendered, I'm trying to run the tests inside a local container so that we sort out these differences.

All the browsers are running, but most of the tests are failing for unknown reasons.

I fixed the table inconsistencies, now there's only that issue where javascript doesn't seem to be running... This is 100% a playwright issue tho so I suppose I will have to wait for some playwright update.


Fix micrometre unit shorthand

Hello,
I listened to Thomas Mansencal's interview on Podcast.__init__('Python') and thought the project sounded really interesting. I'm looking forward to taking a closer look at it for some upcoming calibration work I'll be doing; I think it could turn out to be a valuable resource.
Anyway, I was exploring some of the documentation and noticed that micrometre was was shortened to mm instead of μm in the Luminous Efficiency Functions notebook. As I'm in need of some experience with the workflow involved in contributing to open source projects, I've attached the trivial fix in this PR. The  nm shorthand in the same paragraph has also been enclosed in the math environment for visual consistency with the other occurrences in the notebook.

Thanks @Legendin!

I think it could turn out to be a valuable resource.

Oh and let us know if you need any help :)


Fix for PP3 logic_cell_macro model

This PR fixes the logic_cell_macro simulation model by removing blocking assignment and compacting the FF model into a single assign statement.

@tpagarani Could you please take a look?

@rakeshm75 can you please review the changes in the simulation model as well

Approved.


tetragon: Warn on sensor bug can flood the logs make it debug

Flooding the logs with Warnings when a sensors have an error can be rather noisy. Instead these should be behind metrics that we can collected. Anyways lets make it Debug fow now and prode sensor owners to add proper error metrics for each type.
Signed-off-by: John Fastabend<EMAIL_ADDRESS>

Not sure we might have related metrics. I think we need to do a audit of the code and check we have metrics in the right spots.

Merging seeing it was green before and I simply fixed commit sign off.


basic RFC1459 compliance

[x] Initial handshake commands

[x] NICK
[x] USER

[x] User management commands

[x] QUIT
[x] PING
[x] PONG
[x] WHOIS
[x] WHOWAS
[x] ISON
[x] PRIVMSG
[x] NOTICE
[x] MODE (as wrapper for user properties)

[ ] Channel management commands

[x] JOIN
[x] PART
[x] TOPIC
[ ] KICK
[x] NAMES
[x] LIST
[ ] MODE (as wrapper for channel properties)
[x] WHO

[ ] Oper commands

[ ] OPER
[ ] KILL
[ ] CONNECT
[ ] SQUIT
[ ] STATS (as wrapper for IRCv3.3 XINFO)

[x] Misc commands

[x] INFO
[x] VERSION
[x] MOTD

TBD: implement stub SUMMON/USERS?

I removed PASS as a hard requirement as I think our use of IAL will provide the same use-cases in a better way.

I removed LUSERS as only RFC2812 defines it as mandatory.  We can add it (or some subset of it) later.


Fix "STATICFILES_STORAGE/STORAGES are mutually exclusive" on Django>=4.2

This fixes
django.core.exceptions.ImproperlyConfigured: STATICFILES_STORAGE/STORAGES are mutually exclusive.

when running on Django 4.2 or later. See https://docs.djangoproject.com/en/dev/releases/4.2/#custom-file-storages
This currently blocks pytest-django support for 4.2 (pytest-django has django-configurations support), so a release including this change will be appreciated!

Thanks for the review @pauloxnet, I added a changelog and added djmain.

Thanks for the review @pauloxnet, I added a changelog and added djmain.

Thanks for your work. Unfortunately Django 5.0 supports only Python 3.10 and 3.11, could you remove 'djmain' from older Python pipeline to fix broken tests?

Oops, misread the last sentence of https://docs.djangoproject.com/en/dev/releases/5.0/#python-compatibility.  Let's try again.

Oops, misread the last sentence of https://docs.djangoproject.com/en/dev/releases/5.0/#python-compatibility. Let's try again.

It's working now. I'm going to approve and merge. Thanks for your contribution.


5way 5shot experiment of miniImageNet

Hello,
your work is really good.
But as i try a 5way 5shot experiment in miniImageNet(transductive method), the result of my experiment could not achieve 76.37% as you reported. I did this experiment just with the code 'python3 trainer.py --dataset mini --num_ways 5 --num_shots 5 --trainsductive True' in readme. Since i don't have a file named 'trainer.py', so i changed 'trainer.py' to 'train.py'. Were you having some other adjustments when doing experiments?
Thank you very much!

Hi,
I'm so sorry, there were some typos in README file.
trainer.py --> train.py
trainsductive --> transductive
Because of the second typo, 'transductive' argument is just set with default value 'False', ignoring your command '--trainsductive True'. Therefore, the obtained result is actually the non-transductive result.
I have just fixed them, so please try again with the command in updated README.
'python3 train.py --dataset mini --num_ways 5 --num_shots 5 --transductive True'  should work.


Macbook 8,2 & BCM94331PCIEBT4CAX - Only 802.11 a/b/g/n support (no ac)

Hey,
I've installed the bluetooth&wifi in my early 2011 macbook pro and got handoff and airdrop working with this tool. However, wireless ac isn't listed as a mode on my en1 interface. Is there any way to enable this?
Thanks

The MacBook Pro 2012 does not support 802.11ac. See the Technical Specifications


Popconfirm: Cannot read property 'destroy' of null

Hi,
First of all thanks for the nice library!
I think I've found a bug while using the popconfirm component. I've used it to confirm a deletion of an object. When clicking on 'OK', the component itself is removed (so including the popconfirm component). Although the popconfirm component doesn't exist anymore, it tries to destroy itself after a timeout of 300ms, which results in the following error message:
Uncaught TypeError: Cannot read property 'destroy' of null
A workaround is to set a timeout before removing the component, but that's not really a nice thing to do.
Do you have a solution for this?
Thanks!

Thanks for your kind words :)
Recently I'm busy with other things, so I'm sorry for the late reply. I will look into it, maybe need a few days longer

One year after, this bug still exists in the latest version


System Bridge does not launch following clean install

Description
I have had System Bridge running successfully in the past, but following a machine upgrade and Windows reinstall, it does not launch. Attempting to launch will show a command prompt window for a split-second, but it disappears too fast to see anything. This occurs whether I attempt to launch from the shortcut or exe in Explorer, or from the command prompt. The logs indicate it's the gui that's failing. The node js runtime remains visible in task manager, but as I have not configure an API key or MQTT details. I can't use the API, websocket or MQTT to verify whether the underlying service is working.
I noticed #1254 reports similar behavior, but as the error logs show different messages (mine does not have a 503 anywhere), I raised this as a new issue.
What Platform / OS are you running?
Windows
What version are you running?
2.8.4
Anything in the logs or a references that might be useful?
2022-04-07 15:17:19 info: System Bridge 2.8.4: D:\Program Files\System Bridge - D:\Program Files\System Bridge\system-bridge.exe - D:\Program Files\System Bridge - ["D:\\Program Files\\System Bridge\\system-bridge.exe","C:\\snapshot\\system-bridge\\dist\\index.js"] -  -  -  -
2022-04-07 15:17:19 info: Process Manager - PATH_API: C:\snapshot\system-bridge\dist\components\api\index.js
2022-04-07 15:17:19 info: Process Manager - Starting api - ["D:\\Program Files\\System Bridge\\system-bridge.exe","C:\\snapshot\\system-bridge\\dist\\components\\api\\index.js"]
2022-04-07 15:17:19 info: Process Manager - PATH_GUI_PACKAGED: D:\Program Files\System Bridge\system-bridge-gui\system-bridge-gui.exe
2022-04-07 15:17:19 info: Process Manager - Starting gui - ["D:\\Program Files\\System Bridge\\system-bridge-gui\\system-bridge-gui.exe","--host","localhost","--api-key","***","--api-port","9170","--frontend-port","9170","--log-level","info","--websocket-port","9172"]
2022-04-07 15:17:20 info: API - D:\Program Files\System Bridge - D:\Program Files\System Bridge\system-bridge.exe - D:\Program Files\System Bridge - ["D:\\Program Files\\System Bridge\\system-bridge.exe","C:\\snapshot\\system-bridge\\dist\\components\\api\\index.js"] -  -  -  -
2022-04-07 15:17:20 warn: MDNSBrowser - MDNS error caught: dns service error: service not running
2022-04-07 15:17:20 info: API - API started on port 9170
2022-04-07 15:17:20 error: Process Manager - gui: Exited with code: 1
2022-04-07 15:17:20 info: Process Manager - gui: Restarting in 10 seconds..
2022-04-07 15:17:21 warn: MDNSAdversisement - MDNS error caught: dns service error: service not running
2022-04-07 15:17:30 info: Process Manager - PATH_GUI_PACKAGED: D:\Program Files\System Bridge\system-bridge-gui\system-bridge-gui.exe
2022-04-07 15:17:30 info: Process Manager - Starting gui - ["D:\\Program Files\\System Bridge\\system-bridge-gui\\system-bridge-gui.exe","--host","localhost","--api-key","***","--api-port","9170","--frontend-port","9170","--log-level","info","--websocket-port","9172"]
2022-04-07 15:17:31 error: Process Manager - gui: Exited with code: 1
2022-04-07 15:17:31 info: Process Manager - gui: Restarting in 10 seconds..

Additional information
No response

Resolved in #1551
The release will be when I am happy that 3.0.0 is stable


:book: Minor formatting tweaks to architecture docs

Summary
Fixed some bullet formatting in the architecture document to resolve inconsitency between the intent (from the markdown) vs the rendered docuemntation.
Related issue(s)
None

/ok-to-test

@jewzaam Thanks for the PR. Can you please sign off your commit?  You can simply amend it .

@ezrasilvera thanks for the poke, missed that in my review of contributing guide.  done :)

Thanks for the PR
/approve


Files.CreateDirectory implementation

Files.CreateDirectory based https://github.com/FrendsPlatform/Frends.Directory task and supported on .net 6

Please add documentation link to https://github.com/FrendsPlatform/Frends.Files/blob/main/README.md.


error while loading library(intansv)

Hi
I am getting the following error when i load the intansv.

library(intansv)
Error in fetch(key) :
lazy-load database '/Library/Frameworks/R.framework/Versions/3.2/Resources/library/intansv/help/intansv.rdb' is corrupt
In addition: Warning message:
In fetch(key) : internal error -3 in R_decompress1
Error in fetch(key) :
lazy-load database '/Library/Frameworks/R.framework/Versions/3.2/Resources/library/intansv/help/intansv.rdb' is corrupt
In addition: Warning message:
In fetch(key) : internal error -3 in R_decompress1

Please try the latest version of intansv at Github.


What propType should I use for this.props.router?

I inject router context using the withRouter function from react-router. I specify the type in propTypes as React.PropTypes.object.  i.e:
static propTypes = {
  router: React.PropTypes.object.isRequired,
}

Is there a more specific type for this?

Nope, it's just an object.


The selected image doesn't fits properly in the imageview🐞🐞

after clicking the save image button it always shows no image selected before showing the image saved toast.

ok we are assigning you this task.

Thank you for your contribution @vinitfreakk.


Add support for CircuitBreaker.getRemainingDelay()

Fixes the second part of #188 by adding support for CircuitBreaker.getRemainingDelay().
@whiskeysierra - Let me know if this is what you had in mind and feel free to review.

Coverage decreased (-0.1%) to 91.051% when pulling 9463f7a50a1fcee3a675c08e1d033407f4a320ec on remaining-delay into 1eebb664a631cb838279721635069e999598adf8 on master.

@whiskeysierra - Let me know if this is what you had in mind and feel free to review.

Yes, looks great!


Graph getting shifted towards right during reflow.

Bug Report
Description

When we create a graph with space as a y-axis label and try to update the y-axis label with reflow, the graph is shifting the position to the right.
Steps to Reproduce

Create a graph having only y-axis with space as y-axis label
Try to update the y-axis label with the reflow method
graph gets shifted towards the right to accommodate the y-axis label.

Sandbox example here
Expected Behavior

when y-axis label is updated, the graph should not get shifted.

Hey @sdadn , We have our application where graph and other components align with the timeline. But with this design, when we pass space as the label, the graph will no longer align with the timeline and other components. I have attached the screenshot of how the graph does not align with the timeline and other graph components when we pass space as a label.


gtk: 3.24.35 -> 3.24.36

Description of changes
Updated to latest bug fix release 3.24.36.
changelog: https://gitlab.gnome.org/GNOME/gtk/-/compare/3.24.35...3.24.36?from_project_id=665&straight=false

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.05 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

/cc @raskin @NixOS/gnome

https://github.com/NixOS/nixpkgs/pull/208973


Inconsistency between paper and code regarding decoder input

Dear authors,
In the paper it is said that the decoder takes some portion of the input sequence as start tokens. The term "recent past" is used here thus I suppose it should be the last label_len portion of the input sequence that is used. However in the code it's actually the first label_len portion that is used, which seems to be consistent with Informer. Is this intended?

Not a problem here, it is indeed the last portion of data_x, which corresponds to the first portion of data_y.


linux kernel modules

Don't load properly. Need to recognize system instructions as well as parse the different program header / init / exit functions.

Also worth understanding the various kind of exception table sections that things like get_user and put_user use to redirect execution to a fixup function when a fault occurs.
See here:
http://code.woboq.org/linux/linux/arch/x86/include/asm/asm.h.html#47
http://code.woboq.org/linux/linux/arch/x86/include/asm/uaccess.h.html#195

@lucasduffey  wants me to click the thumb but i won't.

Support added as of v1.1.1345


Ring documentation

In GitLab by @franzi233 on Aug 18, 2021, 15:11
Documentation of the ring-architeture

In GitLab by @franzi233 on Aug 18, 2021, 15:11
assigned to @franzi233

In GitLab by @franzi233 on Aug 18, 2021, 15:11
marked this issue as related to #21


FIX Script editor doesn´t send unsaved script #28693

This commit fix #28693.
Script editor doesn´t send unsaved version of a script in editor_script_changed signal (sends disk stored version) unless you close other script and apply_scripts() is performed.
I did this pull request https://github.com/godotengine/godot/pull/28694 but i will sure that test eliminating "if (current)" comprobation but don´t. sorry about that. This commit is tested, works, respect changing script -> docs docs -> script, respect undo, etc...

Thanks!


Got this error when running forgae node

C:\Users\goote_000\Documents\smart_contracts\new_aepps\voting_app>forgae node
error: 'Error: Command failed: docker   ps
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.39/containers
/json: open //./pipe/docker_engine: The system cannot find the file specified. I
n the default daemon configuration on Windows, the docker client must be run ele
vated to connect. This error may also indicate that the docker daemon is not run
ning.
' stdout = '' stderr = 'error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker
_engine/v1.39/containers/json: open //./pipe/docker_engine: The system cannot fi
nd the file specified. In the default daemon configuration on Windows, the docke
r client must be run elevated to connect. This error may also indicate that the
docker daemon is not running.
'

there is a pre-requisite to have docker installed on your system, is this true for your configuration?

ok i did nw i have this
error: 'Error: Command failed: docker   ps
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.39/containers/json: open //./pipe/docker_engine: The
system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run ele
vated to connect. This error may also indicate that the docker daemon is not running.
' stdout = '' stderr = 'error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.39/containers/json: open //./
pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docke
r client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

when i run docker ps on my commandline i get this
C:\Users\goote_000\Documents\smart_contracts\new_aepps\voting_app>docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED
STATUS              PORTS               NAMES

but forgae node still gives
C:\Users\goote_000\Documents\smart_contracts\new_aepps\voting_app>forgae node
error: 'Error: Command failed: docker   ps
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.39/containers
/json: open //./pipe/docker_engine: The system cannot find the file specified. I
n the default daemon configuration on Windows, the docker client must be run ele
vated to connect. This error may also indicate that the docker daemon is not run
ning.
' stdout = '' stderr = 'error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker
_engine/v1.39/containers/json: open //./pipe/docker_engine: The system cannot fi
nd the file specified. In the default daemon configuration on Windows, the docke
r client must be run elevated to connect. This error may also indicate that the
docker daemon is not running.
'

any idea?????
i'm using windows 8.1

did you restart your pc? docker daemon is not running is not a issue related to forgae but docker problem in general

i did and my docker is working

also got this err when i ran forgae compile
C:\Users\goote_000\Documents\smart_contracts\new_aepps\voting_app>forgae compile
===== Compiling contracts =====
API ERROR: Error: connect ECONNREFUSED <IP_ADDRESS>:3001
What am i missing???

@maptuhec @alekseytsekov can you help here?

i was using docker toolbox


Compatibility with Elixir v1.15

Hi there,
I was just trying to use the latest RC in a project with elixir v1.15 and ran into a bit of a problem. Not sure if you intended to make this compatible with elixir 1.15 but apparently I am not the only one trying to do this.

Hey @kbredemeier, we can give it a try but I think we should require at least https://github.com/elixir-lang/elixir/releases/tag/v1.15.1 so that important Logger fixes are already there. Can you please update the version spec to something like ~> 1.16 or ~> 1.15.1?

At least the title was refering to v1.15 :sweat_smile:
Sure thing, changed the version to v1.15.1 and updated the CI matrix.


Downmerged BDT Task def from master for Azure Support

@acesiddhu can you accept/close as appropriate.

not going for m95


1042 add license headers

Description:

This PR modifies all src files to include hedera sdk license headers.
Related issue(s):
Fixes #1042
Notes for reviewer:

Checklist

[x] Documented (Code comments, README, etc.)
[x] Tested (unit, integration, etc.)

I think we need to table this PR for a bit because there are some issue:

The current eslint-plugin-license-header plugin is really slow from my use. Eslint typically takes ~40s which is already slow, and with this plugin enabled it was taking several minutes.
Even if we remove eslint-plugin-license-header we still have the issue where prettier will automatically remove trailing spaces from the license header which is not allowed in this case. The other side of this, is if we keep the trailing spaces there then linting will fail indicating we have trailing white space.
So, our current options are:
Remove our linting trailing white space and remove prettier as an autoformatter. The huge downside to this is we'll need to manually format our files which is extremely tedious and something I don't think we should be doing. To eliminate this issue we can go further and completely remove our use of eslint, but the downside to that is we're more likely to make silly mistakes.
Update the license headers to not have trailing spaces?

Note: I've tried using // prettier-ignore-start and // prettier-ignore-end https://prettier.io/docs/en/ignore.html but it doesn't seem to apply (maybe I'm doing something wrong?).
Just figured I'd check the mirror node since they use JS as well and https://github.dev/hashgraph/hedera-mirror-node/blob/74050227b0754f12ef48479691066525bd37401e/hedera-mirror-test/k6/src/rest/apis.js#L12 doesn't have a trailing space. So, I'm a confused if the trailing space is needed or not, I thought it was a requirement but maybe not?

I'm going to guess I'm overreacting to this so I'm going to go ahead and merge this in. If necessary we can fix the trailing spaces issue later.


IIS-HttpPlatformHandler-Kestrel app not processing POST's

In reference to an app that I just refactored (steps listed here) from IIS-Helios (beta7) to IIS-HttpPlatformHandler (beta8), GET is processed properly (e.g., the Contact view loads) ...
[HttpGet]
[Route("/contact/{d?}")]
public IActionResult Index(string d, Visitor visitor = null) { ... }

... but POST is resulting in a 404 (e.g., POST to the Contact controller fails) ...
[HttpPost]
[Route("/contact/{d?}")]
[ValidateAntiForgeryToken]
public async Task<IActionResult> Index(Visitor visitor) { ... }

IIS is seeing the POST, from the IIS log ...
2015-10-16 17:33:14 <IP_ADDRESS> POST /contact - 8001 - <IP_ADDRESS> Mozilla/5.0+(Windows+NT+10.0;+WOW64)+AppleWebKit/537.36+
(KHTML,+like+Gecko)+Chrome/46.0.2490.71+Safari/537.36
http://www.~~~~~~~~.com:8001/contact 404 0 0 2007

The HttpPlatformHandler log (stdout.log) is up but not showing anything (can I enable some more detailed tracing here? Also a bit curious about why it says "Now listening on: http://localhost:33176" when this is on the VM/IIS?) ...
Hosting environment: Production
Now listening on: http://localhost:33176
Application started. Press Ctrl+C to shut down.
<end of entries>

@davidfowl had me remove the --server.urls argument from the web.cmd command to get the app responsive (to GET's anyway), resulting in this ...
"commands": {
  "web": "Microsoft.AspNet.Hosting --server Microsoft.AspNet.Server.Kestrel"
},

Nothing changed in the app between going from Helios to HttpPlatformHandler. POST works under IIS Express locally but is failing on the VM under IIS-HttpPlatformHandler.
Packages:
"Microsoft.AspNet.Diagnostics": "1.0.0-beta8",
"Microsoft.AspNet.Diagnostics.Entity": "7.0.0-beta8",
"Microsoft.AspNet.Hosting": "1.0.0-beta8",
"Microsoft.AspNet.Mvc": "6.0.0-beta8",
"Microsoft.AspNet.Mvc.TagHelpers": "6.0.0-beta8",
"Microsoft.AspNet.Server.Kestrel": "1.0.0-beta8",
"Microsoft.AspNet.StaticFiles": "1.0.0-beta8",
"System.ComponentModel.TypeConverter": "4.0.1-beta-*",
"System.Net.Http": "4.0.0-beta-*",
"System.Net.Security": "4.0.0-beta-*",
"System.Net.Sockets": "4.0.10-beta-*",
"Microsoft.AspNet.Antiforgery": "1.0.0-beta8",
"System.Runtime.Serialization.Primitives": "4.0.10-beta-*",
"WindowsAzure.Storage": "5.0.3-preview",
"Microsoft.Framework.Configuration": "1.0.0-beta8",
"Microsoft.Dnx.Compilation.CSharp.Abstractions": "1.0.0-beta8",
"Microsoft.VisualStudio.Web.BrowserLink.Loader": "14.0.0-beta8"

Runtime:
dnx-coreclr-win-x<IP_ADDRESS>-beta8

Server:
Azure VM: WS 2012 (not R2), IIS 8

Do you need to add app.UseIISPlatformHandler(); to you Startup.cs?
For what it's worth, my log also says "Now listening on: http://localhost:2256", but my app is working fine in IIS.

@MaxxDelusional I just tried it ... same result ... 404 when POST'ing back to that controller.
Your POST's are working ok?
btw- I didn't even know about the Microsoft.AspNet.IISPlatformHandler package ... it would cool if someone from the team could say when that package is required. The app seems to run fine (without that package and including POST's) when run locally.

Ok, I see it now ... Microsoft.AspNet.IISPlatformHandler is described. It is required beyond loading the app for forwarding windows auth, scheme, and client ip.
https://github.com/aspnet/Templates/issues/189
Anyway ... still work'in this POST-404 problem.

@GuardRex Yep, I tested my POSTS and they are working. I honestly didn't know what UseIISPlatformHandler did, I just saw it in the new template, so I thought it was required.
I'm wondering if it has something to do with [ValidateAntiForgeryToken]. Could you try removing that attribute and see if it works.

@MaxxDelusional That's good. It's just me then.
I tried without Antiforgery, but it didn't fix it. Not surprising really, since I would think the Antiforgery cookie and header bits come after the pipeline gets back to the controller. This is acting like it can't find the POST route. I'll try putting a different controller and view up and see if this is just isolated to that one Contact Us webform.

@MaxxDelusional Yeah, so another [HttpPost] controller in the Home controller did work. This is a route problem apparently with that one controller. I'll keep digging.

Does IActionResult affect the route in some way?
async Task<string> WORKS :+1: ... 200 OK
[HttpPost]
[Route("/contact/{d?}")]
[ValidateAntiForgeryToken]
public async Task<string> Contact(Visitor visitor)
{
    return await Task.Run(() => { return "Contact test okey-dokey!"; });
}

async Task<IActionResult> does NOT :-1: work ... 404!
[HttpPost]
[Route("/contact/{d?}")]
[ValidateAntiForgeryToken]
public async Task<IActionResult> Contact(Visitor visitor)
{
    ViewBag.StatusMessage = await Task.Run(() => { return "Contact test okey-dokey!"; });
    return View(visitor);
}

IActionResult does NOT :-1: work ... 404!
[HttpPost]
[Route("/contact/{d?}")]
[ValidateAntiForgeryToken]
public IActionResult Contact(Visitor visitor)
{
    ViewBag.StatusMessage = "Contact test okey-dokey!";
    return View(visitor);
}

Two separate issues found here ... I'm going to close, open a separate issue on each, and reference back to this issue in each.

@GuardRex I'm actually seeing the same issue as you (GET works but POST doesn't).
Our action returns Task<IActionResult and we get 404 (like you).
Did you ever get to the bottom of this? We're using released beta8 and everything else works just fine.

@GuardRex False alarm, the error is actually banal - we do not have a route for "/error" (yet it is configured right there in Startup.cs) and there was an error (and rather early in the process).
Logs finally helped me understand where the issue was, just had to turn it on in web.config: new publish already creates logs next to the approot and webroot but doesn't enable it.


Checksum

HTTP supports a Want-Digest request header and a Digest response header. The tiled server should support these, and the tiled Python client should support optional digest verification after download.

Note: as an implementation detail, we alright compute the md5 digest for most ETag headers, though this should not be generally relied on. I wonder if there is a clean way to avoid computing the md5 twice though, in those instances where ETag and Digest would happen to be the same.


Promise keep node process from exit

I write a tool for migrating data using Bluebird promise, so that user can trigger this tool directly via node command. Example:

node migrate.js

The problem is, node process will not exist after complete all operation. Here is the content of main migrate.js, the exec() function return a promise.
var migrate = require('../elasticsearch/migrate');
var setting = require('../../config/setting');

var cmd = new migrate(setting.NewConfig.search, true);
cmd.exec()
    .then(function () {
        console.info('Operation completed');
        //process.exit(0);
    })
    .catch(function (err) {
        console.error(err);
        //process.exit(1);
    });

At the moment I must trigger process.exit() to kill the process.

Promise doesn't keep process alive, it is some other api that you are using.

Thank for you support, after rechecking current open handles via process._getActiveHandles(), the process was kept from exiting because of Knex library.


Can you open-source your full prompt bank?

Hi Kim:
Thank you for your great work. But I had some problem with your code as it does not open source all prompt set. As I am comparing your work with my own, lacking this prompt will result in a unfair compare.
best

Thank you for your interest in our work. The relevant documents are currently located in the "prompt_bank" folder for your review.


Converting the covariance estimate problem as a first pass

Let's use this ticket to keep track of discussions on building the covariance estimation DSC benchmark. The goal is two-fold: testing out DSC2, and building a meaningful benchmark on this interesting problem that will shed lights into research in relevant problems. Will try to schedule an in person meeting with people involved and update here.

Moving this discussion to
https://github.com/stephenslab/dsc2-omega


Updated Readme to reflect all the latest changes and improvements

I would add:

[ ] Add a separate part with requirements (ADK version, Host/VM having Hyper-V installed and enabled, VirtIO (specific versions for ws2016 and others)

I would add:

[ ] The Powershell example script should be written with splatting workflow

I would add:

[ ] Present the users the method to create a Windows image (not syspreped) with the asociated risks.

Points that would help being mentioned:
What a golden image is, what is its purpose and how can it be generated (step by step guide and tips maybe?)
What is a MaaS image and its purpose (step by step guide and some tips and tricks)
How do you generate a final image that is ready to be used from a golden image (also)
A short description on what the script does when building each type of image, following the script execution flow.


Release 1.12.0

Current coverage is 96.05% (diff: 100%)

Merging #729 into master will not change coverage

@@             master       #729   diff @@
==========================================
  Files            87         87
  Lines          2459       2459
  Methods           0          0
  Messages          0          0
  Branches        329        329
==========================================
  Hits           2362       2362
  Misses           68         68
  Partials         29         29

Powered by Codecov. Last update acf2314...d34d381

Good luck on the conference, @artem-zinnatullin!

:+1:


Adding simple dockerd config file to rotate logs from containers

Related issue is here: https://github.com/awslabs/amazon-eks-ami/issues/36
I myself have seen pods evicted due to disk pressure. Similar configuration is in place on other managed Kubernetes services already.

Hey thanks for this PR! We'll have to vet this and get back to you

We'll have to vet this and get back to you

Please do, I think it's important and there's already other users who have had issues with disk space. And I've had pods evicted due to disk pressure.
I actually tried to build the AMI myself to test it but packer fails to find the source AMI. Not sure how to fix that.

This seems like a must have in a default image. +1 from me

I've tested the PR but as is it's not working for me, I had to add:

OK done.

Why can't I build the AMI myself to test it?
$ make all
packer validate eks-worker-al2.json
Template validated successfully.
packer build -var source_ami_id=ami-0abb414482ac85a71 eks-worker-al2.json
amazon-ebs output will be in this color.

==> amazon-ebs: Prevalidating AMI Name: amazon-eks-node-1540976573
==> amazon-ebs: Error querying AMI: InvalidAMIID.NotFound: The image id '[ami-0abb414482ac85a71]' does not exist
==> amazon-ebs: 	status code: 400, request id: 6a22ead4-b494-42fd-a462-4d1071ac1613
Build 'amazon-ebs' errored: Error querying AMI: InvalidAMIID.NotFound: The image id '[ami-0abb414482ac85a71]' does not exist
	status code: 400, request id: 6a22ead4-b494-42fd-a462-4d1071ac1613

Ahh, I had to run export AWS_DEFAULT_REGION=us-west-2 first.

Yeah I ran into that issue too... to change it to us-east-1 you need to export AWS_DEFAULT_REGION and change this variable:
https://github.com/awslabs/amazon-eks-ami/blob/master/eks-worker-al2.json#L3
The other gotcha is that you can't update this variable to us-east-1 otherwise it don't work...
https://github.com/awslabs/amazon-eks-ami/blob/master/eks-worker-al2.json#L6

@micahhausler if you need more convincing 😉
https://techmovers.salemove.com/infrastructure/2018/11/01/Productionproofing+EKS.html#no-docker-log-rotation

@micahhausler would be great to see this released! 😸

Any eta when the image will be released? We're seeing prod issues that would be resolved by this.

We are planning a release on Dec 5th with this patch.

@eswarbala is there a new date for the release which includes this patch? I was hoping to use official AMIs with this issue resolved.

Yes, it's in amazon-eks-node-1.10-v20181210 but still no release on this repo 🤔

Ah, it looks like the version/naming convention has changed. I was waiting for an AMI called amazon-eks-node-v26 (to match version 23 to 25, versions 18 to 23 were named slightly differently). It looks like amazon-eks-node-1.10-v20181210 is the one that is referenced in the documentation.
(Unrelated to this change – is it possible to have something like Subscribing to Amazon ECS-Optimized Amazon Linux AMI Update Notifications but for the EKS AMIs?)

Still we are running manually docker system prune -a -f to remove unused images and killed containers on each worker node to avoid eviction on pods , can you please confirm if this works and how often it will remove images and containers or do we need to add any flag while creating/attaching nodes to EKS.
we are using latest version of AMI
let me know if need more details

@yrsurya this is already done by kubelet: https://kubernetes.io/docs/concepts/cluster-administration/kubelet-garbage-collection/


file upload cannot working

upload file button cannot working in webview can help?
@andreipfeiffer @DanielMSchmidt @marconett

@hellohaidev can you please provide more information?
RN version, compileSdkVersion, buildToolsVersion, etc

web.js
import React,{Component} from 'react'
import {Text,WebView,BackHandler} from 'react-native'
import CustomWebView from "react-native-webview-android-file-upload";

export default class Web extends Component {
  constructor(props) {
    super(props)

    this.state = {
      canGoBack: false
    }
   }

componentDidMount() {
    BackHandler.addEventListener('hardwareBackPress', this.handleBackPress);
}

componentWillUnmount() {
    BackHandler.removeEventListener('hardwareBackPress', this.handleBackPress);
}

handleBackPress = () => {
   if (this.state.canGoBack) {
      this.refWeb.goBack();
    }
  else{
    this.props.navigation.goBack(null)
    }
  return true;
}

onNavigationStateChange(navState) {
    this.setState({
    canGoBack: navState.canGoBack
 });
}

    render(){
        return(

            <CustWeomWebView
              source={{ uri: "http://<IP_ADDRESS>/sigadis/mobile/" }}
              startInLoadingState={true}
              ref={(myWeb) => this.refWeb = myWeb}
              // onNavigationStateChange={this.onNavigationStateChange.bind(this)}

            />

            // <WebView
            // ref={(myWeb) => this.refWeb = myWeb}
            // onNavigationStateChange={this.onNavigationStateChange.bind(this)}
            // source={{ uri: 'http://<IP_ADDRESS>/webmaterial' }}
            // allowUniversalAccessFromFileURLs={true}
            // />

        )
    }

}

package.json

{
  "name": "diskominfo",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest"
  },
  "dependencies": {
    "exit-on-double-back": "^1.0.1",
    "init": "^0.1.2",
    "native-base": "^2.12.0",
    "react": "16.6.3",
    "react-native": "0.58.4",
    "react-native-app-intro-slider": "^1.0.1",
    "react-native-gesture-handler": "^1.0.16",
    "react-native-super-grid": "^2.4.4",
    "react-native-webview-android": "^1.1.17",
    "react-native-webview-android-file-upload"<EMAIL_ADDRESS>    "react-native-webview-file-upload-android": "^1.1.2",
    "react-navigation": "^2.18.3"
  },
  "devDependencies": {
    "babel-core": "7.0.0-bridge.0",
    "babel-jest": "24.1.0",
    "jest": "24.1.0",
    "metro-react-native-babel-preset": "0.51.1",
    "react-test-renderer": "16.6.3"
  },
  "jest": {
    "preset": "react-native"
  }
}

build.gradle
apply plugin: "com.android.application"

import com.android.build.OutputFile

/**
 * The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
 * and bundleReleaseJsAndAssets).
 * These basically call `react-native bundle` with the correct arguments during the Android build
 * cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the
 * bundle directly from the development server. Below you can see all the possible configurations
 * and their defaults. If you decide to add a configuration block, make sure to add it before the
 * `apply from: "../../node_modules/react-native/react.gradle"` line.
 *
 * project.ext.react = [
 *   // the name of the generated asset file containing your JS bundle
 *   bundleAssetName: "index.android.bundle",
 *
 *   // the entry file for bundle generation
 *   entryFile: "index.android.js",
 *
 *   // whether to bundle JS and assets in debug mode
 *   bundleInDebug: false,
 *
 *   // whether to bundle JS and assets in release mode
 *   bundleInRelease: true,
 *
 *   // whether to bundle JS and assets in another build variant (if configured).
 *   // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
 *   // The configuration property can be in the following formats
 *   //         'bundleIn${productFlavor}${buildType}'
 *   //         'bundleIn${buildType}'
 *   // bundleInFreeDebug: true,
 *   // bundleInPaidRelease: true,
 *   // bundleInBeta: true,
 *
 *   // whether to disable dev mode in custom build variants (by default only disabled in release)
 *   // for example: to disable dev mode in the staging build type (if configured)
 *   devDisabledInStaging: true,
 *   // The configuration property can be in the following formats
 *   //         'devDisabledIn${productFlavor}${buildType}'
 *   //         'devDisabledIn${buildType}'
 *
 *   // the root of your project, i.e. where "package.json" lives
 *   root: "../../",
 *
 *   // where to put the JS bundle asset in debug mode
 *   jsBundleDirDebug: "$buildDir/intermediates/assets/debug",
 *
 *   // where to put the JS bundle asset in release mode
 *   jsBundleDirRelease: "$buildDir/intermediates/assets/release",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in debug mode
 *   resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in release mode
 *   resourcesDirRelease: "$buildDir/intermediates/res/merged/release",
 *
 *   // by default the gradle tasks are skipped if none of the JS files or assets change; this means
 *   // that we don't look at files in android/ or ios/ to determine whether the tasks are up to
 *   // date; if you have any other folders that you want to ignore for performance reasons (gradle
 *   // indexes the entire tree), add them here. Alternatively, if you have JS files in android/
 *   // for example, you might want to remove it from here.
 *   inputExcludes: ["android/**", "ios/**"],
 *
 *   // override which node gets called and with what additional arguments
 *   nodeExecutableAndArgs: ["node"],
 *
 *   // supply additional arguments to the packager
 *   extraPackagerArgs: []
 * ]
 */

project.ext.react = [
    entryFile: "index.js"
]

apply from: "../../node_modules/react-native/react.gradle"

/**
 * Set this to true to create two separate APKs instead of one:
 *   - An APK that only works on ARM devices
 *   - An APK that only works on x86 devices
 * The advantage is the size of the APK is reduced by about 4MB.
 * Upload all the APKs to the Play Store and people will download
 * the correct one based on the CPU architecture of their device.
 */
def enableSeparateBuildPerCPUArchitecture = false

/**
 * Run Proguard to shrink the Java bytecode in release builds.
 */
def enableProguardInReleaseBuilds = false

android {
    compileSdkVersion rootProject.ext.compileSdkVersion

    defaultConfig {
        applicationId "com.diskominfo"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 1
        versionName "1.1.1"
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86", "arm64-v8a"
        }
    }
     signingConfigs {
        release {
            if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
                storeFile file(MYAPP_RELEASE_STORE_FILE)
                storePassword MYAPP_RELEASE_STORE_PASSWORD
                keyAlias MYAPP_RELEASE_KEY_ALIAS
                keyPassword MYAPP_RELEASE_KEY_PASSWORD
            }
        }
    }
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
            signingConfig signingConfigs.release
        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
            def versionCodes = ["armeabi-v7a":1, "x86":2, "arm64-v8a": 3]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
}

dependencies {

    implementation project(':react-native-webview-file-upload-android')
    implementation project(':react-native-webview-android-file-upload')
    implementation project(':react-native-gesture-handler')
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
    implementation "com.facebook.react:react-native:+"  // From node_modules

}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    ext {
        buildToolsVersion = "28.0.2"
        minSdkVersion = 16
        compileSdkVersion = 28
        targetSdkVersion = 27
        supportLibVersion = "28.0.0"
    }
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.2.1'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        mavenLocal()
        google()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
    }
}

task wrapper(type: Wrapper) {
    gradleVersion = '4.7'
    distributionUrl = distributionUrl.replace("bin", "all")
}

androidmanifest.xml
<```
manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.diskominfo">
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
 <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />

<application
  android:name=".MainApplication"
  android:label="@string/app_name"
  android:icon="@mipmap/ic_launcher"
  android:roundIcon="@mipmap/ic_launcher_round"
  android:allowBackup="false"
  android:theme="@style/AppTheme">
  <activity
    android:name=".MainActivity"
    android:label="@string/app_name"
    android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
    android:windowSoftInputMode="adjustResize">
    <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
    </intent-filter>
  </activity>
  <activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
    <provider
      android:name="android.support.v4.content.FileProvider"
      android:authorities="${applicationId}.fileprovider"
      android:exported="false"
      android:grantUriPermissions="true">
      <meta-data
          android:name="android.support.FILE_PROVIDER_PATHS"
          android:resource="@xml/file_provider_paths" />
  </provider>
</application>

@andreipfeiffer this file im use

procces build failed and error here :
> Task :react-native-webview-android-file-upload:verifyReleaseResources FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-webview-android-file-upload:verifyReleaseResources'.

@andreipfeiffer if im use react-native-webview  do i have change my code??

@hellohaidev you have 2 different packages included there:
:react-native-webview-file-upload-android
:react-native-webview-android-file-upload
Please remove both of them:

react-native unlink <package>
npm uninstall <package>

Then install react-native-webview as described the Getting Started section.

ok im already for uninstall this package,and im install react-native-webview, and my question is for upload image,do i have change my code??

One of the packages that you've used is released by me react-native-webview-android-file-upload.
That package was included into this official package react-native-webview.
They both support File Upload.
Please checkout the File Upload Guide.
Code changes should be minimal:
import { WebView } from "react-native-webview";
// instead of
import WebView from "react-native-webview-android-file-upload";

ok im try
On Sun, Mar 3, 2019 at 5:10 PM Andrei Pfeiffer<EMAIL_ADDRESS>wrote:

One of the packages that you've used is released by me
react-native-webview-android-file-upload.
That package was included into this official package react-native-webview.
They both support File Upload.
Please checkout the File Upload Guide
https://github.com/react-native-community/react-native-webview/blob/master/docs/Guide.md#add-support-for-file-upload
.
Code changes should be minimal:
import { WebView } from "react-native-webview";
// instead of
import WebView from "react-native-webview-android-file-upload";
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/react-native-webview/issues/379#issuecomment-469008099,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArNpD1dTM2QYAHZWrFqezwR_OXsPrhrCks5vS5-PgaJpZM4baz14
.

I have same issue, any solution please?

@hellohaidev first of all, your problem is that you cannot build for release? Or what exactly is the issue?
@xuho what "same issue" do you have exactly? The example @hellohaidev pasted here uses a different Custom WebView package.

@xuho what "same issue" do you have exactly?
In my website, user can pick multiple file to upload, but in webview, user can only pick 1 file, any option to pick multiple file to upload?
Thank you.

@xuho this package supports multiple file upload. Just specify the multiple attribute to your input element:
<input type="file" multiple />

Doing so, should allow you to select multiple files from your device.

I want disabled fiture camera or hiden camera??why
On Mon, Mar 4, 2019, 8:36 PM Andrei Pfeiffer<EMAIL_ADDRESS>wrote:

@xuho https://github.com/xuho this package supports multiple file
upload. Just specify the multiple
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file#multiple
attribute to your input element:

Doing so, should allow you to select multiple files from your device.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/react-native-webview/issues/379#issuecomment-469254935,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArNpDysSdY0aM1GFtLHyIhQKLp_1DLbuks5vTSFRgaJpZM4baz14
.

Can i hiden or disabled camera fiture?
On Mon, Mar 4, 2019, 8:37 PM hello dev<EMAIL_ADDRESS>wrote:

I want disabled fiture camera or hiden camera??why
On Mon, Mar 4, 2019, 8:36 PM Andrei Pfeiffer<EMAIL_ADDRESS>wrote:

@xuho https://github.com/xuho this package supports multiple file
upload. Just specify the multiple
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file#multiple
attribute to your input element:

Doing so, should allow you to select multiple files from your device.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/react-native-webview/issues/379#issuecomment-469254935,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArNpDysSdY0aM1GFtLHyIhQKLp_1DLbuks5vTSFRgaJpZM4baz14
.

@hellohaidev please explain more clearly your use case. I don't understand what you are asking.
Also, if your question is not related to this Issue, please open another Issue.
Thank you.

Sory,when I use the file upload feature, it displays the camera and sotrage
file options, the features I use are only uploading files from storage, how
can the file upload feature be clicked, the camera feature cannot be used,
as in library react native webview upload android previous
On Mon, Mar 4, 2019, 8:41 PM Andrei Pfeiffer<EMAIL_ADDRESS>wrote:

@hellohaidev https://github.com/hellohaidev please explain more clearly
your use case. I don't understand what you are asking.
Also, if your question is not related to this Issue, please open another
Issue.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/react-native-webview/issues/379#issuecomment-469256445,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArNpD1jgGFuq2UTAE_LfVDJYYQwIa45Rks5vTSJ4gaJpZM4baz14
.

@hellohaidev to disable photo/video capture, and allow only existing file selection, try this "hack" (not sure if it works):
<input type="file" accept="*/*" />

@andreipfeiffer is it any possible to enable only camera, and disable file chooser? Thanks in advance.

@Hamada92 currently that's not supported, as far as I'm aware.
We would need to support the capture attribute for that.
There's already an Issue for that: #378
Unfortunately, I'm currently very busy in organizing a conference, so any help would be highly appreciated.

@Titozzz I think this can be closed.


Revert internal data structure to simple hash

Previous versions of MemoWise used an array as the
internal cache data structure, where each memoized method
uses a unique array index. However, complex inheritance
structures make it easy to have multiple methods accidentally
share the same array index on the same object, resulting
in nondeterministic and incorrect behavior.
While we may explore that optimization again in the future,
for the time being we are switching to a hash data structure
keyed on method name, which is safer because two methods
cannot share the same name in Ruby.
Fixes #251
Before merging:

[ ] Copy the table printed at the end of the latest benchmark results into the README.md and update this PR
[x] If this change merits an update to CHANGELOG.md, add an entry following Keep a Changelog guidelines with semantic versioning

Thank you @PikachuEXE !

I just notice the branch name is back-to-the-future... 🤣


Create link_multistage_frame_io.yml

Description
Add new coverage for abused frame.io as landing pages
Associated samples

Sample 1
Sample 2

Associated hunts

Hunt 1

/update-test-rules

No hits in shared EML.  Will continue to monitor for another week.

still no hits in shared EMLs, ready for review


Error sending Delta files to Azure Gen2 Storage if over a certain size.

dlt version
1.3.0
Describe the problem
I have a pipeline that copies a table from sql server to azure gen2 storage. It creates delta files and works fine if the parquet files are small however when they get larger I get a failure sending and it goes into a retry loop.
Logging the azure storage I can see this sort of error details
StatusCode         500
StatusText         InternalError
DurationMs         29870
ServerLatencyMs	   379
Uri                https://playgrounddatapstorage.blob.core.windows.net:443/bronze/risk360_us_sql_server_test/elapsedtime/part-00001-151d1409-68ce-4e58-8065-f6c535dfdd38-c000.snappy.parquet
ServiceType        blob
ObjectKey          /playgrounddatapstorage/bronze/risk360_us_sql_server_test/elapsedtime/part-00001-151d1409-68ce-4e58-8065-f6c535dfdd38-c000.snappy.parquet
RequestHeaderSize  452
RequestBodySize    58179144
ResponseHeaderSize 173
Category           StorageWrite
TlsVersion         TLS 1.2
MetricResponseType NetworkError
SourceAccessTier   Invalid

the pipeline part looks like this
           # Create a dlt pipeline object
            pipeline = dlt.pipeline(
                pipeline_name="client_tables_to_delta_az",
                destination=filesystem(bucket_url=f'az://bronze/'), #abfss
                dataset_name=folder_dataset_name,
            )

            # Run the pipeline
            load_info = pipeline.run(all_data(connection_string, database_item),
                                     write_disposition="append",
                                     table_format="delta",
                                    )

and this is a chunk of the log file around where it fails though it only shows that its waiting and that if fails after 5 retries.
2024-11-21 17:34:11 - azure.core.pipeline.policies.http_logging_policy - INFO - Request URL: 'https://playgrounddatapstorage.blob.core.windows.net/bronze/risk360_us_sql_server_test/init'
Request method: 'DELETE'
Request headers:
    'x-ms-version': 'REDACTED'
    'Accept': 'application/xml'
    'x-ms-date': 'REDACTED'
    'x-ms-client-request-id': 'd22291ad-a82e-11ef-9aac-8c3b4a05b5bc'
    'User-Agent': 'azsdk-python-storage-blob/12.23.1 Python/3.12.6 (Windows-11-10.0.22631-SP0)'
    'Authorization': 'REDACTED'
No body was attached to the request
2024-11-21 17:34:12 - azure.core.pipeline.policies.http_logging_policy - INFO - Response status: 202
Response headers:
    'Content-Length': '0'
    'Server': 'Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0'
    'x-ms-request-id': '6b951afc-201e-0061-763b-3cd464000000'
    'x-ms-client-request-id': 'd22291ad-a82e-11ef-9aac-8c3b4a05b5bc'
    'x-ms-version': 'REDACTED'
    'x-ms-delete-type-permanent': 'REDACTED'
    'x-ms-deletion-id': 'REDACTED'
    'Date': 'Thu, 21 Nov 2024 17:34:11 GMT'
2024-11-21 17:34:12 - azure.core.pipeline.policies.http_logging_policy - INFO - Request URL: 'https://playgrounddatapstorage.blob.core.windows.net/bronze/risk360_us_sql_server_test/init?comp=REDACTED'
Request method: 'PUT'
Request headers:
    'Content-Length': '52'
    'x-ms-meta-is_directory': 'REDACTED'
    'x-ms-version': 'REDACTED'
    'Content-Type': 'application/xml'
    'Accept': 'application/xml'
    'x-ms-date': 'REDACTED'
    'x-ms-client-request-id': 'd237588e-a82e-11ef-9e2e-8c3b4a05b5bc'
    'User-Agent': 'azsdk-python-storage-blob/12.23.1 Python/3.12.6 (Windows-11-10.0.22631-SP0)'
    'Authorization': 'REDACTED'
A body is sent with the request
2024-11-21 17:34:12 - azure.core.pipeline.policies.http_logging_policy - INFO - Response status: 201
Response headers:
    'Content-Length': '0'
    'Last-Modified': 'Thu, 21 Nov 2024 17:34:12 GMT'
    'Etag': '"0x8DD0A52B69D7BFC"'
    'Server': 'Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0'
    'x-ms-request-id': '6b951b43-201e-0061-333b-3cd464000000'
    'x-ms-client-request-id': 'd237588e-a82e-11ef-9e2e-8c3b4a05b5bc'
    'x-ms-version': 'REDACTED'
    'x-ms-content-crc64': 'REDACTED'
    'x-ms-request-server-encrypted': 'REDACTED'
    'Date': 'Thu, 21 Nov 2024 17:34:11 GMT'
2024-11-21 17:34:12,193|[INFO]|54140|53952|dlt|load.py|resume_started_jobs:291|Found 0 that are already started and should be continued
2024-11-21 17:34:12,193|[INFO]|54140|53952|dlt|load.py|complete_jobs:390|Will complete 0 for<PHONE_NUMBER>.2547312
2024-11-21 17:34:12,195|[INFO]|54140|53952|dlt|load.py|start_new_jobs:274|Will load additional 2, creating jobs
2024-11-21 17:34:12,196|[INFO]|54140|53952|dlt|load.py|submit_job:169|Will load file<PHONE_NUMBER>.2547312\new_jobs\elapsedtime.ea8c3353ec.0.parquet with table name elapsedtime
2024-11-21 17:34:12,669|[INFO]|54140|53952|dlt|load.py|submit_job:169|Will load file<PHONE_NUMBER>.2547312\new_jobs\_dlt_pipeline_state.4857574e24.0.jsonl with table name _dlt_pipeline_state
2024-11-21 17:34:13,686|[INFO]|54140|53952|dlt|load.py|complete_jobs:390|Will complete 2 for<PHONE_NUMBER>.2547312
2024-11-21 17:34:13,687|[DEBUG]|54140|53952|dlt|load.py|complete_jobs:393|Checking state for job elapsedtime.ea8c3353ec.parquet
2024-11-21 17:34:13,694|[INFO]|54140|53952|dlt|load.py|create_followup_jobs:369|Job elapsedtime.ea8c3353ec.parquet CREATED a new FOLLOWUP JOB C:\Users\PHILAR~1\AppData\Local\Temp\elapsedtime.ea8c3353ec.0.reference placed in new_jobs
2024-11-21 17:34:13,696|[INFO]|54140|53952|dlt|load.py|complete_jobs:459|Job for elapsedtime.ea8c3353ec.parquet completed in load<PHONE_NUMBER>.2547312
--------------------- Load all_data in<PHONE_NUMBER>.2547312 ----------------------
Jobs: 1/2 (50.0%) | Time: 4.19s | Rate: 0.24/s
Memory usage: 266.70 MB (83.70%) | CPU usage: 0.00%

2024-11-21 17:34:13,717|[DEBUG]|54140|53952|dlt|load.py|complete_jobs:393|Checking state for job _dlt_pipeline_state.4857574e24.jsonl
2024-11-21 17:34:13,719|[INFO]|54140|53952|dlt|load.py|complete_jobs:459|Job for _dlt_pipeline_state.4857574e24.jsonl completed in load<PHONE_NUMBER>.2547312
2024-11-21 17:34:13,720|[INFO]|54140|53952|dlt|load.py|start_new_jobs:274|Will load additional 1, creating jobs
2024-11-21 17:34:13,721|[INFO]|54140|53952|dlt|load.py|submit_job:169|Will load file<PHONE_NUMBER>.2547312\new_jobs\elapsedtime.ea8c3353ec.0.reference with table name elapsedtime
2024-11-21 17:34:13,751|[INFO]|54140|53632|dlt|filesystem.py|run:138|Will copy file(s) ['C:\\Users\\PhilArmstrong\\.dlt\\pipelines\\client_tables_to_delta_az\\load\\normalized\\1732210401.2547312\\completed_jobs\\elapsedtime.ea8c3353ec.0.parquet'] to delta table az://bronze/risk360_us_sql_server_test/elapsedtime [arrow buffer: 0]
2024-11-21 17:34:14,764|[INFO]|54140|53952|dlt|load.py|complete_jobs:390|Will complete 1 for<PHONE_NUMBER>.2547312
2024-11-21 17:34:14,765|[DEBUG]|54140|53952|dlt|load.py|complete_jobs:393|Checking state for job elapsedtime.ea8c3353ec.reference
2024-11-21 17:34:14,766|[DEBUG]|54140|53952|dlt|load.py|complete_jobs:397|job elapsedtime.ea8c3353ec.reference still running
2024-11-21 17:34:14,768|[INFO]|54140|53952|dlt|load.py|start_new_jobs:274|Will load additional 0, creating jobs
2024-11-21 17:34:15,777|[INFO]|54140|53952|dlt|load.py|complete_jobs:390|Will complete 1 for<PHONE_NUMBER>.2547312
2024-11-21 17:34:15,778|[DEBUG]|54140|53952|dlt|load.py|complete_jobs:393|Checking state for job elapsedtime.ea8c3353ec.reference
2024-11-21 17:34:15,778|[DEBUG]|54140|53952|dlt|load.py|complete_jobs:397|job elapsedtime.ea8c3353ec.reference still running
2024-11-21 17:34:15,779|[INFO]|54140|53952|dlt|load.py|start_new_jobs:274|Will load additional 0, creating jobs
2024-11-21 17:34:16,790|[INFO]|54140|53952|dlt|load.py|complete_jobs:390|Will complete 1 for<PHONE_NUMBER>.2547312
2024-11-21 17:34:16,791|[DEBUG]|54140|53952|dlt|load.py|complete_jobs:393|Checking state for job elapsedtime.ea8c3353ec.reference
2024-11-21 17:34:16,792|[DEBUG]|54140|53952|dlt|load.py|complete_jobs:397|job elapsedtime.ea8c3353ec.reference still running
2024-11-21 17:34:16,793|[INFO]|54140|53952|dlt|load.py|start_new_jobs:274|Will load additional 0, creating jobs
2024-11-21 17:34:17,802|[INFO]|54140|53952|dlt|load.py|complete_jobs:390|Will complete 1 for<PHONE_NUMBER>.2547312

2024-11-21 17:44:33,778|[DEBUG]|36652|42288|dlt|load.py|complete_jobs:393|Checking state for job elapsedtime.ea8c3353ec.reference
2024-11-21 17:44:33,780|[DEBUG]|36652|42288|dlt|load.py|complete_jobs:397|job elapsedtime.ea8c3353ec.reference still running
2024-11-21 17:44:33,781|[INFO]|36652|42288|dlt|load.py|start_new_jobs:274|Will load additional 0, creating jobs
2024-11-21 17:44:34,788|[INFO]|36652|42288|dlt|load.py|complete_jobs:390|Will complete 1 for<PHONE_NUMBER>.2547312
2024-11-21 17:44:34,789|[DEBUG]|36652|42288|dlt|load.py|complete_jobs:393|Checking state for job elapsedtime.ea8c3353ec.reference
2024-11-21 17:44:34,790|[DEBUG]|36652|42288|dlt|load.py|complete_jobs:397|job elapsedtime.ea8c3353ec.reference still running
2024-11-21 17:44:34,792|[INFO]|36652|42288|dlt|load.py|start_new_jobs:274|Will load additional 0, creating jobs
2024-11-21 17:44:35,586|[ERROR]|36652|17540|dlt|load.py|w_run_job:248|Transient exception in job elapsedtime.ea8c3353ec.reference in file C:\Users\PhilArmstrong\.dlt\pipelines\client_tables_to_delta_az\load\normalized\1732210401.2547312\started_jobs\elapsedtime.ea8c3353ec.1.reference
Traceback (most recent call last):
  File "C:\Users\PhilArmstrong\OneDrive - POWWR\Dev\venv\Lib\site-packages\dlt\common\destination\reference.py", line 420, in run_managed
    self.run()
  File "C:\Users\PhilArmstrong\OneDrive - POWWR\Dev\venv\Lib\site-packages\dlt\destinations\impl\filesystem\filesystem.py", line 161, in run
    write_delta_table(
  File "C:\Users\PhilArmstrong\OneDrive - POWWR\Dev\venv\Lib\site-packages\dlt\common\libs\deltalake.py", line 88, in write_delta_table
    write_deltalake(  # type: ignore[call-overload]
  File "C:\Users\PhilArmstrong\OneDrive - POWWR\Dev\venv\Lib\site-packages\deltalake\writer.py", line 323, in write_deltalake
    write_deltalake_rust(
OSError: Generic MicrosoftAzure error: Error after 5 retries in<PHONE_NUMBER>s, max_retries:10, retry_timeout:180s, source:error sending request for url (https://playgrounddatapstorage.blob.core.windows.net/bronze/risk360_us_sql_server_test/elapsedtime/part-00001-36118c25-ac6d-43b3-aad3-90a6131126f2-c000.snappy.parquet)
2024-11-21 17:44:35,801|[INFO]|36652|42288|dlt|load.py|complete_jobs:390|Will complete 1 for<PHONE_NUMBER>.2547312
2024-11-21 17:44:35,802|[DEBUG]|36652|42288|dlt|load.py|complete_jobs:393|Checking state for job elapsedtime.ea8c3353ec.reference
2024-11-21 17:44:35,805|[WARNING]|36652|42288|dlt|load.py|complete_jobs:430|Job for elapsedtime.ea8c3353ec.reference retried in load<PHONE_NUMBER>.2547312 with message Generic MicrosoftAzure error: Error after 5 retries in<PHONE_NUMBER>s, max_retries:10, retry_timeout:180s, source:error sending request for url (https://playgrounddatapstorage.blob.core.windows.net/bronze/risk360_us_sql_server_test/elapsedtime/part-00001-36118c25-ac6d-43b3-aad3-90a6131126f2-c000.snappy.parquet)
2024-11-21 17:44:35,805|[INFO]|36652|42288|dlt|load.py|start_new_jobs:274|Will load additional 1, creating jobs
2024-11-21 17:44:35,806|[INFO]|36652|42288|dlt|load.py|submit_job:169|Will load file<PHONE_NUMBER>.2547312\new_jobs\elapsedtime.ea8c3353ec.2.reference with table name elapsedtime
2024-11-21 17:44:35,852|[INFO]|36652|17540|dlt|filesystem.py|run:138|Will copy file(s) ['C:\\Users\\PhilArmstrong\\.dlt\\pipelines\\client_tables_to_delta_az\\load\\normalized\\1732210401.2547312\\completed_jobs\\elapsedtime.ea8c3353ec.0.parquet'] to delta table az://bronze/risk360_us_sql_server_test/elapsedtime [arrow buffer: 0]
2024-11-21 17:44:36,870|[INFO]|36652|42288|dlt|load.py|complete_jobs:390|Will complete 1 for<PHONE_NUMBER>.2547312
2024-11-21 17:44:36,924|[DEBUG]|36652|42288|dlt|load.py|complete_jobs:393|Checking state for job elapsedtime.ea8c3353ec.reference
2024-11-21 17:44:36,928|[DEBUG]|36652|42288|dlt|load.py|complete_jobs:397|job elapsedtime.ea8c3353ec.reference still running
2024-11-21 17:44:36,947|[INFO]|36652|42288|dlt|load.py|start_new_jobs:274|Will load additional 0, creating jobs
2024-11-21 17:44:37,962|[INFO]|36652|42288|dlt|load.py|complete_jobs:390|Will complete 1 for<PHONE_NUMBER>.2547312

Expected behavior
I would expect the files to either be successfully sent to azure storage either as a single file as with the smaller files or broken into blocks.
Steps to reproduce
I've managed to create some code to generate the issue
It works if the file is sent as parquet but if the format is delta it fails.
import dlt
from dlt import pipeline
from dlt.sources.filesystem import filesystem, read_csv
from dlt.destinations import filesystem as fs_destination
import pandas as pd
import numpy as np

dlt.config["normalize.data_writer.file_max_bytes"] = 5000000
dlt.config["runtime.log_level"] = "DEBUG"
dlt.config["progress"] = "log"

# Generate a dataset of 100MB
def generate_data(num_rows=4000000):
    data = {
        'id': np.arange(num_rows),
        'value': np.random.rand(num_rows),
        'timestamp': pd.date_range(start='1/1/2022', periods=num_rows, freq='T')
    }
    df = pd.DataFrame(data)
    return df

@dlt.resource(table_name='data3')
def reader():
    data = generate_data()
    yield data

# Define the destination (Azure Blob Storage)
mydestination = fs_destination(
    destination=filesystem(bucket_url=f'az://bronze/'),
    #credentials={
    #    "account_name": "your-azure-account-name",
    #    "account_key": "your-azure-account-key",
    #},
)

# Create a pipeline
pipeline = dlt.pipeline(
    pipeline_name="dummy_to_delta",
    dataset_name="dummy_to_delta",
    destination=mydestination,
)

info = pipeline.run(reader, write_disposition="append",
                    #loader_file_format="parquet",
                    table_format="delta",)
print(info)

Operating system
Windows
Runtime environment
Local
Python version
3.11
dlt data source
microsoft sql server but the problem also happens with a df datasource
dlt destination
Filesystem & buckets
Other deployment details
No response
Additional information
I have a pipeline that copies a table from sql server to azure gen2 storage. It creates delta files and works fine if the parquet files are small however when they get larger I get a failure sending and it goes into a retry loop.
Logging the azure storage I can see this sort of error details
StatusCode         500
StatusText         InternalError
DurationMs         29870
ServerLatencyMs	   379
Uri                https://playgrounddatapstorage.blob.core.windows.net:443/bronze/risk360_us_sql_server_test/elapsedtime/part-00001-151d1409-68ce-4e58-8065-f6c535dfdd38-c000.snappy.parquet
ServiceType        blob
ObjectKey          /playgrounddatapstorage/bronze/risk360_us_sql_server_test/elapsedtime/part-00001-151d1409-68ce-4e58-8065-f6c535dfdd38-c000.snappy.parquet
RequestHeaderSize  452
RequestBodySize    58179144
ResponseHeaderSize 173
Category           StorageWrite
TlsVersion         TLS 1.2
MetricResponseType NetworkError
SourceAccessTier   Invalid

the pipeline part looks like this
           # Create a dlt pipeline object
            pipeline = dlt.pipeline(
                pipeline_name="client_tables_to_delta_az",
                destination=filesystem(bucket_url=f'az://bronze/'), #abfss
                dataset_name=folder_dataset_name,
            )

            # Run the pipeline
            load_info = pipeline.run(all_data(connection_string, database_item),
                                     write_disposition="append",
                                     table_format="delta",
                                    )

Looking at the azure logs for smaller files they look like this
StatusCode         201
StatusText         Success
DurationMs         10
ServerLatencyMs    10
Uri                https://playgrounddatapstorage2.blob.core.windows.net:443/bronze/risk360_us_sql_server/customercountlog/database_name=Dfsc_Clearview/year=2028/part-00001-38473a92-4ebc-4991-bb54-381028d88834-c000.snappy.parquet
ServiceType        blob
ObjectKey          /playgrounddatapstorage2/bronze/risk360_us_sql_server/customercountlog/database_name=Dfsc_Clearview/year=2028/part-00001-38473a92-4ebc-4991-bb54-381028d88834-c000.snappy.parquet
RequestHeaderSize  489
RequestBodySize    4581
ResponseHeaderSize 279
Category           StorageRead
TlsVersion         TLS 1.2
MetricResponseType Success
SourceAccessTier   Invalid
SourceSystem       Azure

I also tried sending the larger parquet file using a standalone python script and the azure.storage.blob package
from azure.storage.blob import BlobServiceClient
from datetime import timedelta  # Import timedelta

# Create a BlobServiceClient with custom timeout settings
blob_service_client = BlobServiceClient(
    account_url="https://playgrounddatapstorage.blob.core.windows.net/",
    credential="Mykey")

# Upload a large file
blob_client = blob_service_client.get_blob_client(container="bronze", blob="test_load_large_file.parquet")
with open("C:/data/dlt/load_data_delta/dbo_elapsedtime/risk360_us_sql_server/elapsedtime/database_name=PJM_Settlements/year=2018/part-00001-8d376a4b-848b-4f27-84bc-34b70f9999b7-c000.snappy.parquet", "rb") as data:
   blob_client.upload_blob(data, overwrite=True)

This worked fine and seemed to send the file in blocks
the logs for one block look like this
StatusCode         201
StatusText         Success
DurationMs         6812
ServerLatencyMs    205
Uri                https://playgrounddatapstorage.blob.core.windows.net:443/bronze/test_load_large_file.parquet?comp=block&blockid=TURBd01EQXdNREF3TURBd01EQXdNREF3TURBd01EQXdNakE1TnpFMU1qQSUzRA%3D%3D
ServiceType        blob
ObjectKey          /playgrounddatapstorage/bronze/test_load_large_file.parquet
RequestHeaderSize  652
RequestBodySize    4194304
ResponseHeaderSize 237
Category           StorageWrite
TlsVersion         TLS 1.3
MetricResponseType Success
SourceAccessTier   Invalid
SourceSystem       Azure

I was also able to send pure parquet files to azure without an issue however delta seems to create larger parquet files.
I also tried adjusting a number of the dlt config items e.g.
# Set the DLT configuration
dlt.config["buffer_max_items"] = 25000
dlt.config["sources.sql_database.buffer_max_items"] = 25000
dlt.config["extract.workers"] = 1
dlt.config["normalize.workers"] = 1
dlt.config["load.workers"] = 1
dlt.config["normalize.data_writer.file_max_bytes"] = 5000000
dlt.config["data_writer.file_max_bytes"] = 10000
dlt.config["sources.data_writer.file_max_bytes"] = 10000
dlt.config["data_writer.file_max_items"] = 15000
dlt.config["file_max_items"] = 15000
dlt.config["sources.data_writer.file_max_items"] = 25000
dlt.config["sources.data_writer.file_max_items"] = 25000

I think that your problem is related to this: https://github.com/dlt-hub/dlt/issues/2030 which in turn unfortunately waits for a delta "bug" to be fixed.
we'll probably merge #2030 to give our users workaround (merge many files instead of a single big dataset)

ok. not sure of the details of that issue. Its worth pointing out that the file is created correctly in the normalized completed_jobs folder, but when it sends to azure it tries do it in a single block. If I use parquet and not delta the file is sent using small blocks. Also Delta files are created fine to a local filesystem its just when I want to use azure that if fails. Not sure if other cloud services have a similar issue.

@pwr-philarmstrong yes, if you set it to parquet, we use our own upload code and send it file by file (parallelized but limited to the amount of load step workers). For delta tables we use python deltalake which loads all files into memory before sending them. Like @rudolfix pointed out, we are waiting for a bug to be fixed in the deltalake rust backend.

Thanks for the clarification. I'll watch out for that bug being fixed.


build failure

I'm trying to build and getting this error:
https://gist.github.com/swills/c0b2852bafb507c4b06c71eb19d81f94
only thing I can find related is:
https://svn.boost.org/trac10/ticket/1011
but that's quite old. I am building on FreeBSD 12-CURRENT using clang 6.0.1. What am I missing?

I fixed the build, at least temporarily, so that it works under FreeBSD 12-CURRENT.  Since I'm building some of the boost libraries outside of bjam, I think some definitions are missing.  Temporarily I'm adding __USE_ISOC99 which fixes the build issue with boost.  I also add the PIC flag.


Building for Android does not work on Mac

As there are examples shown on Twitter of successful Android builds, I also wanted to give it a try but all I got was:
[ERROR] Failed to execute goal com.gluonhq:client-maven-plugin:0.1.10:compile (default-cli) on project hellofx: Error: You specified an android ndk, but it doesn't contain /Users/mpaus/Library/Android/sdk/ndk/toolchains/llvm/prebuilt/linux-x86_64/bin/ldlld -> [Help 1]

Obviously some path are hard-coded for a Linux environment.
I am using the client-maven-plugin 0.1.10 and GraalVM <IP_ADDRESS>.

We don't support Android development yet on Mac. (instructions for Linux will follow).


Network Injected Azure Cloud Shell Not Supported

Windows Terminal version
1.17.11461.0
Windows build number
10.0.22621.0
Other Software
No response
Steps to reproduce

Configure Cloud Shell with Azure Virtual Network injection according to the documentation. IMPORTANT: Deploy the virtual network in a Cloud Shell primary region to avoid failures, e.g. East US, West US, or South Central US as it seems secondary region support isn't guaranteed for the virtual network injection scenario in other regions.
Open an Azure Cloud Shell tab and perform device code login.
[Optional] Select a tenant from the list displayed by Terminal if appropriate for your account.
Elect whether to save connection settings.
Observe outputs.

Expected Behavior
A terminal prompt.
Actual Behavior
After logging in, selecting a tenant from my account list, and confirming saving connection settings, the terminal immediately displays:

Requesting a cloud shell instance...
Succeeded.
Requesting a terminal (this might take a while)...
[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

You may want to check with Cloud shell web version, which may give you more detailed error message.
One possible reason is that your fileshare which was mounted to cloud shell is unmounted. If this is the case, then:
https://learn.microsoft.com/en-us/azure/cloud-shell/persisting-shell-storage#the-clouddrive-mount-command

@JoeyC-Dev Thank you for the suggestion. However, the network injected cloud shell works normally via the web interface.


Access Guard

This is not an issue, but more like a feature request, do you think it is feasible to implement an Access Guard, which essentially can control if you want to allow users (or tenants) to login only from a given IP, or ban access from a certain IP range? Or do you think this feature is best to be in networking level?

I believe it would be more suitable to address this at the network layer.


add updated test script/assets for .webp files

Summary
Adds an updated test script and test.webp image
See also #2712 - https://github.com/apostrophecms/apostrophe/issues/2712
See also  - https://github.com/apostrophecms/apostrophe/pull/3677
Test cases
What are the specific steps to test this change?

Clone the repository and install dependencies
./webp-test.js or npm run webp

What kind of change does this PR introduce?

[ ] Bug fix
[x] New feature
[x] Refactor
[ ] Documentation
[ ] Build-related changes
[ ] Other

Make sure the PR fulfills these requirements:

[x] It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
[ ] The changelog is updated
[ ] Related documentation has been updated
[ ] Related tests have been updated

If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
Other information:

Conflicts require resolution.


Example on CodeSandbox?

Could you maybe create an example on the code sandbox, because I am not able to get the button to work.

install returns null on Chrome desktop on MacOS.

I would suggest to do something like this
  const { supportsInstall, triggerInstallPrompt } = usePWAInstall()

instead of hiding everything in one variable.

Do you fulfill PWA requirements set by Chrome? Do you have service worker and webmanifest? https://web.dev/install-criteria/

Do you use supported browser? (Yes, you do.)

Did you already installed the app?

null is returned if the app can't be installed.

Everything is fine if I click on the icon in the address bar. Only the button does not work.
Button works fine on mobile browsers though.

I see. It happens to me too on another project. I will investigate. I suspect some Apple weirdness. Chrome on Windows works.

To the original request I've made a demo on Glitch https://glitch.com/edit/#!/react-use-pwa-install-demo.


Allow configuring puppeteer via code

🚀 Feature Proposal
It would be nice if I could add puppeteer launch options via other mechanisms than jest-puppeteer.config.js.
For example there is testEnvironmentOptions in the jest config, and other plugins may also use globals for this.
See:
https://jestjs.io/docs/en/configuration#testenvironmentoptions-object
https://kulshekhar.github.io/ts-jest/user/config/#introduction
Motivation
I don’t want to have to put things into a jest-puppeteer.config.js when I can just as well use the normal jest config mechanisms. The less separate files I have to maintain, the happier I am :-)
Example
testEnvironmentOptions: {
  launch: { headless: false },
},

Pitch
Well obviously, its all about configuring the environment :-)

We don't have access to testEnvironmentOptions in globalSetup, sorry not possible.


feat(@angular/cli): expose test include list

The karma entry in .angular-cli.json now supports an include property, listing the test specific files to be included in the TypeScript compilation:
  "test": {
    "karma": {
      "config": "./karma.conf.js"
    },
    "include": [
      "**/*.spec.ts",
      "test.ts"
    ]
  },

Existing projects will default to the list abose.
This list will also be used as an exclude list for AoT Compilations.
Fix #3973

Superseded by https://github.com/angular/angular-cli/pull/4924


Ensure always goes to https

In _config.yml lets add:
url: https://opengazettes.or.ke   # with the https protocol
enforce_ssl: opengazettes.or.ke   # without any protocol

In <head>:
<script type="text/javascript">
  var host = "{{ site.enforce_ssl }}";
  if ((host == window.location.host) && (window.location.protocol != "https:"))
      window.location.protocol = "https";
</script>

@chegejames ☝


Bad type for Revolver.settings

Revolver.settings lacks a declared type, so the compiler infers a really hairy one:
object RevolverPlugin extends Plugin {
  object Revolver extends RevolverKeys {
    lazy val settings = Seq(
      // ...

this causes awesome problems like:
[error]  found   : Seq[sbt.Project.Setting[_ >: sbt.State => sbt.State with sbt.Task[sbt.ForkScalaRun] with Seq[java.lang.String] with java.lang.String with sbt.Task[Unit] with sbt.InputTask[cc.spray.revolver.AppProcess] with sbt.Task[Option[java.lang.String]] <: java.lang.Object]]
[error]  required: scala.collection.GenTraversableOnce[sbt.Project.Setting[_ >: sbt.Types.Id[Seq[sbt.Resolver]] with _4]] where type _4 >: sbt.State => sbt.State with sbt.Task[sbt.ForkScalaRun] with Seq[java.lang.String] with java.lang.String with sbt.Task[Unit] with sbt.InputTask[cc.spray.revolver.AppProcess] with sbt.Task[Option[java.lang.String]] <: java.lang.Object

You can make all those problems go away by changing it to:
object RevolverPlugin extends Plugin {
  object Revolver extends RevolverKeys {
    lazy val settings: Seq[Setting[_]] = Seq(

Please do! :)

You are right of course. Thanks.

Wohoo, what a funky inferral!
Thanks for reporting, I wish all issues were as easy to straighten out...

<EMAIL_ADDRESS>http://www.spray.cc
On 24.02.2012, at 21:03, Michael Bayne wrote:

Revolver.settings lacks a declared type, so the compiler infers a really hairy one:
object RevolverPlugin extends Plugin {
object Revolver extends RevolverKeys {
lazy val settings = Seq(
// ...
this causes awesome problems like:
[error]  found   : Seq[sbt.Project.Setting[_ >: sbt.State => sbt.State with sbt.Task[sbt.ForkScalaRun] with Seq[java.lang.String] with java.lang.String with sbt.Task[Unit] with sbt.InputTask[cc.spray.revolver.AppProcess] with sbt.Task[Option[java.lang.String]] <: java.lang.Object]]
[error]  required: scala.collection.GenTraversableOnce[sbt.Project.Setting[_ >: sbt.Types.Id[Seq[sbt.Resolver]] with _4]] where type _4 >: sbt.State => sbt.State with sbt.Task[sbt.ForkScalaRun] with Seq[java.lang.String] with java.lang.String with sbt.Task[Unit] with sbt.InputTask[cc.spray.revolver.AppProcess] with sbt.Task[Option[java.lang.String]] <: java.lang.Object
You can make all those problems go away by changing it to:
object RevolverPlugin extends Plugin {
object Revolver extends RevolverKeys {
lazy val settings: Seq[Setting[_]] = Seq(
Please do! :)

Reply to this email directly or view it on GitHub:
https://github.com/spray/sbt-revolver/issues/10