Error installing in YottaDB r1.34: %YDB-E-SETECODE, Non-empty value assigned to $ECODE (user-defined error trap)

I have a newly-installed Debian 11 system, with a fresh installation of YottaDB r1.34. When I follow the installation instructions for the webinit routine, it terminates with:
[... lots of warnings ...]
%YDB-W-BLKTOODEEP, Block level too deep
%YDB-E-SETECODE, Non-empty value assigned to $ECODE (user-defined error trap)

Here's my complete process from a fresh Debian 11 install:
YottaDB installation (building from source because it seems to be unhappy with ICU version otherwise):
$ sudo apt update && \
    sudo apt upgrade -y && \
    sudo apt install -y build-essential icu-devtools git curl cmake pkg-config tcsh {libconfig,libelf,libicu,libncurses,zlib1g,libicu}-dev
 [...]
$ sudo reboot
 [... a short while later ...]
$ curl https://gitlab.com/YottaDB/DB/YDB/raw/master/sr_unix/ydbinstall.sh > /tmp/ydbinstall.sh
$ chmod +x /tmp/ydbinstall.sh
$ sudo /tmp/ydbinstall.sh --utf8 default --from-source --branch r1.34
 [...]
Since you are running systemd we changed memory settings and you need to restart
the systemd-logind service using this command "systemctl restart systemd-logind".

If your Desktop session is managed by the systemd-logind service (e.g., a Gnome
or Plasma desktop), restarting systemd-logind will restart your GUI. Save all
your work prior to issuing "systemctl restart systemd-logind".
YottaDB version r1.34 installed successfully at /usr/local/lib/yottadb/r134
YottaDB pkg-config file installed successfully at /usr/share/pkgconfig/yottadb.pc
$ sudo systemctl restart systemd-logind

YottaDB environment:
$ source /usr/local/lib/yottadb/r134/ydb_env_set
$ yottadb -version
YottaDB release:         r1.34
Upstream base version:   GT.M V6.3-011
Platform:                Linux x86_64
Build date/time:         2022-08-29 20:02
Build commit SHA:        f2f77cc184d9fe2e272d7b1d39b64434e9769804

Restoring webinit:
$ curl -L https://github.com/shabiel/M-Web-Server/releases/download/1.1.5/webinit.rsa > /tmp/webinit.rsa
$ yottadb -dir

YDB>W $ZRO
/home/mwilson/.yottadb/r1.34_x86_64/o/utf8*(/home/mwilson/.yottadb/r1.34_x86_64/r /home/mwil
son/.yottadb/r) /usr/local/lib/yottadb/r134/utf8/libyottadbutil.so
YDB>D ^%RI

Routine Input Utility - Converts RO file to *.m files.

Formfeed delimited <No>?
Input device: <terminal>: /tmp/webinit.rsa

Routines

Output directory : /home/mwilson/.yottadb/r

webinit

Restored 525 lines in 1 routine.

Running webinit:
YDB>D ^webinit
         Q:$$CACHE $ZU(168)
                    ^-----
                At column 13, line 66, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVFCN, Invalid function name
         I $$CACHE S %=$ZU(168,^%SYS("TempDir")) QUIT  ; Cache
                        ^-----
                At column 17, line 73, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVFCN, Invalid function name
         I $$CACHE N % S %=$ZU(168,DIR) QUIT
                            ^-----
                At column 21, line 79, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVFCN, Invalid function name
         I $P($P($ZV,") ",2),"(")<2012 S NMSP=$ZU(5)
                                               ^-----
                At column 40, line 91, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVFCN, Invalid function name
         I $P($P($ZV,") ",2),"(")>2011 S NMSP=$NAMESPACE
                                               ^-----
                At column 40, line 92, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVSVN, Invalid special variable name
         ZN "%SYS" ; Go to SYS
         ^-----
                At column 2, line 96, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVCMD, Invalid command keyword encountered
         N % S %=##Class(Config.Namespaces).Get(NMSP,.PROP) ; Get all namespace properties
                 ^-----
                At column 10, line 100, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         I '% W !,"Error="_$SYSTEM.Status.GetErrorText(%) S $EC=",U-CONFIG-FAIL," QUIT
                                  ^-----
                At column 27, line 101, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         S %=##class(Config.Configuration).GetGlobalMapping(NMSP,G,"",DBG,DBG)
             ^-----
                At column 6, line 110, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         I '% S %=##class(Config.Configuration).AddGlobalMapping(NMSP,G,"",DBG,DBG)
                  ^-----
                At column 11, line 111, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         I '% W !,"Error="_$SYSTEM.Status.GetErrorText(%) S $EC=",U-CONFIG-FAIL," QUIT
                                  ^-----
                At column 27, line 112, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         N % S %=##Class(Config.MapRoutines).Get(NMSP,G,.PROPRTN)
                 ^-----
                At column 10, line 115, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         I '% S %=##Class(Config.MapRoutines).Create(NMSP,G,.PROPRTN)
                  ^-----
                At column 11, line 117, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         I '% W !,"Error="_$SYSTEM.Status.GetErrorText(%) S $EC=",U-CONFIG-FAIL," QUIT
                                  ^-----
                At column 27, line 118, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         ZN NMSP ; Go back
         ^-----
                At column 2, line 119, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVCMD, Invalid command keyword encountered
         N $NAMESPACE S $NAMESPACE="%SYS"
            ^-----
                At column 5, line 127, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVSVN, Invalid special variable name
         N $NAMESPACE S $NAMESPACE="%SYS"
                         ^-----
                At column 18, line 127, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVSVN, Invalid special variable name
         n % s %=##class(Security.SSLConfigs).Exists("encrypt_only",.config,.status) ; check if conf
ig exists
                 ^-----
                At column 10, line 129, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         . s %=##class(Security.SSLConfigs).Create("encrypt_only",.prop) ; create a default ssl conf
ig
               ^-----
                At column 8, line 132, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         . i '% w $SYSTEM.Status.GetErrorText(%) s $ec=",u-cache-error,"
                         ^-----
                At column 18, line 133, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         . s %=##class(Security.SSLConfigs).Exists("encrypt_only",.config,.status) ; get config
               ^-----
                At column 8, line 134, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         e  s %=config.Activate()
                      ^-----
                At column 15, line 135, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         d config.TestConnection("encrypted.google.com",443,.rtn)
                 ^-----
                At column 10, line 139, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         set httprequest=##class(%Net.HttpRequest).%New()
                         ^-----
                At column 18, line 151, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         . set httprequest.Https=1
                          ^-----
                At column 19, line 153, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EQUAL, Equal sign expected but not found
         . set httprequest.SSLConfiguration="encrypt_only"
                          ^-----
                At column 19, line 154, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EQUAL, Equal sign expected but not found
         set httprequest.Server=server
                        ^-----
                At column 17, line 159, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EQUAL, Equal sign expected but not found
         if port set httprequest.Port=port
                                ^-----
                At column 25, line 160, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EQUAL, Equal sign expected but not found
         set httprequest.Timeout=5
                        ^-----
                At column 17, line 161, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EQUAL, Equal sign expected but not found
         new status set status=httprequest.Get(filepath)
                                          ^-----
                At column 35, line 162, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         new response set response=httprequest.HttpResponse.Data
                                              ^-----
                At column 39, line 163, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         new sysfile set sysfile=##class(%Stream.FileBinary).%New()
                                 ^-----
                At column 26, line 164, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         set status=sysfile.FilenameSet(filename)
                           ^-----
                At column 20, line 165, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         set status=sysfile.CopyFromAndSave(response)
                           ^-----
                At column 20, line 166, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         set status=sysfile.%Close()
                           ^-----
                At column 20, line 167, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-SPOREOL, Either a space or an end-of-line was expected but not found
         D $SYSTEM.Process.SetZEOF(1) ; Cache stuff!!
           ^-----
                At column 4, line 262, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-LABELEXPECTED, Label expected in this context
         O ROPATH:("RS"):0 E  S $EC=",U-ERR-OPEN-FILE,"
                   ^-----
                At column 12, line 267, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-DEVPARPARSE, Error parsing device parameter specification
         O DIR_"test.txt":"NWS":0
                          ^-----
                At column 19, line 300, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-DEVPARPARSE, Error parsing device parameter specification
         C DIR_"test.txt":"D"
                          ^-----
                At column 19, line 304, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-DEVPARPARSE, Error parsing device parameter specification
         . O TCPIO:(:PORT:"ACT"):2
                    ^-----
                At column 13, line 385, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-DEVPARPARSE, Error parsing device parameter specification
         D CHKTF^%ut('$D(^$R("%ZVEMD")))
                          ^-----
                At column 19, line 451, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-GBLNAME, Either an identifier or a left parenthesis is expected after a ^ in this con
text
         N NS S NS=$NAMESPACE
                    ^-----
                At column 13, line 460, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVSVN, Invalid special variable name
         ZN "%SYS"
         ^-----
                At column 2, line 461, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVCMD, Invalid command keyword encountered
         S %=##class(Config.Configuration).AddGlobalMapping(NS,"%Z*","",NS,NS)
             ^-----
                At column 6, line 462, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         S A("Database")=NS S %=##Class(Config.MapRoutines).Create(NS,"%Z*",.A)
                                ^-----
                At column 25, line 463, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-EXPR, Expression expected but not found
         ZN NS
         ^-----
                At column 2, line 464, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-INVCMD, Invalid command keyword encountered
         D CHKTF^%ut($D(^$R("%ZVEMD")))
                         ^-----
                At column 18, line 467, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-GBLNAME, Either an identifier or a left parenthesis is expected after a ^ in this con
text
         D:$D(^$R(R))  F  S R=$O(^$R(R)) Q:R=""  Q:($P(R,NMSP,2)="")  D
               ^-----
                At column 8, line 475, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-E-GBLNAME, Either an identifier or a left parenthesis is expected after a ^ in this con
text
         . X "ZR  ZS @R"
           ^-----
                At column 4, line 476, source module /home/mwilson/.yottadb/r/webinit.m
%YDB-W-BLKTOODEEP, Block level too deep
%YDB-E-SETECODE, Non-empty value assigned to $ECODE (user-defined error trap)

@racingmars Thank you for using YottaDB.
I am interested in this statement:

YottaDB installation (building from source because it seems to be unhappy with ICU version otherwise):

We (I work for YottaDB) test on Debian 11, so I am interested in learning about the ICU issue.
I figured out the problem: The mws.rsa file in the release got an encoding corruption, as I added some Japanese text to test UTF-8 handling, but somehow the Japanese isn't showing up correctly.
I am moving this project (slowly) to https://gitlab.com/YottaDB/Util/YDB-Web-Server, and should be done in the next couple of weeks I think. Do you need this fixed sooner rather than later? Can you tell me what do you plan to use the M Web Server for, or is it just a hobby thing for now?

@racingmars I just fixed the issue. Turns out a script I was using didn't support UTF-8; It's now fixed. Please close the issue after you retry this.

@racingmars I just fixed the issue. Turns out a script I was using didn't support UTF-8; It's now fixed. Please close the issue after you retry this.

Thanks, that did the trick! Installs correctly now and I can access the web service.

I am interested in this statement:

YottaDB installation (building from source because it seems to be unhappy with ICU version otherwise):

We (I work for YottaDB) test on Debian 11, so I am interested in learning about the ICU issue.

If that's unexpected, I'll go ahead and reproduce it when I have a chance to set up another new machine and open an issue over in the YDB repo. I'm going to be mostly away from the computer for the next few days but I'll circle back with the details when I can.

Can you tell me what do you plan to use the M Web Server for, or is it just a hobby thing for now?

Just a hobby thing :-)

If that's unexpected...
ICU is a pain to work with, so it usually is an issue of not installing the right packages, or something like that. So please create an issue, and we have to probably improve the documentation to warn people on what to install.


It is necessary to create PSL predicates to reflect basic ontology relations?

We need to check if it is needed or good for our domain to have ontology predicates in our PSL model such as domain, range, inverse, etc. This paper utilizes them in their PSL model.
Also, this paper proposes a way of using the ontological knowledge in the PSL model.

Can you please elaborate with an example. i tried to read papers but could not understand the way to use it.

Can you initially reproduce this again in the code?
For examples about this, you can check the initial OntologyAlignment example. There are predicates for domain, range and subclass. For now, we should include only those.

Updated:
Please add ontology folder path in config.ttl
uri:URI "C:/Users/omar/Documents/workspace-sts-3.7.0.RELEASE/Alligator-PSL/resources/".
so now we have hasDomain and hasRange and also hasType for current data so we can map it on to hasDomain and hasRange
However, i am not sure how to write rules for them. Can you take a look for rules?

In the current version hasDomain and hasRange does not contain facts when converting. Can you please fix this?

you must include the ontology folder in config.ttl , then it will work. It reads this information from ontology file.
uri:URI "C:/Users/omar/Desktop/SemCPS-/resources/".

I did it and still not working.

hi pull first

From: Irlan Grangel-Gonzalez<EMAIL_ADDRESS>Sent: Friday, July 28, 2017 12:27:58 AM
To: i40-Tools/SemCPS
Cc: omar; Assign
Subject: Re: [i40-Tools/SemCPS] It is necessary to create PSL predicates to reflect basic ontology relations? (#9)
I did it and still not working.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/i40-Tools/SemCPS/issues/9#issuecomment-318639174, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALmM8woygk4Q3tAwch-Lnv9KkvvwtDS3ks5sSdPNgaJpZM4NNTr7.


For some reason, the backgrounds aren't being restored when the project is loaded from file.

It seems to only happen in certain situations. Still trying to figure out the cause.


Speculative sampling

Works with DollyV2 for machines with at least 64GB local memory. By default, we use GPT2 for smaller machines.
Leveraging speculative sampling with KV caching, this notebook's code will generate text using standard autoregressive sampling and speculative sampling and compare the times needed to generate N tokens. By default, N is set to 100. Another parameter K is set to 5 but can be adjusted to determine the number of candidate tokens to generate from the smaller draft model.
This code uses gradio to provide an interface labeling the models used and handling the input.

@haim-barad please check the CI failures as it seems some of the are quite easy to fix

Code_check failure is another notebook. Spelling errors are ignoring the  tag (as noted in your instructions).

@haim-barad, for spell check you need to add unknown words reported by tools into vocabulary. You can find more info about that contributing guide

I had added the required entries and now I see the latest push created some conflicts, I apologize for this, but can someone with permissions do a merge?

code check is failing for 263-latent-consistency-models-image-generation, not this notebook.

Both code_check and docker_treon are failing on other notebooks, not because of this PR. Please approve. Thanks.

There's still a small link to fix. I see this was renumbered to 266. There's a "open in Collab" button in the readme - the link needs to be 266 instead of 265. Can one of you fix it to avoid the review process?


Unusable checkpoints

Hi,
Very often when I try to restart training from an existent checkpoint I face the exception below.
When it happens I start trying the previous checkpoints until I find one that works.
Has anyone seen this ?  Any clue on what might be wrong ?
Caused by op 'ppo/observe-timestep/store/ScatterUpdate', defined at:
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/user/project/main.py", line 189, in <module>
    main()
  File "/home/user/project/main.py", line 131, in main
    seconds=600
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/agents/ppo_agent.py", line 155, in __init__
    entropy_regularization=entropy_regularization
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/agents/learning_agent.py", line 141, in __init__
    batching_capacity=batching_capacity
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/agents/agent.py", line 80, in __init__
    self.model = self.initialize_model()
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/agents/ppo_agent.py", line 183, in initialize_model
    likelihood_ratio_clipping=self.likelihood_ratio_clipping
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/models/pg_prob_ratio_model.py", line 88, in __init__
    gae_lambda=gae_lambda
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/models/pg_model.py", line 98, in __init__
    requires_deterministic=False
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/models/distribution_model.py", line 90, in __init__
    discount=discount
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/models/memory_model.py", line 114, in __init__
    reward_preprocessing=reward_preprocessing
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/models/model.py", line 221, in __init__
    self.setup()
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/models/model.py", line 274, in setup
    independent=independent
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/models/memory_model.py", line 607, in create_operations
    independent=independent
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/models/model.py", line 1147, in create_operations
    self.create_observe_operations(reward=reward, terminal=terminal)
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/models/model.py", line 1083, in create_observe_operations
    reward=reward
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorflow/python/ops/template.py", line 427, in __call__
    return self._call_func(args, kwargs)
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorflow/python/ops/template.py", line 370, in _call_func
    result = self._func(*args, **kwargs)
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/models/memory_model.py", line 507, in tf_observe_timestep
    reward=reward
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorflow/python/ops/template.py", line 419, in __call__
    return self._call_func(args, kwargs)
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorflow/python/ops/template.py", line 364, in _call_func
    result = self._func(*args, **kwargs)
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorforce/core/memories/queue.py", line 172, in tf_store
    updates=state
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorflow/python/ops/state_ops.py", line 294, in scatter_update
    use_locking=use_locking, name=name)
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorflow/python/ops/gen_state_ops.py", line 1108, in scatter_update
    use_locking=use_locking, name=name)
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
    op_def=op_def)
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3414, in create_op
    op_def=op_def)
  File "/home/user/.virtualenvs/project/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1740, in __init__
    self._traceback = self._graph._extract_stack()  # pylint: disable=protected-access

InvalidArgumentError (see above for traceback): Must have updates.shape = indices.shape + params.shape[1:] or updates.shape = [], got updates.shape [533,80,80,4], indices.shape [183], params.shape [5000,80,80,4]
	 [[Node: ppo/observe-timestep/store/ScatterUpdate = ScatterUpdate[T=DT_FLOAT, Tindices=DT_INT32, use_locking=true, _device="/job:localhost/replica:0/task:0/device:GPU:0"](ppo/initialize/latest/initialize/state-state, ppo/observe-timestep/store/mod/_589, ppo/strided_slice, ^ppo/observe-timestep/store/AssignSub/_593)]]

Is this for the most recent GitHub version of TensorForce? As far as I know, a related problem was fixed at some point...

I'm currently using: tensorforce==0.4.2 installed via pip.
Should I install from master ?

I think you meant this one: https://github.com/reinforceio/tensorforce/issues/421
I'll try the master version.

It was indeed #421
Thanks.


Feature Request: allow overriding private DNS zones in complete_multi_region

Is there an existing issue for this?

[x] I have searched the existing issues

Infrastructure as Code Type? (Required)
terraform
Starter Module? (Required)
terraform - complete_multi_region
Use Case (Required)
As a user I'd like to override the DNS zones that are deployed.
Proposed Solution (Required)
Allow a parameter to be used instead of null here: https://github.com/Azure/alz-terraform-accelerator/blob/aeaa83416a1c58ee8524bf6aa3117c6395865c64/templates/complete_multi_region/modules/hub-and-spoke-vnet/main.tf#L55
This will allow users to override the list of DNS zones deployed.
Important Factoids (Optional)
No response
References (Optional)
No response

Good idea, will implement. :)


Fix typo in example error message

The error message on line 311 said "y must be... when it was supposed to be "x must be...
Pull Request Check List
This is just a reminder about the most common mistakes.  Please make sure that you tick all appropriate boxes.  But please read our contribution guide at least once, it will save you unnecessary review cycles!

[ ] Added tests for changed code.
[ ] New features have been added to our Hypothesis testing strategy.
[x] Updated documentation for changed code.
[x] Documentation in .rst files is written using semantic newlines.
[ ] Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.
[ ] Changes (and possible deprecations) are documented in CHANGELOG.rst.

If you have any questions to any of the points above, just submit and ask!  This checklist is here to help you, not to deter you from contributing!

Thanks!


Modified scrollbar

On hover, only the color of the scroll bar should change and not the width of the track.
Scroll bar should not appear in pre-loader

Changes done.

The scrollbar is absent on the Research Page

The scroll bar still appears during the preloader (fixed in the current version on master branch)

I would suggest to make a fresh PR after pulling all the recent changes if required or else make a squash commit to this one itself

This issue was exclusively for the react version. Please have a look at the Issue Titles and Descriptions carefully.
Make sure you follow the PR Guidelines in the Contributing.MD


pre-loop refactor

Added a Value property to ResourceDeclarationSyntax and ModuleDeclarationSyntax to have one of the following values:

ObjectSyntax - this is created by the parser for non-conditional resources and modules.
IfConditionSyntax - used for conditional resources and modules.

Also modified IfConditionSyntax to have a Body property of type ObjectSyntax.
This refactor makes it easier to add the currently spec'd out syntax for resource and module loops. (ForSyntax will be added as a 3rd possible value in the list above.) In addition, we will be able to compose IfCondition with ForSyntax for conditional loops without creating new AST node types.

Just rebased on top of decorators and module path completions.

Just rebased on top of decorators and module path completions.

Codecov Report

Merging #1399 (cca2edc) into main (98ad149) will increase coverage by 0.47%.
The diff coverage is 85.30%.

@@            Coverage Diff             @@
##             main    #1399      +/-   ##
==========================================
+ Coverage   94.76%   95.23%   +0.47%
==========================================
  Files         351      347       -4
  Lines       18188    18107      -81
  Branches       14        0      -14
==========================================
+ Hits        17235    17245      +10
+ Misses        953      862      -91

Flag
Coverage Δ

dotnet
95.23% <85.30%> (-0.03%)
:arrow_down:

typescript
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/Bicep.Core/Syntax/SyntaxRewriteVisitor.cs
71.20% <73.75%> (-0.12%)
:arrow_down:

...piler/Rewriters/ParentChildResourceNameRewriter.cs
91.11% <81.81%> (-1.66%)
:arrow_down:

src/Bicep.Core/TypeSystem/DeclaredTypeManager.cs
95.27% <88.46%> (-1.73%)
:arrow_down:

...p.Decompiler/Rewriters/DependsOnRemovalRewriter.cs
95.94% <95.45%> (-1.03%)
:arrow_down:

src/Bicep.Core/Syntax/ModuleDeclarationSyntax.cs
97.56% <97.50%> (-2.44%)
:arrow_down:

src/Bicep.Core/Syntax/ResourceDeclarationSyntax.cs
97.56% <97.50%> (-2.44%)
:arrow_down:

src/Bicep.Core/Emit/TemplateWriter.cs
98.05% <100.00%> (+0.03%)
:arrow_up:

src/Bicep.Core/Parsing/Parser.cs
97.80% <100.00%> (-0.02%)
:arrow_down:

src/Bicep.Core/PrettyPrint/DocumentBuildVisitor.cs
100.00% <100.00%> (ø)

src/Bicep.Core/Semantics/NameBindingVisitor.cs
99.13% <100.00%> (+0.02%)
:arrow_up:

... and 11 more

Codecov Report

Merging #1399 (cca2edc) into main (98ad149) will increase coverage by 0.47%.
The diff coverage is 85.30%.

@@            Coverage Diff             @@
##             main    #1399      +/-   ##
==========================================
+ Coverage   94.76%   95.23%   +0.47%
==========================================
  Files         351      347       -4
  Lines       18188    18107      -81
  Branches       14        0      -14
==========================================
+ Hits        17235    17245      +10
+ Misses        953      862      -91

Flag
Coverage Δ

dotnet
95.23% <85.30%> (-0.03%)
:arrow_down:

typescript
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/Bicep.Core/Syntax/SyntaxRewriteVisitor.cs
71.20% <73.75%> (-0.12%)
:arrow_down:

...piler/Rewriters/ParentChildResourceNameRewriter.cs
91.11% <81.81%> (-1.66%)
:arrow_down:

src/Bicep.Core/TypeSystem/DeclaredTypeManager.cs
95.27% <88.46%> (-1.73%)
:arrow_down:

...p.Decompiler/Rewriters/DependsOnRemovalRewriter.cs
95.94% <95.45%> (-1.03%)
:arrow_down:

src/Bicep.Core/Syntax/ModuleDeclarationSyntax.cs
97.56% <97.50%> (-2.44%)
:arrow_down:

src/Bicep.Core/Syntax/ResourceDeclarationSyntax.cs
97.56% <97.50%> (-2.44%)
:arrow_down:

src/Bicep.Core/Emit/TemplateWriter.cs
98.05% <100.00%> (+0.03%)
:arrow_up:

src/Bicep.Core/Parsing/Parser.cs
97.80% <100.00%> (-0.02%)
:arrow_down:

src/Bicep.Core/PrettyPrint/DocumentBuildVisitor.cs
100.00% <100.00%> (ø)

src/Bicep.Core/Semantics/NameBindingVisitor.cs
99.13% <100.00%> (+0.02%)
:arrow_up:

... and 11 more


Incomplete python sample

The python example for Standalone language identification is incomplete - parts for audio config and language list are completely missing.
Also please add to results output also Confidence value, not only language detected (it is available in result.properties[speechsdk.PropertyId.SpeechServiceResponse_JsonResult]).

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7953b10a-1a9e-2607-1fdd-4e0fd1336f5b
Version Independent ID: 9197efed-fb78-daf4-2fae-795f8b0f0e6d
Content: Language identification - Speech service - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/language-identification.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @laujan
Microsoft Alias: lajanuar

@marki555 Thanks for the question. We are investigating the issue and will update you shortly.

@marki555 Thanks, Please follow the sample in GitHub for python. https://github.com/Azure-Samples/cognitive-services-speech-sdk/blob/master/samples/python/console/speech_language_detection_sample.py

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


swift deploy mini-internvl-chat-2b-v1_5 能部署成功，但是调用会失败

参照mutlimodal-deployment.md，
curl http://localhost:8000/v1/chat/completions \ -H "Content-Type: application/json" \ -d '{ "model": "mini-internvl-chat-2b-v1_5", "messages": [{"role": "user", "content": "Picture 1:https://modelscope-open.oss-cn-hangzhou.aliyuncs.com/images/rose.jpg\nWhat kind of flower is in the picture and how many are there?"}], "max_tokens": 256, "temperature": 0 }',
报错内容:    local variable 'labels' referenced before assignment

fixed


Fix(49198): Added missing definition for Atomics.waitAsync and es2022 sharedmemory file

Fixes #
This issues relates to #49198
I was not able to try the code sample to be sure about the return value of waitAsync when async flag is true. Perhaps Eyal-Shalev could help me in this one :)

Oh, wait. es2022.sharedmemory needs to be added to the list of libs (I think in program.ts?) and the new baselines need to be added after the test passes.

I searched for occurencies of es2020.sharedmemory and there was missing es2022.sharedmemory declaration in commandLineParser
but still wont pass in tests 😢 maybe I'm looking in the wrong place ?

Well, the error has changed to indicate missing baselines. Run gulp baseline-accept and commit the resulting files. Then I can see what errors you're getting.

tried the command but it did not changed nothing 😭
the screenshot above shows how this I'm in the repo as it is here on github.
I have deleted the folder and installed everthing again and tried again and still does not updates other files running  gulp baseline-accept

Ah. You need to
$ gulp runtests --t=es2022SharedMemory

first. Actually, gulp runtests-parallel to get all the test failures, in case there's more than one.

Awesome! gulp runtests --t=es2022SharedMemory showed the errors and I have adjusted them.
Also I had commited the new base lines is that all right ?

reactJsxReactResolvedNodeNext.tsx still broken =(
I'll try checking out the branch locally.

what was wrong ? if I may ask.

I think there were two related tests -- reactJsxResolvedNodeNext and reactJsxResolvedNodeNextEsm -- and you had only updated one baseline. I updated the other one.


[Feature Request]: Update Node.js version to 18

Feature description
Looks like Node.js 14 is losing maintenance in April, so updating is becoming a concern.
https://github.com/nodejs/release#release-schedule
There are UBI 8/9 base images for Node.js 18 available.
https://catalog.redhat.com/software/containers/search?product_listings_names=Node.js&p=1&q=nodejs-18
Describe alternatives you've considered
No response
Anything else?
No response

Good catch Chris -- we should look into updating.

This will need to get iterations on it before we can merge it -- won't make this release, should be able to take Lucas' work and merge it at the start of the next sprint (March 13th)


-- fix: viewLogs button query no data

[General Service]-[Service]-[Trace]-[View Logs] button query fixed

Confirm working

@binbin666 Please update submodule of main repo to make this works.


Job from all to alphanumeric

Change job regex to alphanumeric only
Update Job test and test utility classes to support above change (CommandUtil and JSON files)

Codecov Report

Merging #79 (ca7a0cc) into master (1a09b14) will increase coverage by 0.07%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #79      +/-   ##
============================================
+ Coverage     72.93%   73.00%   +0.07%
- Complexity      428      429       +1
============================================
  Files            74       74
  Lines          1293     1293
  Branches        135      135
============================================
+ Hits            943      944       +1
  Misses          316      316
+ Partials         34       33       -1

Impacted Files
Coverage Δ

...main/java/seedu/linkedout/model/applicant/Job.java
90.00% <ø> (+10.00%)
:arrow_up:

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 1a09b14...ca7a0cc. Read the comment docs.


Classic installer fails with "the parameter is incorrect" on Windows 11

Description
I am unable to install the application on Windows 11 due to an error in the installer.
Steps To Reproduce
Download from https://cdn.files.community/files/download/Files.Stable.exe
Run the installer
Installation does not proceed and stops with "The parameter is incorrect"

Requirements
A more specific error would be helpful and may possibly lead to a solution.
Files Version
<IP_ADDRESS>
Windows Version
21H2 build 22000.2538
Log File
I am unable to locate a log file.  If anyone has advice on how to log the failed installation, I'm willing to provide more information.

If you're using an unofficial Windows install (AtlasOS, ReviOS, disabled Windows update system, removed the Microsoft store, etc.) these are not supported but you can try the below.

Type Services in Windows start menu > Open the Windows update and Delivery optimization services > Set startup type to automatic > Click ok > restart Windows and try installing again.

You can also try

Opening PowerShell (Windows default not PowerShell 7) as administrator
Run this command
Add-AppxPackage -AppInstallerFile https://cdn.files.community/files/stable/Files.Package.appinstaller
See if Files is in the start menu all apps section

If the above doesn't work you won't be able to use Files without reinstalling Windows using the official installer from https://www.microsoft.com/software-download/windows11.

2 (ii) was the solution.  I am not running anything non-standard, however, it looks like Delivery optimisation is enabled.

OK, old version was still there after downloading and running https://cdn.files.community/files/stable/Files.Package.appinstaller.
Powershell option shown in the attachment:

As you can see from the output, we don't have any additional info to display. Anyways, can you confirm if Files is installed on your device?


Comparer

Hi Tim,
I have modified the label options in plot_model and plot_fit_and_residuals so that we can choose if we want legends in each subplot or only the general legend showing which color corresponds to each model.
Macla

I think this is a good idea. Maybe we can collect more plotting related things and merge them together if that is fine?


Logs advanced patterns

Currently, the functionality involves viewing only ERROR and WARN patterns at the log level.  This is a big problem for services with high fault tolerance where there are errors being processed.  It is quite normal for them that the error is processed and entered into the log at the INFO level.  At the same time, there is a big problem of excessive logging, which needs to be solved as part of troubleshooting the logging systems themselves.  I would like to be able to fine-tune new patterns in real time.  Or at least expand the current set to INFO level

@kirillyu the Coroot uses a self-written logparser, most likely you need to create a discussion in its project https://github.com/coroot/logparser

I will copy it there, ok


choosealicense.com and SPDX mismatch for CECILL-2.1

I noticed that CECILL-2.1 appears in French in choosealicense.com, while SPDX uses the English version. This is not on par with some of the requirements in the "Adding a license" documentation [1], such as "the text of the license should match the corresponding text found in spdx/license-list-data".
[1]https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license

This is known https://github.com/github/choosealicense.com/pull/527#issuecomment-348392371 but I don't think we have an open issue for it, so thanks!

Ok

nschaeff:patch-1

I don't want to remove the French version, so waiting on a solution that allows for both.


Adding simple express app with basic crud functionality based on the schema

In the readme is the details on how to deploy the application in OpenShift. It requires a running mongodb and a secret with the db url/credentials.
This is a basic implementation which only handles the crud operations for the schema provided in this repo. Additional functionality and testing are desired, but wanted to get out an initial app for a starting point.
Edit:
Important note, in order to test this before it is merged in, the .openshift-applier/params/omp-be/build needs to be set to use the logandonley/omp-be:node fork/branch.

Thanks for the suggestions @oybed I've made those changes.

Everything looks good from my perspective. I'll wait for @oybed and @springdo to sign off on this before merging.

Updated per everyone's suggestions.


Use Azure Compute Gallery images from subscription?

I don't see it documented anywhere, but is it possible to use your own custom images from an Azure Computer Gallery in the subscription? If so, how would I do that?

Theoretically, if you have an URN associated, and it's accessible to you, you can use it. The image URN is translated to an Azure ARM image reference consisting of an Offer, Publisher, SKU and version.
I am sorry about the really late reply!

feel free to re-open this issue if you need to.

Okay, I completely missed the point of what you were saying, but hopefully #16 actually fixes this and you can simply reference the image by ID instead of URN.


Support environment variables in Favorites.conf

Could you please add support for environment variable expansion in Favorites.conf?
Any type of notation is fine, but it would be really helpful because I use multiple computers (home and work) and both share a common configuration repository.  The use of environment variables allows for all of this to happen (i.e., same environment variable on each machine, but different values).  FWIW, the USERPROFILE environment variable is the most important.
code = "%USERPROFILE%\scoop\apps\vscode\current\Code.exe"
code = "$env:USERPROFILE\scoop\apps\vscode\current\Code.exe"
code = "$USERPROFILE\scoop\apps\vscode\current\Code.exe"

I can add support for environment variables, using the first variant. Hopefully within a week.

The new version is now online.

@stax76 - Thanks for doing that!  I tried it out and it works.  This may be due to me not understanding how to update Flow Launcher plugins, but I couldn't get it to update - actually had to uninstall it and then reinstall it to get your latest version.  It would show there was a new version available, but then it would fail to update saying something about already having the same or newer version installed.  It still says version 1.4.0 is installed.  I'm guessing it's because the plugin.json file needs to have the version number increased from 1.4.0 to 1.5.0.

Sorry, I missed updating the plugin.json file. I've re-uploaded it now with updated plugin.json file.

No worries.  That did the trick!


Android Release version cannot be build: resource android:attr/lStar not found

When trying to build a release version for Android, the following error occurs:

Execution failed for task ':react-native-document-scanner-plugin:verifyReleaseResources'.

A failure occurred while executing com.android.build.gradle.tasks.VerifyLibraryResourcesTask$Action
Android resource linking failed
ERROR:/Users/users/Projects/MyProject/app/node_modules/react-native-document-scanner-plugin/android/build/intermediates/merged_res/release/values/values.xml:2753: AAPT: error: resource android:attr/lStar not found.

build.gradle contains
    ext {
        buildToolsVersion = "33.0.0"
        minSdkVersion = 29
        compileSdkVersion = 33
        targetSdkVersion = 33

        // We use NDK 23 which has both M1 support and is the side-by-side NDK version from AGP.
        ndkVersion = "23.1.7779620"

        ...
   }

used versions:
"react-native": "0.71.1",
"react-native-document-scanner-plugin": "^0.7.3"

https://github.com/WebsiteBeaver/android-document-scanner/blob/master/documentscanner/build.gradle
compileSdk 30

defaultConfig {
    minSdk 21
    targetSdk 30

    testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    consumerProguardFiles "consumer-rules.pro"
}

Try changing 33 to 30.

https://github.com/WebsiteBeaver/android-document-scanner/blob/master/documentscanner/build.gradle
compileSdk 30

defaultConfig {
    minSdk 21
    targetSdk 30

    testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    consumerProguardFiles "consumer-rules.pro"
}

Try changing 33 to 30.

Hi @dmarcs , in your package ?


Does not work in published Databricks html

Story does not appear in the html which is published by databricks:
Uncaught SecurityError: Failed to read the 'cookie' property from 'Document': The document is sandboxed and lacks the 'allow-same-origin' flag.

fixed in vizzu-story 0.2.1


mvp-cockpit: S3 actor fails with KeyError: 'pop from an empty set'

Blueprint:
g8client__cl:
  url: uk-g8-1.demo.greenitglobe.com
  login: yves
  password: ****
  account: Account of Yves

vdc__vdc4s3:
  g8client: cl
  account: Account of Yves
  location: uk-g8-1

sshkey__main:

disk.ovc__disk1:
  size: 1000

s3__s3server:
  vdc: vdc4s3
  sshkey: main
  disk:
    - 'disk1'
  domain: 'mystorage.com'
  key.access: 'access'
  key.secret: 'secret'

actions:
  - action: 'install'

Result of ays run:
Error of job: fs.btrfs!data (autoscale):
*TRACEBACK*********************************************************************************
Traceback (most recent call last):
  File "/opt/jumpscale8//lib/JumpScale/core/processmanager/ProcessManagerFactory.py", line 195, in start
    res = self.method(**self.args)
  File "/tmp/actions/fs.btrfs/autoscale.py", line 36, in action
    disk_name = added.pop()
KeyError: 'pop from an empty set'

******************************************************************************************

**** TRACEBACK ***
Traceback (most recent call last):
  File "/usr/local/bin/ays", line 538, in <module>
    cli()
  File "/usr/local/bin/ays", line 46, in run
    run.execute()
  File "/opt/jumpscale8/lib/JumpScale/baselib/jobcontroller/Run.py", line 261, in execute
    raise j.exceptions.RuntimeError("Error during execution of step %d\n See stacktrace above to identify the issue" % step.dbobj.number)
JSExceptions.RuntimeError: ERROR: Error during execution of step 1
 See stacktrace above to identify the issue ((type:runtime.error)

Autoscale shouldn't have been part of the installation. Was this installation resumed after being partially installed?

no, blocked there

Software Version
Verified on 8.1.0 rc1


Variable interpolation Cannot work When input a parameter by --arg in command

How to reproduce

Download the cadl project I used.
npm install
npx cadl compile . --emit @azure-tools/cadl-java --arg "java-repo-folder=/tmp/java"

Result
The codes are generated in {cwd}/azure-sdk-for-java.
Expected
The codes should be generated in /tmp/java.
Other Issue:
In the cadl-project.yaml, you can find the value of emitter-output-dir is surrounded by double quotes. If I delete the double quotes, the cadl reports error: bad indentation of a mapping entry (6:45)

@allenjzhang @weshaggard @timotheeguerin

@timotheeguerin thank you. Is there an ETA to fixed it?

This has been resolved and a new version of the compiler has been released<EMAIL_ADDRESS>

Thanks @timotheeguerin It work now. But the value must be surrounded by double quotes, otherwise there will be issues. If it's expected, please also update the document:


Compound App

[x] 1. There is no such thing as Top up concept in Compound. Related to lending there is only supply and withdraw
[x] 2. When I accessed the main page with DAI I had a positive balance in the wallet but not in Compound, there it was zero. When I enter a number in the ‘Amount’ input field, both buttons are enabled: Withdraw and Top Up. There is nothing to Withdraw, balance is 0.
[x] 3. When I click on Withdraw I get a Max value is 0.0000 which the app already knew so the error is avoidable.
[x] 4. After supplying 10 DAIs I got this 10 DAIs as Interest earned which is wrong.
[x] 5. Negative interest
[x] 6.Should the TBD ETH be there? It is a fact that it is 0.
[x] 7. In the compound app the Locked Dai label is called "Supply Balance" which is made of the locked asset + interest earned. Probably is not a bad idea to have both values separated to get a better understanding of what was deposited/supplied and the interests generated, nevertheless wording and consistency is important. In Etherescan they mention the action Supply: https://etherscan.io/loantracker#compoundloan

Note: Let's triage before jumping into implementation.

Status update: Waiting on @mikheevm review for https://app.zenhub.com/workspace/o/gnosis/safe-react-apps/issues/13. Afterwards, QA will be done.


sort-order test fails with 2.3

Doesn't matter if I run the tests with perl-5.20.3 or 5.22.1, I get the following error:
#   Failed test 'location - sortcase=1'
#   at t/sort-order.t line 504.
#     Structures begin differing at:
#          $got->[6] = 'L6'
#     $expected->[6] = 'L5'
t/sort-order.t ........ Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/15 subtests
# Looks like you failed 1 test of 15.

Please let me know if I can provide additional informa

This happens on Windows due to locale issues which don't really matter. You might try 2.4 dev branch as I think I fixed this test.


[Refactoring] rename cancelable with cancellable

too many files, but not critical changes, just var renaming

Oh, you renamed it. Then: "cancelable" is fine too, since it's American :)

oh, that we can close it


bgpv1: Avoid creating resource.Store in Start() hive hooks of BGP CP

This PR ensures that resource.Store is not created in Start() hive hooks of the BGP CP. The motivation is:

If CRDs are not yet installed, this blocks the agent initialization, which can lead to issues in case of non-default operator.tolerations (see https://github.com/cilium/cilium/issues/29371#issuecomment-1842841350)
To not slow down the agent startup process (see https://github.com/cilium/cilium/pull/28593#discussion_r1363589573).

Please also see commit messages for some more details.
Fixes: #29371
bgpv1: Avoid creating `resource.Store` in `Start()` hive hooks of BGP CP to ensure proper BGP CP initialization.

/test

:wave: is this fix worth backporting?

👋 is this fix worth backporting?

yeah, would be worth to backport at least to 1.15 - added the label


Allow DispatcherRouteCallback class to be easily overridden or extended

Instantiate the DispatcherRouteCallback core class via the IoC container to allow it to be easily overridden or extended via application/bootstrap/app.php.
Doing so would make this type of thing easier without having to resort to something like this.
-Steve

Can you explain a little bit as to why you'd want to do this? Not saying it's a bad idea, really, just wondering if there aren't better ways we could make this work. For example, recently i wanted to specify my own route callback type in a package that would behave specially. Now, I don't think overriding dispatcher route callback was good for this – instead, I wanted to be able to specify a completely different callback type (this was for a REST package.) Would functionality like that work instead? I haven't gotten that into the core yet, as it was taking a bit too much time – but I'm wondering if the dispatcher callback is a bit too specialized to be messing around with in this way, and we might just have better luck creating completely new ones, if there were an easy way to do so.

Symfony uses methods that return the value of properties or a default value for classnames like this, but that is pretty much what we get with shotster's change. I agree with @aembler that the ideal way to override this core functionality probably shouldn't be something like \Core::bind('\Concrete\Core\Routing\DispatcherRouteCallback', '\My\Custom\Callback'));, but I think I'd just suggest binding a constructor with a standard name rather than trying to fallback to class instantiation:
\Core::bind('concrete/dispatcher/callback', function() {
    return new \My\Custom\Callback();
});

so that we don't have trouble renaming the class in the future.


need update to <IP_ADDRESS>

Is your feature request related to a problem? Please describe.
need update to <IP_ADDRESS>
Describe the solution you'd like (Required)
need update to <IP_ADDRESS>
Describe alternatives you've considered
need update to <IP_ADDRESS>
Additional context
need update to <IP_ADDRESS>

Thanks for reporting it. I will update it soon.
If you can't fill out the proper form, please come to Discord and just leave a chat.
Sorry, but I will ban this account.


LIFX brightness 0 issue

The LIFX component perceives brightness 0 as a valid brightness.
If the brightness value is decreased till 0 with nuimo and the light is then turned-on after this, the light stays off.
The unexpected behaviour is also that sometimes the light turn on even if brightness 0 is applied.
To be analyzed if the issue is in nuimo app or lifx home assistant component but the second option is more probable because it does not takes place with lightify and dali (light nuimo app component) through home assistant.
2017-06-26 12:59:24,060 DEBUG nuimo_app.components.light Is On: False, Brightness: None
2017-06-26 12:59:24,964 DEBUG nuimo_app Ignoring gesture event: Gesture.BUTTON_RELEASE
2017-06-26 13:00:33,697 DEBUG nuimo_app Processing gesture event: Gesture.BUTTON_PRESS
2017-06-26 13:00:33,700 DEBUG nuimo_app.components Call service light:turn_on with data: {'entity_id': 'light.lifx_bulb_203d10'}
2017-06-26 13:00:33,701 DEBUG nuimo_app.hass Sending request id: 378
2017-06-26 13:00:33,702 DEBUG nuimo_app.hass {'domain': 'light',
 'id': 378,
 'service': 'turn_on',
 'service_data': {'entity_id': 'light.lifx_bulb_203d10'},
 'type': 'call_service'}
2017-06-26 13:00:33,731 DEBUG nuimo_app.hass Received result id: 378 success: True result:
2017-06-26 13:00:33,732 DEBUG nuimo_app.hass None
2017-06-26 13:00:33,733 DEBUG nuimo_app.components Calling service light:turn_on succeeded with result: {'id': 378, 'result': None, 'success': True, 'type': 'result'}
2017-06-26 13:00:33,757 DEBUG nuimo_app.components.light Updated light state: {'attributes': {'brightness': 0,
                'color_temp': 400.0,
                'friendly_name': 'LIFX Bulb 203d10',
                'max_mireds': 500,
                'min_mireds': 154,
                'rgb_color': [0, 0, 0],
                'supported_features': 51},
 'entity_id': 'light.lifx_bulb_203d10',
 'last_changed': '2017-06-26T13:00:33.738737+00:00',
 'last_updated': '2017-06-26T13:00:33.738737+00:00',
 'state': 'on'}
2017-06-26 13:00:33,758 DEBUG nuimo_app.components.light Is On: True, Brightness: 0
2017-06-26 13:00:34,614 DEBUG nuimo_app Ignoring gesture event: Gesture.BUTTON_RELEASE

Solved in home assistant lifx_legacy component at line #225:
        if ATTR_BRIGHTNESS in kwargs:
            brightness = kwargs[ATTR_BRIGHTNESS] * (BYTE_MAX + 1)
        else:
            brightness = self._bri
+            if brightness == 0:
+               brightness = 1

When the turn_on command without an associated brightness value is received from nuimo app the stored brightness is checked and, if the value equal is to 0 then it is changed to 1 (could it be changed to max brightness value).
I will test it and propose a PR to home assistant.

Now it works but I noticed that reaching the brightness 0 with nuimo is still perceived as light-on.
So a better fix could be provided on the nuimo_app light component on_rotation() method and removing the previous correction.
From line #39:
    def on_rotation(self, delta):
        if (not self.is_on or (self.brightness or 0) <= 0) and delta <= 0:
            self.nuimo.display_matrix(matrices.LIGHT_OFF)
            return
        if self.brightness is None:
            self.brightness = 1
        else:
            self.brightness = min(max(int(self.brightness + 255 * delta), 0), 255)
+        if self.brightness == 0:
+            self.on_button_press()
+        else:
+            self.send_brightness()
        self.nuimo.display_matrix(matrices.progress_bar(self.brightness / 255.0), fading=True, ignore_duplicates=True)

fixed with PR #201


Really respect the env variable CLICOLOR_FORCE.

Prior to this commit, ninja disables color output even if CLICOLOR_FORCE is set, if it fails to set VT processing on Windows terminal. This does not respect the user's wish.
One use case of this is to force color on MSYS terminal.

This is a recreation of https://github.com/ninja-build/ninja/pull/2126. I messed up the original git branch.


Currently only English is supported?

Describe the solution you'd like
Chinese  supported

Hello, i18n multilingual support is currently under development, and Chinese is also in the development plan. Please stay tuned.


release 18.4.1

Codecov Report

Merging #983 into master will increase coverage by 0.02%.
The diff coverage is 60.6%.

@@            Coverage Diff             @@
##           master     #983      +/-   ##
==========================================
+ Coverage   62.68%   62.71%   +0.02%
==========================================
  Files          74       74
  Lines       13095    13105      +10
  Branches     2078     2086       +8
==========================================
+ Hits         8209     8219      +10
+ Misses       4189     4186       -3
- Partials      697      700       +3

Impacted Files
Coverage Δ

autobahn/_version.py
100% <100%> (ø)
:arrow_up:

autobahn/wamp/message.py
64.06% <40%> (-0.15%)
:arrow_down:

autobahn/wamp/protocol.py
54.14% <68.18%> (+0.81%)
:arrow_up:

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 039e224...5e94402. Read the comment docs.


Fixing file path to the tools jar file

Making the file path work in a platform independent manner - necessary to run on a Windows platform
Signed-off-by: Gary O'Neall<EMAIL_ADDRESS>

@goneall It works locally too. Are you planning to change more file paths? If not, we can merge this.

I didn't see any other paths to fix, so I'll go ahead and merge.


The Settable implementation in RAFT is not friendly to the StateMachine when current thread is interrupted

When calling setAsync in leader node, the RAFT will be called directly by current thread, because there is a BlockingQueue.put operation in the process, that make the process interruptible, and the InterruptedException is not thrown out, instead return a CompletableFuture that never be completed. It only happens on leader node but not followers since there is no interruptible operations in followers. I think either making the setAsync uninterruptible or throwing out the InterruptedException are both OK, that makes the StateMachine easier to control its methods are interruptible or not.

Makes sense to me. I would return a CompletableFuture.failedFuture(exception) instead of adding a checked exception. The internal queue is something I had in mind to re-work in the future when time is available. So I wouldn't expose the exception for callers.

How about use non-blocking interface instead, the failure result returns immediately if there is no space, that make a consistent result for both leader and follower nodes, and avoid to handle a uncontrolled interrupted status of external thread.
            if (!processing_queue.offer(request)) {
                retval.completeExceptionally(new IllegalStateException("processing queue is full"));
                return retval;
            }

Unfortunately, we can't do that right now. The processing queue is shared for user requests and RAFT messages. This means we could drop internal messages without retrying. We have plans to split the queue in the future. Issue #168 also gives some more details on other issues.
The simplest change (for now) is to complete the operation if the put request fails.


fix(hydration): avoid self-closing tag sub-element hydraye matches

fix #12136

I don't think this is a correct fix.

Firstly, rendering elements inside an  tag is unreasonable.
Secondly, 1, the internal  will be rendered. But <component is="img">1</component>, the internal  will not be rendered. see Playground

If we really want to solve this issue, the internal  should be rendered. When mounting an element, if it is a void tag, its children should be rendered as sibling nodes. Not sure if this is worth it. But it is definitely incorrect to hide hydration mismatch warnings in the DEV environment.

you're right, hydrate checks shouldn't be skipped no matter what.

@yangxiuxiu1115
The solution I recommend is to give warnings in the DEV. Both ssr and client, when render the child node to a void tag, give the user a warning.
Note, this only happens in <component is="VOID_TAG">child nodes</component>
Would you like to give it a try?

sure, I'd love to.


feat: Expanding API surface area by generating all Matchers

This PR pivots the intent of the library slightly from providing the buildMatchers function publicly and expecting consumers to generate their own definition matchers to using code generation to generate all available matchers. This accomplishes a few things:

hides the internal details of the buildMatcher function
makes the library more user friendly by providing all available matchers up-front
allows for regeneration of the matchers based on updates to the spec.

This PR adds:

an npm run generate command, which generates the following

a new Definition union type, which is the union of all available definitions in the SARIF schema
a matcher for each definition
an index.ts in the root of the ./src/matchers directory, which exports each matcher
a doc definition in the README for each matcher.

⚠ The only human-written files to review in this PR are:

./packages/jest-sarif/scripts/generate-sources.js, which is the codegen script
all files in ./packages/jest-sarif/templates, which are the template files used by the above script
a cursory look at the generated file output to ensure it looks OK (you only need to review one)

The rest of the files are the result of the codegen, and are largely boilerplate.
TODO

[ ] Add generated tests, each pointing to a fixture of data for each type

Have we tried moving the call to ajv.compile "higher up"? Also would leveraging ajv.getSchema('#/definitions/___') simplify things?
I'm a bit hesitant about the API "spam". Some of these definitions (and thus APIs) are getting into esoteric parts of the spec.

Have we tried moving the call to ajv.compile "higher up"? Also would leveraging ajv.getSchema('#/definitions/___') simplify things?

Could you comment on the specific file you're referring to? Also, can you elaborate on why you think this would be beneficial (potential cacheability of the compile operation, for example). Thanks!

Also would leveraging ajv.getSchema('#/definitions/___') simplify things?

Could you explain why you think it'd simplify things? Most of that API surface area is private, so if there's a strong reason to make the private API calls simpler, I'm all for it, but for this specific callout it seems arbitrary (I may be missing something!).

I'm a bit hesitant about the API "spam". Some of these definitions (and thus APIs) are getting into esoteric parts of the spec.

I understand the sentiment, and thought about this myself. Some of the reasons I went this way are

The entire schema is public, therefore all parts of that schema are public (however esoteric!) and we should look to support them.
Supporting only a subset of the schema means that we have to pick and choose what's supported and what isn't. That seems largely arbitrary, specifically if we're targeting tools and libraries that will be producing SARIF logs. Only supporting a portion of those logs in testing seems like a gap.
The API 'spam' is mitigated since you aren't required to import anything specifically.

Happy to discuss further!

Currently it looks to be compiling per toMatchSarif...() call. Between moving ajv.compile and using ajv.getSchema, I think you may be able to reduce that number. At the extreme, I think just once for the module. Also, ajv.getSchema may be able to remove the need for getFragmentSchema. Some of this may require shared/global ajv instance.

It does, because each compilation is per unique schema. I'm sure we could reduce the number, but it's also a one-time cost as the index is imported/required. Additionally, this is test infrastructure, so it may end up with us over optimizing code targeted for test infra that, while important to ensure the perf of, may not result in any meaningful gain.
I'd like to try to balance the cleanliness and readability of the code with the need to optimize. Does that make sense?

Here's an approximation/sketch. We can skip getSchema and getValidatorAndSchema and leverage Ajv for the caching and schema fragments. Also, the current version seems to be unintentionally locked on a SARIF version when using definitionName so treating that as a separate issue.
import Ajv from 'ajv';
import fetch from 'sync-fetch';

const sarifV2SchemaUrl = 'https://raw.githubusercontent.com/schemastore/schemastore/master/src/schemas/json/sarif-2.1.0-rtm.5.json';
const ajv = new Ajv({
  schemaId: 'auto',
  validateSchema: false,
});
ajv.addSchema(fetch(sarifV2SchemaUrl).json());

function buildSarifMatcher(definitionName?: string) {
  const keyRef = definitionName
    ? `${sarifV2SchemaUrl}#/definitions/${definitionName}`
    : sarifV2SchemaUrl;
  const validate = ajv.getSchema(keyRef);
  return received => {
    // Transform errors to messages here.
    return {
      actual: received,
      message: () => 'foobar',
      name: 'toMatchSarif___',
      pass: validate(received),
    };
  };
}

This seems fine to move to creating a single instance in module scope, so long as that doesn't cause unforeseen issues WRT ajv's state. Specifically, if there's a conflict between schema validations as the result of the instance's internal state, we may need to keep it as is.

Also, the current version seems to be unintentionally locked on a SARIF version when using definitionName so treating that as a separate issue.

I'm not sure what you mean here - could you elaborate?

@jeffersonking and I synced up offline. It turns out that referencing specific definitions within the parent schema is natively supported in ajv, so we're moving to that vs creating a specific sub-schema and loading that.
We're also exploring the pros/cons of using autogenerated APIs for all definitions vs. a single API that can be passed a definition string to reference the schema's definition itself.
Example:
Auto-generated API matcher:
expect(result).toBeValidSarifResult();

vs.
Generic definition matcher:
expect(result).toBeValidSarifFor('result');

The former allows the consumer to pick from an available list of definition matchers vs. having to know the string that corresponds to the definition. It does add a larger API surface area, which potentially can seem overwhelming to consumers.
That said, if the goal is to make this very easy for consumers to onboard to using/testing parts of the SARIF spec, using the former won't require them to look up the definitions they're needing to test. The counter argument could be that if consumers are constructing SARIF, and specific parts of the schema based on a definition, they'd likely know that definition name already, and thus could simply pass it in as a param.
I'm open to other's opinions on this, as I'm not tied to any one particular direction.
cc/ @jeffersonking @rwjblue

Great feedback! I was just chatting with @scalvert about this. I like both of these APIs (I think they would both satisfy our requirements for testability). If folks don't have a strong preference one way or the other, lets go with the latter suggestion .toMatchSarifFor('result'). This path still allows us to easily add the other matcher functions if we want, but limits the initial API surface.

Yep, I'm inclined to agree. The way the first one evolved was through my initial work in attempting to improve dynamic typing for the buildMatcher API. It evolved to creating APIs for each definition, but @jeffersonking correctly pointed out that a smaller API surface area may be slightly better/simpler. Moving to using this API is likely an incremental improvement to exposing the buildMatcher function directly, so I think we get the best of both worlds.
I'll make those changes now.

Glad we're having this discussion. I would not object either way. One slight tip towards the "generic" approach is that the docs (assuming they're auto-generated) may be easier to read or at least fit on one page.

OK, this PR is ready to go.


fix(video): set maxWidth/maxHeight 100% to prevent overflow

Unlike images, videos do not shrink to fit the size of the container.
This is inconsistent with the expected behavior of object-fit: contain, which is the default user-agent style for <video/>.
With this, not only partial of video but controls could also be out of the viewport and make users hard to reach.
You can check the behavior below:
https://codesandbox.io/s/fix-yet-another-react-lightbox-video-size-uw4dre?file=/src/App.tsx

[x] I have followed the 'Sending a Pull Request' section of the contributing guide

Thank you for your contribution!


Revise Lexer

Use BigInt for integers.

Fix https://github.com/ArkArk/d-prolog/issues/33

Support binary and hexadecimal integers.
Some refactorings.

Codecov Report

Merging #43 into master will increase coverage by 0.32%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #43      +/-   ##
==========================================
+ Coverage   71.95%   72.27%   +0.32%
==========================================
  Files          35       35
  Lines        1419     1439      +20
==========================================
+ Hits         1021     1040      +19
- Misses        398      399       +1

?- X = 0b1010.
std.conv.ConvException@/usr/include/dmd/phobos/std/internal/math/biguintcore.d(1922): invalid digit


Search method

which file contains the implementation of the research_papers.search method().

https://github.com/dgunning/cord19/blob/master/cord/cord19.py

Closed


Streams should be reset when the RequestStream dropped

See the rfc:
Implementations SHOULD cancel requests by abruptly terminating any directions of a stream
 that are still open. To do so, an implementation resets the sending parts of streams and
 aborts reading on the receiving parts of streams; see [Section 2.4](https://www.rfc-
editor.org/rfc/rfc9000#section-2.4) of [[QUIC-TRANSPORT]
(https://datatracker.ietf.org/doc/html/rfc9000)].

In many cases, The request stream will be dropped directly. For example in reqwest, if total timeout occurs, The entire future that sends the request will be dropped.
We are writing a quic implementation and also using it.
In our implementation, if the application layer drop the stream before the sender or.and receiver sides of the stream are reset or complete, The program will panic directly.
We stand by this. It is no longer possible for the application layer to read and write on the stream, but the stream has not ended. This is unreasonable.
This does bring us a lot of trouble, especially when using the reqwest library. Because h3 does not implement a SHOULD in rfc.

This seems reasonable!


feat(JA): WIP - Add force-rehash option to snapshot command. Integ test refactoring.

What was the problem/requirement? (What/Why)

Customers have requested APIs and CLI interfaces to use Job Attachments.
We designed  new CLI + APIs:

manifest snapshot
manifest diff
manifest download
manifest upload
attachment upload
attachment download.

What was the solution? (How)

In this PR, I am working on the code coverage, bug fix and adding feature parity to manifest snapshot. In manifest diff, I added a force-rehash option code path that allows users to rehash all files. I'm adding this also to snapshot so users can explicitly re-hash all files instead of comparing only by time stamp.

What is the impact of this change?

This new CLI + API will allow users to compare a Job Attachment manifest against the latest files in the local file system. Then customers can make a decision to make a new manifest file or not.

How was this change tested?

Yes, hatch run test passes.

Yes hatch run integ:test passes.

=======================================================================================
24 passed, 2 skipped, 5 warnings in 52.69s =======================================================================================

Have you made changes to the download or asset_sync modules? If so, then it is highly recommended
that you ensure that the docker-based unit tests pass.

Not applicable, Diff and Snapshot only does manifest operations.

Was this change documented?

Are relevant docstrings in the code base updated?

Yes

Has the README.md been updated? If you modified CLI arguments, for instance.

Readme and examples will be added once the feature stablizes.

Does this PR introduce new dependencies?
This library is designed to be integrated into third-party applications that have bespoke and customized deployment environments. Adding dependencies will increase the chance of library version conflicts and incompatabilities. Please evaluate the addition of new dependencies. See the Dependencies section of DEVELOPMENT.md for more details.

[ ] This PR adds one or more new dependency Python packages. I acknowledge I have reviewed the considerations for adding dependencies in DEVELOPMENT.md.
[X] This PR does not add any new dependencies.

Is this a breaking change?

No.

Does this change impact security?

Yes, this will be security reviewed.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Could you remove the src/hello file committed from https://github.com/aws-deadline/deadline-cloud/pull/465?

Could you remove the src/hello file committed from #465?

Doh, this was my test file for snapshot. I snapshot the source code itself.


features = ["abi3", "num-bigint"] silently ignore "num-bigint"

Bug Description
It happens because num_bigint.rs has #![cfg(all(feature = "num-bigint", not(any(Py_LIMITED_API))))] on the top, right?
If the features are actually not compatible, could there be any error or warning?
Steps to Reproduce

Add num-bigint features and use the conversion features.
Add abi3
Then conversion code build fails.

Backtrace
No response
Your operating system and version
MacOS / 13.3.1
Your Python version (python --version)
Python 3.11.1
Your Rust version (rustc --version)
rustc 1.69.0 (84c898d65 2023-04-16)
Your PyO3 version
0.19.0
How did you install python? Did you use a virtualenv?
pyenv install 3.11.1 && pyenv virtualenv 3.11.1 pyo3 && pyenv local pyo3
Additional Info
Another suggestion is implementing num-bigint for Py_LIMITED_API. Since it is already using ffi::_PyLong_FromByteArray, using a python call through int.from_bytes and int.to_bytes will makes sense (with additional overhead).
I am sorry if this is a silly idea. Is this expected to be implemented on user side?

In #3185 we are in the process of fixing a different abi3 case where support for num-complex diverged. I would happily accept a PR where we used a lower performance fallback to add support here. (Most likely using int.from_bytes and int.to_bytes as you propose.)

Thank you! I'll take a shot.


How to install and use it with slicer 4.13.0?

hi, I'm very interested in this extension module, but I could not install and get it run with slicer 4.13.
so, would you please give me some instructions on the installation?  thanks.

This module has not been bundled into an extension that can be installed using the Extensions Manager, instead you need to add it through a straightforward but more manual process:

Download this repository as a .zip file,
then unzip, everything will be in a folder called SlicerStitchImageVolumes-main.
Open Slicer, then open Application Settings (ctrl-2), then select "Modules" on the left, and then click on the ">>" button to the right of the Additional Module Paths section, then click the "Add" button.
Navigate to the unzipped SlicerStitchImageVolumes-main folder and select it.  Restart Slicer, and the "Stitch Volumes" module should now be available.

This module definitely works in versions 4.11-4.13, and likely works in at least 4.10 as well.
If I can get to it, this module may also be added to the SlicerSandbox extension soon, which would provide a way for it to be installed via the Extensions Manager, but that is not yet available.


SQLite: interface{} instead of time.Time for json extracted queries

Version
1.26.0
What happened?
When generating some queries for some extracted JSON data on SQLite, the generated query row model uses interface{} instead of time.Time.
I reproduced with the following query:
SELECT id, DATETIME(data ->> createdAt) as created_at FROM authors;
Which produces:
type GetAuthorRow struct {
	ID        string
	CreatedAt interface{}
}

I've tried casting the output but SQLite only supports basic casting: https://www.sqlite.org/lang_expr.html#castexpr
Using DATETIME with CAST(DATETIME(data ->> createdAt) AS DATETIME)` results in the correct type being generated on go side with SQLC, but the data is not correctly extracted from the SQLite database.
I also tried to use the overrides with no sucess as I'm not dealing with existing SQLite columns but "generating" them with the queries.
Relevant log output
No response
Database schema
CREATE TABLE authors (
  id    text PRIMARY KEY,
  data  text
);

SQL queries
SELECT id, DATETIME(data ->> createdAt) as created_at FROM authors;

Configuration
- engine: "sqlite"
    queries:
      - "queries.sql"
    schema: "./sql/sqlite/migrations/"
    gen:
      go:
        package: "queries"
        out: "internal/services/sqlite/queries"
        emit_interface: true
        emit_empty_slices: true
        emit_all_enum_values: true

Playground URL
https://play.sqlc.dev/p/596c5ead0510249c37a5f0aefda2441ce806c9ed7827e361b6568b0e1f18fe93
What operating system are you using?
Linux, macOS
What database engines are you using?
SQLite
What type of code are you generating?
Go

SQLite does not have a DATETIME type, which is why it behaves this way. However, a string should be returned. We need to add the definition of the DATETIME function to sqlc's catalog.


using asyncTask without useEffect

I just want to check I have not missed anything when you say there should be a better abstraction from #6.
There currently is no better abstraction, I see useEffect used in asyncTask?
I sort of struggle to see the usefulness of all these hook libraries if they cannot be used in event handlers.
I really want to check that I am not missing something about why these libraries exist when a major use case is not possible.
I have seen the start example but start does not take any arguments, what if the api call is made when say an autocomplete is selected?

OK, let's open up a new discussion here.
Because my original motivation is abotrability, which almost means async call (or fetch) lives in component lifecycle (updates), I didn't think about using it in event callbacks. If put differently, we could simply call fetch in event callbacks without a library.
Now, I would like to learn your "major use case", so that I can understand what is the fundamental problem, and how a library can help for it.
In summary, your use case is probably not covered at the moment, but I am willing to extend it if it makes sense. So, please teach me what your problem is.

what if the api call is made when say an autocomplete is selected?

I wish we had a concrete example to play with.
Can you create a codesandbox? or I can create one if I understand the expected behavior. The autocomplete is a toggle to start a typeahead example? (But, that sounds like a use case of the current library, so I may misunderstand the expected behavior.)

First of all, thank you for taking the time to answer my question.  Much appreciated.
I have a lot of buttons in a view, some will cause HTTP Gets, some Deletes etc. and because they will be triggered from event handlers I cannot use hooks which must be declared in the function body.
Most of the event handlers construct URLs due to user input.
e.g.
     <Button
        data-testid="load-button"
        disabled={businessIdInput.trim() === ''}
        id="load-button"
        onClick={() => fetch(urlJoin('base', someSetStateValue, {method: HTTP.Get})}
        primary
      >
        Load
      </Button>

I could have a table with a list of rows and each row would have a button to delete which would construct the URL and call HTTP Delete with that URL.
I like the way this package looks with the useAsyncCallback.
So I guess you could create a high level hook that you would later call with the dynamic arguments that would in turn call fetch.

First of all, you are not only the one who suggested this kind of use cases. In addition to #6, there's a similar discussion in #8.
So, it's me having missing some use cases. I don't have a concrete idea yet, but definitely consider this.

Thinking this more, I guess the feature wanted is what is proposed in #8.
I didn't accept the solution then, but now it seems the request is valid.
Basically, a) task reusability, b) passing arguments, and c) overcoming the limitation of initial render are requested (the last one is from #6).
OK, I'm not sure if I can come up with the implementation without breaking the current API, but let me try.

https://github.com/dai-shi/react-hooks-async/issues/6#issuecomment-479487865

Is there a reason that can’t be fixed?

Past implementation dealt with it. However, it was a very complex implementation with useRef, and I felt like it may not work correctly in concurrent mode in some edge cases. The current implementation is much cleaner in that sense. This library is meant to use with useEffect (= useAsyncRun), and it's not a big problem with that use case.

Well, I think I now have a better understanding of how to implement it.
Hmm, but it's not easy.

I like the way it is done here.  So you create the hook and then you get an execute method that you can pass arguments to for later use in event handlers.
I've built my own abstractions on top of this.
Is this how start behaves?

Yes, but as I noted above there are three limitations a, b, c at this point. I’m working on it to remove/mitigate those limitations.

@dagda1 Please try this PR #18.
It should behave just like you want. (No README ready, but questions are welcome.)

Implemented in #18. Please use the latest version.


Regression: application that works in v2.2.1 fails in v2.3.4 and later

TypeScript Version:  2.3.4 or 2.4.0
Upgraded an Angular project from Typescript 2.0.3 to 2.3.4 and the previously working app now throws unexpected errors  at compile/design time.
component.ts
public tabs:Array<{
  title:string,
  description:string,
  data:Array<{name:string}>
}>=[];

component.html
<section *ngFor="let t of tabs">
  ...
  <div *ngFor="let i of t.data">{{i.name}}</div>
                                  ^^^^^^
</section>

Compiler error (design time, in the IDE)

Angular: Identifier 'name' is not defined. <anonymous> does not contain such a member

If you open this plunk you will notice that the application crashes (never loads). However if you go to line 44 of config.js and change the Typescript version to earlier (I've tried 2.2.1), the application will load successfully
Expected behavior:
This code, which worked with earlier versions of TS should still work. The variables in question are strongly typed and well defined, so what's the problem?

I would report this on the agular issue tracker first. The TS compiler does not handle the template checking directly.

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


Autogenerate customernumbers on managed systems

Importing a list of customers results in empty customernumbers which makes it hard to handle in systems where the customernumber is managed.
This PR checks for managed state and uses the number generator if no customernumber is set inside the import file.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/PT-10211
Please use this issue to track the state of your pull request.

Hey @shopwareBot, any chance that this will somehow merged 1 year later? Its ridiculous that the import tool can't handle customer numbers

thanks for your contribution @pascalheidmann-bedarf :+1: :tada: :blue_heart:


bug/wong-example-file-path-in-readme: Get "No such file or directory" error by following the steps in Readme

Describe the bug
I follow the readme to run the example in docker container, but encountered a "No such file or directory." error.
To Reproduce
Just follow the steps in README.md:
python3

>>> from unstructured.partition.pdf import partition_pdf
>>> elements = partition_pdf(filename="example-docs/layout-parser-paper-fast.pdf")

Expected behavior
No error be reported.
Screenshots

Environment Info
This is from the latest docker image(downloads.unstructured.io/unstructured-io/unstructured:latest), not my local env. The bug is a document bug, not related with code.
Additional context
No; You just try it will know.

I created a PR for this, please take a review: https://github.com/Unstructured-IO/unstructured/pull/3714

to fix your trouble check this solution click
maybe this will solve your problem.


load bundles on-demand?

Hi,
is it possible to load bundles on demand? The major reason for this request is that I installed too many bundle ( 50+). The vim starting time becomes annoying long ...

duplicates #124, closing


Change File menu to Project menu for VS 2017

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/ide/how-to-create-item-templates.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thank you for your pull request. This update for VS 2017 was handled by https://github.com/MicrosoftDocs/visualstudio-docs/pull/208


fix #2117: fix migrations so that user model appropriately responds to un…

Fixed

#2117: fix migrations so that user model appropriately responds to unsubscribe_token

I'm not 100% sure why schema.rb is changed so much here I would recommend do the following in the appropriate non-production environment (I could not get vagrant to provision correctly with your current configuration on my machine):
rm db/schema.rb
rake db:migrate

This should re-generate the schema.rb appropriately I don't >>THINK<< this is necessary but, better safe than sorry IMO.

cc @andrew @xadamy ^^

ah upon further examination it looks like you were using btree to generate UUID's and Postgres has decided to prefer to use the new extension that has been enabled in my PR.

Thanks, I'm just redeploying this out now, will keep an eye on it


feat: Bump apollo to v4

BREAKING CHANGE
Remove apollo-server-koa and replace with @apollo/server v4 💥
Bump graphql to version 16

Bumped typescript to v5 for compatibility 💥
Remove tslint in favour of eslint for compatibility with TS v5

Update examples to use @apollo/server and @apollo/subgraph
Update CI to use node-16 💥

@danLDev don't forget to change this to feat or it won't publish

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


pth/yaml files for PointRCNN not present

Hi,
I am looking at section 5.3,  ST3D++ which is really detailed and insightful!  There were some comparisons done against MLC-Net/SF-UDA for unsupervised performance , using PointRCNN for nuScenes->KITTI.
I want to reproduce the same, but PointRCNN pretrained ckpts /yaml files isn't given yet. Is there any plans to release the same?

Hello, I will update these files soon. Please stay tuned.

Supported.


[BUG] Wrong Slider Range on Audio Stop

When stopping the audio (and also the non-audio session), the currently open slider annotation should be completed (end time). At the moment when pressing stop, the wrong end time is used in an audio session (not verified in non-audio sessions).

Fixed in release 0.9.24


Bug: config error: invalid digit found in string in Dapp env compat

Component
Forge
Have you ensured that all of these are up to date?

[ ] Foundry
[ ] Foundryup

What version of Foundry are you on?
forge 0.2.0 (01325bc 2022-08-03T00:08:52.682886Z)
What command(s) is the bug in?
forge build
Operating System
macOS (Intel)
Describe the bug
config error: invalid digit found in string in Dapp env compat
The application panicked (crashed).
Message:  failed to extract foundry config
Location: config/src/lib.rs:389

This is a bug. Consider reporting it at https://github.com/foundry-rs/foundry

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   1: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   2: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   3: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   4: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   5: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   6: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   7: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   8: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   9: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
  10: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
  11: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
  12: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
  13: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
  14: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Abort trap: 6

$ rm .dapprc

$ RUST_BACKTRACE=full forge install
config error: invalid digit found in string in Dapp env compat
The application panicked (crashed).
Message:  failed to extract foundry config
Location: config/src/lib.rs:389

This is a bug. Consider reporting it at https://github.com/foundry-rs/foundry

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   1: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   2: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   3: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   4: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   5: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   6: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   7: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   8: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
   9: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
  10: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
  11: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
  12: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
  13: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>
  14: __mh_execute_header<unknown>
      at <unknown source file>:<unknown line>

Run with COLORBT_SHOW_HIDDEN=1 environment variable t

What DAPP_ environment variables do you have set?

yeh this is one of the DAPP_* env vars, maybe DAPP_BUILD_OPTIMIZE? this expects 0 or 1

I think this is because I have a modline at the top most of the dapprc file
# -*- shell -*-
export ETH_RPC_URL=''
export FOUNDRY_CI=0

We don't source .dapprc automatically, so it has to be something that sets your environment for you externally. The error is related to environment variables prefixed with DAPP_, do you have one of those set?


Use fetchWithAuth: fix #92

Well, I can confirm it doesn't break anything and it looks good so... let's try it :)