Docs

C'mon Nate, people need this stuff...
Planning on using TJ's dox...

http://tootallnate.github.com/NodObjC


Update Errors.msg

Just saw this exception today and wanted to fix the grammatical error

Thank you for your contribution.
Matthias


the params in main.py for save model

remember best Accu and save checkpoint
    is_best = accu > best_accu
    best_accu = max(accu, best_accu)

    if epoch in args.decay_epoch:

the is_best param is not use for save model anywhere , if i want to auto save model according the best metric ,how to define it??/

if is_best:     save_checkpoint(...)

if is_best: save_checkpoint(...)

ok， got it , thx doctor

another question is that  does this model is perform better than  resnet50 model  such as this repo ??  furthermore ,what‘s mean for this li for idx in range(105):
dataset['att_name'].append(data['peta'][0][0][1][idx, 0][0])
in the transform_peta.py，isn't attribute num 65 for peta data？？？

What do you mean? There is no transform_peta.py.

What do you mean? There is no transform_peta.py.

just refer this train code  :—> https://github.com/dangweili/pedestrian-attribute-recognition-pytorch  ,and   i find you make an ccommment under this repo. i cannot understand” for idx in range(105):
dataset['att_name'].append(data['peta'][0][0][1][idx, 0][0])　“ in transform_peta.py

It seems PETA originally have 105 attributes, including many color attributes, but only 61 attributes are commonly used.
I didn't use this script. I downloaded the train/test list from https://github.com/asc-kit/vespa/tree/master/generated .


Add bdougie

Bdougie has a MySpace-themed README. I think it is pretty cool!
https://twitter.com/bdougieYO/status/1281699715466199040?s=20

@filiptronicek It's really nice! Thanks for adding 🚀


Merge functionality of inverse_grid.py into inverse.py

inverse_grid.py could become our standard retrieval strategy.  It would run with an empty grid of "fixed" parameters by default, making it equivalent to inverse.py unless specified.  This would reduce duplication and simplify the codebase.

Handled in #92.


Adding a ranking utility to sort/rank fronts

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
closes #1475
What are the significant changes in functionality due to this change request?
enables ranking non dominated fronts recursively

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

@Jimmy-INL @mandd sorry, I did not see this because  @aalfonsi aalfonsi  is my personal github account.
Checklist passed...
PR can be merged.


Create app in advance with only username and password

Apps such as RedReader create an app and authorize access with only a username and password. They do not require an app to be created beforehand. From reading over the documentation, snoowrap does not provide such functionality. snoowrap.getAuthUrl and snoowrap.fromAuthCode handles authorization in advance, but not app creation in advance.

I don't think you can create apps through the api, you'd have to go to preferences and create it there each time. Technically you can automate this with something like selenium

Hi! I don't believe RedReader is actually creating apps on the fly! From what I can see and this line of code they are using a hardcoded application, this is supported in snoowrap.

Yes, I made progress on my extension once I realized the code was hardcoded. I'll close this now.


Auto parens happens for except clauses

Want to discuss this item to see how people feel about the algorithm I'm changing it to.
The new algorithm is:

Any assignment to a class will put the parens. So like x = Foo(). This means that if the user intended to set the assigment to a static field of the class, the parens might show up when they don't want them to.
Any passing of a class as an argument if that class is a builtin, will also have parens. That means something likefoo(list()) will have a parens, but something like foo(Foo) will not.

It's not clear to me why these two scenarios would behave differently. But I'm also a relatively new Python user, so maybe I'm missing something here.
Do we have data to support this algorithm?

Personally, I wouldn't want auto parentheses in either of these cases, especially the second.
On the second bullet, you mentioned "if that class is a builtin". Why does the fact that it's a builtin matter? Builtin classes are just like all other classes in Python, so I'm not sure why these should be singled out for different behavior. So, if you decide to keep that second bullet, I think it should be consistent for all classes.

The current implementation puts parens on all builtin class usages. Hence the parens for the usage of OSError in an except clause.
I believe the reason for just builtins before was because they have fewer static methods? Not entirely sure.
This was an attempt to make it more useful.

I think it's worth revisiting the decision to treat builtins specially. If anything, builtins are less likely to be instantiated explicitly through a constructor call because many of them have language syntax for instantiation. For example, you would rarely use int(0) or list() in favor of 0 or []. The language syntax is simpler and more idiomatic. I suspect that most of the time someone types the name of a builtin symbol within an argument list, their intent is probably not to call the constructor.

This issue has been fixed in prerelease version 2023.3.41, which we've just released. You can find the changelog here: CHANGELOG.md


in 'shadow-dom' mode, class "bg-#d00" will be converted to “.bg-\#dd0000 {...}”

配置项

vue文件

浏览器中输出的内容

依赖版本

输出的.bg-\\#dd0000选择器无法正确的被浏览器解析掉，正确的输出应该是.bg-\#dd0000

This will be fixed in #1945. however, you are not opt-in to Vue's Web Components feature. Styles defined in your components will be hoisted to . This will be problematic if you have multiple components like that. Because you will have duplicated CSS in your app. It's pointless to use shadow-dom that way. If you want to use UnoCSS with Web Compenents defined in Vue SFCs please refer to this section in Vue Docs for proper setup. Once you set up your components as described in the Vue Docs and when #1945 is released your styles will be isolated in shadow dom as you would expect.

This will be fixed in #1945, however, you are not opt-in to Vue's Web Components feature. Styles defined in your components will be hoisted to <head>. This will be problematic if you have multiple components like that. Because you will have duplicated CSS in your app. It's pointless to use shadow-dom that way. If you want to use UnoCSS with Web Components defined in Vue SFCs please refer to this section in Vue Docs for proper setup. Once you set up your components as described in the Vue Docs and when #1945 is released your styles will be isolated in shadow dom as you would expect.

think you !
the project is here: https://github.com/NMTuan/base_vite_chrome_extension/tree/feature/20221122
I didn't think too much about it, it just works so far.
in content-scripts, i will use the shadow-dom mode.
and in other files, i want use the default mode.
but the config only supports one mode.

I haven't tested really but I believe you can initialize UnoCSS multiple times and pass the related file patterns in include option.
const presets = [
  presetAttributify(),
  presetUno(),
  presetIcons(),
  presetRemToPx()
]
// vite plugins
UnoCSS({
  mode: 'shadow-dom',
  include: ['src/content/*'],
  presets
}),
UnoCSS({
  include: ['src/options/*', 'src/popup/*'],
  presets
}),


Case: while using use GPIOA port jtag tools not work. What can I do?

[Stlink/v2-onboard ] Programmer/board type: e.g Stlink/v1, Stlink/v2, Stlink/v2-onboard
[ V2J27M15] Programmer firmware version: e.g STSW-LINK007 2.27.15
[ OpenSUSE 13.2] Operating system: e.g Linux, Mac OS X, Windows (with specific version)
[ v1.2.0/git-9daea3c273] Stlink tools version and/or git commit hash: e.g v1.1.0/git-c722056
[ st-flash] Stlink commandline tool name: e.g st-info, st-flash, st-util
[STM32F411RE (Nucleo-F411RE) ] Target chip (and optional board): e.g STM32F402VG (STM32Fxxx Discovery)

Hello.
I am novice in STM32. But I read all issue carefully and after many attempts to solve my problem write my result. So I adapt 1-st blinky program from STM32-Discovery to my Nucleo-F411RE. I use stlink for burn flash. And 1-st time was success. But no more times, every time I got result some like:
blinky > make burn
/home/kv193/Programs/arm/stlink/build/st-flash --reset write blinky.bin 0x8000000
st-flash 1.2.0-129-gee3f7a1
2016-09-30T18:18:34 INFO /home/kv193/Programs/arm/stlink/src/common.c: Loading device parameters....
2016-09-30T18:18:34 WARN /home/kv193/Programs/arm/stlink/src/common.c: unknown chip id! 0xa05f0000
Makefile:51: recipe for target 'burn' failed
make: *** [burn] Error 255

After spent time I find decision: use STM ST-LINK Utility for Windows.
This utility success erase my chip ONLY IN SWD connection settings with mode "Connect Under Reset". In JTAG mode also I had error. After reading documentation I notice that used GPIOA por is include JTAG pins. And result if I config "RCC->AHB1ENR |= RCC_AHB1ENR_GPIOAEN;" then JTAG not work, but SWD work fine. Is it true? And if "yes" how to use SWD in Linux?

When you program the STM32F411RE on the nucleo with the onboard programmer there should be no problem. However when you use the SWD pins in your firmware it should also work as texane/stlink will also connect under reset and those pins are available under reset.
When you have access to a linux machine you cloud try openocd: openocd -f <conffile> with conffile:
source [find interface/stlink-v2.cfg]
transport select hla_swd
source [find target/stm32f4.cfg]
reset_config srst_only

Closing due to inactivity, feel free to comment.

Excuse me for long time silence (I work on other project with Cortex-M3 from diff manufacturer ).
Now I return to study STM32. And I continue ... Without / with reset I get different errors (see attachments). What is my wrong?
console.txt

You should try a least the newer released v1.3.1.

Yes, I am already do it.The ver 1.3.1work fine.Thank you. -- Best wishesKlochkov V. A.email<EMAIL_ADDRESS>+7-911-9141440    20.03.2017, 21:24, "Jerry Jacobs" notifications@github.com:You should try a least the newer released v1.3.1.—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

@kv193 thank you for your feedback and testing.


Allow Android devices without GPS to still install

Apps with this plugin being used will not be install the Android app from the Google Play store due to permission restrictions. Setting android:required to false will still add this permission to the project but not preclude the app from being installed on a device without GPS.

Actually, this should be on uses-feature not uses-permission. You can disregard this.

@stevengill
i got this email from google,
====
Hello Google Play Developer,
We're writing to let you know that the apps listed at the end of this email may be affected by an upcoming platform change.
Action required: If your app requires GPS hardware to operate properly, you will need to explicitly add the "android.hardware.location.gps" uses-feature to your manifest.
What’s changing
We’re making a change on October 15th, 2016 that will affect apps targeting API version 21 (Android 5.0, Lollipop) or higher that use ACCESS_FINE_LOCATION but don't explicitly have the "android.hardware.location.gps" uses-feature. Going forward, these apps will be available to install on devices that don't have GPS hardware. In most cases this won't be an issue since Wi-Fi and Cell-ID based location provides high enough fidelity for the typical operation of these apps. However, any apps that require GPS hardware, such as GPS navigators, should explicitly add the "android.hardware.location.gps" uses-feature to their manifest.
If your app requires GPS to function properly and you do not include android.hardware.location.gps in your manifest declaration, your users may have a poor app experience.
Also, if you’re using the fused location provider and wish to receive the most accurate location samples from GPS (i.e. with PRIORITY_HIGH_ACCURACY), you must include the "android.hardware.location.gps" feature in your app’s manifest to ensure that Google Play only distributes your app to devices with GPS sensors.
You can read more about this change in the Android Developers Help Center.
Regards,
The Google Play Team
====
So are you going to fix this issue before October 15th, 2016

@mahmoudkhalafallah we are working on adding the permission to the plugin + release it before Oct 15th.


THRIFT-5502: Log SocketException at WARN level only

and proposition to move logging to one place

and proposition to move logging to one place

Why?

instead of the private method isIgnorableException we can just have a method to log proper message and add mentioned in THRIFT-5502 ignore for specific Socket exceptions.
if not this way - please suggest how this ticket should be solved

and proposition to move logging to one place

I misunderstood this. I thought you were removing duplicate code and consolidating into a single method, but it didn't make sense, since this code is only called once.
What you're actually doing is combining the exception handling logic, so it's all handled in one place. That makes sense to me now.


chore(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-k8s-27-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4122

Questions ?
Please refer to the Backport tool documentation


[Bug]: When executing create TABLE or truncate table in odc oracle mode, a semicolon will be added to the built-in execution record table.

ODC version
ODC423
OB version
Oceanbase324
Oracle
What happened?
When executing create TABLE or truncate table in odc oracle mode, a semicolon will be added to the built-in execution record table.

What did you expect to happen?
execute normally with obclient
How can we reproduce it (as minimally and precisely as possible)?
truncate TABLE TEST1
executing the sql  with obclient and ODC
obclient> SELECT * from __all_virtual_ddl_operation where tenant_id=1003 order by gmt_modified desc limit 10;
Anything else we need to know?
No response
Cloud
No response

can not reproduce this:

I execute a sql truncate table number_range_parti_tbl

I look up this sql in __all_virtual_ddl_operation:

as you can see: there is no semicolon at the end of the statement.


githubmerge: make public name/email access of users more robust.

Recent changes in github API or in the @jpages account broke the script.

+1 but I did not change anything in my account...

+1


Simulation question

When I directly run the make command after git this repo, here I got an error
make[1]: Entering directory '/work/kleine-riscv/tests'
Building build/misc/ackermann
clang-10: warning: argument unused during compilation: '-fuse-ld=lld' [-Wunused-command-line-argument]
error: unable to create target: 'No available targets are compatible with triple "riscv32-unknown-unknown"'
1 error generated.
make[1]: *** [makefile:35: build/misc/ackermann] Error 1
make[1]: Leaving directory '/work/kleine-riscv/tests'
make: *** [makefile:46: tests/build] Error 2

Do you have any suggestion to solve this?
and make sim command got this error
Building build/Vcore
make[1]: Entering directory '/work/kleine-riscv/build'
g++  -I.  -MMD -I/usr/local/share/verilator/include -I/usr/local/share/verilator/include/vltstd -DVM_COVERAGE=0 -DVM_SC=0 -DVM_TRACE=0 -DVM_TRACE_FST=0 -faligned-new -fcf-protection=none -Wno-bool-operation -Wno-sign-compare -Wno-uninitialized -Wno-unused-but-set-variable -Wno-unused-parameter -Wno-unused-variable -Wno-shadow      -std=gnu++14 -Os -c -o core.o ../sim/core.cpp
In file included from ../sim/core.hpp:2,
                 from ../sim/core.cpp:2:
./Vcore.h:17:13: error: variable ‘Vcore VL_NOT_FINAL’ has initializer but incomplete type
 class Vcore VL_NOT_FINAL {
             ^~~~~~~~~~~~
./Vcore.h:18:3: error: expected primary-expression before ‘private’
   private:
   ^~~~~~~
./Vcore.h:18:3: error: expected ‘}’ before ‘private’
./Vcore.h:17:26: note: to match this ‘{’
 class Vcore VL_NOT_FINAL {
                          ^
./Vcore.h:18:3: error: expected ‘,’ or ‘;’ before ‘private’
   private:
   ^~~~~~~
./Vcore.h:22:3: error: expected unqualified-id before ‘public’
   public:
   ^~~~~~
In file included from ./Vcore.h:11,
                 from ../sim/core.hpp:2,
                 from ../sim/core.cpp:2:
./Vcore.h:28:13: error: ‘reset’ declared as reference but not initialized
     VL_IN8(&reset,0,0);
             ^~~~~
/usr/local/share/verilator/include/verilated.h:252:38: note: in definition of macro ‘VL_IN8’
 #define VL_IN8(name, msb, lsb) CData name  ///< Declare input signal, 1-8 bits
                                      ^~~~
./Vcore.h:29:13: error: ‘meip’ declared as reference but not initialized
     VL_IN8(&meip,0,0);
             ^~~~
/usr/local/share/verilator/include/verilated.h:252:38: note: in definition of macro ‘VL_IN8’
 #define VL_IN8(name, msb, lsb) CData name  ///< Declare input signal, 1-8 bits
                                      ^~~~
./Vcore.h:30:14: error: ‘ext_valid’ declared as reference but not initialized
     VL_OUT8(&ext_valid,0,0);
              ^~~~~~~~~
/usr/local/share/verilator/include/verilated.h:262:39: note: in definition of macro ‘VL_OUT8’
 #define VL_OUT8(name, msb, lsb) CData name  ///< Declare output signal, 1-8 bits
                                       ^~~~
./Vcore.h:31:14: error: ‘ext_instruction’ declared as reference but not initialized
     VL_OUT8(&ext_instruction,0,0);
              ^~~~~~~~~~~~~~~
/usr/local/share/verilator/include/verilated.h:262:39: note: in definition of macro ‘VL_OUT8’
 #define VL_OUT8(name, msb, lsb) CData name  ///< Declare output signal, 1-8 bits
                                       ^~~~
./Vcore.h:32:13: error: ‘ext_ready’ declared as reference but not initialized
     VL_IN8(&ext_ready,0,0);
             ^~~~~~~~~
/usr/local/share/verilator/include/verilated.h:252:38: note: in definition of macro ‘VL_IN8’
 #define VL_IN8(name, msb, lsb) CData name  ///< Declare input signal, 1-8 bits
                                      ^~~~
./Vcore.h:33:14: error: ‘ext_write_strobe’ declared as reference but not initialized
     VL_OUT8(&ext_write_strobe,3,0);
              ^~~~~~~~~~~~~~~~
/usr/local/share/verilator/include/verilated.h:262:39: note: in definition of macro ‘VL_OUT8’
 #define VL_OUT8(name, msb, lsb) CData name  ///< Declare output signal, 1-8 bits
                                       ^~~~
./Vcore.h:34:13: error: ‘ext_address’ declared as reference but not initialized
     VL_OUT(&ext_address,31,0);
             ^~~~~~~~~~~
/usr/local/share/verilator/include/verilated.h:265:38: note: in definition of macro ‘VL_OUT’
 #define VL_OUT(name, msb, lsb) IData name  ///< Declare output signal, 17-32 bits
                                      ^~~~
./Vcore.h:35:13: error: ‘ext_write_data’ declared as reference but not initialized
     VL_OUT(&ext_write_data,31,0);
             ^~~~~~~~~~~~~~
/usr/local/share/verilator/include/verilated.h:265:38: note: in definition of macro ‘VL_OUT’
 #define VL_OUT(name, msb, lsb) IData name  ///< Declare output signal, 17-32 bits
                                      ^~~~
./Vcore.h:36:12: error: ‘ext_read_data’ declared as reference but not initialized
     VL_IN(&ext_read_data,31,0);
            ^~~~~~~~~~~~~
/usr/local/share/verilator/include/verilated.h:255:37: note: in definition of macro ‘VL_IN’
 #define VL_IN(name, msb, lsb) IData name  ///< Declare input signal, 17-32 bits
                                     ^~~~
In file included from ../sim/core.hpp:2,
                 from ../sim/core.cpp:2:
./Vcore.h:44:28: error: uninitialized const ‘rootp’ [-fpermissive]
     Vcore___024root* const rootp;
                            ^~~~~
./Vcore.h:51:36: error: expected ‘)’ before ‘*’ token
     explicit Vcore(VerilatedContext* contextp, const char* name = "TOP");
                   ~                ^
                                    )
./Vcore.h:52:20: error: expected unqualified-id before ‘const’
     explicit Vcore(const char* name = "TOP");
                    ^~~~~
./Vcore.h:52:20: error: expected ‘)’ before ‘const’
     explicit Vcore(const char* name = "TOP");
                   ~^~~~~
                    )
./Vcore.h:54:20: error: declaration of ‘~Vcore’ as non-member
     virtual ~Vcore();
                    ^
./Vcore.h:55:3: error: expected unqualified-id before ‘private’
   private:
   ^~~~~~~
In file included from /usr/local/share/verilator/include/verilated.h:27,
                 from ./Vcore.h:11,
                 from ../sim/core.hpp:2,
                 from ../sim/core.cpp:2:
/usr/local/share/verilator/include/verilatedos.h:380:32: error: ‘Vcore& operator=(const Vcore&)’ must be a nonstatic member function
     Type& operator=(const Type&) = delete
                                ^
./Vcore.h:56:5: note: in expansion of macro ‘VL_UNCOPYABLE’
     VL_UNCOPYABLE(Vcore);  ///< Copying not allowed
     ^~~~~~~~~~~~~
In file included from ../sim/core.hpp:2,
                 from ../sim/core.cpp:2:
./Vcore.h:58:3: error: expected unqualified-id before ‘public’
   public:
   ^~~~~~
./Vcore.h:71:5: error: ‘VerilatedContext’ does not name a type; did you mean ‘VerilatedMutex’?
     VerilatedContext* contextp() const;
     ^~~~~~~~~~~~~~~~
     VerilatedMutex
./Vcore.h:73:24: error: non-member function ‘const char* name()’ cannot have cv-qualifier
     const char* name() const;
                        ^~~~~
./Vcore.h:74:1: error: expected declaration before ‘}’ token
 } VL_ATTR_ALIGNED(VL_CACHE_LINE_BYTES);
 ^
make[1]: *** [Vcore.mk:64: core.o] Error 1
make[1]: Leaving directory '/work/kleine-riscv/build'
%Error: make -C build -f Vcore.mk exited with 2
%Error: Command Failed /usr/local/bin/verilator_bin -Isrc -Isrc/pipeline -Isrc/units -Wall -Mdir build --cc --exe --build -LDFLAGS -lelf src/core.v sim/core.cpp sim/memory.cpp sim/simulator.cpp
make: *** [makefile:43: build/Vcore] Error 2

Make sense, Thank you

From the error message, I assume that your build of clang does not support the riscv target. (You can check the targets it was build for with llc --version or llvm-config --targets-built)
In any case, if you want to use the Makefile as is, you need both clang and lld with support for riscv32 targets. If you have a gcc toolchain for riscv32 installed, you could also change in the file tests/makefile the variable CC to the gcc binary (something like riscv32-elf-gcc probably) and remove the -fuse-ld=lld option from CFLAGS.

That worked, thank you very much!


Remove duplicate metric

PACKETS_SIZE was the same as BYTES_TOTAL, but only for one direction. This fixes it to always be BYTES_TOTAL for both directions.

Does this fix #605 ?


[YUNIKORN-2675] A Example doc of RayCluster and RayJob management wit…

What is this PR for?
doc for run Ray Cluster and RayJob with Yunikorn
What type of PR is it?

[ ] - Bug Fix
[ ] - Improvement
[ ] - Feature
[x] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2675
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

@MortalHappiness @rueian @kevin85421 KubeRay guys PTAL, thanks

LGTM

LGTM

@mean-world This example relies on YK's admisssion controller to add default queue/applicationId labels. All the RayJob will use the same queue/applicationId value.
If the admission controller is not enabled, the RayJob will be scheduled by default scheduler.
Could we add an explanation for this?
It would be better if we can and a note for the Ray REP @kevin85421 mentioned? (Which add the ability to submit jobs to non-default applicationId)

I will add this part of the explanation

Hi @mean-world
You can apply the new config to the yunikorn config if you wonder how to manage resources when summiting applications.
partitions:
  name: default
  queues:
  - name: root
    queues:
    - name: ray
      resources:
        guaranteed:
          vcore: 2
          memory: 4G
        max:
          vcore: 4
          memory: 8G
      queues:
      - name: jobs
      - name: clusters

pod yaml (Raycluster CRD also use Pod template)
metadata:
  labels:
    applicaionId: ray-cluster-0001
    queue: root.ray.clusters
spec:
  schedulerName: yunikorn # k8s will inform yunikorn based on this

A Yunikorn application including one or multiple pods based on the 'applicationId' label in pod.metadata.labels.
The queue where pods is in is  decided by the queue label in pod.metadata.label.
Yunikorn labels


Support for arm64

Currently, iSpy is full of assumptions that it will be built for 32bit devices.

Completely true.

Any progress on this / iSpy2 ?


Unable to put marker on L.GeoJSON drawed layer

Hello,
I am using Leaflet 0.7.3 with Leaflet.Draw 0.2.4 on Android 4.4+ device. Following example code works fine on desktop web browsers and android Google Chrome browser but in my custom webview application on Android 4.4+ ,putting marker on L.GeoJSON drawed polygon has not been detected touch event by leaflet. But at outside of polygon, everything is OK. Here is my example code:
var campus = {
            "type": "Feature",
            "properties": {
                "popupContent": "This is the Auraria West Campus",
                "style": {
                    weight: 2,
                    color: "#999",
                    opacity: 1,
                    fillColor: "#B0DE5C",
                    fillOpacity: 0.8
                }
            },
            "geometry": {
                "type": "MultiPolygon",
                "coordinates": [
                    [
                        [
                            [-105.00432014465332, 39.74732195489861],
                            [-105.00715255737305, 39.74620006835170],
                            [-105.00921249389647, 39.74468219277038],
                            [-105.01067161560059, 39.74362625960105],
                            [-105.01195907592773, 39.74290029616054],
                            [-105.00989913940431, 39.74078835902781],
                            [-105.00758171081543, 39.74059036160317],
                            [-105.00346183776855, 39.74059036160317],
                            [-105.00097274780272, 39.74059036160317],
                            [-105.00062942504881, 39.74072235994946],
                            [-105.00020027160645, 39.74191033368865],
                            [-105.00071525573731, 39.74276830198601],
                            [-105.00097274780272, 39.74369225589818],
                            [-105.00097274780272, 39.74461619742136],
                            [-105.00123023986816, 39.74534214278395],
                            [-105.00183105468751, 39.74613407445653],
                            [-105.00432014465332, 39.74732195489861]
                        ],[
                            [-105.00361204147337, 39.74354376414072],
                            [-105.00301122665405, 39.74278480127163],
                            [-105.00221729278564, 39.74316428375108],
                            [-105.00283956527711, 39.74390674342741],
                            [-105.00361204147337, 39.74354376414072]
                        ]
                    ],[
                        [
                            [-105.00942707061768, 39.73989736613708],
                            [-105.00942707061768, 39.73910536278566],
                            [-105.00685214996338, 39.73923736397631],
                            [-105.00384807586671, 39.73910536278566],
                            [-105.00174522399902, 39.73903936209552],
                            [-105.00041484832764, 39.73910536278566],
                            [-105.00041484832764, 39.73979836621592],
                            [-105.00535011291504, 39.73986436617916],
                            [-105.00942707061768, 39.73989736613708]
                        ]
                    ]
                ]
            }
        };

        var map = L.map('map').setView([39.74739, -105], 13);
        var drawnItems = new L.FeatureGroup();
        map.addLayer(drawnItems);
        var drawControl = new L.Control.Draw({
            edit: {
                featureGroup: drawnItems,
                edit: false,
                remove: false
            }
        });
        map.addControl(drawControl);

        map.on('draw:created', function(e) {
            drawnItems.addLayer(e.layer);
        });

        L.tileLayer('https://api.tiles.mapbox.com/v4/{id}/{z}/{x}/{y}.png?access_token=pk.eyJ1IjoibWFwYm94IiwiYSI6IjZjNmRjNzk3ZmE2MTcwOTEwMGY0MzU3YjUzOWFmNWZhIn0.Y8bhBaUMqFiPrDRW9hieoQ', {
            maxZoom: 18,
            id: 'mapbox.light'
        }).addTo(map);

        var baseballIcon = L.icon({
            iconUrl: 'baseball-marker.png',
            iconSize: [32, 37],
            iconAnchor: [16, 37],
            popupAnchor: [0, -28]
        });

        L.geoJson([campus], {

            style: function (feature) {
                return feature.properties && feature.properties.style;
            },

            pointToLayer: function (feature, latlng) {
                return L.circleMarker(latlng, {
                    radius: 8,
                    fillColor: "#ff7800",
                    color: "#000",
                    weight: 1,
                    opacity: 1,
                    fillOpacity: 0.8
                });
            }
        }).addTo(map);

    });

@sabandemirci Touch was not well supported in 0.2.4 -<EMAIL_ADDRESS>will become the official 0.3.0 release and should support most touch events. 0.3.0 is scheduled for release tomorrow with patches to follow (It's quite stable, but I expect full-use to show some bugs).


Added status to each article in review list; limited article list to …

Formatting and filtering:

article list only shows those that have been approved
search bar now queries article list
review page only shows those "waiting for review"

👍


Replace bash shell to powershell in docker for windows

Signed-off-by: yuexiao-wang<EMAIL_ADDRESS>Proposed changes
Replace bash shell to powershell in docker for windows

@mstanleyjones PTAL
It has been done. but I didn't modify  the Powershell prompts in engine and machine.

LGTM, thanks @yuexiao-wang , merging


Should MutableObjectTypeAdapter be setting description?

I'm just trying to get my head around this library works, I tried adding a static type defition mapping like so:
$myStaticTypeMapper = new StaticTypeMapper();
$myStaticTypeMapper->setTypes([
	Example::class => new ExampleOutputType(),
]);
$schemaFactory->addTypeMapper($myStaticTypeMapper);

When I run
SchemaPrinter::doPrint($schema);
And I get an error that there is no description set on the MutableObjectTypeAdapter that is wrapping ExampleOutputType.  It appears the printer calls $def->description even though the mutable object type adapter never sets a description.
Guessing i'm trying to use the static type mapper incorrectly, but figured i'd ask, thanks!

I don't see StaticTypeMapper::setTypes.  It's passed through the constructor it seems.  I'm guessing you just wrote pseudo code here.  I haven't used the StaticTypeMapper in an implementation, personally.  I don't think many people are using it - opting instead for actual objects and standard mapping.  That said, I would expect a description to default to null.  Do you have a stacktrace?

Thanks for the response, I see setTypes is only a 6.2 branch concept.  I had initial trouble working off of 7.0 so we downgraded.  Maybe I should have gone back to 7.0/main branch.

Checked on master, and i got the same error (using the constructor).  Again i'm more just trying to learn how custom type mappers work at this point rather than this being an actual issue.  This can be closed if thats best, thanks.
<b>Fatal error</b>: Uncaught Error: Typed property GraphQL\Type\Definition\ObjectType::$description must not be accessed
before initialization in
/vendor/webonyx/graphql-php/src/Utils/SchemaPrinter.php:246
Stack trace:
#0
/vendor/webonyx/graphql-php/src/Utils/SchemaPrinter.php(382):
GraphQL\Utils\SchemaPrinter::printDescription(Array,
Object(TheCodingMachine\GraphQLite\Mappers\Proxys\MutableObjectTypeAdapter))
#1
/vendor/webonyx/graphql-php/src/Utils/SchemaPrinter.php(106):
GraphQL\Utils\SchemaPrinter::printObject(Object(TheCodingMachine\GraphQLite\Mappers\Proxys\MutableObjectTypeAdapter),
Array)
#2

So, that ObjectType::$description is required according to webonyx, the underlying GraphQL lib used by GraphQLite.  It seems we need to at least set this as null, either implicitly or explicitly.


[eCBIS] Editing the Household and family member details

Name of feature to enhance

We would like to add the ability to edit the family and the family member details

Description of feature
Family Edit

[x] Add ad Edit Info Menu on the family profile.
[x] On clicking the Edit Info button, this should open the add family Questionnaire and prepopulate it with the details from the family head patient resource.
[ ] If the family name is updated then the same update should be cascaded to all the other patients linked with the old family name.
[ ] On save, generate a questionnaire response and generate the relevant resources

Family Member Edit

[x] Add ad Edit Info Menu on the family member profile.
[x] On clicking the Edit Info button, this should open the add family member Questionnaire and prepopulate it with the details from the family member patient resource.
[ ] The family name should not be editable.
[ ] On save, generate a questionnaire response and generate the relevant resources

Edit member menu

@dubdabasoduba can we edit ANC Patient as well? and if an ANC patient is a house head then what should be done because if we open Patient Details from ANC client we don't have family information so house head information is unknown and can't decide which form needs to be populated family registration or family member registration.

Update Dec 14th

Failing CI test cases
Failing Engines tests  for  Measure Evaluate  - I think due to the OutOfMemoryIssue reason the MeasureEvaluate test failing


upgrade to phpunit 6

ref: https://github.com/daylerees/scientist/pull/19

Either use import the classes, or \ the root namespace :+1:

actually this is slightly annoying to support all php versions. how about a new major for php 7.x and up @daylerees @rodnaph ?

That would help on https://github.com/daylerees/scientist/pull/20

I'll see if I can find some time later tonight to get these two PRs in, fix up the tests and tag a new version. Thanks chaps. 🤘

Changed target to develop to merge with Rod's changes and then can fix tests for the new version there. (Just in case any nutters are versioned against dev-master)


chore: Cleanup unused or duplicated dependencies where possible

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

LGTM, thanks


Project title

Project title
(Write project title over here)
Project Description
(Describe the project over here)
Stack:
[ ] Html
[ ] CSS
[ ] JavaScript

/assign


Fix coverage setup

Fixes coverage setup according to the common ROM dev-tools API.

Approved in #23 (10211e19058271cd04fd45729de7c2debbafa273)

Approved in #23 (10211e19058271cd04fd45729de7c2debbafa273)


Placement won't work

I have a simple bootstrap template with some divs containing dummy text.
If I set the placement's attribute to anything value the tooltip box appears always on the right side.
Same thing if I set the placement's attribute to 'auto' and smartPlacement to true.
This is my code
`var tour = new Tour({
steps: [
	{
		element:    '#head-1',
		title:      "Step 1",
		content:    "Step 1 content"
	},
	{
		element:    '#par-1',
		title:      "Step 2",
		content:    "Step 2 content"
	},
	{
		element:    '#par-2',
		title:      "Step 3",
		content:    "Step 3 content"
	}
],
placement: 'auto',
smartPlacement: true,
storage: false,
backdrop: true,
backdropPadding: 10

});
`
Where I'm wrong?

To solve the issue replace the following line (bootstrap-tour.js:108) placement: 'right' with placement: this._options.placement

It might be a bit late to answer, but recently I faced same problem. I was able to solve it by passing placement property directly to each step I had like this:
placement: "bottom"

Documentation should explicit that the placement should be inside the step object.


Philio PST02 4 in 1 Sensor

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
YES, BUT a Home Assistant developer has told me to come here
Is your problem within ZWaveJS2MQTT?
YES, BUT a ZWaveJS2MQTT developer has told me to come here
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug? I included PST02A to home assistant running Z-Wave JS driver
What do you observe?
Motion sensor and Door/Window sensor do not work.
Motion sensor detects the first motion and then it remains detected. Also Door/Window sensor does not work at all. but all other sensors are okay.
What did you expect to happen?
All sensors work fine
Steps to reproduce the behavior:

Go to '...'
Click on '...'
Scroll down to '...'
See error

Device information
Manufacturer:  Philio Technology Corp
Model name: PST02A
Node ID in your network: 14
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
node-zwave-js branch:0.1.28
zwavejs2mqtt branch:
Z-Wave JS
Current version: 0.1.28 (Changelog)
Control a ZWave network with Home Assistant Z-Wave JS.
Visit the Z-Wave JS page for more details
Did you change anything?
yes (please describe)
If yes, what did you change?
I tested the device by setting Parameter 7 to 2,6,16,18,22 but nothing happend
Did this work before?
Yes (please describe)
If yes, where did it work?
I read on the net that changing parameter 7 had worked
Attach Driver Logfile
param 7 set to 18.txt
param 7 set to 16.txt
pst02 HA.txt
param 7 set to 6.txt

Sorry I missed this somehow. The logfiles you attached are on on loglevel "debug", so they aren't helpful. Please make a new one, ensure it is on the correct loglevel and trigger the sensors so we can see if and what gets sent.

Motion sensor detects the first motion and then it remains detected.

If the device does not reset the motion status on its own, we need to add a compat flag. I want to verify with the log first though.


Option to extract all HTTP headers

When discovering behavior of a service or API it is useful to examine content of HTTP headers. We extract several headers by default. We also provide a means to extract user defined headers. However, when first examining a service we don't know what headers are used. It would be nice to have an option to temporarily extract all headers to see what's being used and then dial back.
This would affect the appscope source primarily as we move to http1/2 support in LogStream.
This would affect libscope for http1 extraction at the edge.

This may already be in place when payloads are enabled or with the new HTTP support. The full response content is in there too.


What to do if the thread calls SSL_shutdown during the SSL asynchronous encryption process

During the SSL negotiation process, when asynchronous hardware encryption is required, call ASYNC_pause_job to switch back from the coroutine and continue processing other events. At this time, when the TCP connection is disconnected, SSL_shutdown will be called, and ASYNC_start_job will be called to switch back to ASYNC_pause_job. Is it unreasonable in this case?

At this time, when the TCP connection is disconnected, SSL_shutdown will be called, and ASYNC_start_job will be called to switch back to ASYNC_pause_job. Is it unreasonable in this case?

You must not call other IO functions (including SSL_shutdown) on the SSL object while an asynchronous job is running. You must wait until the asynchronous job is complete.


#19851: Proof-of-concept to implement deferred side inputs for combiners

#19851
This is a proof-of-concept draft for fixing/implementing deferred side inputs with Combiners. I could use feedback on how to proceed and then I'll clean it up as well.
Issue:
Currently if you try to use a side input with a combine function, you end up with a traceback during the pipeline translation step:
  File "/Users/jtran/builds/2024-2/build/internal/lib/python3.11/site-packages/apache_beam/runners/portability/fn_api_runner/translations.py", line 1367, in lift_combiners
    expansion = lifted_stages if can_lift(transform) else unlifted_stages
                                 ^^^^^^^^^^^^^^^^^^^
  File "/Users/jtran/builds/2024-2/build/internal/lib/python3.11/site-packages/apache_beam/runners/portability/fn_api_runner/translations.py", line 1239, in can_lift
    context.components.pcollections[only_element(
                                    ^^^^^^^^^^^^^
  File "/Users/jtran/builds/2024-2/build/internal/lib/python3.11/site-packages/apache_beam/runners/portability/fn_api_runner/translations.py", line 2082, in only_element
    element, = iterable
    ^^^^^^^^
ValueError: too many values to unpack (expected 1)

Fix?:
The issue is because in the code where we determine whether or not to lift a combiner, we assume the combiner has a single input pcoll, which is not true when the combiner has a deferred side input.
I went through fixing this and then realized that we also don't have plumbing for deferred side inputs implemented at the operations.py layer either. It seemed like a lot of work to duplicate all the side input plumbing that ParDo has when the phases of the combiners can be expressed as ParDos anyways.
Inside of direct/helper_transforms.py we actually already define a ParDo-based version of a lifted combiner. I tried adding an override to use it only if we have a combiner with side inputs but at that point we've already substituted away the side input for a ArgumentPlaceholders. I instead updated it and returned it in CombinePerKey.__new__. I couldn't put it in CombinePerKey.expand since CombinePerKey has the special urn that would've resulted in the subtransforms getting ignored

reviewer: @robertwb


Update partner-twilio-python-how-to-use-voice-sms

Replace PHP samples and links with Python ones.
Replace old URLs with theirs newer counterparts.

Hi @smendes, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@smendes : Thanks for your contribution to the Azure documentation! The author, @devinrader, has been notified to review your proposed change.

#sign-off


status: resources stuck in "not reconciled"

2021-01-21T20:00:18.944756Z     error   status  Encountered unexpected error updating status for networking.istio.io/v1alpha3/virtualservices/default/reviews1124/1, will try again later: Operation cannot be fulfilled on virtualservices.networking.istio.io "reviews1124": the object has been modified; please apply your changes to the latest version and try again
2021-01-21T20:00:18.947161Z     error   status  Failed to update VirtualService/default/reviews1195 in ledger, status will be out of date.

Log show a bunch of stuff like ^
Resource shows it never reconciles fully.
Resource:
status:
  conditions:
  - lastProbeTime: "2021-01-21T20:08:19.284066026Z"
    lastTransitionTime: "2021-01-21T20:08:19.284066328Z"
    message: 2412/2424 proxies up to date.
    status: "False"
    type: Reconciled
  observedGeneration: "1"

I am 100% certain this is actually fully distributed, as this is being sent to 0 proxies.

not stale
On Wed, Apr 21, 2021 at 10:05 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2021-01-21.
It will be closed on 2021-05-06 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/30284#issuecomment-824540994, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXOPP366RH3JZK3QPZDTJ6VCRANCNFSM4WNOCUDA
.

Are there any more insights on this? I am currently seeing this Istio 1.10.2

not stale


Clonning big repostories ends in error

trying to clone big repositories (with lots of history)
I get the following error.
Currently I see no way to recover as the pull will not work and clone will complain that the repository is not empty.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
I propose to introduce an option where the clone will continue where it left off as the system currently tracks the changesets.
Also I am looking for any work around that will not require to delete the local repository and start over :)

We are trying to clean up old/stale issues. As this issue hasn't seen any updates (or progress with pull requests) in quite a while, the issue will be closed. In case further information is provided, we can revisit that and reopen the issue.


Improve Elixir syntax highlight for modules and atoms

Related to: https://github.com/arcticicestudio/nord-visual-studio-code/issues/165
Before it was like this:

After this change:

Hi @feliperenan :wave:, thanks for your contribution :+1:
I'll review it in the near future and get back to you.

Thanks for your patience @feliperenan, I think that the “near future“ is no longer an appropriate term, but unfortunately the maintenance and organization (overhead) tasks of the whole Nord project go to the cost of individual issues and PRs that are missed in the large amount of notifications.
Anyway, I tried to reproduce the highlighting, but it looks like that Vim is not shipped with Elixir syntax highlighting by default. At least I get not highlighting at all with the recent version 9.0.0200 and there is no syntax highlighting group detected when specifying and token like the defmodule keyword. Did you use a (third-party) plugin and added the groups accordingly, and if so, was it elixir-editors/vim-elixir?
When Vim does not bundle Elixir syntax highlighting by default any longer we can add support for the mentioned plugin of course.

Hi @svengreb
yes, I was vim-elixir plugin for back when I did this patch. Now I don't anymore - I'm using treesiter from neovim and not sure how that plays along. Also, I'm not using this theme anymore so not sure if this fixes is still relevant.
With that being said, feel free to either close or accept this patch.
Thanks

@feliperenan Thank (again!) you for your patience! 🙏🏼
It‘s been a while since I had free time to focus more on Nord, and my open source projects in general, and invest time in this issue due to work-life balance.
I recently published the first “Northern Post — The state and roadmap of Nord“ announcement which includes all details about the plans and future of the Nord project, including the goal of catching up with the backlog. This issue is part of the backlog and therefore I want to triage and process it to get one step closer to a “clean state“. Read the announcement about reaching the “clean“ contribution triage state in Nord‘s discussions for more details about the goal.
Therefore it has been added to the queue in the central and single-source-of-truth project board that is also described in more detail in the roadmap announcement.

@feliperenan Thanks again for your contribution 🚀
The pull request has been added to the queue and the review will be planned for the next iterations!
Adding support for Neovim will be handled through a dedicated Nord port to tree-sitter will be supported too as soon as this port is available. Of course this "Vanilla" Vim port will be continued and support for the vim-elixir plugin will be started with this pull request.


GroundSubstation

No longer shows visual of object in game and when trying to place a new one the following error screen pops up...

Unfortunately Unity project files for Ground Substation were lost, so I'm unable to update or maintain the mod.


View issues when checkout_date > start_date

This is a slight consequence of #1389 (although it would also be problematic if an admin currently edited a reservation start date after checkout or we gave patrons a grace period following the start date to check out equipment). If you view the reservation page when the checkout date is later than the start date, the progress bar on top still starts on the start date. This would be further complicated in cases where the checkout date was later than the due date, but I'm not sure how we'd best visually represent that case. We might want to resolve this by adding additional validations to prevent such cases from happening, so this issue will be the place for that discussion.

Moving to wishlist after discussion w/Oren. Maybe put in larger progress bar overhaul.


apt update fails in arm32v7/httpd:2.4.33 image

After runnnig apt-get update I got the follwoing error:
W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease  Unable to find expected entry 'main/binary-armhf/Packages' in Release file (Wrong sources.list entry or malformed file)

W: Failed to fetch http://deb.debian.org/debian/dists/jessie-backports/main/binary-armhf/Packages  404  Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.

Some of the repos are not maintained anymore.
But we can bypass the problem by returning true if this happens.

I've tried debian:jessie-20190326 in the playground and it just never try to access the URLs you've posted.

Make sure you are not MITM-ed and you have the latest debian:8 image.

debian:jessie-20190326 is OK, but arm32v7/httpd:2.4.33 which is used to build webui image from, is failing in sandbox.
I've ran following commands:
docker run -it arm32v7/httpd:2.4.33 bash
apt update

And here is the output:

Sorry I didn't notice that it is using the seperate stage build (or whatever it is callled).
I think it better to switch to the latest version of httpd image like 2.4.39, since it should contain some fixes.
For example, until httpd:2.4.37, apt-get --version shows the version of apt is 1.4.8, which should be vulnerable to CVE-2019-3462.

Sorry for the delay.
I've checked: httpd:2.4.39 works ok.
I've changed my PR.

Good job!
@anthonyraymond @ziahamza I have finished my review (though I forgot to start it as a review :P ).


Build failure: enumeration value ‘kFP8’ not handled in switch [-Werror=switch]

Click to expand!
Issue Type
Build/Install
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
Latest master branch (3.17), tf-nightly 2.13
Custom Code
No
OS Platform and Distribution
Linux Ubuntu 22.04
Mobile device
No response
Python version
3.10.9
Bazel version
5.3.0
GCC/Compiler version
11
CUDA/cuDNN version
CUDA12.1 cuDNN8.8.1 TensorRT8.6.0
GPU model and memory
RTX 3070 8G
Current Behaviour?
Cannot build with bazel

ERROR: /tmp/tensorflow/tensorflow/compiler/tf2tensorrt/BUILD:188:11: Compiling tensorflow/compiler/tf2tensorrt/common/utils.cc failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command external/local_config_cuda/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -MD -MF bazel-out/k8-opt/bin/tensorflow/compiler/tf2tensorrt/_objs/common_utils/utils.pic.d ... (remaining 176 arguments skipped)
tensorflow/compiler/tf2tensorrt/common/utils.cc: In function ‘std::ostream& nvinfer1::operator<<(std::ostream&, const nvinfer1::DataType&)’:
tensorflow/compiler/tf2tensorrt/common/utils.cc:209:10: error: enumeration value ‘kFP8’ not handled in switch [-Werror=switch]
  209 |   switch (v) {
      |          ^
cc1plus: some warnings being treated as errors
Target //tensorflow/tools/pip_package:build_pip_package failed to build

Standalone code to reproduce the issue
bazel build --config=cuda --cxxopt="-march=native" --cxxopt="-O3" //tensorflow/tools/pip_package:build_pip_package

Relevant log output
/tmp/tensorflow/tensorflow/compiler/tf2tensorrt/BUILD:188:11: Compiling tensorflow/compiler/tf2tensorrt/common/utils.cc failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command external/local_config_cuda/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -MD -MF bazel-out/k8-opt/bin/tensorflow/compiler/tf2tensorrt/_objs/common_utils/utils.pic.d ... (remaining 176 arguments skipped)
tensorflow/compiler/tf2tensorrt/common/utils.cc: In function ‘std::ostream& nvinfer1::operator<<(std::ostream&, const nvinfer1::DataType&)’:
tensorflow/compiler/tf2tensorrt/common/utils.cc:209:10: error: enumeration value ‘kFP8’ not handled in switch [-Werror=switch]
  209 |   switch (v) {
      |          ^
cc1plus: some warnings being treated as errors
Target //tensorflow/tools/pip_package:build_pip_package failed to build

I got the same problem while compiling v2.12.0-rc1.
I find new DataType kFP8 added between 8.5.3 and 8.6.0 of TensorRT. (API Reference: 8.5.3, 8.6.0) And, in the case block, enumeration value ‘kFP8’ hasn't handled in switch yet.
https://github.com/tensorflow/tensorflow/blob/v2.12.0-rc1/tensorflow/compiler/tf2tensorrt/convert/weights.cc#L61-L76
I think this problem will be fixed by adding a case for kFP8 with IS_TRT_VERSION_GE macro. According to API Reference, kFP8 is not supported yet and maybe some codes to generate assert error should be inserted.

@linuxmetel ,
Thanks for the PR. Our Team will review and get back to you if any more details needed. Thanks!


Fix autocomplete parameters in demo app

Also fixes the main package's version in package-lock.json.
Signed-off-by: Julius Volz<EMAIL_ADDRESS>

Lol I did the same fix at the same time in #10.
Thanks for the fix 👍
I should put a CI check to verify that the app is working


Change System Columns "Not Allowed" Message Back

Change it back to "Automatically generated" because that's the more appropriate term. This is happening because users don't have "insert" access to those columns.

Why is "Not Allowed" appropriate for the columns that they can't insert?

This is what we decided to change it to. If user doesn't have "insert" access we're saying "Not Allowed" for the column.
Now the issue is that for system columns the "insert" access is missing too. So even for those columns we're saying "Not Allowed" which as we discussed "Automatically generated" would be more appropriate.

should we then handle the system-columns explicitly then?

From: Aref Shafaei<EMAIL_ADDRESS>Sent: Friday, August 24, 2018 11:01 AM
To: informatics-isi-edu/ermrestjs
Cc: Hongsuda Tangmunarunkit; Comment
Subject: Re: [informatics-isi-edu/ermrestjs] Change System Columns "Not Allowed" Message Back (#689)
This is what we decidedhttps://github.com/informatics-isi-edu/chaise/issues/1609 to change it to. If user doesn't have "insert" access we're saying "Not Allowed" for the column.
Now the issue is that for system columns the "insert" access is missing too. So even for those columns we're saying "Not Allowed" which as we discussed "Automatically generated" would be more appropriate.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/informatics-isi-edu/ermrestjs/issues/689#issuecomment-415836329, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAZUDICXwgbdB_4DZw67VpYd4a-KIFmmks5uUD9tgaJpZM4V-_4w.

Yes, and it should be very simple.


Understanding 'dynamicButtonTextSuffix'

By default the button says '6 Checked'
I assumed setting dynamicButtonTextSuffix would let me do this:
dynamicButtonTextSuffix: 'Columns'
Resulting in a button that says '6 Checked Columns'
Is this not what the this property does ?   If not, is there any way to override the 'Checked' text in the settings ?   I didn't see it in the docs
Thanks!!!

I'm using this:
vm.columnSelectionSettings = {
scrollableHeight: '250px',
scrollable: true,
dynamicTitle: false,
buttonDefaultText: 'Columns'
};
and it's still showing 'Select'

Nevermind, I see there is another object to pass in for text settings


changed xlf to xliff and added de & en translation

i added messages.en.yml to switch to translateable keys in a further PR

agreed, I am merging this and releasing a major version

thank you, if not already done, i will switch to translation keys shortly, and we can then create a major release


NPEP-122 Tenancy API: Add Tenancy API design suggestions.

Tracking issue https://github.com/kubernetes-sigs/network-policy-api/issues/122

Since this NPEP is now "implementable" let's make sure Sig-Network API approvers have a look as well.
/assign @thockin @khenidak

Going back to what I was saying above about "cluster default policy", what about:

I find the fact that this struct introduces invisible priorities the most confusing part, because every ClusterDefaultPolicyRules Action is applied somewhere between ANP, NP and BANP (and priority is implied by action type) but also it has "which was not matched by a previous rule" semantics, which is even more confusing. (but may we can make it somehow more explicit)

"I don't care about the traffic within tenants, but I want to make sure traffic is denied to/from everywhere else (including N/S)" is

name: default
spec:
    tenancyLabels:
        - "user"
    ingress:
        withinTenant: DefaultAllow
        default: DefaultDeny
    egress:
        withinTenant: DefaultAllow
        default: DefaultDeny```

Don't we need `Deny` instead of `DefaultDeny` here? I thought this use case wants strict isolation for N/S

I also didn't quite get the usage/meaning of `UserNamespaces` since there were no examples.

@danwinship @astoycos @Dyanngg I tried to sum up provided comments/ideas in a new section called "Another approach". Please take another look and let me know what you think

I find the fact that this struct introduces invisible priorities the most confusing part, because every ClusterDefaultPolicyRules Action is applied somewhere between ANP, NP and BANP (and priority is implied by action type) but also it has "which was not matched by a previous rule" semantics, which is even more confusing. (but may we can make it somehow more explicit)

Huge +1 here. If we are going to introduce new CRD types here (which seems like we are), interoperation between tenancy related objects and AdminNetworkPolicy objects are key here. Any tenancy rules should have a clear and explicit priority so that when there are ANPs on top of these tenancy rules, which would take effect.

Additionally I am still not on board with creating a new NetworkTenancy object..... (And I think generally most of the others are of the same opinion)

+1 to this from my side

I am still not on board with creating a new NetworkTenancy object..... (And I think generally most of the others are of the same opinion)

I agree we should not have tenant-specific objects that mirror a large percentage of the functionality of ANP/BANP. But having an object to just define what tenancy means, which would then be referenced by ANPs/BANPs, would make sense. (Individual ANPs don't define which pods are in which namespaces themselves. Why should they define which namespaces are in which tenants themselves?) Or alternatively, having an object with a very restricted set of tenant policy-setting functionality could make sense.

At the base of this we need an easy way to apply rules to a set of namespaces with the ability to change priority of those rules.

Our user stories do not require the ability to set arbitrary priorities on tenancy-related rules.

ANP + BANP already provide this, if the existing semantics of the API don't work let's add a new subject type AND/OR new peer types if needed.

We already tried putting tenancy into the subject/peer framework, and we didn't like how it came out. Any tenancy system that does not involve any new object types seems like it is going to end up being basically equivalent to what we had in the original API with SameLabels/NotSameLabels. It will be a weird peer type that doesn't behave like any of the other peer types, and it will have the problem that different policies can have different definitions of tenancy, even though that makes the implementation more complicated and there are no user stories for that functionality.

and it will have the problem that different policies can have different definitions of tenancy, even though that makes the implementation more complicated and there are no user stories for that functionality.

In particular... this NPEP started when Nadia pointed out that SameLabels/NotSameLabels tend to result in an explosion of "implementation rules" (i.e. OVN ACLs, iptables rules, etc) because you need to turn the tenancy-based ANP rule into a set of namespace-based implementation rules.
But if we say that there is only a single definition of tenancy for the entire cluster, then that makes it much easier to represent tenancy as a concept within the implementation rules, allowing for more-optimized tenancy matches. Instead of changing "subject and peer are in the same tenant" into "subject's namespace is A or B and peer's namespace is A or B; or subject's namespace is C and peer's namespace is C; or ...", you can just represent it as "subject's tenant == peer's tenant".
To give two examples pertaining to non-existent ANP implementations ( :smile: )

In openshift-sdn, k8s Namespaces all have numeric IDs associated with them, and for pod-to-pod traffic, the namespace ID of the source pod is kept in reg0 and the ID of the destination pod is in reg1, so that namespaceSelector-based NetworkPolicies can be implemented by OVS flows that just check reg0 and reg1 rather than needing to be based on pod IPs. The same approach could be used with "tenant IDs". (In fact, the "namespace IDs" originally were "tenant IDs", in openshift-sdn's "multi-tenant" mode.)
In an nftables-based implementation, if there was only a single definition of tenancy, we could just create a set containing pairs of pod IP addresses for all such pairs of IPs that are in the same tenant. Then a tenancy-matching peer just turns into a single lookup of { ip saddr . ip daddr } in the tenancy set.

(OK, so actually the nftables example could be done even with "every policy creates its own definition of tenancy", by just creating a separate set for each SameLabels/NotSameLabels expression. But you might be less inclined to implement it that way, because those sets would be big. The openshift-sdn example really requires a single cluster-wide definition of tenancy though, since there are only so many registers, so you can't represent "this pod is part of tenant 12 with respect to ANP X, and part of tenant 378 with respect to ANP Y, and ...")

Let me try to address the main point here: using (B)ANP rules for tenancy.
Current (B)ANP semantics is: subject selects pod to which all ingress and egress rules are applied.
Tenancy can't be used in this semantics, because it has its own "subject" defined by the tenancy labels.
It doesn't make a lot of sense to allow something like
apiVersion: policy.networking.k8s.io/v1alpha1
kind: AdminNetworkPolicy
spec:
  priority: 10
  subject:
    namespaces:
      matchLabels:
        kubernetes.io/metadata.name: sensitive-ns
  ingress:
    - action: Deny
      from:
      - namespaces:
         namespaceSelector: {}
   - action: Allow
     tenantLabels: ["user"]

because tenancy doesn't have anything to do with the given subject, it just tries to be injected into existing priority system.
Therefore, we can only use tenancy in (B)ANP at the same level as subject.
kind: AdminNetworkPolicy
spec:
  priority: 10
  # EITHER
  subject: <...>
  ingress: <...>
  egress: <...>
  # OR
  tenant:
# example contents of tenant, the format is not defined yet
    tenancyLabels:
      - "user"
    ingress: Allow
    egress: Allow

This brings a questions about what is the priority between tenancy and ingress/egress. We can either define it (say tenancy is always a higher prio) or only allow setting one part (see EITHER OR). I prefer the first option, but it will require re-prioritization from the existing implementations (since we need to reserve 1 extra priority before ingress and egress rules that wasn't needed before)
If you have other API options that make sense, please let me know, because ^ is the best I can do without adding a new object.

I'd personally vote for External tenant definition, arbitrary rules in ANPs/BANPs as I don't feel like tenancy definition should be overloaded with priority.
On top of that, I think the above proposal still does not solve the original issue we had with sameLabels: the namespaces selected in the subject field can 1. falls exactly into tenancy definition as all of them have the tenancy label(s) 2. intersect with the tenancy definition but not all of them have the tenancy label(s) 3. disjoint from the tenancy definition. We had a hard time agreeing on what we should do to policy subjects when they don't have the tenancy labels (either no-op for these specific namespaces or group these into a "default" tenant, but none of solutions were explicit and ideal).
If we are open to tenant definition as separate object, I will propose something like:
kind: TenantDefinition
metadata:
  name: by-user
spec:
  labels: ["user"]

apiVersion: policy.networking.k8s.io/v1alpha1
kind: AdminNetworkPolicy
spec:
  priority: 10
  subject:
     tenantNamespaces: by-user  # select namespaces by the label list in the by-user tenant definition
  ingress:
    - action: Allow
      from:
      - tenant: Same  # 'same' and 'notSame' is well-defined here as subjects must have all the label keys
    - action: Deny
      from:
      - namespaces:
         namespaceSelector: {}

In this case, the only thing we would need to document is how subject: tenantNamespaces work, which should be pretty straightforward to explain.

@danwinship If you look at my proposal, it is actually trying to add a new field in the AdminNetworkPolicy subject, so that there is no chance that namespaces who aren't part of any tenant is selected in tenancy-rule based ANPs. Also Tenancy definitions do not have to be singleton IMO

I think we agreed some time ago that we want to simplify tenancy subject selection as much as possible, which ended up unifying tenancy labels with subject selector (because we didn't have other use cases), so we wanted to avoid "pods in sensitive namespaces allow ingress from pods in their tenant, but not from pods in other tenants".
We could have something like
apiVersion: policy.networking.k8s.io/v1alpha1
kind: AdminNetworkPolicy
spec:
  priority: 10
  tenancySubject:
     labels: ["user"]
  ingress:
    - action: Allow
      from:
      - tenant: Same  # 'same' and 'notSame' is well-defined here as subjects must have all the label keys
    - action: Deny
      from:
      - namespaces:
         namespaceSelector: {}

and either make tenancySubject and subject mutually exclusive, and only allow tenancy gress rules with the former, or allow both at the same time and say that tenancy rules have their own subject. Second option is closer to @danwinship suggestion, but more clear because tenancy has its own subject without extra selectors, and the first one is closer to @Dyanngg option.
Any option has this either/or switch to turn tenancy mode on, which is a bit ugly, but may be worth it to avoid extra CRDs.
It could also be
kind: AdminNetworkPolicy
spec:
  subject:
# EITHER
     tenantNamespaces:
         labels: ["user"]
# Enables sameTenant rules
# OR
    podSelector/namespaceSelector:

I am pretty sure if we don't want tenancy to have its own priority, then we can avoid creating an extra CRD at all

I'd personally vote for External tenant definition, arbitrary rules in ANPs/BANPs as I don't feel like tenancy definition should be overloaded with priority.

I'm fairly aligned with @Dyanngg and @danwinship  here but, I also don't hate what @npinaeva Just presented, as per usual the smaller API change should be "easier" to get done, I think as long as we can express.
Additionally as it pertains to the "pods not explicitly in a tenant suggestions" that @danwinship presented above I'd lean towards

Some namespaces aren't part of any tenant, but for tenancy rule purposes, all such namespaces form a tenant with each other (the "nil"/"default" tenant)

IMO one of the main use cases that will be used/desired will be, "Lets build a tenant and stop it from communicating with ALL other non-same tenants/pods" and I think this option would be the easiest to parse/ understand for users wanting to build tenants.
So I would like
apiVersion: policy.networking.k8s.io/v1alpha1
kind: AdminNetworkPolicy
spec:
  priority: 10
  subject:
     tenantNamespaces: by-user  # select namespaces by the label list in the by-user tenant definition
                               # in this case, this is equivalent to {namespaces where label "user" exists}
  ingress:
    - action: Allow
      from:
      - tenant: Same  # 'same' and 'notSame' is well-defined here as subjects must have all the label keys
    - action: Deny
      from:
      - namespaces:
         namespaceSelector: {}

To mean the same as
apiVersion: policy.networking.k8s.io/v1alpha1
kind: AdminNetworkPolicy
spec:
  priority: 10
  subject:
     tenantNamespaces: by-user  # select namespaces by the label list in the by-user tenant definition
                               # in this case, this is equivalent to {namespaces where label "user" exists}
  ingress:
    - action: Allow
      from:
      - tenant: Same  # 'same' and 'notSame' is well-defined here as subjects must have all the label keys
    - action: Deny
      from:
      - tenant: NotSame

Otherwise I don't want to muddle up the conversation as I feel like you've all presented really great opinions and points and I think we're close/ headed in the right direction :) It seems like we're centering in on something like Dan's

A single external tenant definition, arbitrary rules in ANPs/BANPs:

Can we try and decide on a way forward before Friday? I'd love to start working on an actual implementation PR

Any option has this either/or switch to turn tenancy mode on, which is a bit ugly, but may be worth it to avoid extra CRDs.

 A single external tenant definition, arbitrary rules in ANPs/BANPs: ^^https://github.com/kubernetes-sigs/network-policy-api/pull/178#issuecomment-1930447439
Why do we need to "inject a new priority"?  Wouldn't priority just be governed by the ANP which references the TenantDefinition?

@npinaeva If we go with @danwinship's
1. A single external tenant definition, arbitrary rules in ANPs/BANPs: ^^#178 (comment)
Why do we need to "inject a new priority"? Wouldn't priority just be governed by the ANP which references the TenantDefinition?

We discussed the disadvantages of this approach in the following comments, reflected here https://github.com/kubernetes-sigs/network-policy-api/pull/178/files#diff-4bfb2f198b356812cfea399edc57d4232a6ec7cefcdc221b2fb8531a03360d87R284-R285.
It is almost the same as what we have right now, and has the same problems we are trying to solve here.

OK thanks for clarifying @npinaeva  :)

Latest update based on the feedback from the SIG meeting on Feb 13.
Pros ans cons for every priority option are updated, check Final suggestion to discuss fields of the final CRD version.

OK, Nadia and I met to talk about this.
I don't really the current "Final suggestion" as proposed, because it makes the common cases complicated because you need both a Tenancy object and a separate ANP or BANP. But as Nadia points out, my version of the proposal doesn't implement all of the user stories we previously agreed upon. But if we do actually agree on all of those user stories, then the API I had proposed wasn't a good API and we should do it differently. :slightly_frowning_face:
Part of the problem is that the existing user stories aren't entirely clear (eg, there were several places where they talk about "allowing" traffic, which I interpreted as "don't interfere with", but in Nadia's examples she interpreted as "action: Allow"). And, eg, Nadia's example for 4.3 used an ANP-level Allow rule, which seemed bizarre to me, but it makes a lot more sense if it was supposed to be BANP-level (which is a use case that Nadia brought up several times in our call: basically, "I want default-deny for everything except within-tenant traffic"). (But even with that interpretation it's still not implementable with my proposed API.)
So maybe we need to revisit the user stories again, at least to clarify the wording. It might also help to explicitly indicate the expected results for every interesting pair of pods in each case:

a pod connecting to a pod in the same namespace in the same tenant
a pod connecting to a pod in a different namespace in the same tenant
a pod connecting to a pod in a different tenant
a pod connecting to a pod in the same namespace, which is not in a tenant
a pod connecting to a pod in a different namespace, neither of which is a tenant
a pod in a tenant connecting to a pod in a non-tenant namespace
a pod in a non-tenant namespace connecting to a pod in a tenant
a pod in a tenant connecting to a cluster-external IP
a pod in a non-tenant namespace connecting to a cluster-external IP

In particular, I feel (though Nadia does not) that some of the user stories lead to "bad" results that probably aren't what any administrator would actually want. (eg, "I want default-deny for everything except within-tenant traffic" means that pod to pod in a tenant namespace is allowed by default, but pod to pod in a non-tenant namespace is denied by default. Nadia says they would just have to create NPs in the non-tenant namespaces in that case, but again, to me that seems like a failure of API design on our part; we should have figured out some way to give them the behavior they wanted in both tenanted and non-tenanted namespaces all at once...)
Anyway, I'm on PTO next week so feel free to merge anything you want while I'm not around to object. :slightly_smiling_face:

we should have figured out some way to give them the behavior they wanted in both tenanted and non-tenanted namespaces all at once...
This can be done by assigning every namespace that is not a part of a tenant a unique tenancy label, so making it a one-namespace-tenant. Potentially always-allow-same-namespace policy could be expressed as tenancy with kubernetes.io/metadata.name tenancy label, but if it needs to be combined with another tenancy... well we need 2 tenancies then (and they would need to be allow-based not deny-based)

/remove-lifecycle rotten


compat level ordering in new database dialog is almost backwards

suggest we order these descending, not whatever order this is

Dupe of #23649 (sorry just a bit too slow, @dzsquared 😄)


Support in Trogon

Recently I discovered Trogon (https://github.com/Textualize/trogon) which seems pretty incredible (look at their video demo, this is some great stuff). In short, it turns a well-defined CLI app into a discoverable TUI which shows you all the options, defaults, types etc, lets you choose from available choices etc.
Especially useful for large apps, less so for trivial ones. Still, I think it kind of shows why standardizing your argument parsing etc makes sense, and I am fully on board with cyclopts' ambition to do that using plain Python.
Trogon wraps around click, yet there is some success people have reported with Typer, and an ongoing effort towards enabling mainline support + docs. Trogon+Typer does not fully work for me yet (it crashes unexpectedly when trying to execute the resulting command), and I suspect this has to do with some minor differences between vanilla Click and Typer. In my disenchantment with Typer recently and having decided I was switching over to Cyclopts, I will most likely not get involved there.
But Trogon remains a cool tool and there are efforts to make it work with other stuff including e.g. argparse - BTW this is from the author of https://www.fresh2.dev/r/yapx/ which builds on top of Argparse and seems like a good tool to make a comparison against. That effort in Trogon has stalled a bit, and the yapx developer seems to have forked Trogon to provide TUI support for his argparse-based lib, but I'd potentially be happy to help resurrect the effort to make Trogon more generic and support adding Cyclopts.
As far as comparisons are concerned, besides yapx, it might also make sense to look at clize, but I digress...
I guess the main purpose of the issue is to ask you, do you think having support for Cyclopts in Trogon would be useful? I wouldn't want to push for it if you a) found this to be useless and/or b) thought it was fundamentally impossible to do due to the way Cyclopts is implemented as compared to Click/argparse (which I doubt). It most likely won't really require any changes to Cyclopts itself.
And a bit of nostalgia, the first time when I realized how awesome building CLIs in Python can be some years ago was while reading the plac docs for advanced usage and all the nifty tricks described there. I was going to ask what your thoughts were on adding an interactive prompt (which I think is the niftiest of the nifty tricks)... until I found you'd already added it. Awesome!

I hadn't seen Trogon before, it looks very nice! I would love for Cyclopts to be compatible (it would actually help out one of my other projects, gnwmanager)! I think I'd want the following before investigating further:

Get v2 in a state i'm happy with and let Cyclopts mature a little bit.
Let trogon mature a little bit; if they support argparse, then I'd be much more optimistic it could also easily support Cyclopts since there would be an established API to hook into.

Oh man, awesome, have you seen Renode (https://github.com/renode/renode)? I didn't know you were even working on embedded stuff. STM32 is supported pretty well - take a look at the Zephyr Dashboard and scroll to the STMs. There are some interactive test results previews and Google Colabs even :)
As for trogon, yeah, I think for it to mature we'd have to give it a little push, since it seems like it's not a core project for @Textualize. I guess we'd need to prod the yapx dev to see whether they want to contribute their changes back to Trogon or should we consider theirs a hard fork. I think they did want to contribute, but reactions were slow, so they opted for forking.
Anyway will need to investigate more.

minor update: I overhauled data-resolution in v2. Previously each section would derive (and fallback) data in adhoc manner. It's all centralized now. This would make a potential integration with trogon much easier now.


Could not Share with other apps like GMail in Android 11

We could not share the pdf with other apps. As the pdf is stored in the app specific storage and Android 11 restrict this access.
https://developer.android.com/about/versions/11/privacy/storage

Have you tested your app on android 10, are you sure you have implemented a FileProvider Authority in you app.
I have to tested this library in Android 11, but one of our production app is not facing any such issue.

Yes, I have tested in Android 10 and I did not face any issue there. It occurs only in Android 11. Yes, I have implemented Fileprovider authority.

Ok, will look into this.

Will look into this.

It works with File provider when using FileProvider.getUriForFile.
Previous i used only getUriForFile directly.

We could not share the pdf with other apps. As the pdf is stored in the app specific storage and Android 11 restrict this access.
https://developer.android.com/about/versions/11/privacy/storage

I also also used the library on Android as well as the app on Android 11 but it couldn't attach the file.
A fix was passing the Uri to the intent instead of the absolute path.
https://github.com/tejpratap46/PDFCreatorAndroid/pull/34


is it possible to use custom methods inside views in Render()?

as title.

The view is simply a PHP script with template variables injected into them. You can run whatever PHP code you want in it.


[Fix #9799] Fix invalid line splitting by Layout/LineLength for send nodes with heredoc arguments

When a send node has heredoc arguments, the line cannot be split after the heredoc or it will be a syntax error.
Fixes #9799.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!


Timeline to release the code of SpeechGPT-Gen ?

Thanks for your attention. We've made some modification to our model structure and are re-training the updated version. We'll release it next month.


Resolver changes

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2760 into master will increase coverage by 0.49%.
The diff coverage is 46.04%.

@@            Coverage Diff             @@
##           master    #2760      +/-   ##
==========================================
+ Coverage   65.08%   65.58%   +0.49%
==========================================
  Files         198      195       -3
  Lines        9893     9919      +26
  Branches     1996     2045      +49
==========================================
+ Hits         6439     6505      +66
+ Misses       3178     3125      -53
- Partials      276      289      +13

Impacted Files
Coverage Δ

...aphql-transformer-core/src/util/transformConfig.ts
11.26% <ø> (ø)
:arrow_up:

.../graphql-transformer-core/src/util/amplifyUtils.ts
6.18% <ø> (ø)
:arrow_up:

...ackages/graphql-transformer-core/src/util/index.ts
100% <100%> (ø)
:arrow_up:

packages/graphql-transformer-core/src/index.ts
100% <100%> (ø)
:arrow_up:

...aphql-auth-transformer/src/ModelAuthTransformer.ts
89.87% <22.72%> (-1.93%)
:arrow_down:

...graphql-transformer-core/src/TransformerContext.ts
37.24% <30%> (-0.26%)
:arrow_down:

...ges/graphql-transformer-core/src/util/syncUtils.ts
32.5% <32.5%> (ø)

...ages/graphql-dynamodb-transformer/src/resources.ts
68.29% <41.17%> (-19.64%)
:arrow_down:

packages/graphql-mapping-template/src/dynamodb.ts
41.33% <44.68%> (-4.83%)
:arrow_down:

...s/graphql-transformer-core/src/GraphQLTransform.ts
30.21% <62.5%> (+0.95%)
:arrow_up:

... and 10 more

Continue to review full report at Codecov.

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


Issue #14012 - Update source.md

Issue with k8s.io/docs/tutorials/services/source-ip/ #14012
Use a a common IP Address either "ExternalIP" Adresss or "InternalIP" Address to get Cluster node IP Addresses

/assign @stewart-yu

/approve

This has been approved by @tengqm .
/lgtm


Make all CFG children BasicBlock, of two subtypes

Discussed in https://github.com/CQCL-DEV/hugr/discussions/155

Originally posted by cqc-alec June 11, 2023
In the current implementation, there are two kinds of BasicBlock: Block and Exit. In the spec, BasicBlock and ExitBlock are distinguished:

All children except the second are BasicBlock-nodes, the first is the entry block. The second child is an ExitBlock node

Which is the more natural approach?

BasicBlock::{DFB, Exit}


Ability to choose the webcam and microphone

Problem
A user can have multiple devices attached. But current implementation does not allow the user to select a camera or microphone.
Solution
Allow the user to choose the mic. and camera devices from dropdown controls which can be initialized by using navigator.mediaDevices.enumerateDevices() on page load.

Sounds great. Let me know if you start working on this, otherwise I can take a stab.

I've started to code and will send a pull request.


Fix woke violations in test files

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Closes #38
What is the current behavior? (You can also link to an open issue here)
Tests use the set of default rules, which mean tests have insensitive language in them.
What is the new behavior (if this is a feature change)?
No longer use the Default ruleset and use a test rule instead for all tests
Does this PR introduce a breaking change? (What changes might users need to make due to this PR?)
No
Other information:

Appreciate your feedback, but I don't see anything in this PR that referenced "race" "condition". If you'd like to include this term in your own projects, feel free to define your own rule in your config file https://github.com/get-woke/woke#rules.


(GH-2363) Deprecate inventoryfile config option

This deprecates the inventoryfile config option, which is slated for
removal in Bolt 3.0.
!deprecation

Deprecate inventoryfile configuration option
(#2363)
The inventoryfile configuration option has been deprecated and will
be removed in Bolt 3.0. Users should move contents from non-default
inventory files to the inventory.yaml file in a Bolt project, or can
use the --inventoryfile command-line option to load a non-default
inventory file.

Ah, that's because we don't currently validate project's with a bolt.yaml. Updated.

Seems to need a rebase.


TypeError: URL is not a constructor

I'm trying to make a simple post request but i'm getting the error
TypeError: URL is not a constructor     at new CentraRequest (CentraRequest.js?0a95:14)     at module.exports (createRequest.js?ca09:4)     at phin (phin.min.js?e014:1)     at _callee$ (VM1328 index.vue:333)     at tryCatch (runtime.js?96cf:45)     at Generator.invoke [as _invoke] (runtime.js?96cf:274)     at Generator.prototype.<computed> [as next] (runtime.js?96cf:97)     at asyncGeneratorStep (asyncToGenerator.js?1da1:3)     at _next (asyncToGenerator.js?1da1:25)     at eval (asyncToGenerator.js?1da1:32)
Here's my code:
await p({           url: "example.com",           method: "POST",           data: { test: 'hello'           }         });
Does anybody know how to fix this?

The issue is probably that your URL is not correctly formatted! Be sure to append an “https:” or “http:” scheme to the start of the address.

i changed 'example.com' to 'http://example.com' but i'm still getting the same error

Hmm, ok. Which Node version are you using?

i'm using v12.16.2

I have the same issue.
NPM version 6.14.5

Running into the same issues here. I am using phin 3.5.0, node 14.5.0 and npm 6.14.5 in a React project (react 16.13.1).

I just realized that phin is not meant for frontend usage, which explains the URL error.

@maxall41 it looks like you're trying to use this with Vue. It is a Node package that uses native Node modules. You could try using Browserify but you may run into this issue https://github.com/ethanent/centra/issues/6


[fonts] they don't show up on the system fonts

Probably something to do with fontconfig? Gotta figure it out eventually

Workaround in 1f8f8fa


The Flashing Bandits

Hope is all fine now for listing Flashing Bandits

Hello guy, Your upload format is not supported. You can refer to the readme file at the link  below for guidance. Please make a modification, thanks!

README


[SC] Experimental! An approach to nesting mappings and lists

Hey @rowandh @fassadlr,
Would be great if you could take a look at this. I've left all of the existing mapping and list implementations there, and just added a couple of methods and classes to demonstrate a way of nesting. If this is looking appealing for us I'll clean this up and make it into a formal PR next week.
The idea:
When getting an object from a mapping or list, if it is a primitive or struct, then we check in persistent state at ${this.name}[{key}]. If the object we are getting is a mapping or list (i.e. nested), then we return a new mapping/list, which has the name= ${this.name}[{key}]. Obviously what this means is when we retrieve from this new mapping / list, the persistentstate gets all actually happen from {originalName}[{key1}][{key2}] (e.g. in persistentstate it might go to mates[jordan][0] for a IScMapping<IScList<string>>("mates") !! (See ScMapping and ScList)
As for serialization, if we come up against a mapping or list in serialization, we just store the name to the db, and will load the mapping or list back when deserializing. (See PersistentStateSerializer).
How to review:

Check out ScMapping and ScList, especially the part with the generic identification and construction.
Check out PersistentStateSerializer
Check out the contract: Mappings.cs, and then the tests that run on it, in SmartContractExecutorTests
Excuse the couple of hacks I've put around the place.

Hey, @codingupastorm Jordan, could you please resolve merge conflicts.
Thank you.


Implement build cancelation

fixes #127

This is a bit different than the original https://github.com/mvndaemon/mvnd/pull/195 : the cancellation request is not enforced while the DaemonConnector is connecting. It is rather stored in a temporary outbound queue, waiting for the connection and is send to the daemon only after when the connection is established. Could you please review @gnodet ?

I'd like to keep the ability to cancel the client during the first few seconds while it's trying to connect to a daemon.
I think it currently somewhat works because of https://github.com/mvndaemon/mvnd/issues/193, so I think the daemon is killed very early when hitting Ctrl+C.
Also, it seems the client is waiting for the daemon to process the cancellation request cleanly.  I don't think this is a desirable behaviour.  It can slow the response on the client side a few seconds.  The client should send the cancel message and exit early.

I'd like to keep the ability to cancel the client during the first few seconds while it's trying to connect to a daemon.
I think it currently somewhat works because of #193, so I think the daemon is killed very early when hitting Ctrl+C.
Also, it seems the client is waiting for the daemon to process the cancellation request cleanly. I don't think this is a desirable behaviour. It can slow the response on the client side a few seconds. The client should send the cancel message and exit early.

I should have a proposal in a few minutes...

@ppalaga see https://github.com/gnodet/mvnd/commit/3a38265fac9bb8ce1695b84f5f3f90c770d4d7db

Thanks, amended with minor changes in c52dfa3


added configuration file support

Let's get this merged b/c some of this code is needed for install-apps!