Proposal: move nouns array to global scope

Move nouns array to global scope
Basic rationale for this is to make the nouns array easily accessible to console and manually injected scripts. Very simple change, which I am ready to open a PR for given the appropriate permissions. This will allow more technically inclined users to augment the collection of nouns.

Sounds like a fine plan to me especially for the short term -- you shouldn't need permissions to issue a PR!  Just send it over and I'll check it out.

Oddly enough, it gives me a 403 when I try to publish a branch. I'm executing git push --set-upstream origin global-noun-array.
Regardless, I've attached the modified repo for your review.
internet_noise.zip

Ah is it possible you are working directly with this repo instead of a forked copy? If you fork your own copy and set your upstream to THAT you should be in good shape.  From there you would use github's interface to make the pull request.  (I'd rather do it that way in the spirit of commit history!)

Yesterday was a long day (or at least, that's the excuse I'm going with for such a simple goof 😁). The pull request can be found here: https://github.com/slifty/internet_noise/pull/22.

Thanks! Closing the issue (merge https://github.com/slifty/internet_noise/pull/22).

Absolutely!  And thank you for the contribution and idea (also no excuse needed -- goofs are nothing to be ashamed of!)


Controlling what happens onBlur

If the user tabs out of the drop down, it always selects the last selected item - even if they've completely typed out a different value.
I think it would be beneficial to add another function that deals with what to do when the focus leaves the component (either because of tabbing out or clicking outside). I am looking at using it in two different spots, and in one case I want to just select the first prediction on blur, in another - I want to just leave what they typed.

I believe you did not create any boundaries for your last item. Even if you click outside, it will select the last element.
If you were clicking outside, Downshift should reset by triggering the mouseUp state
.
To change the default behavior of clicking outside, you need to modify the stateReducer
https://github.com/paypal/downshift#statereducer
I do not know how to tab out.

Looks like I can figure out what I want to do with stateReducer.
Only pain point is that there is no access to highlightedItem (i.e. - that's not a property that is recorded in the state).
It seems like you could capture the currently highlighted option when they call getItemProps.

I think the workarounds are sufficient for this scenario. Make sure to checkout this example as well: https://codesandbox.io/s/github/kentcdodds/downshift-examples/tree/master/?module=%2Fsrc%2Fordered-examples%2F03-typeahead.js&moduleview=1


Realtek RTS5138 reader quirks.

Restart SD Bug fix.
https://github.com/helloSystem/ISO/issues/451

Looks like we have broken packages since the Q4/2023 packages. I need to fix this first.


Java Inception Client cannot parse image

Hi,
I hit the following error when trying to run the java client for inception example. it's definitely contacting the other end but appears to have problem parsing the incoming jpg image stream. The server end is python running the inception model as per the Tensorflow tutorial @ https://www.tensorflow.org/serving/serving_inception.
Any help is appreciated! Error below:
Start the predict client
Aug 22, 2017 3:04:30 PM io.grpc.internal.ManagedChannelImpl
INFO: [ManagedChannelImpl@d041cf] Created with target <IP_ADDRESS>:9000
Aug 22, 2017 3:04:30 PM com.tobe.InceptionPredictClient do_predict
INFO: Start to convert the image: /Users/joelgooch/Downloads/old_car.jpg
Aug 22, 2017 3:04:33 PM com.tobe.InceptionPredictClient do_predict
WARNING: RPC failed: Status{code=INVALID_ARGUMENT, description=Could not parse example input, value: '????, cause=null}
Aug 22, 2017 3:04:33 PM io.grpc.internal.ManagedChannelImpl maybeTerminateChannel
INFO: [ManagedChannelImpl@d041cf] Terminated
End of predict client

It seems the signature of the inception model has changed and it throws INVALID_ARGUMENT.
I will have a look when I'm free. Thanks for reporting @JoelGooch

I solved this issue. The Model.proto file is outdated when using the new SavedModelBuilder model exporting method. Using the proto compiler to get the new Model.java file allows access to the .setSignatureName( ) function required to communicate.

Thanks @JoelGooch for your report. I will update the code for the latest model spec.


Fixes #180

A program for Binary tree traversal (Inorder Traversal)

Ping @deepanshu-jain1999. Fixing it?


Vim colorschemes backgrounds are incorrect

It seems that vim colorschemes are not able to change the background to match the theme.
Black-Screen vs iTerm2

I believe that's b cause your terminal doesn't support true colors while black screen, does.

I can also confirm the color issue (terminal uses true colors and its enabled in vim)

In Sierra, I'm unable to display my vim color scheme.  It works in iTerm2.

Can't reproduce. Which colorscheme do you use, @aig787?

Can't reproduce. Which colorscheme do you use, @aig787?

I use the jellybeans colorscheme pulled in from 'flazz/vim-colorschemes' via vundle.

Still getting some weird graphical bugs, here is my vim config.

TODO
[ ] Cursor is one line lower than it should be.

@aig787, @Fuzen-py, @aftaylor2 should be fixed in master.


Full-chip STA (make caravel-sta) fails due to changed decap_12 cell references

With tag 2024.09.12-1 (which incidentally, at the time of writing, is the same commit as the more-recent 2024.09.13-1), you will get this error if you try to run full-chip STA (i.e. the final make caravel-sta step):
Error: /home/.../caravel_user_project/caravel/verilog/gl/housekeeping_alt.v line 142360, syntax error, unexpected '[', expecting '('

This occurs since commit https://github.com/efabless/caravel-lite/commit/25a2260d385eab795823949628fd42f8b9287a1b where individual decap_12 cell instances were removed, and Verilog "arrayed instances" were used instead, and thus this sort of pattern was replaced:
...
 sky130_ef_sc_hd__decap_12 FILLER_100_159 (.VGND(VGND),
    .VNB(VGND),
    .VPB(VPWR),
    .VPWR(VPWR));
 sky130_ef_sc_hd__decap_12 FILLER_100_171 (.VGND(VGND),
    .VNB(VGND),
    .VPB(VPWR),
    .VPWR(VPWR));
 sky130_ef_sc_hd__decap_12 FILLER_100_183 (.VGND(VGND),
    .VNB(VGND),
    .VPB(VPWR),
    .VPWR(VPWR));
...

...and this sort of pattern is what took its place:
  sky130_ef_sc_hd__decap_12 decap_12[2308:0] (.VGND(VGND),
    .VNB(VGND),
    .VPB(VPWR),
    .VPWR(VPWR));

Note the [2308:0]. While this is valid Verilog, the tools (which?) don't support it in this format.
There are a few caravel & caravel-lite files that are affected by this.
I was able to work around this (for the time being) by just using an older tag when doing make setup for my caravel_user_project, i.e.:
MPW_TAG=mpw-9k make setup

Steps I took to recreate this issue:
# Start clean:
unset OPENLANE_IMAGE_NAME OPENLANE_RUN_TAG OPENLANE_ROOT OPENLANE_TAG PDK_ROOT PDK MCW_ROOT

# Clone repo and check tag:
git clone --depth=1 https://github.com/efabless/caravel_user_project CUP-decap-test
cd CUP-decap-test
egrep 'MPW_TAG.*2024' Makefile
# => MPW_TAG ?= 2024.09.12-1
git log
# => 5020a223187c1693d5e5dd121e65ab7f6b770620, tags: 2024.09.13-1 and 2024.09.12-1

# Set everything up, and check tags:
make setup
cd caravel; git log; cd ..
# => a317f6d94d117702034babd0f6900395adbce85f, tags: 2024.09.13-1 and 2024.09.12-1
cd mgmt_core_wrapper; git log; cd ..
# => 503eda0790085712ffef7f4ad8934c7daed3237f, tags: mpw-9k/j/i/h, 2024.09.13-1, 2024.09.12-1, 2024.09.03-1
cd dependencies/openlane_src; git log; cd -
# => 30ee1388932eb55a89ad84ee43997bfe3a386421, tag: 2023.07.19-1
cd dependencies/timing-scripts; git log -1; cd -
# => 5b5dab63a257849dbb31881bec6f45439b6bdecb from 2023-10-19. MANY tags, including 2024.09.13-1, 2024.09.12-1

I then included these lines in the openlane/*/config.json files to speed up hardening, but also to use the different decap/fill strategy expected for CI2411+ (increasing GDS from 50MB to 120MB):
    "RUN_KLAYOUT_DRC": 0,
    "RUN_KLAYOUT_XOR": 0,
    "RUN_MAGIC_DRC": 0,
    "ROUTING_CORES": 16,
    "DECAP_CELL": "sky130_fd_sc_hd__decap_3",
    "FILL_CELL": "sky130_fd_sc_hd__fill_2 sky130_fd_sc_hd__fill_1",

I also edited verilog/rtl/user_defines.v to replace all "_INVALID" entries with GPIO_MODE_USER_STD_OUTPUT.
Next...
# Do hardens:
make user_proj_example
make user_project_wrapper

# Run full-chip STA steps:
make extract-parasitics
make create-spef-mapping
make caravel-sta

The last make caravel-sta is where it fails with:
exec> read_verilog /home/anton/WORK/dev/CUP-decap-test/caravel/verilog/gl/housekeeping_alt.v
exec> read_verilog /home/anton/WORK/dev/CUP-decap-test/caravel/verilog/gl/constant_block.v
exec> read_verilog /home/anton/WORK/dev/CUP-decap-test/caravel/verilog/gl/housekeeping_alt.v
Error: /home/anton/WORK/dev/CUP-decap-test/caravel/verilog/gl/housekeeping_alt.v line 142360, syntax error, unexpected '[', expecting '('
Error: /home/anton/WORK/dev/CUP-decap-test/caravel/verilog/gl/housekeeping_alt.v line 142360, syntax error, unexpected '[', expecting '('
Error: /home/anton/WORK/dev/CUP-decap-test/caravel/verilog/gl/housekeeping_alt.v line 142360, syntax error, unexpected '[', expecting '('
make[1]: *** [/home/anton/WORK/dev/CUP-decap-test/dependencies/timing-scripts/timing.mk:244: caravel-timing-typ-min] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [/home/anton/WORK/dev/CUP-decap-test/dependencies/timing-scripts/timing.mk:244: caravel-timing-typ-nom] Error 1
make[1]: *** [/home/anton/WORK/dev/CUP-decap-test/dependencies/timing-scripts/timing.mk:244: caravel-timing-typ-max] Error 1
make[1]: Leaving directory '/home/anton/WORK/dev/CUP-decap-test/dependencies/timing-scripts'
make: *** [Makefile:426: caravel-sta] Error 2

In this case, the file affected is https://github.com/efabless/caravel-lite/blob/main/verilog/gl/housekeeping_alt.v, but there are others that will come up.

I did the following to work on a fix for this...
TL;DR: I did the following:

Forked caravel
Deleted 'caravel' dir from my caravel_user_project-based repo
Cloned my fork in as the replacement 'caravel' subdirectory
In caravel/verilog/gl, replaced all array instances of decap_12, fill_4, and fill_8 with expansions into individual cell instances instead, in each of these 4 files:

housekeeping_alt.v
housekeeping.v
caravan_core.v
caravel_core.v

Detailed description of what I did...
I forked https://github.com/efabless/caravel as https://github.com/amm-efabless/caravel -- NOTE: caravel-lite is generated from caravel, so I decided to go for the source.
I then went into my CUP-decap-test clone of caravel_user_project (as seen above)...
# Throw away old caravel-lite:
rm -rf caravel
# Clone my fork of the full caravel into CUP-decap-test, instead (warning: 17 GB):
git clone git@github.com:amm-efabless/caravel.git caravel
# Try running again to verify full-chip STA still breaks in the same way:
make caravel-sta

Now find any GL files that are using array instances by doing cd caravel; egrep -r --include="*.v" -i '[a-z0-9_]+\[[0-9]+:0\]\s*\(' verilog/gl/ -- Output is:
verilog/gl/housekeeping_alt.v:  sky130_ef_sc_hd__decap_12 decap_12[2308:0] (.VGND(VGND),
verilog/gl/housekeeping_alt.v:  sky130_ef_sc_hd__fill_4 fill4[768:0] (.VGND(VGND),
verilog/gl/housekeeping_alt.v:  sky130_ef_sc_hd__fill_8 fill8[768:0] (.VGND(VGND),
verilog/gl/housekeeping.v:  sky130_ef_sc_hd__decap_12 decap_12[1815:0] (.VGND(VGND),
verilog/gl/housekeeping.v:  sky130_ef_sc_hd__fill_4 fill4[604:0] (.VGND(VGND),
verilog/gl/housekeeping.v:  sky130_ef_sc_hd__fill_8 fill8[604:0] (.VGND(VGND),
verilog/gl/caravan_core.v: sky130_ef_sc_hd__decap_12 EF_decap_12[53703:0] (.VGND(vssd),
verilog/gl/caravan_core.v: sky130_ef_sc_hd__fill_4 EF_fill_4[53702:0] (.VGND(vssd),
verilog/gl/caravan_core.v: sky130_ef_sc_hd__fill_8 EF_fill_8[53702:0] (.VGND(vssd),
verilog/gl/caravel_core.v: sky130_ef_sc_hd__decap_12 EF_decap_12[65364:0] (.VGND(vssd),
verilog/gl/caravel_core.v: sky130_ef_sc_hd__fill_4 EF_fill_4[57192:0] (.VGND(vssd),
verilog/gl/caravel_core.v: sky130_ef_sc_hd__fill_8 EF_fill_8[57192:0] (.VGND(vssd),

Across the 4 files, we see:

The pattern is always 3 types of devices, in order: decap_12, fill4, and fill8 -- sometimes though with slightly different names for the instances (not that I think it matters).
decap_12 is always one quantity (e.g. 2308), while the next 2 are always an equal quantity (e.g. 768).
The power and ground net names differ between files.
From inspection, I've found that these always appear at the end of each file.

For each of the 4 files in turn:

I took note of their power/ground net names, and the 3 max indices of array indices.
I deleted the tail end of each file, i.e. the first decap_12 array instance, all the way to the end of the file, including deleting the final endmodule
I used the clunky script below (called recap.sh) to generate and append replacement elaborated (individual) instances for all the cells on each file...

#!/bin/bash
gnd="${gnd:-VGND}" # Default to VGND
pwr="${pwr:-VPWR}" # Default to VPWR
for i in $(seq -f "%06g" 0 $1); do
cat <<EOH
  sky130_ef_sc_hd__decap_12 EF_decap12_$i (.VGND($gnd),
    .VNB($gnd),
    .VPB($pwr),
    .VPWR($pwr));
EOH
done
for i in $(seq -f "%06g" 0 $2); do
cat <<EOH
  sky130_ef_sc_hd__fill_4 EF_fill4_$i (.VGND($gnd),
    .VNB($gnd),
    .VPB($pwr),
    .VPWR($pwr));
EOH
done
for i in $(seq -f "%06g" 0 $3); do
cat <<EOH
  sky130_ef_sc_hd__fill_8 EF_fill8_$i (.VGND($gnd),
    .VNB($gnd),
    .VPB($pwr),
    .VPWR($pwr));
EOH
done
echo "endmodule"

In particular, I ran:
pwr=VPWR gnd=VGND ./recap.sh 2308 768 768 >> verilog/gl/housekeeping_alt.v
pwr=VPWR gnd=VGND ./recap.sh 1815 604 604 >> verilog/gl/housekeeping.v
pwr=vccd gnd=vssd ./recap.sh 53703 53702 53702 >> verilog/gl/caravan_core.v
pwr=vccd gnd=vssd ./recap.sh 65364 57192 57192 >> verilog/gl/caravel_core.v

I then manually checked each file to make sure they seemed valid.
I went back up a directory level into my CUP-decap-test repo and ran make caravel-sta again.
There are no errors now, and the full-chip STA results are as expected.
I committed the changes in 'caravel' and pushed to my fork: https://github.com/amm-efabless/caravel/commit/324aa7a44327be13e883667d002c8e90ed755367


what are the guidelines to adding new error codes?

What are 1000-2000-3000-4000-5000-6000 ranges for?

It used to matter, but now it's kinda sorta just about grouping related things somewhat closely.
For instance, I'd place something regarding warning users of parameter covariance as soon after the noImplicitAny errors as possible.

Thanks!

for future references here are the meanings:https://github.com/Microsoft/TypeScript/wiki/Coding-guidelines#diagnostic-message-codes

Thanks!
Offtopic: I am surprised you encourage the use of the map and filter
functions over arrays but say nothing about fold/reduce
On Jan 5, 2016 3:11 PM, "Mohamed Hegazy"<EMAIL_ADDRESS>wrote:

for future references here are the meanings:
https://github.com/Microsoft/TypeScript/wiki/Coding-guidelines#diagnostic-message-codes
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/6089#issuecomment-169117763
.

I think it usually turns out that folds are a little less readable, and are mostly useful when you want to "atomically" initialize a value. It's all subjective, but this is coming from a guy who really likes Haskell, SML, and F# if that counts for anything.

i wish for once someone defined "readable" for me
will you be that guy?
what audience are we keeping in mind saying "readable"?
ugly truth is, FP isn't a mainstream paradigm whereas TypeScript is a mainstream language...
back to work.


DOC: Morlet wavelet length in tfr_morlet

Closes #11645.
This PR adds clarification of the Morlet wavelet temporal window length used with mne.time_frequency.tfr_array_morlet and mne.time_frequency.tfr_morlet.

FYI CircleCI will fail with a warning about bool builting linking until https://github.com/mne-tools/mne-python/pull/12068 is merged

Looks like there is a failure in mne/tests/test_docstring_parameters.py::test_docdict_order
  +  'temporal-window_tfr_morlet_notes',
     'temporal-window_tfr_multitaper_notes',
  -  'temporal-window_tfr_morlet_notes',

i.e. it's no longer alphabetical

The robots seem to be happy, how about the humans? @drammock

Seems that the CIs failing are unrelated @drammock (?)

Seems that the CIs failing are unrelated @drammock (?)

yes definitely unrelated, however the rendering still squashes the paragraphs together; @larsoner is looking into it.

Marking for merge when green, thanks @ruuskas !


Integrations: Infinite Scale DICOM

This is an example for an integration/extension project with Infinite Scale.
The DICOM server orthanc  is a successful and mature open source DICOM server that stores and manages medical images. It is very well documented and commercial support is offered.
Orthanc offers a variety of REST APIs and a plugin structure which allow implementation of storage backends. With that, the following integrations could be built:

Orthanc uses Infinite Scale as storage backend leveraging Infinite Scales WebDAV API. Dicom files are organized by spaces to (for example) reflect the medical organization / units.
Orthanc authentication uses OIDC
The DICOM Viewer is integrated with the ownCloud Web extension system
ownCloud Web displays DICOM metadata if clicked on a DICOM file

More ideas to come?

DICOM support . That’s really useful . +1 from me

The DICOM viewer has been implemented meanwhile: https://github.com/owncloud/web-app-dicom-viewer


fix(ngAria): do not set aria attributes on input[type="hidden"]

This fixes a error found by @edclements  using the Google Accessibility Developer Tools audit.
Input fields of type hidden shouldn't have aria attributes.
https://www.w3.org/TR/html-aria/#allowed-aria-roles-states-and-properties-1
Closes #15113

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
aria attributes added to input type hidden
What is the new behavior (if this is a feature change)?
Not anymore.
Does this PR introduce a breaking change?
I would say not actually, because the previous behavior didnt follow the spec and I can'T see why anyone would rely on this behavior. It was marked as breaking change in https://github.com/angular/angular.js/pull/15113, though
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Fix/Feature: Docs have been added/updated
[x] Fix/Feature: Tests have been added; existing tests pass

Other information:
Rebased and updated version of https://github.com/angular/angular.js/pull/15113

Thanks @gkalpak . Just to clarify, are you okay with thi going into 1.6.x too? Because I currently have not added a  BC notice.

Hm...you are sneaky 😛
Technically, it is a fix, but it can theoretically break a test. Probably safest to go into 1.7, but I'm on the fence :smiley:
(Maybe @mgol has a stronger opinion - he added the needs: breaking change to the original PR :grin:)

@gkalpak you said it was a BC and that you would add the BC label: 😛 https://github.com/angular/angular.js/pull/15113#issuecomment-253906041

But I didn't 😛
I still mostly agree with myself though (always a good sign 😛).
It is theoretically a BC and I would rather treat it as such. (But if you feel otherwise - and @mgol doesn't have a strong opinion in favor of a BC - I can live with getting it into 1.6.x (as I said in my original comment anyway 😛).)

But I didn't

Because you forgot 😛
I'll add a BC notice - it's such a small change, and I guess screen readers already ignore hidden inputs, so I doubt this really affects anyone as is


Console is flooded with error. Idek

Bot still responds to commands however. this message cycles through every 10 or so minute's.
https://pastebin.com/KwLrhtqM

possibly your internet connection.
Just in case try disabling logs on your server and see if problem persists

I believe it is internet related, I left my computer for an hour to go idle. Probably disabled any unneeded outbound connections.

@AJdisco you still having this issue or can we close this?

@AJdisco can you close this ticket?


Put tracker code in a class

Current the tracker code is just written all over the place in the ros node. It would be much better if it were placed in a class.

Working on this now. I was working on #6 and it seems testing the timing of each detector would be a lot simpler if I put everything in a class first.

I created a new class called TrackLandingMark and moved all the detector and tracker logic code there. The code is much cleaner now and we can continue with other more important things.


training on cloud

I met a few problems to compile on the cloud, such as GCC version issues.
Could you help to indicate which files shall be move to cloud without compile on the cloud.
Could you help to provide a simplified setup_py.bash which can be used on cloud with compiled files transferred from local machine to cloud.

hi
it is necessary to compile the source code. there is no simple way of just "move files to cloud".
I would recommend using Docker if you want to train on the cloud.
We are planning to provide a Docker file, but this is not guaranteed since we are currently very busy with other research projects


AsyncStorage is null.

Current behavior
Error on device (cant test on emulator because on issue with android studio currently)

Environment

Async Storage version: 1.9.0
React-Native version:
Platform tested: Android

if you are running expo, keep asyncstorage from the repo react-native or eject expo to use from the community

im running ejected expo..

What RN Version are you using? Did you link the package?

System:
OS: macOS 10.15.4
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 1018.14 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.12.0 - /usr/local/bin/node
npm: 6.11.3 - /usr/local/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
IDEs:
Android Studio: 3.5 AI-191.8<IP_ADDRESS>10548
Xcode: 11.4/11E146 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.0.tar.gz => 0.61.4
npmGlobalPackages:
react-native-cli: 2.0.1

i have the same issue now on ios on testFlight.
on the simulator everything is working, on the device im getting:

What about linking the package? I guess auto-linking does not work for ejected projects, so you'd have to try do it manually

are you sure? i linked it once and i got warning..

@gwumkt Do you have other native modules? How do you handle them? Can you post your Podfile ?

platform :ios, '10.0'

require_relative '../node_modules/react-native-unimodules/cocoapods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

target 'app' do
  rnPrefix = "../node_modules/react-native"

  # React Native and its dependencies
  pod 'FBLazyVector', :path => "#{rnPrefix}/Libraries/FBLazyVector"
  pod 'FBReactNativeSpec', :path => "#{rnPrefix}/Libraries/FBReactNativeSpec"
  pod 'RCTRequired', :path => "#{rnPrefix}/Libraries/RCTRequired"
  pod 'RCTTypeSafety', :path => "#{rnPrefix}/Libraries/TypeSafety"
  pod 'React', :path => "#{rnPrefix}/"
  pod 'React-Core', :path => "#{rnPrefix}/"
  pod 'React-CoreModules', :path => "#{rnPrefix}/React/CoreModules"
  pod 'React-RCTActionSheet', :path => "#{rnPrefix}/Libraries/ActionSheetIOS"
  pod 'React-RCTAnimation', :path => "#{rnPrefix}/Libraries/NativeAnimation"
  pod 'React-RCTBlob', :path => "#{rnPrefix}/Libraries/Blob"
  pod 'React-RCTImage', :path => "#{rnPrefix}/Libraries/Image"
  pod 'React-RCTLinking', :path => "#{rnPrefix}/Libraries/LinkingIOS"
  pod 'React-RCTNetwork', :path => "#{rnPrefix}/Libraries/Network"
  pod 'React-RCTSettings', :path => "#{rnPrefix}/Libraries/Settings"
  pod 'React-RCTText', :path => "#{rnPrefix}/Libraries/Text"
  pod 'React-RCTVibration', :path => "#{rnPrefix}/Libraries/Vibration"
  pod 'React-Core/RCTWebSocket', :path => "#{rnPrefix}/"
  pod 'React-Core/DevSupport', :path => "#{rnPrefix}/"
  pod 'React-cxxreact', :path => "#{rnPrefix}/ReactCommon/cxxreact"
  pod 'React-jsi', :path => "#{rnPrefix}/ReactCommon/jsi"
  pod 'React-jsiexecutor', :path => "#{rnPrefix}/ReactCommon/jsiexecutor"
  pod 'React-jsinspector', :path => "#{rnPrefix}/ReactCommon/jsinspector"
  pod 'ReactCommon/jscallinvoker', :path => "#{rnPrefix}/ReactCommon"
  pod 'ReactCommon/turbomodule/core', :path => "#{rnPrefix}/ReactCommon"
  pod 'Yoga', :path => "#{rnPrefix}/ReactCommon/yoga"
  pod 'DoubleConversion', :podspec => "#{rnPrefix}/third-party-podspecs/DoubleConversion.podspec"
  pod 'glog', :podspec => "#{rnPrefix}/third-party-podspecs/glog.podspec"
  pod 'Folly', :podspec => "#{rnPrefix}/third-party-podspecs/Folly.podspec"

  # Other native modules

  # Automatically detect installed unimodules
  use_unimodules!

  # react-native-cli autolinking
  use_native_modules!

end

i tried to link it and im getting the exact same error on the device..

it might work on simulator, but not on the device after build
On Mon, Apr 20, 2020 at 3:49 PM Mahmoud Mortada<EMAIL_ADDRESS>wrote:

I faced the same situation.
uninstall app
run nxp react-native run-android or nxp react-native run-ios
it will work
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/async-storage/issues/332#issuecomment-616531056,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG4P4V3O5CQVG6GBISEHWSLRNRAGTANCNFSM4MJ74TKQ
.

i gave up.
now im using:
import { AsyncStorage } from 'react-native';

it might work on simulator, but not on the device after build
Your Podfile looks fine. Have you run pod install and then react-native run-ios/build the app again?

yep
On Thu, Apr 23, 2020 at 12:14 PM Krzysztof<EMAIL_ADDRESS>wrote:

it might work on simulator, but not on the device after build
Your Podfile looks fine. Have you run pod install and then react-native
run-ios/build the app again?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/async-storage/issues/332#issuecomment-618283626,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG4P4V6LT2DQFGQ42RIX4JLROABGTANCNFSM4MJ74TKQ
.

I think I was wrongly thinking we're talking about iOS platform, but you have problem with Android, right?
In that case, did you try running react-native run-android ?

its on ios + android, and i tried it all
On Thu, Apr 23, 2020 at 12:24 PM Krzysztof<EMAIL_ADDRESS>wrote:

I think I was wrongly thinking we're talking about iOS platform, but you
have problem with Android, right?
In that case, did you try running react-native run-android ?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/async-storage/issues/332#issuecomment-618289055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG4P4V6FF3GW457SQEEDPRTROACNNANCNFSM4MJ74TKQ
.

Did you upgrade pre-60 version maybe?


Feature Request: Ability to Default Multi Items to Selected

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[ ] Linux
[x] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce
This is less a problem than a feature request.  I'd like to be able to specify certain (or all) items of the input to default to being 'checked' or selected when in multi mode.  Perhaps a regex run on each line of input to determine if it should be checked?  So could be lines starting with a 1 start as checked?
My apologies if there is already some way to achieve this but I was not able to determine how to do so by reading through the manual and other issues.

Duplicate #395, but I think there are more recent issues, where you might find junegunn's stance on this issue.

No plan to support regex-based solution. But with the latest version of fzf, you can try using start or load event to perform actions to select the entries you want.
https://github.com/junegunn/fzf/issues/3548#issuecomment-1868433219
If writing down the list of actions is not feasible, you can perhaps write a script that performs multiple actions via HTTP server (--listen).


[nuxt] Error while mounting app: HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method.

Hi,
I have uploaded my nuxt app to a plesk server.
I ran build --scripts-prepend-node-path to create .nuxt folder. i then ran start --scripts-prepend-node-path
The site "works" but not all the features/events work.
When i open the console. i get the following errors
  TypeError: Cannot read property '$scopedSlots' of undefined @ _nuxt/259a4998f26830aa9f74.js:2

this error correlates to the following function
   function te(t, e, n) {
        if (!tt && !et || "undefined" == typeof console)
            throw t;
        console.error(t) //<-- this is the error
    }

Additionally, the following error is included
 Error: [nuxt] Error while mounting app: HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method. @ _nuxt/989b40654fd3805a3347.js:3460

this error correlates to this piece of code (which is part of a larger snippet)
 function L() {
        return (L = Object(n.a)(regeneratorRuntime.mark(function e(o) {
            var t, n, l, d, h;
            return regeneratorRuntime.wrap(function(e) {
                for (; ; )
                    switch (e.prev = e.next) {
                    case 0:
                        return v = o.app,
                        m = o.router,
                        o.store,
                        e.next = 5,
                        Promise.all(C(m));
                    case 5:
                        return t = e.sent,
                        n = new r.default(v),
                        l = w.layout || "default",
                        e.next = 10,
                        n.loadLayout(l);
                    case 10:
                        if (n.setLayout(l),
                        d = function() {
                            n.$mount("#__nuxt"),
                            m.afterEach(E),
                            m.afterEach(R.bind(n)),
                            r.default.nextTick(function() {
                                A(n)
                            })
                        }
                        ,
                        n.setTransitions = n.$options.nuxt.setTransitions.bind(n),
                        t.length && (n.setTransitions(k(t, m.currentRoute)),
                        y = m.currentRoute.matched.map(function(e) {
                            return Object(c.b)(e.path)(m.currentRoute.params)
                        })),
                        n.$loading = {},
                        w.error && n.error(w.error),
                        m.beforeEach(_.bind(n)),
                        m.beforeEach(O.bind(n)),
                        !w.serverRendered) {
                            e.next = 21;
                            break
                        }
                        return d(),
                        e.abrupt("return");
                    case 21:
                        h = function() {
                            E(m.currentRoute, m.currentRoute),
                            S.call(n, m.currentRoute),
                            d()
                        }
                        ,
                        O.call(n, m.currentRoute, m.currentRoute, function(path) {
                            if (path) {
                                var e = m.afterEach(function(o, t) {
                                    e(),
                                    h()
                                });
                                m.push(path, void 0, function(e) {
                                    e && x(e)
                                })
                            } else
                                h()
                        });
                    case 23:
                    case "end":
                        return e.stop()
                    }
            }, e)
        }))).apply(this, arguments)
    }
    Object(h.b)().then(function(e) {
        return L.apply(this, arguments)
    }).catch(function(e) {
        var o = new Error(e);
        o.message = "[nuxt] Error while mounting app: " + o.message,
        x(o) // <-- ERROR
    })

Any help is greatly appreciated

This question is available on Nuxt community (#c9121)

Hi, do you fix it?
I have the same problem

Hi,
I cannot honestly remember what i did.... I know for certain that i was running into problems when i created a directory with the admin user/root user and then uploaded/modified the app root folder structures using a different user i would run into problems. If you like me uploaded the contents of the app using ftp make sure you are using the same user as the owner of the directory

i also updated and then reinstalled all my packages

Hi,
I have the same problem after deploying to production.

Check this thread for solution: https://github.com/nuxt/nuxt.js/issues/5800

i recently had this issue, and i was running in SSR, worked fine on local but not in heroku. The issue was i was displaying an iframe but i needed to wrap the iframe with  tag.


Config paramater PORT has wrong jsonConfig type

Describe the bug
The configuration parameter 'port'has jsonCOnfig type 'port'. Type port is incorrect as this type is designed to work for listener ports and raises an error if the port number entered ist already used at the host system. As the mqtt-client 'port' config data specifies teh port at the remote system, no check against any ports at the local host should be performed.
To Reproduce
Open UI interface an enter any port which is used at local host (i.e. 8081). There is an error displayed which is incorrect.
Expected behavior
Entering any port should be valid
Screenshots & Logfiles
Versions:

Adapter version: 2.0.0
JS-Controller version: 6.0.11
Node version: 20
Operating system: windows 10

Additional context

fixed at 2.0.1


Use correct pyqt version in tests

Description
small fix to make sure we're testing the pinned version of pyqt5 on cirrus.
see fail in https://github.com/napari/napari/runs/734105957

I have no understanding of that codecov-bot comment. Why does it show such carnage and then when you click on it (or in the checks list) it shows no changes???

I have no understanding of that codecov-bot comment. Why does it show such carnage and then when you click on it (or in the checks list) it shows no changes???

yeah, I don't get it either... there are still many things I don't understand about codecov 😅


Improve CommandInvocationIntrinsics API documentation and style

PR Summary
Using this API, I found I had to inspect the source code to determine the behaviour of the overloads I was looking over.
I've added comments so that in future that won't be necessary.
I think it's particularly interesting that the string overloads execute in a local scope, while the ScriptBlock overloads dot-source — so this seems like an important thing to capture in documentation.
I've also hung the parameters ~and renamed one parameter because it was inconsistently named across overloads~ (reverted this second part since it's a breaking change for named parameters).

PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@rjmholt @TravisEz13 Any changes needed for this PR?


use sha256 instead of sha1

Because brew is telling me to do so:
$ brew upgrade
Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/usr/local/Library/Taps/jlhonora/homebrew-lsusb/lsusb.rb:8:in `<class:Lsusb>'
Please report this to the jlhonora/lsusb tap!

Warning: Calling SoftwareSpec#sha1 is deprecated!
Use SoftwareSpec#sha256 instead.
/usr/local/Library/Taps/jlhonora/homebrew-lsusb/lsusb.rb:8:in `<class:Lsusb>'
Please report this to the jlhonora/lsusb tap!

Warning: Calling Resource#sha1 is deprecated!
Use Resource#sha256 instead.
/usr/local/Library/Taps/jlhonora/homebrew-lsusb/lsusb.rb:8:in `<class:Lsusb>'
Please report this to the jlhonora/lsusb tap!

Hi Thomas, thanks for reporting this. We did address it in https://github.com/jlhonora/homebrew-lsusb/pull/2 , but it seems that wasn't enough. I'll have a closer look and update this accordingly.

Does running brew update && brew upgrade fix the problem?

Nope, unfortunately not, see log (I run it twice, just to be sure):
$ brew update && brew upgrade
Already up-to-date.
Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/usr/local/Library/Taps/jlhonora/homebrew-lsusb/lsusb.rb:8:in `<class:Lsusb>'
Please report this to the jlhonora/lsusb tap!

Warning: Calling SoftwareSpec#sha1 is deprecated!
Use SoftwareSpec#sha256 instead.
/usr/local/Library/Taps/jlhonora/homebrew-lsusb/lsusb.rb:8:in `<class:Lsusb>'
Please report this to the jlhonora/lsusb tap!

Warning: Calling Resource#sha1 is deprecated!
Use Resource#sha256 instead.
/usr/local/Library/Taps/jlhonora/homebrew-lsusb/lsusb.rb:8:in `<class:Lsusb>'
Please report this to the jlhonora/lsusb tap!

Nope, unfortunately not, see log (I run it twice, just to be sure):
$ brew update && brew upgrade
Already up-to-date.
Warning: Calling Formula.sha1 is deprecated!
Use Formula.sha256 instead.
/usr/local/Library/Taps/jlhonora/homebrew-lsusb/lsusb.rb:8:in `<class:Lsusb>'
Please report this to the jlhonora/lsusb tap!

Warning: Calling SoftwareSpec#sha1 is deprecated!
Use SoftwareSpec#sha256 instead.
/usr/local/Library/Taps/jlhonora/homebrew-lsusb/lsusb.rb:8:in `<class:Lsusb>'
Please report this to the jlhonora/lsusb tap!

Warning: Calling Resource#sha1 is deprecated!
Use Resource#sha256 instead.
/usr/local/Library/Taps/jlhonora/homebrew-lsusb/lsusb.rb:8:in `<class:Lsusb>'
Please report this to the jlhonora/lsusb tap!

Ok, thanks. Note that a quick and dirty workaround is to do:
wget https://raw.githubusercontent.com/jlhonora/lsusb/master/lsusb && chmod +x lsusb && mv lsusb /usr/local/bin/

But I'd rather solve this problem anyhow. What's the output of brew --version and brew log -p lsusb?

 It looks like you still have an old version of the tap.
Maybe try with:
brew uninstall lsusb
brew untap jlhonora/lsusb
brew tap jlhonora/lsusb
brew install lsusb

Yep. That's it. Weird, since the taps are the same, thought there is no difference. However it worked:
$ brew doctor
Your system is ready to brew.


update 'findPerfByHost' to accept a list of hosts

btw, don't know if your code does this or not, but it would be good to get total_duration = maxHostResponseEnd - minHostFetchStart


Add ListRecords.

Adds List support for Records, including pagination and filtering. This
is largely borrowed from ListResults, adapted for the Record type.
Code is refactored as best as possible to share logic between Results
and Records, though duplication remains due to typing. I suspect generic
might help here in the future.
Also starts documenting common queries in a cookbook. We should build on
this with common queries as we start using the API.
Fixes #18

/lgtm


Could not build Objective-C module 'SwiftEntryKit'

Describe the bug
i have problem, i got this error while building
Could not build Objective-C module 'SwiftEntryKit'
iPhone (please complete the following information):

iPhone X
iOS Version: iOS 11.1.3
Xcode Version 10.2
Dependency Manager Version CocoaPods 1.5.2
SwiftEntryKit Release  1.0.1
Swift: 5

Hi @UAEpro,
What are you trying to build exactly (example project, your own project)?
I don't have enough info, but it might be a caching issue. Please follow these [steps].(https://github.com/huri000/SwiftEntryKit/issues/138#issuecomment-438986841)

the problem was because of using older compiler, (thought project was on swift 5)
After changing to swift 5 and then re installing pods everything seems to work fine


[Project proposal] cargo-quickinstall

Project name: cargo-quickinstall
Project details: cargo-quickinstall provides pre-built (quick-installable) tarballs for binary crates.
The cargo-quickinstall client is ~300 lines of rust that compiles in < 5 seconds. It is pretty simple. It uses Command to shell out to curl and tar, and spawns a thread to report statistics in the background. Other than that, it doesn't use async or anything fancy.
Supporting it, there are also:

a typescript server running on vercel that keeps stats of which packages people are requesting (https://github.com/alsuren/warehouse-clerk-tmp/commit/6a75e9ef111f2fece5a82a4983f040a080e184a1)
a bunch of supporting bash scripts
some slightly gnarly github actions

Short bio: I've been using rust in my spare time and as part of commercial projects for a few years. I'm now working at tably.com, which is a data startup that's using rust on the frontend and backend.
Looking for: All experience levels are welcome.
https://github.com/alsuren/cargo-quickinstall/projects/1 is my kanban board, and there are a lot of [tiny] tasks marked on there. I will try to tag them as rust / bash / typescript as well, to make things easier.
If you are interested in writing command-line apps, I would like to start adding more features. In order to do this, I will need to start doing argument parsing. I would like to try using pico-args for this. (On a normal project, I would recommend Clap or similar. I am currently trying to keep cargo-quickinstall's build time low. The recommended way to bootstrap is currently cargo install cargo-quickinstall, which takes < 5s, and is suitable for bootstrapping CI servers). I would propose pairing/mobbing on getting the initial argument-parsing infrastructure in place, and then work on things like https://github.com/alsuren/cargo-quickinstall/issues/41 ,  https://github.com/alsuren/cargo-quickinstall/issues/20 and https://github.com/alsuren/cargo-quickinstall/issues/33 (either as a group, or in parallel).
If you are interested in build-systems (cargo, cross, github-actions) and you know bash, I would like to try to make cargo-quickinstall try to cross-compile packages for ARM (aarch64 Linux and M1 MacOS). This would be on a "best effort" basis, and I wouldn't expect ARM targets to have all of the same packages as x86_64 targets. The ticket for this is https://github.com/alsuren/cargo-quickinstall/issues/32 .
The other thing that might be interesting to do is convert my current set of supporting bash scripts into rust, using the cargo xtask pattern described at https://github.com/matklad/cargo-xtask . This would be a "rewrite it in rust" project, suitable for anyone who doesn't mind reading my dreadful bash code. This rust code would not be part of cargo-quickinstall client crate, so it could use Clap for argument parsing if desired.

I'm not free the the upcoming hack and learn, and most of the low hanging fruit have already been picked, so I'm going to close this issue.
It might be interesting to port the stats server over to shuttle.rs if anyone wants to join next time.


When I do training, why are the results of the validation set obtained by using the teacher model?

021-07-18 18:20:35 | INFO | valid | epoch 006 | valid on 'valid' subset | loss 3.932 | nll_loss 2.125 | distil_rate 0 | ppl 4.36 | bleu 42.08 | wps 10164.3 | wpb 10722.3 | bsz 332.8 | num_updates 15150 | best_bleu 42.08

It is solved, thanks.

how can you solve this issue?

how can you solve this issue?

Firstly, after I use the loss metric, this error will been removed.

how can you solve this issue?

Firstly, after I use the loss metric, this error will been removed.

how can you solve this issue?

Firstly, after I use the loss metric, this error will been removed.    ( --best-checkpoint-metric loss)    Besides that, I rewrote some
rows of fairseq_cli/train.py  to remove this error radically.   I will send the file to you by using email.  Hope it is helpful to you!

------------------ 原始邮件 ------------------
发件人:                                                                                "LeslieOverfitting/selective_distillation"                                                                                @.>;
发送时间: 2021年12月22日(星期三) 晚上8:48
@.>;
抄送: "wangchenglong @.>;"State @.>;
主题: Re: [LeslieOverfitting/selective_distillation] When I do training, why are the results of the validation set obtained by using the teacher model? (#1)
how can you solve this issue?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you modified the open/close state.Message ID: @.***>

Thank you, I have moved line 117 of fairseq_cli/train.py to line 67 (before " model = task.build_model(args) "). And then it works well (in a ugly way).

@Chenglong-coder  Met the same issue, could you share the code snippet? or maybe made a PR to the repo? Thanks!


v2.4.1

Codecov Report
Patch and project coverage have no change.

Comparison is base (d9a7ee3) 78.85% compared to head (81b9159) 78.85%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff            @@
##           master    #2615    +/-   ##
========================================
  Coverage   78.85%   78.85%
========================================
  Files         631      628     -3
  Lines       51705    51366   -339
========================================
- Hits        40770    40506   -264
+ Misses       8917     8858    -59
+ Partials     2018     2002    -16

Flag
Coverage Δ

go-1.15-386
?

go-1.15-amd64
?

go-1.16-386
78.85% <ø> (-0.01%)
:arrow_down:

go-1.16-amd64
?

go-1.17-386
?

go-1.17-amd64
?

go-1.18-386
?

go-1.18-amd64
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 12 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


underscore lib missing from index.html

First of all, thanks for this neat implementation of phylotree!
This is just a PR as a possible fix to the missing underscore lib in index.html

Thank you! It's much appreciated.


Update prefix var description

Description

Fix typo (lowerccase) in vsi pattern
Make prefix descriptions consistent.terraform ini

@toddgiguere: only the prefix var in patterns/roks-quickstart/variables.tf  has 13 characters. All the rest had 16. I changed it to 16 but want to make sure that's correct.
Release required?

[x] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

I think 13 is correct for the roks patterns, right @toddgiguere ?

@ocofaigh approved, but not clear on the infra test failures.

Pipeline failed with [ERROR] Create Transit Gateway connection err The requested network is already connected to an existing transit gateway.
Unrelated to changes in this PR so re-trying..

/run pipeline

@toddgiguere It failed again with same error [ERROR] Create Transit Gateway connection err The requested network is already connected to an existing transit gateway.
Is there an issue in our account? Or did something change on backend??

/run pipeline

I am still working on narrowing down the issue with transit gateways. If I run the unit tests individually I am getting success, but when the PR tests are run (many in parallel) we get issues with both creation (already exists for this network) and destroy (still has active connections) for the transit gateway resources. During each PR test run most of the tests (but not all) will fail with this, and when testing those same tests individually I do not see the errors.

/run pipeline

@toddgiguere maybe we should also not provision transite gws in some tests? They are very expensive too, so maybe just have 1 test create one?

I have disabled the deployment of transit gateway from all tests except for Quickstart tests. This should provision less gateways in total.

/run pipeline

Getting a little closer with unit tests. Latest run had three failed tests. Two of them took too long to destroy, and one of them encountered a "Bad Gateway" from cloudflare when executing the API call, none of the errors relate to Transit Gateway.
Will execute again as all three of these issues are hopefully intermittent.

/run pipeline

The latest test failed when trying to delete subnets:
 2024/04/17 13:45:24 Terraform destroy | Error: timeout while waiting for state to become 'done, failed' (last state: 'deleting', timeout: 10m0s)
 2024/04/17 13:45:24 Terraform destroy |
 2024/04/17 13:45:24 Terraform destroy |
 2024/04/17 13:45:24 Terraform destroy | Error: timeout while waiting for state to become 'done, failed' (last state: 'deleting', timeout: 10m0s)

There is defiantly backend issues impacting us here. I'm going to force merge this PR since its only updating variable descriptions.

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

GitHub release
v5.20.4

Your semantic-release bot :package::rocket:


FR: Decorate metrics with polling interval

As an engineer, it would be useful to have SNMP metrics decorated with the polling interval for the purposes of reporting, alerting, and troubleshooting. With the ability to specify per OID collection intervals (thank you!) this FR will us understand where further data optimization can be implemented.

Added in #204


Document how to set up the app

It would be awesome if you could document how to set up the app and its dependencies (if any) in the README (or some other doc in the repository).

Added a first description.
Let me know if anything is unclear or needs further explanation.

There's everything needed, thanks :)
Only issue now is that we don't have enough RAM on the droplet to launch sbt (same problem with crawler):
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000b0000000, 357892096, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 357892096 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /var/apps/game-creator/hs_err_pid8022.log

I'll try to assemble the JAR locally and only run it on the host but I'm not hopeful. I'll upgrade the droplet to 1GB RAM (let's hope it's gonna be enough for both crawler and game-creator).

I used upstart on the server and created the corresponding services:
sudo service game-creator start
sudo service game-creator stop

This should limit the ram to 128, but we still ran into memory problems.
Maybe that helps

Oh sweet!
We should document that kind of thing somewhere in the wiki.
I’ll see how it goes, and will upgrade the droplet if necessary.
--
Romain Ruetschi
https://romac.me
On Sunday, 4 January 2015 at 21:00, Roger Küng wrote:

I used upstart on the server and created the corresponding services:
sudo service game-creator start sudo service game-creator stop
This should limit the ram to 128, but we still ran into memory problems.
Maybe that helps
—
Reply to this email directly or view it on GitHub (https://github.com/reminisceme/game-creator/issues/1#issuecomment-68646567).

Reopening this, to make sure we don't forget about the upstart recipe!
@Aranir: can you document this step in the README, and include scripts (if any) directly in the repo? (maybe in a deploy/ directory)

A lot changed since this issue was last discussed, I will document the deployment process before the end of the week, feel free to ping me before if necessary.

I added a document to explain how to deploy the app on Amazon Elastic Beanstalk. To run a local version you can simply follow the install guide.


Use Datum for string kernels

Which issue does this PR close?
Closes #4595.
What changes are included in this PR?
For the moment I only implemented the change for LIKE and I would like your feedbacks before implementing other kernels.
Are there any user-facing changes?
There will be some deprecated functions once it's finished.

Really cool to see this, and thank you for breaking this up. I'm away for the next week but will try to get some time to sit down with this, but otherwise will get back to you on my return.
I'm keen to see if there is some way to use type-erasure, i.e. &dyn Fn(&str, &str) or similar to both cut down on codegen and simplify the code easier to read. This does assume the dyn dispatch is negligible compared to the cost of the string operation, but I suspect this may be the case

I did a quick and dirty experiment, and it would appear my hunch is broadly correct
fn do_bench() {
   let cmp: &dyn Fn(&str, &str) -> bool = black_box(&|l, r| l == r);
    c.bench_function("eq_simple_dyn", |b| {
        b.iter(|| {
            let l = black_box(&l);
            let r = black_box(&r);
            l.iter()
                .zip(r)
                .map(|(l, r)| match (l, r) {
                    (Some(l), Some(r)) => Some(cmp(l, r)),
                    _ => None,
                })
                .collect::<Vec<_>>()
        })
    });

    let l = create_string_array::<i32>(1024, 0.);
    let needle = l.value(0);
    c.bench_function("eq_simple_scalar", |b| {
        b.iter(|| {
            let l = black_box(&l);
            let needle = black_box(needle);
            l.iter().map(|v| v.map(|x| x == needle)).collect::<Vec<_>>()
        })
    });

    let cmp = black_box(make_eq_scalar(needle));
    c.bench_function("eq_simple_dyn_scalar", |b| {
        b.iter(|| {
            let l = black_box(&l);
            l.iter().map(|v| v.map(|x| cmp(x))).collect::<Vec<_>>()
        })
    });

    dyn_cmp_dict_benchmarks(c);
}

fn make_eq_scalar(needle: &str) -> Box<dyn Fn(&str) -> bool + '_> {
    Box::new(move |a| a == needle)
}

And got
eq_simple               time:   [5.4250 µs 5.4278 µs 5.4308 µs]

eq_simple_dyn           time:   [6.5201 µs 6.5227 µs 6.5253 µs]

eq_simple_scalar        time:   [4.4315 µs 4.4334 µs 4.4355 µs]

eq_simple_dyn_scalar    time:   [4.9554 µs 4.9575 µs 4.9600 µs]

Equality is the cheapest of the string operations and yet the dyn dispatch is barely registering. I suspect if you tweaked it to have a signature like Fn([&str; 64, &str; 64)]) -> u64 the overheads would disappear entirely. Something worth thinking about possibly...

Sorry for taking so long to get back to you, I think I would like this to follow a similar pattern as https://github.com/apache/arrow-rs/pull/4701 and https://github.com/apache/arrow-rs/pull/4465.
I appreciate this is a much more intrusive change, and is quite fiddly, and so no hard feelings if you would like to back out of this. I already have a partially implemented version of this

I was just reading #4701 :)
Yeah I think that it will take me a while to figure this out completely. It might be more productive that you go further with it. Anyway, it allowed me to learn more about the code base. Feel free to close this PR!

Closing in favor of https://github.com/apache/arrow-rs/pull/4732, thank you for your work on this :+1:


DesktopWallpaper generated as a struct instead of a class

Actual behavior
The Windows.Win32.UI.Shell.DesktopWallpaper type is generated as a struct instead of a class:

Expected behavior
I expected it to be generated as a class and with the ComImport attribute.
To make this work, I had to manually create the DesktopWallpaperCoClass class:
using Windows.Win32;
using Windows.Win32.UI.Shell;
using System.Runtime.InteropServices;
using SkiaSharp;

namespace Example
{
    [ComImport]
    [Guid("C2CF3110-460E-4FC1-B9D0-8A1C0C9CC4BD")]
    public class DesktopWallpaperCoClass
    {
    }

    class Program
    {
        static void Main(string[] args)
        {
            var desktopWallpaper = (IDesktopWallpaper)new DesktopWallpaperCoClass();

            desktopWallpaper.GetBackgroundColor(out uint backgroundColorNative);

            var backgroundColor = new SKColor(backgroundColorNative);
            Console.WriteLine("BackgroundColor={0}", backgroundColor);
        }
    }
}

Repro steps

NativeMethods.txt content:

// NB this file is handled by the Microsoft.Windows.CsWin32 package source generator from:
//          https://github.com/microsoft/CsWin32/blob/v0.1.619-beta/src/Microsoft.Windows.CsWin32/SourceGenerator.cs#L20

DesktopWallpaper        // aka Windows.Win32.UI.Shell.DesktopWallpaper
IDesktopWallpaper       // aka Windows.Win32.UI.Shell.IDesktopWallpaper

NativeMethods.json content (if present):

Any of your own code that should be shared?

Please see the above Expected behavior section.
I would appreciate guidance on whether its the correct way of doing this.
Context

CsWin32 version: 0.1.619-beta
Win32Metadata version (if explicitly set by project):
Target Framework: net6.0-windows
LangVersion (if explicitly set by project): [e.g. 9]

I believe this may already be fixed in the main branch: https://github.com/microsoft/CsWin32/issues/453#issuecomment-977010738

Indeed it is! Thank you for pointing that out!
Changing the reference to:
  <ItemGroup>
    <PackageReference Include="Microsoft.Windows.CsWin32" Version="0.1.631-beta">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
    </PackageReference>
  </ItemGroup>

And using the daily repository by adding a nuget.config file (to the current directory) with the content:
<configuration>
  <packageSources>
    <add key="winsdk" value="https://pkgs.dev.azure.com/azure-public/winsdk/_packaging/CI/nuget/v3/index.json" />
  </packageSources>
</configuration>

Did the trick!


onLoadingFinish on Android not working as expected

Bug description:
The issue only persists in Android.
A change in the navigation state url causing Android Webview's viewState to be forever stuck in "LOADING" due to previous url having some capital letters when compared to current loading url. However, i found that Webview.ios.js doesnt have such checking in the onLoadingFinish function.
To Reproduce:
Redirect from any url with the SAME url but with some capital alphabets.
Example: from www.google.com to www.Google.com
Expected behavior:
onLoadingFinish function should have the same checking function in iOS and Android.
Screenshots/Videos:

(Webview.ios.js)

_(Webview.android.js)_
Environment:

react-native version: 0.61.5
react-native-webview version: 8.0.2

Issue still persist on latest version of React-Native-Webview: 10.3.1
Suggest to change to compare the start and current urls in lowercases.
if (url && this.startUrl && url.toLowerCase() === this.startUrl.toLowerCase()) { this.setState({ viewState: 'IDLE' }); }
I'm not sure about the impact to the rest but this works fine for me.

#1487

@Foomethod I have similar problem as well. Were you able to make temp fix for this issue without modifying the lib files?

@dabonnestor
The main reason why it was loading forever was because the state of the webview component was still in "LOADING" after a strict comparison (===) of the current and previous url.
if (url === _this.startUrl) {       _this.setState({             viewState: 'IDLE'       }); }
The webview component doesn't provide any other way to modify it's own state to "IDLE".
I resorted to modifying the lib file because webviewRef.current.stopLoading() wasn't an ideal solution for me as the website I'm on does multiple redirects, doing stopLoading() would stop the entire redirection process.
stopLoading may just work for you if the website you are visiting doesn't redirect too much.
Alternately, you may replace the above code with the below in the lib files. (Webview.android.js)
if (url && _this.startUrl && url.toLowerCase() === _this.startUrl.toLowerCase()) {                 _this.setState({                     viewState: 'IDLE'                 });             }

#1487


Ethnicity bias in face encoder

Through experimentation I've observed that the identity transfer performance is quite poor for African ethnicity faces as opposed to other ethnicities. I've delved a bit deeper and I suspect it's due to the training datasets used for the antelopev2 face recognition model (Glint360k). Insightface offers another face encoder buffalo_l that was trained on WebFace260M, a much more diverse dataset (see Fig 8 in the paper).  Insightface currently recommends buffalo_l throughout their repo and it's also the one used by IP-Adapter-FaceID.
What do y'all think about training future versions using buffalo_l?  It would be awesome for InstantID to work well on all ethnicities.

Yes, this is a good suggestion, we will do it later.


Get rid of Travis?

Get rid of Travis and use only Github Actions?

I think that's a good idea.

I think that's a good idea.

It looks like Travis is not triggered anyway, or at least not reporting back. I opened a PR removing it. Also added the Python and JavaScript tests to the CI as they were not run on the Github actions,

It looks like Travis is not triggered anyway, or at least not reporting back. I opened a PR removing it. Also added the Python and JavaScript tests to the CI as they were not run on the Github actions,


Fail the Runtime tests check if the previous jobs were cancelled or failed

Short description of the problem this fixes or functionality that this introduces. This may be used for the CHANGELOG
Fail the Runtime tests check if the previous jobs were cancelled or failed

Give a summary of what the PR does, explaining any non-trivial design decisions
If the required tests fail or get cancelled, the last check is skipped which gets treated as success and PRs are able to merge.

Link of any specific issues this addresses

I'm going to test this first with a manual cancel / fail.

Lets try it!


Makes liveness test faster

Makes the "should *not* restart" liveness e2e test take 2 instead of 4 minutes.
I measured the timing of this section of the e2e test, and the positive tests ("should restart") consistently take exactly 26 seconds. (See Jenkins history for this regularity.) However, the parallel tests (that run on PRs) take longer—usually around ~1 minute, and never longer than 1m30s in the last 100 runs (for the entire test, mind you, not just this loop). Thus, 2 minutes will cut the test time (the test always waits for a timeout) in half, and should still give 0 flakes.
Other minor improvements:

print elapsed time during test
change printing from "pod %s in namespace %s", pod, ns to the more concise "pod %s/%s", ns, pod
increase polling interval (5s → 2s)
use more precise types for printing (%t instead of %v for bools)
change Fail(fmt.Sprintf(...)) to Failf(...)

It appears 45s, while begin plenty long for normal runs, isn't long enough for parallel runs :-( Bumped to 1m.

This is good now. We've got two Jenkins flakes/failures:
[Fail] Services [It] should serve multiport endpoints from pods
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:959

[Fail] Services [It] should serve a basic endpoint from pods
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:959

The tests in question finish in either 28s or 10s.

@ixdy let me know if you've already got an issue for the flaking service test (I see flakes in the Jenkins kubernetes-e2e-gce-parallel job).

@k8s-bot test this please

@k8s-bot test this please

@ixdy is probably swamped, so playing PR roulette

ha, I was just starting to take a look at this!
I really wish there were a better way to do the negative test than wait for timeout.

hooray, back to @ixdy !

@ixdy PTAL

LGTM, thanks for the thorough fix, even the commented out tests!
(... wait, there are commented-out tests? augh!)

Haha :-)


Is there a way to use this with .NET resources files .resx

A have a question.
Is it possible to use this with .net .resx files?

What do you mean? This is an AngularJS plugin, and this is a JS framework. We have nothing to do with .NET. If you have an .NET based web app.. why not.

There is a resx to json converter somewhere, that is what I used

I have no idea what you want. Again: What is the link to us? What is a resxfile? Why does it matters for us?

just use something like gulp-resx2 to convert your resx file to json file then you can use angular-translate.

I think I can say: no.
However, as the (async) loader is only a function, it is up to you implementing a loader which can handle reading such a file and returning corresponding json.

Actually for our .Net to Angular migration , I need to implement localization using ngx translate. Is there any way I can convert resx files into JSON


TypeError: OAuthStrategy requires a consumerKey option

I did npm install in / and /server and started gulp dev in /
That resulted in
/Users/admin/git/loklak_webclient/server/node_modules/passport-twitter/node_modules/passport-oauth1/lib/strategy.js:83
  if (!options.consumerKey) { throw new TypeError('OAuthStrategy requires a co
                                    ^
TypeError: OAuthStrategy requires a consumerKey option
    at Strategy.OAuthStrategy (/Users/admin/git/loklak_webclient/server/node_modules/passport-twitter/node_modules/passport-oauth1/lib/strategy.js:83:37)
    at new Strategy (/Users/admin/git/loklak_webclient/server/node_modules/passport-twitter/lib/strategy.js:53:17)
    at Object.<anonymous> (/Users/admin/git/loklak_webclient/server/index.js:37:14)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)
    at node.js:814:3
[09:29:28] [nodemon] app crashed - waiting for file changes before starting...
[BS] Proxying: http://localhost:3001
[BS] Now you can access your site through the following addresses:
[BS] Local URL: http://localhost:3000
[BS] External URL: http://<IP_ADDRESS>:3000

You have to create a Twitter app at https://apps.twitter.com
Set the twitterConsumerKey var in custom_configFile.json to set the Consumer Key (API Key) from your Twitter app
Set the twitterConsumerSecret var in custom_configFile.json to set the Consumer Secret from your Twitter app
I updated the Readme about it

Fixed via 54dd21744ccf43049d8a78ebee8e6c734eabc170

This is not the complete solution. I expect that parts of the application, which do not use or need a twitter app key should work without the configuration of a consumer key+secret


Entity.active_path

Easily hide/disable a complex nested structure of Visuals/Entities by just setting its root entity to active = true/false;
Entity has a new property .active_path that checks if the Entity and all of its parents have .active==true (think of Unity's .activeInHierarchy). Only updated when hierarchy changes.
Entity only receives events when active_path == true, Visuals are only visible when active_path == true (may be disabled via Visual._ACTIVE_BASED_VISIBILITY = false).

Thanks a lot for the effort! I appreciate the desire to contribute, and I'm glad you did.
Unfortunately this PR is incompatible with the library design goals.
Events is an agnostic class, it must not be coupled to Entity. The all caps underscored static variables are not a convention in luxe (and can't be for later reasons). The visuals and entity coupling like this is also against the idea. There may also be the assumption that the root is the relevant tier to consider (i.e all of the parents up to the root), which would mean that this value only makes sense for root type nodes and asking halfway up the tree doesn't apply, which would mean you might need even more queries and states to track, and more and more chance of a ball of state moving around that has no real meaning to the API it's trying to facilitate. It would be better if the coupling was managed by a higher level construct, not internally.
I will note that there will be facility like this from the engine when the focus sheet for Entities comes around.
If you want this specific query it would make more sense to me atm as a static extension, the engine code will be changing in it's focus sheet anyway. Here is an example:
class EntityTools {

    public static function active_path(e:luxe.Entity) : Bool {

        if(e.parent != null) {
            return e.active && active_path(e.parent);
        }

        return e.active;

    }

}

You would use it by adding using EntityTools; at the top of your module somewhere:
        var r = new luxe.Entity({name:'root'});
        var a = new luxe.Entity({name:'a'});
        var b = new luxe.Entity({name:'b'});
        var c = new luxe.Entity({name:'c'});

        c.parent = b;
        b.parent = a;
        a.parent = r;

        trace(c.active_path());
        trace(b.active_path());
        trace(a.active_path());
        trace(r.active_path());

        a.active = false;

        trace(c.active_path());
        trace(b.active_path());
        trace(a.active_path());
        trace(r.active_path());

Cool, thanks for clearing it up! I assumed there were some design constraints, I just needed the functionality now and wasn't sure about how to approach it correctly. I'll have a look at static extensions.
And thanks for keeping the codebase strict and focused! :)


Enable UglifyJsPlugin

Brings main.js from 7.64mb down to 3.04mb. 🍻

Bonus points: Trying to enable UglifyJsPlugin, i (or rather uglifyjs) noticed that unbabeled ES6 code was imported from node_modules, so the current main.js fails in non-ES6 browsers. This is fixed with this PR.

Excellent! Will merge this in.


Add container-based build workflow and improve build tooling

This PR introduces a new container-based build workflow and several improvements to the build system:
Major Changes

Added a new Makefile for streamlined container-based builds
Created tools/build_firmware.sh script to standardize build steps
Updated CI to use the new build script
Added QA checks for shell scripts using reviewdog
Fixed various build-related issues
Mitigate certain supply chain attacks using sha256sums for external dependencies

New Build Workflow Features

Simple make-based commands for building firmware
Support for both Docker and Podman
Flexible firmware manifest selection
Shared build steps between local and CI environments

Technical Improvements

Fixed permission issues with extension symlinks under rootless podman
Improved error reporting in build_project.py
Added shellcheck and shfmt QA checks
Standardized build steps between local and CI environments

Usage Example
Build all firmware
make

Build specific manifest
make build_firmware MANIFESTS=manifests/nabucasa/yellow_bootloader.yaml

Documentation
Added comprehensive documentation in README.md covering:

Prerequisites installation
Build workflow usage
Available make targets
Customization options

Fixes

Permission issues with rootless podman
Git commit ID error reporting
Build step standardization

Just fixed the input device is not a TTY when running make all in GitLab CI within Docker In Docker GitLab runner
docker run --rm -it --user 0:0 -v /builds/prpl-foundation/mirrors/silabs-firmware-builder:/build -v /builds/prpl-foundation/mirrors/silabs-firmware-builder/outputs:/outputs -v /builds/prpl-foundation/mirrors/silabs-firmware-builder/build_dir:/build_dir silabs-firmware-builder \
	bash -c " \
		build_firmware.sh \
		--build-dir /build_dir \
		--output-dir /outputs \
		--manifest manifests/nabucasa/skyconnect_zigbee_ncp.yaml --manifest manifests/nabucasa/yellow_bootloader.yaml --manifest manifests/nabucasa/skyconnect_openthread_rcp.yaml --manifest manifests/nabucasa/yellow_openthread_rcp.yaml --manifest manifests/nabucasa/yellow_zigbee_ncp.yaml --manifest manifests/nabucasa/zwave_stick.yaml --manifest manifests/nabucasa/skyconnect_bootloader.yaml --manifest manifests/prpl_foundation/wnc_freedom_openthread_rcp.yaml --manifest manifests/prpl_foundation/wnc_freedom_bootloader.yaml \
	"
the input device is not a TTY

just improved the UX by providing No container engine found, please install docker or podman when neither podman or docker is installed and make was run

Thanks for the PR! I will give it a thorough review in January.


existing iframe export urls need an extra embed parameter to see only code

Describe the bug
existing iframe export urls need an extra embed parameter to see only code.
It looks like the iframe export url structure changed today, when I exported code via the iframe option this afternoon around 2pm eastern, I got the first url, added it to a presentation, then went back to the presentation around 6pm and the entire carbon.now.sh page shows in the presentation instead of the code snippet I was trying to embed. I realized adding an extra embed to the url, seems to fix this.
Is this change intended?
I believe this changed occurred in either 4.3.11 or 4.3.12.
To Reproduce
Go to:
https://carbon.now.sh/embed/?bg=rgba(255%2C255%2C255%2C0)&t=night-owl&wt=none&l=javascript&ds=false&dsyoff=20px&dsblur=68px&wc=false&wa=true&pv=32px&ph=10px&ln=false&fl=1&fm=Hack&fs=14px&lh=133%25&si=false&es=4x&wm=false&code=function%2520firstPromise()%2520%257B%250A%2520%2520return%2520new%2520Promise(resolve%2520%253D%253E%2520%257B%250A%2520%2520%2520%2520setTimeout(resolve%252C%25201000%252C%2520'%25F0%259F%2598%25BA')%250A%2520%2520%257D)%250A%257D%250A%250Afunction%2520secondPromise(element)%2520%257B%250A%2520%2520return%2520new%2520Promise(resolve%2520%253D%253E%2520%257B%250A%2520%2520%2520%2520setTimeout(resolve%252C%2520500%252C%2520%27%25F0%259F%2590%25B6%27)%250A%2520%2520%257D)%250A%257D%250A%250Afunction%2520thirdPromise(element)%2520%257B%250A%2520%2520return%2520new%2520Promise(resolve%2520%253D%253E%2520%257B%250A%2520%2520%2520%2520setTimeout(resolve%252C%2520800%252C%2520%27%25F0%259F%2590%25A2%27)%250A%2520%2520%257D)%250A%257D%250A%250Aconst%2520animals%2520%253D%2520Promise.all(%255B%250A%2520%2520firstPromise()%252C%250A%2520%2520secondPromise()%252C%250A%2520%2520thirdPromise()%250A%255D).then(function(value)%2520%257B%250A%2520%2520return%2520value%250A%257D)%250A
Compare to:
https://carbon.now.sh/embed/embed/?bg=rgba(255%2C255%2C255%2C0)&t=night-owl&wt=none&l=javascript&ds=false&dsyoff=20px&dsblur=68px&wc=false&wa=true&pv=32px&ph=10px&ln=false&fl=1&fm=Hack&fs=14px&lh=133%25&si=false&es=4x&wm=false&code=function%2520firstPromise()%2520%257B%250A%2520%2520return%2520new%2520Promise(resolve%2520%253D%253E%2520%257B%250A%2520%2520%2520%2520setTimeout(resolve%252C%25201000%252C%2520'%25F0%259F%2598%25BA')%250A%2520%2520%257D)%250A%257D%250A%250Afunction%2520secondPromise(element)%2520%257B%250A%2520%2520return%2520new%2520Promise(resolve%2520%253D%253E%2520%257B%250A%2520%2520%2520%2520setTimeout(resolve%252C%2520500%252C%2520%27%25F0%259F%2590%25B6%27)%250A%2520%2520%257D)%250A%257D%250A%250Afunction%2520thirdPromise(element)%2520%257B%250A%2520%2520return%2520new%2520Promise(resolve%2520%253D%253E%2520%257B%250A%2520%2520%2520%2520setTimeout(resolve%252C%2520800%252C%2520%27%25F0%259F%2590%25A2%27)%250A%2520%2520%257D)%250A%257D%250A%250Aconst%2520animals%2520%253D%2520Promise.all(%255B%250A%2520%2520firstPromise()%252C%250A%2520%2520secondPromise()%252C%250A%2520%2520thirdPromise()%250A%255D).then(function(value)%2520%257B%250A%2520%2520return%2520value%250A%257D)%250A
Screenshots
https://carbon.now.sh/embed/? url structure

https://carbon.now.sh/embed/embed/? url structure

Info (please complete the following information):

OS [e.g. macOS, Linux, Windows, iOS]: macOS
Browser [e.g. chrome, safari]: Chrome

The correct address is https://carbon.now.sh/embed?bg=rgba(255%2C255%2C255%2C0)&t=night-owl&wt=none&l=javascript&ds=false&dsyoff=20px&dsblur=68px&wc=false&wa=true&pv=32px&ph=10px&ln=false&fl=1&fm=Hack&fs=14px&lh=133%25&si=false&es=4x&wm=false&code=function%2520firstPromise()%2520%257B%250A%2520%2520return%2520new%2520Promise(resolve%2520%253D%253E%2520%257B%250A%2520%2520%2520%2520setTimeout(resolve%252C%25201000%252C%2520'%25F0%259F%2598%25BA')%250A%2520%2520%257D)%250A%257D%250A%250Afunction%2520secondPromise(element)%2520%257B%250A%2520%2520return%2520new%2520Promise(resolve%2520%253D%253E%2520%257B%250A%2520%2520%2520%2520setTimeout(resolve%252C%2520500%252C%2520%27%25F0%259F%2590%25B6%27)%250A%2520%2520%257D)%250A%257D%250A%250Afunction%2520thirdPromise(element)%2520%257B%250A%2520%2520return%2520new%2520Promise(resolve%2520%253D%253E%2520%257B%250A%2520%2520%2520%2520setTimeout(resolve%252C%2520800%252C%2520%27%25F0%259F%2590%25A2%27)%250A%2520%2520%257D)%250A%257D%250A%250Aconst%2520animals%2520%253D%2520Promise.all(%255B%250A%2520%2520firstPromise()%252C%250A%2520%2520secondPromise()%252C%250A%2520%2520thirdPromise()%250A%255D).then(function(value)%2520%257B%250A%2520%2520return%2520value%250A%257D)%250A
I will update the code to remove the trailing slash ASAP, but in the meantime you can delete it locally as a work around


tools/docker: update Go in the containers

Use 1.22.7.

Will it download 1.22.0 having 1.22.7?

Will it download 1.22.0 having 1.22.7?

No, it looks like it doesn't.


Code - extra spacing, hard to copy

When asking ChatGPT to generate code, it has an extra space/indent at the start any of the lines that aren't indented.
Seems like it's to do with the ``` code blocks - it's a small issue but makes copy/pasting more difficult. Any tips/workarounds appreciated.
Eg. (* shows where a space is)
*function generateList() {
*}
Looking at the session logs, there's no space:
"content": "Here's the function:\n\njavascript\nfunction generateList() {\n}\n"
Thanks for making this open source btw!

I also have this issue

That happens because the Rich Markdown renderer uses a padding of 1 character for the code blocks. And that's not configurable.
I opened an issue in the Rich repository (https://github.com/Textualize/rich/issues/3199). I don't know if this will be taken into consideration, because it seems a minor issue, let's see...

I wrote a workaround on #52 that feels nice to me. Instead of messing with the formatting built in to Rich, I added a /copy command that can be used to directly copy the contents of code blocks or whole messages to the clipboard.

#52 is merged, I think this issue can be closed.


Swift issues

Hi, I have tried to use this for excel reader & writer in my swift project.
But I have failed to build. I followed your instruction. Please help me.

you need to add path to library to Header search paths in build settings

For me the problem lied within the library itself. Somehow Swift expects
import <Folder/Lib> as syntax since the last update.
This Is what I did, I replaces all imports where the Compiler was complaining with the "new" swift
syntax and tada project runs fine. Not sure whether this is really related,
but it might be worth a try :)


Docfix: Change label from Default to Secondary, and reorder dropdowns

This pull request does two thing:

Change typo on dropdowns. They are secondary dropdowns, not default.
Change order to be same as buttons. Primary dropdown before secondary.

Thanks!


chore: release master

:robot: I have created a release beep boop
@allaround/all-components: 1.8.2
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/button bumped from ^1.8.1 to ^1.8.2
@allaround/input bumped from ^2.8.1 to ^2.8.2
@allaround/sidebar bumped from ^1.0.1 to ^1.0.2
@allaround/navbar bumped from ^1.0.1 to ^1.0.2
@allaround/hooks bumped from ^1.0.1 to ^1.0.2
@allaround/textarea bumped from ^1.0.1 to ^1.0.2
@allaround/tags bumped from ^1.0.1 to ^1.0.2
@allaround/dropdown bumped from ^1.0.1 to ^1.0.2
@allaround/select bumped from ^1.0.1 to ^1.0.2
@allaround/upload bumped from ^1.0.1 to ^1.0.2
@allaround/scheduler bumped from ^1.0.1 to ^1.0.2
@allaround/video bumped from ^1.0.1 to ^1.0.2
@allaround/image bumped from ^1.0.1 to ^1.0.2
@allaround/checkbox bumped from ^1.0.1 to ^1.0.2
@allaround/tooltip bumped from ^1.0.1 to ^1.0.2
@allaround/switch bumped from ^1.0.1 to ^1.0.2
@allaround/progress-bar bumped from ^1.0.1 to ^1.0.2
@allaround/notification bumped from ^1.0.1 to ^1.0.2
@allaround/placeholder bumped from ^1.0.1 to ^1.0.2

button: 1.8.2
1.8.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

checkbox: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

dropdown: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

hooks: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

image: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

input: 2.8.2
2.8.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

navbar: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

notification: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

placeholder: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

progress-bar: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

scheduler: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

select: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

sidebar: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

switch: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

tags: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

Dependencies

The following workspace dependencies were updated

devDependencies

@allaround/input bumped from ^2.8.1 to ^2.8.2
@allaround/hooks bumped from ^1.0.1 to ^1.0.2

textarea: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

Dependencies

The following workspace dependencies were updated

devDependencies

@allaround/button bumped from ^1.8.1 to ^1.8.2

tooltip: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

upload: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

video: 1.0.2
1.0.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

allaround-components: 2.9.2
2.9.2 (2023-08-22)
Bug Fixes

internal dependencies (#71) (657df22)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/allaround-components-v2.9.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/all-components-v1.8.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/button-v1.8.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/input-v2.8.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/navbar-v1.0.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/hooks-v1.0.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/textarea-v1.0.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/scheduler-v1.0.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/checkbox-v1.0.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/switch-v1.0.2 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/notification-v1.0.2 :sunflower:


Complex Title not displayed?

Big thanks for this plugin.
I made a test run using a ICAL from Outlook/Exchange server.
In the ICS file, the summary of meeting is written down in the following format: SUMMARY;LANGUAGE=fr:Demo title of a meeting
This renders in the plugin output as "3:30 PM - 6:30 PM: [object Object]".
Is there a way to have more parameter around the "{Title}" template?

Hmm, I'll have to investigate this, could you perhaps share some kind of guide as to how to create an ebent with summary in that format? This is how my events look like.
Do you have perhaps your language set up as something in specific or something?

I am using outlook in a corporate environnement with nothing particular set. I assume the Outlook & Exchange format make it really the far-fetched professional context.
Looking at the "pi.parseICS(e);" function, it is well understood by the library. It is only a matter of exposing it back to logseq I assume:

Can you try the latest release? Should be fixed

I've had to revert this in the latest release as it was causing issues with large calendars. Please stay on the current version until I get something working that doesn't interfere with other functions.


Custom training loop, iteration over Dataset hangs under MultiWorkerMirroredStrategy

System information

Have I written custom code (as opposed to using a stock
example script provided in TensorFlow):  Yes
OS Platform and Distribution (e.g.,
Linux Ubuntu 16.04): TensorFlow 2.0.1 GPU official docker image
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if
the issue happens on mobile device:
TensorFlow installed from (source or
binary): - TensorFlow version (use command below): 2.0.1
Python version: - Bazel
version (if compiling from source):
GCC/Compiler version (if compiling from
source):
CUDA/cuDNN version: - GPU model and memory: CUDA 10.1 V100 16G

Describe the current behavior
I use the following scheme to iterate over Dataset.
for epoch in range(FLAGS.epoch):
        for train_data in train_dataset:
           ...

Train stops at the last few batches of the first epoch. I found that documentation https://www.tensorflow.org/tutorials/distribute/multi_worker_with_keras  mentions only keras.fit
Describe the expected behavior
It should be explicitly mentioned, or produce some logs when running in such scenario.
Currently, before the hang, only one line is printed in log.
INFO:tensorflow:Collective batch_all_reduce: xxx all-reduces, num_workers = xxx
I0225 cross_device_ops.py:1107] Collective batch_all_reduce: xxx all-reduces, num_workers = xxx

Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

@372046933
Request you to share colab link or simple standalone code to reproduce the issue in our environment. It helps us in localizing the issue faster. Thanks!

This is just a documentation issue. The doc currently states (https://www.tensorflow.org/tutorials/distribute/multi_worker_with_keras)

[...] MultiWorkerMirroredStrategy does not support last partial batch handling […]

But this isn't mentioned in the docu of MultiWorkerMirroredStrategy.
Of course it would be better to not have that limitation

@Flamefire Sorry, my company forbid copy any data out. Only data in. Otherwise I have uploaded all the code.

@372046933
Will it be possible to share the sample data so i can test it on the Tesnsorflow tutorials to reproduce the issue.Thanks!

@ravikyram Sorry, can't either. In only, no out :(. The data is actually ImageNet in TFRecord format.  So I think you can build sample data with fixed size image.


Rabbit-Elixir v1.0.0

Rabbit-Elixir v1.0.0

@Arkar-Aung  You have a permission to write in this repo :D
Next time , you can push in this repo instead of fork

Oh, I see bro


Simplify README build instructions

cargo-web will automatically install the relevant target through rustup for the user.
The wasm32-unknown-unknown target is the default now on the newest version of cargo-web, and is officially supported on stable.

Great stuff! Thank you! :+1:

bors r+


Any reason to query cursor in AddTodoMutation?

https://github.com/relayjs/relay-examples/blob/0f6344fd8477db51c4aaad0b78e98f31a2c51da1/todo/js/mutations/AddTodoMutation.js#L24
Is this required for new edge or can be ignored?
Does the backend even need to generate a cursor field?

@kassens Please. I have the same question.

I might be wrong, but I believe we ask for the cursor for pagination. If we want to use the new element as the ancjhor for pagination, we'd need it's cursor. E.g. (first: 10, after: <cursor>)


feat!: update to tree-sitter 0.23

Tree-sitter released version 0.23 recently. This contains a breaking, but ultimately very good change to how parser bindings work (https://github.com/tree-sitter/tree-sitter/pull/3069). The TLDR of that change is that parsers do not depend on tree-sitter anymore, but instead on a shard (and supposedly very stable) tree-sitter-language crate. As a result, clients are free to chose their tree-sitter version as the parser ABI is supported. Library and parser versions are less tighly coupled, and it should no longer be necessary to move all the parsers to the next tree-sitter version in lock-step to be able to upgrade the library.
Most of the changes in this PR are from running tree-sitter generate. I'll add comments on other changes I did to explain why I thought they are necessary, or where I'm not sure I did it correctly.
Please review carefully, since this project has a non-standard setup, and I may have missed something.
Complications with MarkdownParser
The Rust bindings, besides the gramamr, also provide a MarkdownParser implementation. It needs tree-sitter for its implementation. That means we cannot just remove the tree-sitter dependency like for most grammars.
Leaving the tree-sitter dependency as it was would negate the benefit of the switch to tree-sitter-language and still effectively pin the tree-sitter library for any user of this crate.
My proposal, as implemented in the PR, is to put the convenience parser behind a cargo feature 'parser'. Users that do not want it will get the benefits of the tree-sitter-language approach, while others will have to live (reasonably!) with the restriction on tree-sitter version they can use.
The consequence is that users of the MarkdownParser will need to change their Cargo.toml to enable the parser feature on their tree-sitter-md dependency. Since they will probably need to change their Cargo.toml anyway when upgrading I don't think this is such a heavy burden, but it should be communicated clearly in release notes or something to avoid confusion.
Let me know if you think this is an acceptable solution!

Thank you!

@ObserverOfTime Thanks for merging these changes! Is it possible to do a versioned release of these as well?


Feature Request - Add support of Image operation for sharp adapter

Hello,
Sharp allowing the possibility of extract an image (a crop) using http://sharp.pixelplumbing.com/en/stable/api-operation/#extract. Does it make sense to add it to this package?
With this, it would be nice to be able to chain images transformation, with something like:
              use: [
                   {
                       loader: 'file-loader',
                   }
                   {
                       loader: 'responsive-loader',
                       options: {
                           adapter: require('responsive-loader/sharp-extract'),
                           name: "images/responsive/[name]-[width].[ext]"
                       }
                   },
                   {
                       loader: 'responsive-loader',
                       options: {
                           adapter: require('responsive-loader/sharp')
                       }
                   },
               ],

this way, we can resize then extract the image (looks like another feature request).

good stuff; want!
do we have a pending PR for this?

Not sure if it's possible/necessary to chain loaders for this. How about something like
{
  loader: 'responsive-loader',
  options: {
      adapter: require('responsive-loader/sharp'),
      operations: [["rotate", 90], "extract"]
  }
}

// Or even better?
{
  loader: 'responsive-loader',
  options: {
      adapter: require('responsive-loader/sharp'),
      operations: img => img.rotate(90).extract()
  }
}

That do not work in my case, I need to be able to configure it inline: asset.jpg?size=1200&extract_left=151&extract_top=0&extract_width=1200, except if img contains his own query?
For information, I think you are right, I tried to chain it properly but it did not work, I will retry it asap and open an according PR if it works.

@Ngob: Does this loader with sharp support cropping currently?

@strarsis not as it is. I modified code to allow cropping, but it work only with inline queries and you can not crop and resize the same image. I can share the code if you like.


InvalidateRect

InvalidateRect calls do not work. Paint will always get a client rect as a clip rect.

Actually works like it should.


[Models] New AWS Controllers for Kubernetes:  efs, ecs, documented, cloud front

Current Situation
As of the end of Feb. 2024, The ACK collection has expanded with some new controllers:

efs https://gallery.ecr.aws/aws-controllers-k8s/efs-chart
ecs https://gallery.ecr.aws/aws-controllers-k8s/ecs-chart
documentdb https://gallery.ecr.aws/aws-controllers-k8s/documentdb-chart
cloudfront https://gallery.ecr.aws/aws-controllers-k8s/cloudfront-chart

Proposed Change
Add model support for each of these new controllers.

Contributor Guides and Handbook

MeshModel Repository
🖥 MeshModel Overview
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Contributing to Meshery Models
!! See https://docs.meshery.io/project/contributing/contributing-models
Instructions for Models
Forthcoming
Instructions for Components
While the default shape for new components is a circle, each component should be considered for its best-fit shape.

Review and familiarize with the available set of predefined relationship types. Refer the Cytoscape node types for a list of possible shapes.
Propose a specific shape, best-suited to visually represent the Component. Example - Deployment as a pentagon.
Proposee a specific icon, best-suited to visually represent the Component. Example - DaemonSet as a skull icon.

Instructions for Relationships

Identify the relationship and any specific constraints to be enforced between the two specific components, their models or potentially other components, models, or environmental considerations.
Propose a specific visual representation for the relationship. See example on Modeling Relationships.
Prospose the appropriate relationship type, using one of the predefined set of relationship types or suggest a new relationship where an existing type does not fit.
Create a Relationship Definition (yaml).
Create a policy for evaluation of the relationship (rego).
Review a prior pull request as an example of how to define a Relationships: https://github.com/meshery/meshery/pull/9880/files

Instructions for Policies

Forthcoming

Hopefully I can hop on this issue once I am done with the one I am currently handling. I am very interested.

If @SammyBloom haven’t started yet, I’d like to assign myself to this task :)

Thanks for raising your hand @mayocream please move forward, @SammyBloom considering message is old I'm assigning this issue to Mayo however we would appreciate if you like to help with reviewing PR, there are similar issues on which you would like to work on, lemme know if you are still hanging around to grab issues

Confirmed that we have added AWS controllers via https://github.com/meshery/meshery/commit/737e6f2c156097c4ac950ee87582f517ddb82c2d
Can we close this PR, as it's done already? @Yashsharma1911


Plugin Fails to Enable on Spigot 1.16

Issue
Attempting to use MineableSpawners on 1.16 Spigot (first build released yesterday) results in the plugin failing to enable.
Log
https://pastebin.com/raw/C1FFA1Z6
Analysis
It looks like the MineableSpawners is unable to deal with newer or unexpected versions of Spigot than it was originally coded for. The naive fix would just be adding another if check for 1.16 here, but It would be great if the plugin could at least try to enable on newer versions of Minecraft, especially since as you've said this is a project you are working on in your spare time.
Thank you!

#45 should fix this.

@Tacodude7729 your PR is working great on 1.16.1 thank you!

Closing with https://github.com/dnyferguson/MineableSpawners/commit/2870bce88c0485431872140edaca658530c74677