Link Config Dialog

Create a dialog similar to the lists editor for adding custom 3rd party menu links.

Enabled as of v0.0.7


Update deps

Hello !
I'm trying to use this and had some issue.
Deps has been copy/paste from here
Cheers Monsieur chatgris !
PS: still have errors on configure
** (File.Error) could not write to file .currently.json: bad argument
    (elixir) lib/file.ex:712: File.write!/3
    (elixir) lib/kernel/cli.ex:76: anonymous fn/3 in Kernel.CLI.exec_fun/2

:heart_decoration:


codegen proc_macro for dpdk_test

Codecov Report

Merging #93 into master will decrease coverage by 0.47%.
The diff coverage is 98.29%.

@@            Coverage Diff            @@
##           master     #93      +/-   ##
=========================================
- Coverage   51.57%   51.1%   -0.48%
=========================================
  Files          69      70       +1
  Lines        4304    4340      +36
=========================================
- Hits         2220    2218       -2
- Misses       2084    2122      +38

Impacted Files
Coverage Δ

framework/src/packets/tcp.rs
69.84% <100%> (ø)
:arrow_up:

framework/src/testing/mod.rs
100% <100%> (ø)

framework/src/packets/ip/v4.rs
80% <100%> (ø)
:arrow_up:

framework/src/packets/ip/v6/mod.rs
75.81% <100%> (ø)
:arrow_up:

framework/src/operators/queue_batch.rs
82.6% <100%> (ø)
:arrow_up:

framework/src/packets/raw.rs
50.9% <100%> (ø)
:arrow_up:

framework/src/packets/ethernet.rs
86.01% <100%> (ø)
:arrow_up:

framework/src/packets/buffer.rs
90.6% <100%> (ø)
:arrow_up:

framework/src/packets/udp.rs
86.36% <100%> (ø)
:arrow_up:

framework/src/packets/ip/v6/srh.rs
83.01% <100%> (ø)
:arrow_up:

... and 8 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 02b748a...2a6fd35. Read the comment docs.


[site.Author] is deprecated

Describe the bug
Currently, it isn't a bug, but a warning. In the future, when site.Author is dropped, it can lead to failing builds.
To Reproduce
Just build your project with Hugo version  v0.120.0 or higher, and you will get a warning:
WARN  The author key in site configuration is deprecated. Use params.author.name instead.
Expected behavior
No warning in the console.
Desktop (please complete the following information):

OS: NixOS 23.11
Browser: google-chrome-stable
Version: 120.0.6099.216 (Official Build) (64-bit)

Hugo & Blowfish versions
hugo v0.120.3+extended and blowfish 2.51.0
Additional context
The deprecation notice can be viewed in the release notes of v0.120.0 under Notes

I also get this.

I am not getting this deprecation notice with Hugo 0.121.2. Can one of you share your config files?
I think you configure author per https://blowfish.page/docs/configuration/#author in a languages.en.toml config, not in hugo.toml.

Sorry @arunoruto @Ast3risk-ops I am not getting this warning, can you update to the lastes version and help me understand what needs to change?

Sorry @arunoruto @Ast3risk-ops I am not getting this warning, can you update to the lastes version and help me understand what needs to change?

Yeah I don't get it anymore either.


/Users/sharon/.oh-my-zsh/lib/misc.zsh:4: parse error near `then'

when i update oh-my-zsh, i got /Users/sharon/.oh-my-zsh/lib/misc.zsh:4: parse error near `then'
once i open a new tab.
why?

Same issue. Ubuntu 14.04

for d in $fpath; do
        if [[ -e "$d/url-quote-magic"]]; then
                autoload -U url-quote-magic
                zle -N self-insert url-quote-magic
        fi
done

There should be one space between the " and ]

@mysqto Solved. Thanks!

@mysqto  Solved. Thanks!


Use command "ng g component com1" but generate file is empty

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[X] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Description
When I use ng g component com1 command and then
G:\ProjectData\WebstormProjects\AngularTest>ng g component com1
CREATE src/app/com1/com1.component.html (19 bytes)
CREATE src/app/com1/com1.component.spec.ts (614 bytes)
CREATE src/app/com1/com1.component.ts (267 bytes)
CREATE src/app/com1/com1.component.css (0 bytes)
UPDATE src/app/app.module.ts (472 bytes)

But something went wrong when I open com1.component.ts file.

And file property：

Using other component names does not cause this state
🌍 Your Environment
"@angular/cli": "~9.0.5",

It seems that your environment is not configured properly, as the .ts are trying to be opened by media player instead of an editor. This happens because windows just interprets the .ts extension as MPEG-2 TS.
Changing your Open with setting to open ts files to an editor will fix the problem.

It seems that your environment is not configured properly, as the .ts are trying to be opened by media player instead of an editor. This happens because windows just interprets the .ts extension as MPEG-2 TS.
Changing your Open with setting to open ts files to an editor will fix the problem.

No.I use text editor tool to open it.

You see this file size is 0

It seems that your environment is not configured properly, as the .ts are trying to be opened by media player instead of an editor. This happens because windows just interprets the .ts extension as MPEG-2 TS.
Changing your Open with setting to open ts files to an editor will fix the problem.

Can you please provide the full output of ng version?

Can you please provide the full output of ng version?

G:\ProjectData\WebstormProjects\AngularTest>ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 9.0.5
Node: 12.14.1
OS: win32 x64

Angular: 9.0.5
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.900.5
@angular-devkit/build-angular     0.900.5
@angular-devkit/build-optimizer   0.900.5
@angular-devkit/build-webpack     0.900.5
@angular-devkit/core              9.0.5
@angular-devkit/schematics        9.0.5
@ngtools/webpack                  9.0.5
@schematics/angular               9.0.5
@schematics/update                0.900.5
rxjs                              6.5.4
typescript                        3.7.5
webpack                           4.41.2

Also, taking a look at the video again, in the file explorer it shows that the file is 1kb However, upon checking the properties it states that it's 0 bytes.
Can you kindly share your project on github and link it here? Thanks.

Also, taking a look at the video again, in the file explorer it shows that the file is 1kb However, upon checking the properties it states that it's 0 bytes.
Can you kindly share your project on github and link it here? Thanks.

I can not add generate files to git.
G:\ProjectData\WebstormProjects\AngularTest>git add src/app/com1
warning: could not open directory 'src/app/com1/': No such file or directory

You can see this gif.
Generate files all empty when I create component with name "comxxx"
But generate other name component such as bbb it work（normal）.

Also, taking a look at the video again, in the file explorer it shows that the file is 1kb However, upon checking the properties it states that it's 0 bytes.
Can you kindly share your project on github and link it here? Thanks.

I test ng g command
ng g component com1 --> not work
ng g component com1 --> not work
ng g component com1 --> not work
ng g component com1 --> not work
ng g component com1 --> not work
ng g component com1 --> not work
ng g component com1 --> not work

I test ng g component
ng g component com0 --> it work
ng g component com1 --> not work
ng g component com2 --> not work
ng g component com3 --> not work
ng g component com4 --> not work
ng g component com5 --> not work
ng g component com6 --> not work
ng g component com7 --> not work
ng g component com8 --> not work
ng g component com9 --> not work
ng g component com10 --> it work
ng g component coma --> it work
ng g component comaa --> it work
ng g component aaa0 --> it work
ng g component a0 --> it work

Hi @itning, in Windows  COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9 among others are reserved.
More info here: https://docs.microsoft.com/en-gb/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN
Closing as this is not a CLI bug but an OS restriction.

Hi @itning, in Windows COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9 among others are reserved.
More info here: https://docs.microsoft.com/en-gb/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN
Closing as this is not a CLI bug but an OS restriction.

I see, thank you for answering my questions


Factor AsyncQueueStreamer from Netty4Stream.

Netty4Stream implements a generic pattern for implementing a stream on top of
an AsyncQueue of input frames.  We factor out the common pieces of queuing and
accumulation in an input-agnostic way so that other stream implementations are
not required to implement the same state management.
Furthermore, a default Stream implementation may now be constructed with
Stream.apply().

Merged https://github.com/BuoyantIO/linkerd/commit/b0f422286c431d2d00731ebe97ade3a617c9bc53


New Block class wrongly claims that there can be no discrepancies when accessing header attrs via the block instance

The old Block class used to mirror most attributes from its BlockHeader, meaning that one could either get or set header attributes via the block instance, and pyethapp relies on that to work.
That is no longer the case in the new Block, even though it claims that is still the case
Even if the current behaviour were properly documented, I think it makes for a terrible API as documentation can be easily overlooked and developers would be lead to think they can both get/set header attributes via the block, leading to bugs that would be very hard to find (I just spent several hours to find this out myself), so I think we need to either revert to the old behaviour or do away with the ability to get header attributes via the block instance

I think we can just remove the obsolete document. cc @vbuterin

The problem is that this allows us to do read access on the header attributes via the block instance (e.g. nonce = block.nonce), but if you try to write to them (e.g. mined_block.nonce = nonce) one would expect that to either fail or write to the underlying header attribute, but instead it silently sets that value to a new block.nonce instance variable, which will cause the block.nonce to be different from block.header.nonce.
I think the best alternative here is to simply remove the Block.getattr method and force all accesses to the header attributes to go via the header instance variable.


How to compile only changed modules?

I am try to debug and add features to the firmware (dev-esp32 branch). But using docker to compile it takes like 30+ minutes. I would like know if there is a way to only compile changed source code and reuse other compiled objects to link a new binary?

when the container is restarted [...] make still triggers a complete compile & link cycle.

Note: the ESP8266 build is also affected.

Jumping in late and haven't read most of the thread, but as for the original concern:

But using docker to compile it takes like 30+ minutes.

… using a faster docker host might help. The free ones provided by GitHub Actions seem to be able to build the firmware in less than 4 minutes: Example


Can we have the feature to pass the custom categories also to the node-red settings

Description
No response
Requested By

Customer name and/or link to HubSpot contact

@knolleary  i feel it should be quick one to add
`diff --git a/lib/runtimeSettings.js b/lib/runtimeSettings.js
index 264207c..aae0a56 100644
--- a/lib/runtimeSettings.js
+++ b/lib/runtimeSettings.js
@@ -16,7 +16,8 @@ function getSettingsFile (settings) {
nodesExcludes: [],
denyList: [],
allowList: ['*'],

       catalogues: ['https://catalogue.nodered.org/catalogue.json']

       catalogues: ['https://catalogue.nodered.org/catalogue.json'],

       categories: ['subflows', 'common', 'function', 'network', 'sequence', 'parser', 'storage']
   },
   modules: {
       allowInstall: true,

@@ -338,7 +339,8 @@ module.exports = {
${projectSettings.libraries}
tours: ${projectSettings.tours},
palette: {

       catalogues: ${JSON.stringify(projectSettings.palette.catalogues)}

       catalogues: ${JSON.stringify(projectSettings.palette.catalogues)},

       categories: ${JSON.stringify(projectSettings.palette.categories)}
   },
   multiplayer: {
       enabled: true

`

Hi @sunilkumarm080
can you expand on what you want to do? The description is empty.
We are being very selective over which settings we expose in the UI - as we don't want to overwhelm users with lots of options they mostly don't need to worry about.


Optimizer Improvements

Issue Description
What did you expect to see happen?
More adaptive optimizer parameters, both initial unspecified values as well as adaptation of parameters during the optimization search
What did you see instead?
No adaptivity, and default step size does not correlate with total domain size.
Do you have a suggested fix for the development team?
Use the SPSA paper recommendations and explore adaptive options.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or improvement?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)?
[ ] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?

Accidental duplicate of #39.


extend data_source on authoring page

-allow requester to concatenate static text with column names from the spreadsheet file
something like This is my question {column1} and this is the expected answer {column2}.
spaces between {} can be ignored and it should highlight the {column}s as code.
data_source should be a list of objects [{type: 'static', posititon:1, value: 'This is my question '}, {type: 'dynamic', value: 'column_1', ...}]
this goes into the template_items of the authoring interface (create project)
further discussions will happen on Slack

Can we have multiple occurrences of the same dynamic field ?
Like should we consider the case where {column1} is used twice/thrice in question-field ?

No

I am wondering why it shouldn't allow multiple occurrences?
We should infact replace all occurrences wherever applicable whether for same field or different one. We should not be limiting author on how these data sources can be used.

That's the general case I agree, in practice I don't think it happens though, but sure go for it then

@dmorina, @shirishgoyal: In that case, what should be the structure of data_sources ?
Lets say we have the following question string. "hello {column1} this is {column2} for {column1}".

option-1 having separate objects for multiple occurrences with their respective position.

data_sources= [{
 type:'static',
 value:'hello',
 position:0
},{
 type:'dynamic',
 value:'column1'
 position:1
},{
  type:'static',
  value:'this is ,
  position:2
},{
  type:'dynamic'
  value:'column2',
  position: 3
},{
  type:'static'
  value:'for',
  position: 4
},{
  type:'dynamic'
  value:'column1',
  position: 5
}]

option-2 using a single object for multiple occurrences and specify their positions in an array field

data_sources= [{
 type:'static',
 value:'hello',
 position:[0]
},{
 type:'dynamic',
 value:'column1'
 position:[1,5]
},{
  type:'static',
  value:'this is ,
  position:[2]
},{
  type:'dynamic'
  value:'column2',
  position: [3]
},{
  type:'static'
  value:'for',
  position: [4]
}]

I think lean way to handle this will be
to store string value like "hello {column1} this is {column2} for {column1}" in val
AND
data_sources can contain a plain simple array [ 'column1', 'column2']
When task is created all the tags from data_sources are replaced in val in a single pass (to avoid recursive tagging)
We can use auto-complete while creating string above.
Let me know if you need more clarification.

@shirishgoyal : I postulated the same initially: to store only dynamic tokens in data_sources since  static tokens are already being stored in 'value' attribute anyways. However, after discussing it with @dmorina in Wednesday meeting(27/1/2015), he suggested to keep both types in data_sources for better semantics.
Also, following this scheme(to keep an array of objects with type, value and position attributes) fits well with the way we currently handle options field (in case of checkbox/radio-button/select-list questions).

If you feel comfortable with that approach, that is fine too.
But options and data sources are two different things
Options need a way to be sorted. On other hand, data sources used in text have a fixed order already.


rakduo: 2016.04 -> 2016.07

Motivation for this change
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

The commit incorrectly identifies it as rackduo. While I'm testing, would you update the commit message / PR title to say rakudo?

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

thanks, I have fixed it.

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

[nix-shell:~/projects/nixpkgs]$ /nix/store/436vysgxxkajaszxd49g34px57z8yq73-rakudo-star-2016.07/bin/perl6
You may want to `panda install Readline` or `panda install Linenoise` or use rlwrap for a line editor

To exit type 'exit' or '^D'
> print "hi\n"
hi
>

Other than this note about readline / linenoise, looks good from here.

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


License type

Hi @vslinko,
Thanks for working on this plugin; it seems pretty cool. 🙂 I was wondering what kind of license you had planned to put the code under to see if it could be used in other applications (like Standard Notes) as a user on our community Slack pointed us to this repo.

Hi @JaspalSuri
Thank you for your feedback :)
Added MIT license https://github.com/vslinko/obsidian-outliner/blob/main/LICENSE
So you can use the sources.

Thank you, @vslinko!


can we have a tutorial video for adding custom cores ?

Issue summary
hello i try to add ppsspp liberto core but i dont know how i only know that i put the liberto core inside cores and after that the dll inside the other core folder and after that somehow you get a json file with the controller buttons i dont know what name or what extra files are needed  thanks for your time and thanks you if the issue will be solved or not

I am unsure anyone is still maintaining this repository.

I am unsure anyone is still maintaining this repository.

i made one with mame2003 and compiled successfully but when i put the game on integration ui it crashes ..........XD

I am unsure anyone is still maintaining this repository.

well, that's why they should add a message like Nobody maintains this repo


The Expo app React JS Exception

Dear @cyrildiagne ,
I have downloaded your project on my Ubuntu laptop version Ubuntu 18.04.4 LTS.
I have been able to do following things successfully

I have started the Basenet web service (on my Local Ubuntu Laptop)
I was able to start your Server(on my Local Ubuntu Laptop) and connect to the Basenet web service successfully
I made the app run and started the Android App (on My Honor Device) , I can see that 200 ok comes both in server and Basenet Web server ensuring the connection is ok.

But on the Android App , there is only dark screen with white dots, I can see following exception in react JS.

[Unhandled promise rejection: Error: Preview is paused - resume it before taking a picture.]

node_modules/react-native/Libraries/BatchedBridge/NativeModules.js:99:50 in fn
node_modules/@unimodules/react-native-adapter/build/NativeModulesProxy.js:15:46 in moduleName.methodInfo.name

http://<IP_ADDRESS>:19003/node_modules/expo/AppEntry.bundle?platform=android&dev=true&minify=false&hot=false:125673:76 in takePictureAsync$

node_modules/regenerator-runtime/runtime.js:45:44 in tryCatch
node_modules/regenerator-runtime/runtime.js:274:30 in invoke
node_modules/regenerator-runtime/runtime.js:45:44 in tryCatch
node_modules/regenerator-runtime/runtime.js:135:28 in invoke
node_modules/regenerator-runtime/runtime.js:170:17 in PromiseImpl$argument_0
node_modules/promise/setimmediate/core.js:45:7 in tryCallTwo
node_modules/promise/setimmediate/core.js:200:23 in doResolve
node_modules/promise/setimmediate/core.js:66:12 in Promise
node_modules/regenerator-runtime/runtime.js:169:31 in PromiseImpl$argument_0
node_modules/regenerator-runtime/runtime.js:192:38 in enqueue
node_modules/regenerator-runtime/runtime.js:219:8 in exports.async

http://<IP_ADDRESS>:19003/node_modules/expo/AppEntry.bundle?platform=android&dev=true&minify=false&hot=false:125667:42 in takePictureAsync
App.tsx:65:2 in cut

node_modules/regenerator-runtime/runtime.js:45:44 in tryCatch
node_modules/regenerator-runtime/runtime.js:274:30 in invoke
node_modules/regenerator-runtime/runtime.js:45:44 in tryCatch
node_modules/regenerator-runtime/runtime.js:135:28 in invoke
node_modules/regenerator-runtime/runtime.js:170:17 in PromiseImpl$argument_0
node_modules/promise/setimmediate/core.js:45:7 in tryCallTwo
node_modules/promise/setimmediate/core.js:200:23 in doResolve
node_modules/promise/setimmediate/core.js:66:12 in Promise
node_modules/regenerator-runtime/runtime.js:169:31 in PromiseImpl$argument_0
node_modules/regenerator-runtime/runtime.js:192:38 in enqueue
node_modules/regenerator-runtime/runtime.js:219:8 in exports.async

http://<IP_ADDRESS>:19003/node_modules/expo/AppEntry.bundle?platform=android&dev=true&minify=false&hot=false:124988:40 in cut
App.tsx:135:2 in onPressIn

node_modules/regenerator-runtime/runtime.js:45:44 in tryCatch
node_modules/regenerator-runtime/runtime.js:274:30 in invoke
node_modules/regenerator-runtime/runtime.js:45:44 in tryCatch
node_modules/regenerator-runtime/runtime.js:135:28 in invoke
node_modules/regenerator-runtime/runtime.js:170:17 in PromiseImpl$argument_0
node_modules/promise/setimmediate/core.js:45:7 in tryCallTwo
node_modules/promise/setimmediate/core.js:200:23 in doResolve
node_modules/promise/setimmediate/core.js:66:12 in Promise
node_modules/regenerator-runtime/runtime.js:169:31 in PromiseImpl$argument_0
node_modules/regenerator-runtime/runtime.js:192:38 in enqueue
node_modules/regenerator-runtime/runtime.js:219:8 in exports.async

App.tsx:135:2 in onPressIn

node_modules/react-native/Libraries/Components/Touchable/TouchableWithoutFeedback.js:217:49 in createReactClass$argument_0.touchableHandleActivePressIn

[native code]:null in touchableHandleActivePressIn

node_modules/react-native/Libraries/Components/Touchable/Touchable.js:894:75 in TouchableMixin._startHighlight

[native code]:null in _startHighlight

node_modules/react-native/Libraries/Components/Touchable/Touchable.js:858:27 in TouchableMixin._performSideEffectsForTransition

[native code]:null in _performSideEffectsForTransition

node_modules/react-native/Libraries/Components/Touchable/Touchable.js:779:44 in TouchableMixin._receiveSignal

[native code]:null in _receiveSignal

node_modules/react-native/Libraries/Components/Touchable/Touchable.js:718:24 in TouchableMixin._handleDelay

[native code]:null in _handleDelay

node_modules/react-native/Libraries/Components/Touchable/Touchable.js:471:24 in TouchableMixin.touchableHandleResponderGrant

[native code]:null in touchableHandleResponderGrant

node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:814:48 in executeDirectDispatch
node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2274:49 in setResponderAndExtractTransfer
node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2404:10 in ResponderEventPlugin.extractEvents
node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:1071:8 in extractPluginEvents
node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:1091:4 in runExtractedPluginEventsInBatch
node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2796:6 in batchedUpdates$argument_0
node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:18791:14 in batchedUpdates$1
node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2709:30 in batchedUpdates
node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2794:17 in batchedUpdates$argument_0
node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2870:28 in receiveTouches
node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:436:47 in __callFunction
node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:111:26 in __guard$argument_0
node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:384:10 in __guard
node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:110:17 in __guard$argument_0

[native code]:null in callFunctionReturnFlushedQueue

Since i have no understanding of  ReactJS , would be great to get help to resolve this issue.
Regards
Amit

One more thing if i comment line 138 and 142 then exception does not occur
https://github.com/cyrildiagne/ar-cutpaste/blob/master/app/App.tsx#L138
https://github.com/cyrildiagne/ar-cutpaste/blob/master/app/App.tsx#L142
but still functionality of taking image does not work. Hope to get some help in this regards
Regards
Amit

I also take the same problems , hope reslove.

@luorixiangyang thanks, could you please let me know, which machine and mobile you are using?

I am also trying to configure Expo on the Ubuntu laptop. Could you please introduce the configuration method?I can't run apps on my huawei phone.I have successfully configured the Basenet Web service.When I scanned the QR code with my phone, expo showed that the connection failed.Thank you very much


SWN Revised v2.4.10

Changes / Comments
Closes #6742

Fix a bug disallowing decimal encumbrance values.
Introduce a "bundled" toggle for equipment, which will bundle the items in packs of 3. This can be used instead of decimal encumbrance values.

No major astheatics changes, no attributes changed or removed.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
[x] Does this add functional enhancements (new features or extending existing features) ?
[x] Does this add or change functional aesthetics (such as layout or color scheme) ?
[x] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[x] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Also, I've never quite understood how you want me to use those checkboxes. Are they a tool for me to track which questions I've answered? Are they supposed to mean "yes" to those questions? Some of them are really not yes/no questions.

Greeting @Karlinator
The checkboxes are optional. Though they do help me to see what has changed with the update. :)


Secondtex  -Text error "Dorolt" instead of " Dorolț"

ENVIRONMENT: production
URL: https://admin.peviitor.ro/
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:
1 .Open the URL in the browser
2. Click on the " Secondtex "
3. Open https://admin.peviitor.ro/jobs/Secondtex
4. Click on the "See Jobs" button.
EXPECTED RESULTS:
The company's job location is the same us website company.
ACTUAL RESULTS:
Text error "Dorolt" instead of " Dorolț"
ATTACHMENTS:

Validatorul nu suporta diacritice.


[fpv] Fix tcl file for xbar bind file

In current xbar bind file, we should not include in the FPV env, but the
glob command in tcl file will find all bind files, which result in some
compile error. Now fpv tcl file will only glob the input IPs.
Signed-off-by: Cindy Chen<EMAIL_ADDRESS>

I think we should try to minimize the amount of "customizations" added to
this tcl file. hence, a more concise way would be to leverage the
dependency management from fusesoc to include the appropriate sources
instead of adding them in a "hardcoded" way to the tcl file.
each FPV testbench has a core file where it can specify its dependencies,
and the formal.core file could include these dependencies as well such that
the bind files are included appropriately for top level FPV. I started to
do that for the PLIC FPV in #893.
WDYT?
On Wed, Nov 6, 2019 at 2:35 PM NilsGraf<EMAIL_ADDRESS>wrote:

@NilsGraf commented on this pull request.
In hw/formal/fpv.tcl
https://github.com/lowRISC/opentitan/pull/895#discussion_r343364602:

analyze -sv09
-f formal_0.scr \

[glob ../../../../ip//dv/_bind.sv] \
[glob ../../../../ip//dv/tb/_bind.sv] \

[glob ../../../../ip/$env(FPV_TOP)/dv/_bind.sv ../../../../ip/$env(FPV_TOP)/dv/tb/_bind.sv] \

I think you can use the -nocomplain so that it doesn't error out when it
can't find a file (I believe I'm using this switch in one of the previous
lint scripts)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/895?email_source=notifications&email_token=AJ3RJJLXKAQ7GG26O5E735LQSNBCJA5CNFSM4JJ3X6TKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCKSNCMY#discussion_r343364602,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ3RJJIMZN23C5MQK7WL2P3QSNBCJANCNFSM4JJ3X6TA
.

Thanks Michael, I was not aware that we were fixing the same issue when I
created this one. Thanks and I think it sounds good to me. I can close this
PR.
Thanks Nils for your help and suggestions, definitely learned a lot of
scripting from your work.
On Wed, Nov 6, 2019 at 2:45 PM Michael Schaffner<EMAIL_ADDRESS>wrote:

I think we should try to minimize the amount of "customizations" added to
this tcl file. hence, a more concise way would be to leverage the
dependency management from fusesoc to include the appropriate sources
instead of adding them in a "hardcoded" way to the tcl file.
each FPV testbench has a core file where it can specify its dependencies,
and the formal.core file could include these dependencies as well such that
the bind files are included appropriately for top level FPV. I started to
do that for the PLIC FPV in #893.
WDYT?
On Wed, Nov 6, 2019 at 2:35 PM NilsGraf<EMAIL_ADDRESS>wrote:

@NilsGraf commented on this pull request.
In hw/formal/fpv.tcl
https://github.com/lowRISC/opentitan/pull/895#discussion_r343364602:

analyze -sv09
-f formal_0.scr \

[glob ../../../../ip//dv/_bind.sv] \
[glob ../../../../ip//dv/tb/_bind.sv] \

[glob ../../../../ip/$env(FPV_TOP)/dv/_bind.sv
../../../../ip/$env(FPV_TOP)/dv/tb/_bind.sv] \

I think you can use the -nocomplain so that it doesn't error out when it
can't find a file (I believe I'm using this switch in one of the previous
lint scripts)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<
https://github.com/lowRISC/opentitan/pull/895?email_source=notifications&email_token=AJ3RJJLXKAQ7GG26O5E735LQSNBCJA5CNFSM4JJ3X6TKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCKSNCMY#discussion_r343364602
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AJ3RJJIMZN23C5MQK7WL2P3QSNBCJANCNFSM4JJ3X6TA
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/895?email_source=notifications&email_token=ACXPOON2UOKOZQKB4XSZNODQSNCINA5CNFSM4JJ3X6TKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDIICWI#issuecomment-550535513,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXPOOJX72JR7TJMCRWR33DQSNCINANCNFSM4JJ3X6TA
.

Ok, I pulled the other PR in. And sorry about the duplicate work that I caused you to do ;).

No worries Michael, thank you for helping out. I am just buried with emails these days and sorry missed your change.


Add helper functions to convert QWORD to/from BigInt

I think that would be a natural addition to the current set of helper functions.

Add the following conversion to parseValue: QWORD -> BigInt.
Make formatQWORD receive a BigInt instead of a number.

Since this is still a v0, and BigInt is pretty well supported, this seems reasonable. I'd probably do the existing fixes as a 0.3.* and do this a a 0.4 just in case though.

Sorry it took me so long to get around to this. I don't think my approach has any compatibility issues, so I'm leaving it as v0.3 for now, but as it's 11:30PM right now, it's only in @next tag so far. Let me know if this works for you!

Looks like it's working properly, thanks!


Add indonesian and Javanese-ID language

Add Indonesian (id.lproj) and Javanese-ID (jv-ID.lproj) language

Your PR contains a .yml file for building. Please resubmit your PR without it or commit it out.

Already resubmitted


flaky test (failing odo push)

•Running command: odo url create myurl --port 8080
 ✓  URL created for component: nodejs

To create URL on the OpenShift cluster, please run `odo push`
Result:
 stdout:  ✓  URL created for component: nodejs

To create URL on the OpenShift cluster, please run `odo push`

 stderr:
 exitcode: 0
Running command: odo push -v 4
I0416 09:42:45.745489   16663 config.go:587] Git source type detected, not correcting SourcePath location
I0416 09:42:45.748787   16663 preference.go:116] The configFile is /tmp/artifacts/.odo/config.yaml
I0416 09:42:45.748929   16663 occlient.go:445] Trying to connect to server api.ci-op-71467ypl-5186a.origin-ci-int-aws.dev.rhcloud.com:6443
I0416 09:42:45.765117   16663 occlient.go:452] Server https://api.ci-op-71467ypl-5186a.origin-ci-int-aws.dev.rhcloud.com:6443 is up
I0416 09:42:45.831439   16663 occlient.go:375] isLoggedIn err:  <nil>
 output: "developer"
I0416 09:42:45.831673   16663 context.go:339] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: project
I0416 09:42:45.831701   16663 context.go:339] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: app
I0416 09:42:45.831706   16663 context.go:339] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: project
I0416 09:42:45.848583   16663 context.go:339] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: app
I0416 09:42:45.848622   16663 context.go:339] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: output
I0416 09:42:45.848628   16663 context.go:339] Ignoring error as it usually means flag wasn't set: flag accessed but not defined: component
 •  Checking component  ...

I0416 09:42:47.012366   16663 occlient.go:2083] Getting BuildConfig: nodejs-myapp
I0416 09:42:47.057427   16663 occlient.go:2083] Getting BuildConfig: nodejs-myapp
I0416 09:42:47.078766   16663 component.go:1057] Updating the DeploymentConfig nodejs-myapp image to nodejs-myapp:latest
I0416 09:42:47.195031   16663 request.go:485] Throttling request took 114.829796ms, request: PUT:https://api.ci-op-71467ypl-5186a.origin-ci-int-aws.dev.rhcloud.com:6443/apis/apps.openshift.io/v1/namespaces/json-test/deploymentconfigs/nodejs-myapp
I0416 09:42:47.344911   16663 utils.go:52] Desired revision (3) is different from the running revision (2)
I0416 09:42:47.442821   16663 utils.go:52] Desired revision (3) is different from the running revision (2)
I0416 09:42:52.842803   16663 utils.go:52] Desired revision (3) is different from the running revision (2)
I0416 09:42:54.842771   16663 utils.go:52] Desired revision (3) is different from the running revision (2)
I0416 09:42:55.042758   16663 utils.go:52] Desired revision (3) is different from the running revision (2)
I0416 09:43:04.443273   16663 utils.go:52] Desired revision (3) is different from the running revision (2)
I0416 09:43:05.442725   16663 utils.go:52] Desired revision (3) is different from the running revision (2)
I0416 09:47:47.344801   16663 cmdutils.go:23] Error:
unable to update DeploymentConfig image for nodejs component: unable to update the current DeploymentConfig nodejs-myapp: unable to wait for DeploymentConfig nodejs-myapp to update: Timed out waiting for annotation to update
 ✗  Failed to update config to component deployed

$ oc get dc -o yaml
apiVersion: v1
items:
- apiVersion: apps.openshift.io/v1
  kind: DeploymentConfig
  metadata:
    annotations:
      app.kubernetes.io/component-source-type: git
      app.kubernetes.io/url: https://github.com/openshift/nodejs-ex
    creationTimestamp: 2019-04-16T11:04:12Z
    generation: 5
    labels:
      app: myapp
      app.kubernetes.io/component-name: nodejs
      app.kubernetes.io/component-type: nodejs
      app.kubernetes.io/component-version: latest
      app.kubernetes.io/name: myapp
    name: nodejs-myapp
    namespace: json-test
    resourceVersion: "204273"
    selfLink: /apis/apps.openshift.io/v1/namespaces/json-test/deploymentconfigs/nodejs-myapp
    uid: 5e112358-6037-11e9-b9da-0a580a800041
  spec:
    replicas: 1
    selector:
      deploymentconfig: nodejs-myapp
    strategy:
      activeDeadlineSeconds: 21600
      recreateParams:
        timeoutSeconds: 600
      resources: {}
      type: Recreate
    template:
      metadata:
        creationTimestamp: null
        labels:
          deploymentconfig: nodejs-myapp
      spec:
        containers:
        - image: image-registry.openshift-image-registry.svc:5000/json-test/nodejs-myapp@sha256:c91495338896114cdc9b039028df41243ea084262ceb62194867765f1ebc7a8a
          imagePullPolicy: Always
          name: nodejs-myapp
          ports:
          - containerPort: 8080
            name: 8080-tcp
            protocol: TCP
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
        dnsPolicy: ClusterFirst
        restartPolicy: Always
        schedulerName: default-scheduler
        securityContext: {}
        terminationGracePeriodSeconds: 30
    test: false
    triggers:
    - type: ConfigChange
    - imageChangeParams:
        automatic: true
        containerNames:
        - nodejs-myapp
        from:
          kind: ImageStreamTag
          name: nodejs-myapp:latest
          namespace: json-test
        lastTriggeredImage: image-registry.openshift-image-registry.svc:5000/json-test/nodejs-myapp@sha256:c91495338896114cdc9b039028df41243ea084262ceb62194867765f1ebc7a8a
      type: ImageChange
  status:
    availableReplicas: 1
    conditions:
    - lastTransitionTime: 2019-04-16T11:07:46Z
      lastUpdateTime: 2019-04-16T11:07:46Z
      message: Deployment config has minimum availability.
      status: "True"
      type: Available
    - lastTransitionTime: 2019-04-16T11:07:36Z
      lastUpdateTime: 2019-04-16T11:07:47Z
      message: replication controller "nodejs-myapp-2" successfully rolled out
      reason: NewReplicationControllerAvailable
      status: "True"
      type: Progressing
    details:
      causes:
      - imageTrigger:
          from:
            kind: DockerImage
            name: image-registry.openshift-image-registry.svc:5000/json-test/nodejs-myapp@sha256:c91495338896114cdc9b039028df41243ea084262ceb62194867765f1ebc7a8a
        type: ImageChange
      message: image change
    latestVersion: 2
    observedGeneration: 5
    readyReplicas: 1
    replicas: 1
    unavailableReplicas: 0
    updatedReplicas: 1
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

$ oc get rc -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: ReplicationController
  metadata:
    annotations:
      openshift.io/deployer-pod.completed-at: 2019-04-16 11:06:01 +0000 UTC
      openshift.io/deployer-pod.created-at: 2019-04-16 11:05:43 +0000 UTC
      openshift.io/deployer-pod.name: nodejs-myapp-1-deploy
      openshift.io/deployment-config.latest-version: "1"
      openshift.io/deployment-config.name: nodejs-myapp
      openshift.io/deployment.phase: Complete
      openshift.io/deployment.replicas: "1"
      openshift.io/deployment.status-reason: config change
      openshift.io/encoded-deployment-config: |
        {"kind":"DeploymentConfig","apiVersion":"apps.openshift.io/v1","metadata":{"name":"nodejs-myapp","namespace":"json-test","selfLink":"/apis/apps.openshift.io/v1/namespaces/json-test/deploymentconfigs/nodejs-myapp","uid":"5e112358-6037-11e9-b9da-0a580a800041","resourceVersion":"199997","generation":2,"creationTimestamp":"2019-04-16T11:04:12Z","labels":{"app":"myapp","app.kubernetes.io/component-name":"nodejs","app.kubernetes.io/component-type":"nodejs","app.kubernetes.io/component-version":"latest","app.kubernetes.io/name":"myapp"},"annotations":{"app.kubernetes.io/component-source-type":"git","app.kubernetes.io/url":"https://github.com/openshift/nodejs-ex"}},"spec":{"strategy":{"type":"Recreate","recreateParams":{"timeoutSeconds":600},"resources":{},"activeDeadlineSeconds":21600},"triggers":[{"type":"ConfigChange"},{"type":"ImageChange","imageChangeParams":{"automatic":true,"containerNames":["nodejs-myapp"],"from":{"kind":"ImageStreamTag","namespace":"json-test","name":"nodejs-myapp:latest"},"lastTriggeredImage":"image-registry.openshift-image-registry.svc:5000/json-test/nodejs-myapp@sha256:91efa21bbab7df02ead85a86a898818ec8452ce2ddecad06b78c60ff3f07fdbe"}}],"replicas":1,"revisionHistoryLimit":10,"test":false,"selector":{"deploymentconfig":"nodejs-myapp"},"template":{"metadata":{"creationTimestamp":null,"labels":{"deploymentconfig":"nodejs-myapp"}},"spec":{"containers":[{"name":"nodejs-myapp","image":"image-registry.openshift-image-registry.svc:5000/json-test/nodejs-myapp@sha256:91efa21bbab7df02ead85a86a898818ec8452ce2ddecad06b78c60ff3f07fdbe","ports":[{"name":"8080-tcp","containerPort":8080,"protocol":"TCP"}],"resources":{},"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"Always"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","securityContext":{},"schedulerName":"default-scheduler"}}},"status":{"latestVersion":1,"observedGeneration":1,"replicas":0,"updatedReplicas":0,"availableReplicas":0,"unavailableReplicas":0,"details":{"message":"config change","causes":[{"type":"ConfigChange"}]},"conditions":[{"type":"Available","status":"False","lastUpdateTime":"2019-04-16T11:04:13Z","lastTransitionTime":"2019-04-16T11:04:13Z","message":"Deployment config does not have minimum availability."}]}}
    creationTimestamp: 2019-04-16T11:05:43Z
    generation: 3
    labels:
      app: myapp
      app.kubernetes.io/component-name: nodejs
      app.kubernetes.io/component-type: nodejs
      app.kubernetes.io/component-version: latest
      app.kubernetes.io/name: myapp
      openshift.io/deployment-config.name: nodejs-myapp
    name: nodejs-myapp-1
    namespace: json-test
    ownerReferences:
    - apiVersion: apps.openshift.io/v1
      blockOwnerDeletion: true
      controller: true
      kind: DeploymentConfig
      name: nodejs-myapp
      uid: 5e112358-6037-11e9-b9da-0a580a800041
    resourceVersion: "201114"
    selfLink: /api/v1/namespaces/json-test/replicationcontrollers/nodejs-myapp-1
    uid: 9425e645-6037-11e9-816f-0ef72485a714
  spec:
    replicas: 0
    selector:
      deployment: nodejs-myapp-1
      deploymentconfig: nodejs-myapp
    template:
      metadata:
        annotations:
          openshift.io/deployment-config.latest-version: "1"
          openshift.io/deployment-config.name: nodejs-myapp
          openshift.io/deployment.name: nodejs-myapp-1
        creationTimestamp: null
        labels:
          deployment: nodejs-myapp-1
          deploymentconfig: nodejs-myapp
      spec:
        containers:
        - image: image-registry.openshift-image-registry.svc:5000/json-test/nodejs-myapp@sha256:91efa21bbab7df02ead85a86a898818ec8452ce2ddecad06b78c60ff3f07fdbe
          imagePullPolicy: Always
          name: nodejs-myapp
          ports:
          - containerPort: 8080
            name: 8080-tcp
            protocol: TCP
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
        dnsPolicy: ClusterFirst
        restartPolicy: Always
        schedulerName: default-scheduler
        securityContext: {}
        terminationGracePeriodSeconds: 30
  status:
    observedGeneration: 3
    replicas: 0
- apiVersion: v1
  kind: ReplicationController
  metadata:
    annotations:
      openshift.io/deployer-pod.completed-at: 2019-04-16 11:07:46 +0000 UTC
      openshift.io/deployer-pod.created-at: 2019-04-16 11:07:18 +0000 UTC
      openshift.io/deployer-pod.name: nodejs-myapp-2-deploy
      openshift.io/deployment-config.latest-version: "2"
      openshift.io/deployment-config.name: nodejs-myapp
      openshift.io/deployment.phase: Complete
      openshift.io/deployment.replicas: "1"
      openshift.io/deployment.status-reason: image change
      openshift.io/encoded-deployment-config: |
        {"kind":"DeploymentConfig","apiVersion":"apps.openshift.io/v1","metadata":{"name":"nodejs-myapp","namespace":"json-test","selfLink":"/apis/apps.openshift.io/v1/namespaces/json-test/deploymentconfigs/nodejs-myapp","uid":"5e112358-6037-11e9-b9da-0a580a800041","resourceVersion":"201006","generation":3,"creationTimestamp":"2019-04-16T11:04:12Z","labels":{"app":"myapp","app.kubernetes.io/component-name":"nodejs","app.kubernetes.io/component-type":"nodejs","app.kubernetes.io/component-version":"latest","app.kubernetes.io/name":"myapp"},"annotations":{"app.kubernetes.io/component-source-type":"git","app.kubernetes.io/url":"https://github.com/openshift/nodejs-ex"}},"spec":{"strategy":{"type":"Recreate","recreateParams":{"timeoutSeconds":600},"resources":{},"activeDeadlineSeconds":21600},"triggers":[{"type":"ConfigChange"},{"type":"ImageChange","imageChangeParams":{"automatic":true,"containerNames":["nodejs-myapp"],"from":{"kind":"ImageStreamTag","namespace":"json-test","name":"nodejs-myapp:latest"},"lastTriggeredImage":"image-registry.openshift-image-registry.svc:5000/json-test/nodejs-myapp@sha256:c91495338896114cdc9b039028df41243ea084262ceb62194867765f1ebc7a8a"}}],"replicas":1,"revisionHistoryLimit":10,"test":false,"selector":{"deploymentconfig":"nodejs-myapp"},"template":{"metadata":{"creationTimestamp":null,"labels":{"deploymentconfig":"nodejs-myapp"}},"spec":{"containers":[{"name":"nodejs-myapp","image":"image-registry.openshift-image-registry.svc:5000/json-test/nodejs-myapp@sha256:c91495338896114cdc9b039028df41243ea084262ceb62194867765f1ebc7a8a","ports":[{"name":"8080-tcp","containerPort":8080,"protocol":"TCP"}],"resources":{},"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"Always"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","securityContext":{},"schedulerName":"default-scheduler"}}},"status":{"latestVersion":2,"observedGeneration":2,"replicas":1,"updatedReplicas":1,"availableReplicas":1,"unavailableReplicas":0,"details":{"message":"image change","causes":[{"type":"ImageChange","imageTrigger":{"from":{"kind":"DockerImage","name":"image-registry.openshift-image-registry.svc:5000/json-test/nodejs-myapp@sha256:c91495338896114cdc9b039028df41243ea084262ceb62194867765f1ebc7a8a"}}}]},"conditions":[{"type":"Available","status":"True","lastUpdateTime":"2019-04-16T11:06:01Z","lastTransitionTime":"2019-04-16T11:06:01Z","message":"Deployment config has minimum availability."},{"type":"Progressing","status":"True","lastUpdateTime":"2019-04-16T11:06:02Z","lastTransitionTime":"2019-04-16T11:06:02Z","reason":"NewReplicationControllerAvailable","message":"replication controller \"nodejs-myapp-1\" successfully rolled out"}],"readyReplicas":1}}
    creationTimestamp: 2019-04-16T11:07:18Z
    generation: 2
    labels:
      app: myapp
      app.kubernetes.io/component-name: nodejs
      app.kubernetes.io/component-type: nodejs
      app.kubernetes.io/component-version: latest
      app.kubernetes.io/name: myapp
      openshift.io/deployment-config.name: nodejs-myapp
    name: nodejs-myapp-2
    namespace: json-test
    ownerReferences:
    - apiVersion: apps.openshift.io/v1
      blockOwnerDeletion: true
      controller: true
      kind: DeploymentConfig
      name: nodejs-myapp
      uid: 5e112358-6037-11e9-b9da-0a580a800041
    resourceVersion: "201347"
    selfLink: /api/v1/namespaces/json-test/replicationcontrollers/nodejs-myapp-2
    uid: cca75116-6037-11e9-816f-0ef72485a714
  spec:
    replicas: 1
    selector:
      deployment: nodejs-myapp-2
      deploymentconfig: nodejs-myapp
    template:
      metadata:
        annotations:
          openshift.io/deployment-config.latest-version: "2"
          openshift.io/deployment-config.name: nodejs-myapp
          openshift.io/deployment.name: nodejs-myapp-2
        creationTimestamp: null
        labels:
          deployment: nodejs-myapp-2
          deploymentconfig: nodejs-myapp
      spec:
        containers:
        - image: image-registry.openshift-image-registry.svc:5000/json-test/nodejs-myapp@sha256:c91495338896114cdc9b039028df41243ea084262ceb62194867765f1ebc7a8a
          imagePullPolicy: Always
          name: nodejs-myapp
          ports:
          - containerPort: 8080
            name: 8080-tcp
            protocol: TCP
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
        dnsPolicy: ClusterFirst
        restartPolicy: Always
        schedulerName: default-scheduler
        securityContext: {}
        terminationGracePeriodSeconds: 30
  status:
    availableReplicas: 1
    fullyLabeledReplicas: 1
    observedGeneration: 2
    readyReplicas: 1
    replicas: 1
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

#1625

@surajnarwade @mohammedzee1000 Are you seeing anything suspicious in https://github.com/openshift/odo/issues/1628#issuecomment-483620139 and https://github.com/openshift/odo/issues/1628#issuecomment-483620349 with respect to the push failure ?

I've been trying this for about 6-8 hours and I've only able to replicate this TWICE out of about 30 runs of:
▶ odo delete -f && rm -rf .odo && odo create nodejs nodejs --app myapp --project json-test --git https://github.com/openshift/nodejs-ex && odo push -v 4 && odo url create myurl --port 8080 && odo push -v 4

So when the bug occurs, the current revision (after the first push) is:
NAME           REVISION   DESIRED   CURRENT   TRIGGERED BY
nodejs-myapp   2         1         0         config,image(node-myapp:latest)

With the current desired still being 0 and effectively it's still not fully deployed.
When diagnosing this issue, I also ran into ANOTHER issue from doing odo push && odo url create && odo push in quick
unable to update DeploymentConfig image for nodejs component: unable to update the current DeploymentConfig nodejs-myapp: unable to update DeploymentConfig nodejs-myapp: Operation cannot be fulfilled on deploymentconfigs.apps.openshift.io "nodejs-myapp": the object has been
 modified; please apply your changes to the latest version and try again
 ✗  Failed to update config to component deployed

I will add validation for DeploymentConfig as we are not checking for correct DC deployment after BuildConfig is used / has updated DC: https://github.com/openshift/odo/blob/master/pkg/occlient/occlient.go#L1646
We've got to make sure that it's correctly waiting for the DC to fully update as after building git, as we are not waiting for DC to finish.

Reproducible on TravisCI too - https://travis-ci.org/openshift/odo/jobs/521316421 via pr #1632.

attempting to fix this issue in #1634

https://github.com/openshift/odo/issues/1633 is also related to this issue (two issues in one).

@kadel @cdrage Ci consistently reporting the same failure in my pr #1612 - https://travis-ci.org/openshift/odo/jobs/528706216

Similar scenario is covered in generic,  java and json test file. None of the time the issue is hit in each pr run since it was last reproduce. Probably #1633 fixed this flake.
Lets take a call in sprint planning meeting for the next action.

Closing this bug as it is being reproduced


Add support for all ('*') allowed headers

As configuration of allowed headers might be frustrating process (send request => fail => change conf => send request => next header is not allowed => change conf, frustration => ...) it might be useful to have option for all headers allowed '*'. As it's insecure it should not be enabled by default. But it could be an option for development.
The idea in influenced by https://github.com/neomerx/cors-illuminate/issues/11

Also suggestions about config settings were added to logs.


[master] x-oas- to x-oai-

Updates DEVELOPMENT.md and the proposals folder to reflect the decision to change the reserved x-oas- prefix to x-oai-.

Needs updating to reserve both.


How to pass env variable to scss file?

In webpack.mix.js I can access an env variable withprocess.env.MIX_URL, but how can I pass that variable to use is an scss file compiled via:
mix.sass('site.scss', 'public/css')

So we can call it like this:
@font-face {
  font-family: 'My-Font';
  src: url('http://www.site.com/fonts/My-Font.ttf'); // orig working
  src: url(process.env.MIX_URL+'/fonts/My-Font.ttf'); // var not working
}

Any idea how to make it work?

Anyone?

You are looking at wrong place:
https://github.com/webpack-contrib/sass-loader#environment-variables

Thank you so much for the link, it solves the issue!

For people coming here, I think the implied answer was to use the prependData feature of sass-loader?
https://github.com/webpack-contrib/sass-loader#prependdata
Haven't tried it myself yet, but it looks like it can do the job.
// webpack
{
  loader: 'sass-loader',
  options: {
    prependData: '$env: ' + process.env.NODE_ENV + ';',
  }
}

@MovingGifts can you plz explain how did you solve the issue?

How can we implement this in Next js ?


HDMI audio not working

HDMI video is working but no audio comes through.  I expect this is related to issue #13 but wanted to list it since it may be separate.

This is a long-term issue related to #113


Use username and password for authentication

Hi divinity666, thank you so much for building this application this has been a great help since we transitioned to open-source for monitoring purpose and this tool really helps us take reports of the dashboards.
In my scenario, I have many clients under my Grafana which are isolated via Organizations where each tenant has their own Organization. When we switch to a different org, other than our main org, we're not able to take the reports from them. And we had noticed that the service account token only lives under an Organization, so when trying to take reports, since the reporter is not able to validate the token, it prints an empty report.
If it's not too much to ask, would you be able to make changes in authentication method to use the username and password so that I can pass in my admin creds and be able to take reports from all of the organizations?
Please do let me know if it's already in my place. I also posted a comment in an Open Issue but by no means I'm a developer and don't know how to configure it on my own. (Ref issue: https://github.com/divinity666/ruby-grafana-reporter/issues/54)

Hi @kyouma24, thanks for reaching out.
I am using grafana APIs to make the reporter run. Especially, I am also using these APIs to do authentication. At that level, I only have the option to use the service accounts (if I recall correctly...). This is, why I cannot use username and password. Apart from that, this way sounds a bit hacky to me :-)
Anyway, it is possible to configure as many grafana instances in your config file in the grafana section. You can give each grafana instance a name, an API token and URL. In the report calls, you then would have to refer to the corresponding grafana instance. Depending on your use-case, this could be an option for you.
Does this help?


现在部署需要开始收费了吗？

在云端命令行操作的时候，得到这样一条信息反馈，有朋友遇到这样的问题吗？
WARNING: You will be unable to deploy applications after November 30, 2019 without adding a billing instrument to your project. Please add one at https://console.cloud.google.com/billing/linkedaccount?wechattorss
Updating service [default]...failed.
ERROR: (gcloud.app.deploy) Error Response: [7] Access Not Configured. Cloud Build has not been used in project wechattorss before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/cloudbuild.googleapis.com/
overview?project=wechattorss then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.

点那个链接，进去需要绑定信用卡，没关系，只是绑定，不是真的收费，部署还是免费的。

绑定了信用卡，通过，观察下，避免被收费，多谢 jeezy711


Support for Elysiajs 1.0

Are we planning to release a version for the Elysiajs 1.0?
With the breaking changes on the hookType "global" and "local" this package might need some updates

Yes! Pretty busy at work rn but I'll defo try on the weekend :)

Please let me know if you need any help

I haven’t checked the updates tbh but I’m open to reviewing PRs

Released 0.4.0! Thanks y'all!


Subsumption confusing semantics

Subsumption currently works kind of like a query and kind of like an action. For example, this code:
(Subsume (Add (Add 2 3) 4))
Adds (Add 2 3) to the database. However, if (Add (Add 2 3) 4) isn't present, it errors out because it couldn't find an existing entry.
Is this the behavior we want? Perhaps we wanted subsumption to first add the tuple, then subsume it?

I don't have a strong opinion on which semantics is preferable. I do agree maybe it would make sense to add it.
I am curious, is this from just experimenting, or in your use case do you often try to subsume things that don't yet exist?

I ran into a bug in eggcc that was a result of me misusing subsumption. I actually thought the semantics was to add it

I'm actually surprised about this behavior, because delete works fine even if the tuple does not exist, and we rely on this behavior at some places.
(datatype E (A))
(delete (A)) ;; works fine
(subsume (A)) ;; panics

I believe subsume should follow the behavior of delete. As another example, switching the order of the two rules below will cause egglog to panic
(datatype E (A))

(rule () ((A)))
(rule () ((subsume (A))))

(run 1) ;; works fine, but switching causes panic.

Sounds good to fix it. I would assume it works like delete/set as well.


Error on latest beta with controller type MQTT and UFOR11

Tested the latest beta, this error appear at "Check Configuration":-

Invalid config for 'smartir' from integration 'fan' at packages/configuration/fan.yaml, line 37: required key 'remote_entity' not provided
Invalid config for 'smartir' from integration 'fan' at packages/configuration/fan.yaml, line 38: Values are not equal: value:UFOR11 != target:Broadlink for dictionary value 'controller_data->controller_type', got 'UFOR11'
Invalid config for 'smartir' from integration 'fan' at packages/configuration/fan.yaml, line 39: 'mqtt_topic' is an invalid option for 'fan.smartir', check: controller_data->mqtt_topic

Invalid config for 'smartir' from integration 'fan' at packages/configuration/fan.yaml, line 37: required key 'remote_entity' not provided
Invalid config for 'smartir' from integration 'fan' at packages/configuration/fan.yaml, line 38: Values are not equal: value:MQTT != target:Broadlink for dictionary value 'controller_data->controller_type', got 'MQTT'
Invalid config for 'smartir' from integration 'fan' at packages/configuration/fan.yaml, line 39: 'mqtt_topic' is an invalid option for 'fan.smartir', check: controller_data->mqtt_topic

My fan.yaml config:-
  - platform: smartir
    name: Ceiling Fan - Bedroom II
    unique_id: ceiling_fan_bedroom_2
    device_code: 16
    controller_data:
      controller_type: UFOR11
      mqtt_topic: zigbee2mqtt_lan/Bedroom 2 - IR Remote/set
    power_sensor: switch.bedroom_2_lights_fan_switch_left
    power_sensor_restore_state: true

  - platform: smartir
    name: Ceiling Fan - Bedroom II
    unique_id: ceiling_fan_bedroom_2
    device_code: 16
    controller_data:
      controller_type: MQTT
      mqtt_topic: zigbee2mqtt_lan/Bedroom 2 - IR Remote/set/ir_code_to_send
    power_sensor: switch.bedroom_2_lights_fan_switch_left
    power_sensor_restore_state: true

May need to update the checker for MQTT and UFOR11 or please advise otherwise.

Same here.

I have some problem....
my config:
climate:

platform: smartir
name: Obyvačka klima
unique_id: obyvacka_klima
device_code: 1281
controller_data:
controller_type: UFOR11
mqtt_topic: zigbee2mqtt/Dialkove ovladanie 1/set
temperature_sensor: sensor.teplota_obyvacka_temperature
humidity_sensor: sensor.teplota_obyvacka_humidity

platform: smartir
name: Spálňa klima
unique_id: spalna_klima
device_code: 1281
controller_data:
controller_type: UFOR11
mqtt_topic: zigbee2mqtt/Dialkove ovladanie 2/set

error:
Invalid config for 'climate' from integration 'smartir' at configuration.yaml, line 383: required key 'remote_entity' not provided, please check the docs at https://github.com/litinoveweedle/SmartIR Invalid config for 'climate' from integration 'smartir' at configuration.yaml, line 384: Values are not equal: value:UFOR11 != target:Broadlink for dictionary value 'controller_data->controller_type', got 'UFOR11', please check the docs at https://github.com/litinoveweedle/SmartIR Invalid config for 'climate' from integration 'smartir' at configuration.yaml, line 385: 'mqtt_topic' is an invalid option for 'smartir.climate', check: controller_data->mqtt_topic, please check the docs at https://github.com/litinoveweedle/SmartIR
Invalid config for 'climate' from integration 'smartir' at configuration.yaml, line 393: required key 'remote_entity' not provided, please check the docs at https://github.com/litinoveweedle/SmartIR Invalid config for 'climate' from integration 'smartir' at configuration.yaml, line 394: Values are not equal: value:UFOR11 != target:Broadlink for dictionary value 'controller_data->controller_type', got 'UFOR11', please check the docs at https://github.com/litinoveweedle/SmartIR Invalid config for 'climate' from integration 'smartir' at configuration.yaml, line 395: 'mqtt_topic' is an invalid option for 'smartir.climate', check: controller_data->mqtt_topic, please check the docs at https://github.com/litinoveweedle/SmartIR

OMG, me too! What we shall do about it? :-) Litinoveweedle, fix it!
Yes Sir! I propose to fix it by repairing copy paste error in the controller_const.py on the line 37!
Litinoveweedle you have permission to do it!
Already done sir, in the #100
Great job Litinoveweedle, how the poor users can use it?
The can copy the affected file from the master, until new beta is released. May I have proposal sir?
Sure you can.
I would appreciated if next time user instead of writing 'me to'  checked the code and proposed PR, as this one was really obvious to find out.
We can only hope for that, Litinoveweedle.

Released in 1.18.0b3


Get video call duration

Hi guys,
may i ask how can i get the video call duration on flutter web ?
Thanks for your support here.

Our SDK doesn't have a ready solution but you can manage it by yourself. You can calculate it as the timeout between the callback onConnectedToUser and onSessionClosed. Just start the timer after first calling the callback onConnectedToUser and stop it after calling the onSessionClosed.


Adding new driver for Intel Realsense T265 tracking camera

Hi,
I have made a driver for Realsense T265 tracking camera and I would like to share it with you.
Best regards,
Elias

Hello Ellas,
Thanks for this PR, I am hot sure though if this is something for us to upstream.
Our drivers are dependency-less, with the exception of a few core ones (hidapi, libusb, udev etc), the idea is that our drivers are free of blobs or third party services.
Since this uses the RealSense SDK, its not really a FOSS implementation of a driver, just a small bridge with a SDK.
Sine OpenHMD has a compatible ABI, it is perfectly fine to have this on your own repository and share it this way. I am happy to add this to our website and mention it on the devices list as externally developed driver if this is fine by you.
Thanks
Joey

This is a policy decision I guess - whether OpenHMD wants to be a uniform access layer or "just" a collection of drivers. In general, deciding to be  a collection of drivers is fine - there's other layers like OpenXR/monado that can be the uniform access API.
One comment on the code: Should it report class as OHMD_DEVICE_CLASS_GENERIC_TRACKER and not OHMD_DEVICE_CLASS_HMD?

Indeed the class should be OHMD_DEVICE_CLASS_GENERIC_TRACKER since it does not contain a display or any projectionmatrix information.

I'll fix the device class to OHMD_DEVICE_CLASS_GENERIC_TRACKER and if you consider this is best kept externally developed then it would be nice to have it mentioned on the website.

This is great! Just got a T265 yesterday and was amazed by the 6DoF tracking capabilities. Nice to see that OpenHMD community already came up with support for this! :)
This is something that I see fitting in OpenHMD as an optional dependency, so it should be enabled if librealsense2 is found. I don't see any feasible alternative to using librealsense, @TheOnlyJoey do you want to write your own open source realsense userspace driver?
But of course if you want to keep OpenHMD just actual device implementations, so at the same level as librealsense, then this pull request should be moved one layer up in the stack and @e0177 should implement this in Monado.
I will test this soon :)


It wont make multiple accounts spam when i put in tokens

whenever i put more tokens in like this ['token','token','token'] it only makes 1 account spam when using function 1 anyway I can fix this?

I answered your question in discord. Do not duplicate your question in several places at once.


Problem compiling for android

Compiling for android example. Not sure if its a bug
After Trying for  tensorflow/contrib/makefile/compile_android_protobuf.sh -c
checking whether to enable maintainer-specific portions of Makefiles... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... arm-unknown-linux-androideabi
checking target system type... arm-unknown-linux-androideabi
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-linux-androideabi-strip... arm-linux-androideabi-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking for arm-linux-androideabi-gcc...  arm-linux-androideabi-gcc --sysroot ../android-ndk-r14b//platforms/android-21/arch-arm
checking whether the C compiler works... no
configure: error: in /home/vishal/Downloads/tensorflowandroid/tensorflow/tensorflow/contrib/makefile/downloads/protobuf': configure: error: C compiler cannot create executables See config.log' for more details
Config.log is attached
config.txt
Can someone look into it

This seems to be an error with your Android NDK setup. Looking at config.txt, I see things like:
/usr/lib/gcc/arm-linux-androideabi/4.7.4/../../../../arm-linux-androideabi/bin/ld: error: cannot find -llog
/usr/lib/gcc/arm-linux-androideabi/4.7.4/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lz
/usr/lib/gcc/arm-linux-androideabi/4.7.4/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lgnustl_static

suggesting that your NDK installation is incomplete or messed up as it is missing these libraries.
Closing this out since this doesn't seem to be an TensorFlow bug.


fix: more correct types on lucide-icons and helper-icons

individual lucide icons' props were untyped. added SvgProps type on icons and fixed the types with generate script and helper-icons. this fixes a type issue on takeout icons as well.

I think I just left SvgProps off IconProps, I fixed here:  f0362cdccb388bcb05f5b4b8d8acf6d398682867


Redesign Overflow Menu for Action Bar

Describe the solution you'd like
Seeing how the action bar below the address bar has a lot of free space, I think a redesign of the buttons and the overflow menu leads to usability improvements.
I tend to use New and New Pane quite often, not always reaching for the shortcuts though, especially since both are three-stroke-shortcuts. I’d suggest placing these buttons next to the Search and Toggle Preview Pane buttons.
I’d also like to see the open in Terminal button there, I haven’t found a shortcut for that one yet.
I believe this can be improved even further: The New Tab and New Window buttons can stay in that overflow menu, for all I care. But given how the New Tab button is already placed at a different spot, one where it makes sense from a usability point of view - in the tab bar, maybe consider adding the/a Copy Location button to the addres bar, to the side of it or only show it when the bar is selected, like the clear button. Something like this is common practice in many web apps, even GitHub itself has this, if you click the green ↓Code button in any repository, any of the links will have a Copy To Clipboard action right next to them.
Overall, the overflow menu seems a bit all over the place right now, especially since the dual-bar design (address bar and action bar) leaves a ton of free room for two more buttons without adding much clutter.
I might suggest a smart overflow menu which places more and more of the options in the action bar as the window grows bigger / hides them as the window shrinks. That way, clutter will be low when the window is small, but usability will be improved as the window gets bigger.
The Toggle Preview Pane may make more sense down in the Display Options menu at the bottom of the window, and personally I’d have the search button at the very right, with the expanding search bar pushing the other items to the side or overlaying them.

Perhaps follow the Windows 10X route, where there are some quick action buttons (with the Accent color) that change according to the folder or the item selected?

For example, when you select a file or a folder, a set of actions like Copy, Cut etc. appear below the navbar

For example, when you select a file or a folder, a set of actions like Copy, Cut etc. appear below the navbar

I believe these kinds of actions for a specific item are placed well in their respective context menus. What you showed is more friendly to touch users, but leads to A LOT of clutter on desktop and the tough decision what to leave in a context menu and what to put in the action bar.
For me, it’s all about the actions for the working folder aka the one whose path is in the action bar, listed in the overflow menu to the right, since most of the time that’s what you want to use without selecting a specific file.

Merging with #3265.


Write How To for Pub/Sub scopes

Write a How To document that shows how to use Publishing/Subscription scopes and Allowed Topics configurations on Pub Sub.

cc @RicardoNiepel

I will work on it
For reference: https://github.com/dapr/dapr/issues/1294


出现了UserWarning: torch.utils.checkpoin这个错误

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
warnings.warn(
/usr/local/lib/python3.10/dist-packages/torch/utils/checkpoint.py:459: UserWarning: torch.utils.checkpoint: please pass in use_reentrant=True or use_reentrant=False explicitly. The default value of use_reentrant will be updated to be False in the future. To maintain current behavior, pass use_reentrant=True. It is recommended that you use use_reentrant=False. Refer to docs for more details on the differences between the two variants.

Expected behavior
我直接使用docker启动的不应该有这种告警错误
System Info
dockerfile+docker-compose运行
chatGLM3-6b-32k
其他参数默认
Others
No response

忽略

ValueError: torch.utils.checkpoint: please pass in use_reentrant=True or use_reentrant=False explicitly. The default value of use_reentrant will be updated to be False in the future. To maintain current behavior, pass use_reentrant=True. It is recommended that you use use_reentrant=False. Refer to docs for more details on the differences between the two variants.
这样怎么解决？！！！

加一，请问有解决的吗？我的torch版本是2.3.0a0+ebedce2，transformer是4.41.2。前端没有选择checkpoint，为啥会激活checkpoint

+1 docker启动报错 ValueError: torch.utils.checkpoint: please pass in use_reentrant=True or use_reentrant=False explicitly. The default value of use_reentrant will be updated to be False in the future. To maintain current behavior, pass use_reentrant=True. It is recommended that you use use_reentrant=False. Refer to docs for more details on the differences between the two variants.

ValueError: torch.utils.checkpoint: please pass in use_reentrant=True or use_reentrant=False explicitly. The default value of use_reentrant will be updated to be False in the future. To maintain current behavior, pass use_reentrant=True. It is recommended that you use use_reentrant=False. Refer to docs for more details on the differences between the two variants.

您好有解决的办法吗，我也遇到了同样的问题

@AlmightYouth 看不到报错信息

@AlmightYouth 看不到报错信息

抱歉这个是在离线的环境下运行的，没法复制完整的报错信息出来，具体的报错信息是
ValueError: torch.utils.checkpoint: please pass in use_reentrant=True or use_reentrant=False explicitly. The default value of use_reentrant will be updated to be False in the future. To maintain current behavior, pass use_reentrant=True. It is recommended that you use use_reentrant=False. Refer to docs for more details on the differences between the two variants.
在执行到train/sft/workflow.py的train_result = trainer.train(resume_from_checkpoint=training_args.resume_from_checkpoint)时出现了以上问题，我尝试在train = CustionSeq2SeqTrainer 的初始化中加入 gradient_checkpointing=True,gradient_checkpointing_kwargs={"use_reentrant":False}，但是仍然无法解决这个问题

+1 使用单张 A100-80G 微调 qwen-7b-chat 出现以下报错：
ValueError: torch.utils.checkpoint: please pass in use_reentrant=True or use_reentrant=False explicitly. The default value of use_reentrant will be updated to be False in the future. To maintain current behavior, pass use_reentrant=True. It is recommended that you use use_reentrant=False. Refer to docs for more details on the differences between the two variants.
估计是随着 transformers 和 torch 版本的更新，以前的 warning 变成了 error，我使用的 transformers 版本：4.43.3

+1 使用单张 A100-80G 微调 qwen-7b-chat 出现以下报错： ValueError: torch.utils.checkpoint: please pass in use_reentrant=True or use_reentrant=False explicitly. The default value of use_reentrant will be updated to be False in the future. To maintain current behavior, pass use_reentrant=True. It is recommended that you use use_reentrant=False. Refer to docs for more details on the differences between the two variants.
估计是随着 transformers 和 torch 版本的更新，以前的 warning 变成了 error，我使用的 transformers 版本：4.43.3

+1，请问这个问题解决了吗，有合适的版本建议不


Android build failed - "Execution failed for task ':react-native-deepar:bundleReleaseLocalLintAar'."

-Execution failed for task ':react-native-deepar:bundleReleaseLocalLintAar'.
-Error while evaluating property 'hasLocalAarDeps' of task ':react-native-deepar:bundleReleaseLocalLintAar'
-Direct local .aar file dependencies are not supported when building an AAR. The resulting AAR would be broken because the classes and Android resources from any local .aar file dependencies would not be packaged in the resulting AAR. Previous versions of the Android Gradle Plugin produce broken AARs in this case too (despite not throwing this error). The following direct local .aar file dependencies of the :react-native-deepar project caused this error: {projectDir}\node_modules\react-native-deepar\android\libs\deepar-3.4.4.aar
react-native : 0.68.2.
react-native-deepar : ^0.10.5

Seems to me, the issue is related to #1 and #16.
Can you show me a reproducible example? An example project, maybe?

Hi @ridvanaltun thanks for checking. Please check sample project here.
=> Enter API key in App.js.
=> npx react-native-asset.
=> cd android && gradlew assembleRelease.

Hi @ridvanaltun thanks for checking. Please check sample project here. => Enter API key in App.js. => npx react-native-asset. => cd android && gradlew assembleRelease.

Thanks for the example project,
assembleRelease not work somehow, but when I try bundleRelease command, there was no problem. I investigated the issue like for 2 hours with no luck. I suggest you use ./gradlew bundleRelease command to generate release build until the issue resolve.

Can you please try any of the following solutions.
1.) https://stackoverflow.com/questions/60878599/error-building-android-library-direct-local-aar-file-dependencies-are-not-supp
2.) https://github.com/brim-borium/spotify_sdk/issues/99#issuecomment-878910598
Thanks

Found the solution. Instead of ./gradlew assembleRelease try ./gradlew app:assembleRelease. Now APK build is working fine even with ./gradlew assembleRelease.

I have the same issue , it does not work with  ./gradlew app:assembleRelease

what is the error?

I think expo is not supported. https://github.com/ridvanaltun/react-native-deepar/issues/5#issuecomment-1192980673


Typed box, persisting a value on the object?

Question
Is this following the recommended way to persist a single value in a typed box??
Code sample
var hiveBoxUserData = await Hive.openBox<UserData>('userData');
hiveBoxUserData.values.first.stats.all.impact += mission.impact;
await hiveBoxUserData.putAt(0, hiveBoxUserData.values.first);

ps hiveBoxUserData.values.first.stats.all.impact += mission.impact; seems to persist the value in memory, but on app reload it's lost.
Version
[√] Flutter (Channel dev, 1.22.0-12.0.pre, on Microsoft Windows [Version 10.0.19041.450], locale en-GB)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[√] Android Studio (version 4.0)
[√] VS Code (version 1.49.0)
[√] Connected device (1 available)

Hive version: hive: ^1.4.4, hive_flutter: ^0.3.1

I'm using something like this:
var user = Hive.box('user_info').get(0);
user.prop = newValue;
Hive.box('user_info').put(0, user);

You have to call Box.put to update persisted data.

@TheMisir thanks,
just to extend on this,
If I was to filter ...
return hiveBoxFlags.values.where((f) => f.missionUid == missionUid).first()
how do I get a reference to the index or key.. to be able to update and put?

You can use HiveObject.key property to get object's key. (You have to extend objects stored in box with HiveObject type).

you beat me to it.. ;-) could I suggest adding a link for typed objects and persistence the typeAdapter doc, and filters? ;-)
.. hadn't seen https://docs.hivedb.dev/#/custom-objects/hive_object
where in the type adapter you can class Custom extend HiveObject to gain save(), key etc..
var hiveBoxUserData = await Hive.openBox<UserData>('userData');
hiveBoxUserData.values.first.stats.all.impact += mission.impact;
await hiveBoxUserData.values.first.stats.all.save();

@HiveType(typeId: 12)
@JsonSerializable()
class Stat extends HiveObject {
  @HiveField(0)
  double impact;
...


Add test sharding support to the JUnit 5 runner

Since JUnit 5 test plans can have complicated structures, the sharding algorithm uses a hash of the test descriptor's unique ID to determine which shard to assign a given test to.
Dynamic tests and test templates are not affected by PostDiscoveryFilter and thus not individually sharded.

I went for an integration test instead, please take a look


TransactionAmount/SettleAmount should be a complex value vs simple value

When sending a paid request I was getting the following error.
// console.log(util.inspect(err.Body.Response.Errors)
{ Error:
{ Code: 'InvalidParams',
Message: 'transactionAmount.amount can not be null' } }
To fix this you can either flip Transaction amount to a param-data or expand out to TransactionAmount.Value && TransactionAmount.CurrencyCode (which looks to be the default in this file/module/plugin).

(deprecated: use aws-sdk)


uplift-version

Codecov Report

Merging #7 (615cd79) into main (ffc8621) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #7   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          148       148
=========================================
  Hits           148       148

Impacted Files
Coverage Δ

sqlalchemy_model_builder/__init__.py
100.00% <100.00%> (ø)

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 ffc8621...615cd79. Read the comment docs.


feat: Add max-global-retries option

Created based on PR https://github.com/str0zzapreti/pytest-retry/pull/37
As a user, I would like the ability to set an optional global maximum number of retries for tests. If the total count of retried tests due to failures exceeds this number, all subsequent tests will not be retried in the event of a failure. For example:
I have a suite of 10 tests which are all marked retries=2 and global max retries set to 5
The first test passes
The second test fails and is retried twice
The third test fails and is retried twice
The fourth test fails and although it is configured to retry twice, after the first retry the global limit is reached
Now if test 6, 7, 8, 9, and/or 10 fails, it will not be retried because of the global limit
This option should be configurable either via a command line option or through any valid pytest config file. If not specified, there is assumed to be no limit (i.e. the existing default behavior)

@deronnax I created an enhancement ticket for you to track the request facilitate discussion.

After reviewing https://github.com/str0zzapreti/pytest-retry/pull/37, my first thought is this implementation might not work as expected when using pytext-xdist for parallelization. Specifically, unless the retries are tracked on the server, each node would be individually counting and limiting retries. On the other hand, server-based tracking would make this more complicated and would probably introduce some slight loss of precision due to the asynchronous processing, so one or two extra retries might occur before each node received the signal to stop performing additional retries.
Another thought: your stated goal was to "better control the flakiness of the whole test suite", but I'm not sure I understand how this feature would achieve that goal, exactly. Would you mind elaborating a bit? To me, the purpose of this plugin is to help produce consistent, accurate results from test suites which must contend with unstable environments, 3rd party services, or other factors out of the tester's control. Ideally, allowing the tester or their colleagues to work on mitigating those factors in better ways. How would globally limiting retires help?
With that in mind, Pytest has a maxfail parameter which will halt all further test execution after a maximum number of test failures. I haven't tested that with pytest-retry myself, but I was curious to know if you'd tried this option already and what the result was. Any chance it would meet your needs?
Thanks again for the suggested feature, looking forward to hearing your thoughts! 😃

Hello, I am back.
No, --maxfail would not meet our needs because we want to run a maximum possible of tests as long as they only flake once. With maxfail, the test run would stop as soon as a test flakes twice. We are actually OK than the max-retries is not global but per process, so in the current state, the current implementation is correct, no?

Hello. I slightly updated the PR. We will test the current implementation, and use it for us if it works as expected. I understand that this might be too specific, so you are free to close the PR. Just a quick review for you would be very nice. The PR is short is simple. Thank you.

Hey, just catching up after a busy few weeks. My instinct says this might be a bit too niche as well, but I'll happily take another look at your PR and decide if it's something I want to incorporate. Either way, thank you!

@str0zzapreti I think you can close ;)

Sure thing! It looks like you had a working prototype for adding this functionality to your own repo, but let me know if there's another way I can help either with suggested implementation or by making this plugin more extensible if necessary.