Analyzer instantiate to bounds for typedefs is inconsistent

The following program shows that the analyzer is mostly (but not entirely) not doing instantiate to bounds on typedefs.  The assignments in the body of main cause errors which print out the types and show that the inferred type of globalInferred is correctly instantiated to bounds, but the annotated type on global is not.  Most other uses of typedefs don't seem to be instantiated to bounds.
This is mostly being hidden right now since fuzzy arrows will allow the assignment to exist as an implicit downcast.  If I disable fuzzy arrows, then the assignment of global to globalInferred gives a type error!
I can work around this in the short term, but this is fairly high priority since it will block us from turning off fuzzy arrows entirely, and is also probably causing some spurious fuzzy arrow warnings.
typedef T Foo<T extends int>(T x);

Foo global;
// With fuzzy arrows disabled, gives an error
var globalInferred = global;

void main () {
  int causeError;
  // Prints type of global as dynamic -> dynamic
  causeError = global;
  // Prints type of globalInferred as int -> int
  causeError = globalInferred;
}

cc @stereotype441 @scheglov @devoncarew
cc @stefantsov to verify that the front end is doing the right thing here
cc @srawlins

Looks like the common front end handles this situation correctly:
file:///tmp/fuzzy.dart:10:16: Error: A value of type '(dart.core::int) → dart.core::int' can't be assigned to a variable of type 'dart.core::int'.
Try changing the type of the left hand side, or casting the right hand side to 'dart.core::int'.
  causeError = global;
               ^
file:///tmp/fuzzy.dart:12:16: Error: A value of type '(dart.core::int) → dart.core::int' can't be assigned to a variable of type 'dart.core::int'.
Try changing the type of the left hand side, or casting the right hand side to 'dart.core::int'.
  causeError = globalInferred;
               ^
file:///tmp/fuzzy.dart:10:16: Error: A value of type '(dart.core::int) → dart.core::int' can't be assigned to a variable of type 'dart.core::int'.
Try changing the type of the left hand side, or casting the right hand side to 'dart.core::int'.
  causeError = global;
               ^
file:///tmp/fuzzy.dart:12:16: Error: A value of type '(dart.core::int) → dart.core::int' can't be assigned to a variable of type 'dart.core::int'.
Try changing the type of the left hand side, or casting the right hand side to 'dart.core::int'.
  causeError = globalInferred;
               ^

Looks like the common front end handles this situation correctly:

👍

@devoncarew Not sure what milestone to call this, but this may be a blocker for cleaning up internal code.

@scheglov @bwilkerson Any thoughts on how much work this would be to fix?  The impact on internal code isn't huge, but the spurious errors are very perplexing.  If necessary I can probably fix up internal code to work around this, but it's not great.

No, sorry. I'll try to dig into it a bit tomorrow.

Just to keep you updated...
I'm not very familiar with the type system anymore, so it's being quite a challenge to figure this out, but I think that at least part of the problem is the use of GenericTypeAliasElementImpl.typeAfterSubstitution. It's currently used in four places (in three methods).
For example, two of the uses are in TypeNameResolver.resolveTypeName. Without changes, the type name Foo in the declaration of global has type (dynamic) -> dynamic. But if I replace the if statement on 8209 with just the else body (type = typeSystem.instantiateToBounds(type);), then the type name has the type (int) -> int. Replacing the other two uses allows me to get the test case above working.
However, when I replace all uses with either instantiateType or instantiateToBounds, I end up with close to a hundred test failures in other tests. So there's some other factor that I'm not thinking of that requires the old behavior some times. I'm going to take a break from looking at it.

One possible clue is that I believe that the Driver path implements this correctly (or more correctly).
In checker_test.dart, the test
test_fuzzyArrowLegacyAssignability_GlobalInference()
passes with the driver, but not otherwise.
If you pare down that test, you might be able to isolate what the driver is doing, which might tell you what the other code paths should be doing?

@scheglov Any ideas about what might be different between Driver and task model for this case?

So far I found that we perform instantiateToBounds during linking summaries when compute implicit type. I guess we don't do this for explicit types.

I would have guessed that explicit types would have already been instantiated to bounds before the summary is generated. Is that not the case?
In any case, I think that linking summaries is something we do in the driver case (where types are being computed correctly), but not in the task model, so a bug in summary linking wouldn't explain the problem we're seeing in the task model. Right?

I would have guessed that explicit types would have already been instantiated to bounds before the summary is generated. Is that not the case?

Hm...
Yes, we probably should store all types in summaries.

In any case, I think that linking summaries is something we do in the driver case (where types are being computed correctly), but not in the task model, so a bug in summary linking wouldn't explain the problem we're seeing in the task model. Right?

Well, I does not look that even driver case is correct - Foo global is still inferred as Foo<dynamic>, but var globalInferred = global as Foo<int>.

@leafpetersen

Any thoughts on how much work this would be to fix?

It looks like we would need to fix both the Driver and the task model implementations, and it seems likely that doing so would require two independent fixes. Given that, and our current lack of understanding of where and how this needs to happen, I suspect that we're looking at a fairly significant effort to try to fix it. If I had to guess (which is all it would be given my lack of familiarity with this code) I'd probably estimate a full week.

I'm not sure whether or not this needs to be fixed in the task model given other conversations, but I'm worried about not fixing it in the driver given our current plans to keep this around for multiple quarters.  It's hard to know without knowing scope, but the symptoms of this bug are really inexplicable to users.

cc @srawlins who hit this internally.

https://dart-review.googlesource.com/c/sdk/+/46381

It looks like we're still hitting this.  I'm seeing it internally in the presence of summaries and exports.  If I compile the below file by file (i.e., 3 build steps), I get:
[error] Invalid override. The type of 'B.func' ('() → (dynamic) → dynamic') isn't a subtype of 'A<O>.func' ('() → (O) → O'). (override.dart, line 5, col 3)

Since's Func's bound is O, B.func should not be () → (dynamic) → dynamic.
override3.dart:
class O {
}

typedef T Func<T extends O>(T e);

override2.dart:
import 'override3.dart';

export 'override3.dart' show Func;

abstract class A<T extends O> {
  Func<T> get func;
}

override.dart:
import 'override2.dart';

class B extends A {
  Func get func => (x) => x;
}

void main() {
  print(new B().func);
}

@bwilkerson @scheglov - i'm hitting this internally while fixing runtime type errors in user code.

Wasn't able to repro this via unit test:
  void test_issue32114() {
    addNamedSource('/a.dart', '''
class O {}

typedef T Func<T extends O>(T e);
''');
    var bundleB = createPackageBundle('''
import 'a.dart';
export 'a.dart' show Func;

abstract class A<T extends O> {
  Func<T> get func;
}
''', path: '/b.dart');
    addBundle('/b.ds', bundleB);
    createLinker('''
import 'b.dart';

class B extends A {
  Func get func => (x) => x;
}
''');
    LibraryElementForLink library = linker.getLibrary(linkerInputs.testDartUri);
    library.libraryCycleForLink.ensureLinked();
    ClassElementForLink_Class cls = library.getContainedName('B');
    expect(cls.accessors, hasLength(1));
    expect(cls.accessors[0].type.toString(), '() → (O) → O');
  }

Will have to dig a bit deeper here.

Also could not repro using bazel, reached out to @vsmenon over email on tips to repro

Do the repro instructions here: https://github.com/dart-lang/sdk/issues/32114#issuecomment-388512688 not work any more?

Its likely I'm not "compiling it file by file" the same way. But I tried two means already and neither worked

Thanks Leaf! I am not familiar enough with ddc apparently.
I suspect this is a task model only bug, and that we won't need to fix, since I can't repro it with tools that are on the driver model. I will confirm that.

I thought that summaries were not driven by the task model, and that seems to be the key bit here?

Any updates on this?

any updates on this?

I have 4 test failures on a solution to this which I'm working through. It's a small number but don't read too much into that -- my last solution to those 4 failures introduced ~80 new ones :) I rolled that back and I'm trying a different approach, but it might have been the right one and I may end up going back through that path.

Looks like those four failures were do to me being overly defensive in my code. Now I'm just trying to get a clean repro in a unit test, not only to make the CL clean + future proof it, but also to be able to have test coverage around the changes I'm making. It doesn't seem to want to be exposed via unit test. Currently mucking around in the debugger to see why I can't get it down the pathway that is fairly obviously wrong once it gets there.

Woohoo thanks @MichaelRFairhurst this was a doozy!


Error when loading weights during training

Thank you for this powerful tools. I like it very much and want to train the model using our own data. Before that, I downloaded a DAVIS dataset and want to test model training.
(cutie) tervolab@tervolab-ws1:~/Cutie$ HYDRA_FULL_ERROR=1 OMP_NUM_THREADS=2 torchrun --master_port 25357 --nproc_per_node=2 cutie/train.py exp_id=00 model=base data=base weights=weights/cutie-base-mega.pth
However I get following errors. Could you please give me some hints how to solve the problem?

/home/tervolab/Cutie/cutie/model/trainer.py:229: FutureWarning: You are using `torch.load` with `weights_only=False` (the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value for `weights_only` will be flipped to `True`. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via `torch.serialization.add_safe_globals`. We recommend you start setting `weights_only=True` for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.
  src_dict = torch.load(path, map_location={'cuda:0': map_location})
[2024-08-22 21:29:10][INFO][r1] - Importing network weights from weights/cutie-base-mega.pth...
Error executing job with overrides: ['exp_id=00', 'model=base', 'data=base', 'weights=weights/cutie-base-mega.pth']
[rank1]: Traceback (most recent call last):
[rank1]:   File "/home/tervolab/Cutie/cutie/train.py", line 170, in <module>
[rank1]:     train()
[rank1]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/main.py", line 94, in decorated_main
[rank1]:     _run_hydra(
[rank1]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/utils.py", line 394, in _run_hydra
[rank1]:     _run_app(
[rank1]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/utils.py", line 457, in _run_app
[rank1]:     run_and_report(
[rank1]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/utils.py", line 223, in run_and_report
[rank1]:     raise ex
[rank1]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/utils.py", line 220, in run_and_report
[rank1]:     return func()
[rank1]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/utils.py", line 458, in <lambda>
[rank1]:     lambda: hydra.run(
[rank1]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/hydra.py", line 132, in run
[rank1]:     _ = ret.return_value
[rank1]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/core/utils.py", line 260, in return_value
[rank1]:     raise self._return_value
[rank1]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/core/utils.py", line 186, in run_job
[rank1]:     ret.return_value = task_function(task_cfg)
[rank1]:   File "/home/tervolab/Cutie/cutie/train.py", line 98, in train
[rank1]:     trainer.load_weights(cfg['weights'])
[rank1]:   File "/home/tervolab/Cutie/cutie/model/trainer.py", line 232, in load_weights
[rank1]:     self.load_weights_in_memory(src_dict)
[rank1]:   File "/home/tervolab/Cutie/cutie/model/trainer.py", line 223, in load_weights_in_memory
[rank1]:     self.cutie.module.load_weights(src_dict)
[rank1]:   File "/home/tervolab/Cutie/cutie/model/cutie.py", line 244, in load_weights
[rank1]:     log.warning(f'Converting {k} from multiple objects to single object.'
[rank1]: UnboundLocalError: local variable 'k' referenced before assignment
[2024-08-22 21:29:10][INFO][r0] - Importing network weights from weights/cutie-base-mega.pth...
Error executing job with overrides: ['exp_id=00', 'model=base', 'data=base', 'weights=weights/cutie-base-mega.pth']
[rank0]: Traceback (most recent call last):
[rank0]:   File "/home/tervolab/Cutie/cutie/train.py", line 170, in <module>
[rank0]:     train()
[rank0]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/main.py", line 94, in decorated_main
[rank0]:     _run_hydra(
[rank0]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/utils.py", line 394, in _run_hydra
[rank0]:     _run_app(
[rank0]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/utils.py", line 457, in _run_app
[rank0]:     run_and_report(
[rank0]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/utils.py", line 223, in run_and_report
[rank0]:     raise ex
[rank0]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/utils.py", line 220, in run_and_report
[rank0]:     return func()
[rank0]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/utils.py", line 458, in <lambda>
[rank0]:     lambda: hydra.run(
[rank0]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/_internal/hydra.py", line 132, in run
[rank0]:     _ = ret.return_value
[rank0]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/core/utils.py", line 260, in return_value
[rank0]:     raise self._return_value
[rank0]:   File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/hydra/core/utils.py", line 186, in run_job
[rank0]:     ret.return_value = task_function(task_cfg)
[rank0]:   File "/home/tervolab/Cutie/cutie/train.py", line 98, in train
[rank0]:     trainer.load_weights(cfg['weights'])
[rank0]:   File "/home/tervolab/Cutie/cutie/model/trainer.py", line 232, in load_weights
[rank0]:     self.load_weights_in_memory(src_dict)
[rank0]:   File "/home/tervolab/Cutie/cutie/model/trainer.py", line 223, in load_weights_in_memory
[rank0]:     self.cutie.module.load_weights(src_dict)
[rank0]:   File "/home/tervolab/Cutie/cutie/model/cutie.py", line 244, in load_weights
[rank0]:     log.warning(f'Converting {k} from multiple objects to single object.'
[rank0]: UnboundLocalError: local variable 'k' referenced before assignment
E0822 21:29:10.483000<PHONE_NUMBER>43264 torch/distributed/elastic/multiprocessing/api.py:833] failed (exitcode: 1) local_rank: 0 (pid: 115341) of binary: /home/tervolab/anaconda3/envs/cutie/bin/python
Traceback (most recent call last):
  File "/home/tervolab/anaconda3/envs/cutie/bin/torchrun", line 33, in <module>
    sys.exit(load_entry_point('torch==2.4.0', 'console_scripts', 'torchrun')())
  File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py", line 348, in wrapper
    return f(*args, **kwargs)
  File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/torch/distributed/run.py", line 901, in main
    run(args)
  File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/torch/distributed/run.py", line 892, in run
    elastic_launch(
  File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 133, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/home/tervolab/anaconda3/envs/cutie/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 264, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
cutie/train.py FAILED
------------------------------------------------------------
Failures:
[1]:
  time      : 2024-08-22_21:29:10
  host      : tervolab-ws1.hhmi.org
  rank      : 1 (local_rank: 1)
  exitcode  : 1 (pid: 115342)
  error_file: <N/A>
  traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
------------------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2024-08-22_21:29:10
  host      : tervolab-ws1.hhmi.org
  rank      : 0 (local_rank: 0)
  exitcode  : 1 (pid: 115341)
  error_file: <N/A>
  traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
============================================================

Thank you for reporting. Fixed.
Note the warning though. You probably want to continue using main training, not pre-training. See https://github.com/hkchengrex/Cutie/blob/main/docs/TRAINING.md#training-command


rbd: implement deleteImage() with go-ceph

Describe what this PR does
Use go-ceph librdb bindings to delete an RBD image in case CephMgr does not support background deletion.

@Madhu-1 @ShyamsundarR ptal.

Marking Do-Not-Merge for now. Reworking the connection stuff so that it can be shared between rbd/cephfs/rados requests.

This should be ready for review now, @Madhu-1


Add jupyter-book config

A better alternative to #3.
Built HTML again hosted here: https://kanderso-nrel.github.io/PVSC48-Python-Tutorial/Tutorial 0 - Overview.html
Be sure to check out the little rocket ship icon at the top of the page!  I need to figure out how to integrate the JupyterHub option correctly (it 404s right now) though...

@kanderso-nrel  this is amazing! Do we need time to work out the rocket ship? Maybe it needs to be in main to work? Should I hold off on merging or do it now?

Let's merge now and I'll try to get the jupyterhub link working in a follow-up PR


Suggestion: Decouple auto scrolling when user manually scrolls during reply streaming.

Currently, when your interface GPT writes a reply that exceeds the bottom of the page, it automatically scrolls down to keep the streaming text in view. However, it would be more user-friendly if this feature could be decoupled whenever the user manually scrolls, similar to how the official ChatGPT works.
Sometimes we want to start reading the top of the reply, before it finishes streaming the reply.

I will fix this today.

Fixed!


Scale-up-and-down-animation

Description
The idea behind this project:
Nowadays our day starts with the internet and ends with the internet means we are spending lots of time digitally so we often experience buffering problems whenever there is weak bandwidth on the net or while sometimes visiting a new webpage takes time to display the stuff and in the starting, there was a loading animation that tells the user to stop for a while. So, the project idea is there only.
How does it work :
while loading the webpage on the browser in the middle of the webpage there are 4 to 6 lines with two different heights placed
Fixes:  #560

Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] I have made this on my own
[x] I have taken help from some online resources and mentioned in PR
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK
https://user-images.githubusercontent.com/73521123/164492287-07cdb69a-b171-4d22-a7b2-ef27711eab02.mp4

I have done changes plz reviewed and merged.

Actually, I have collectively added the link for all three projects.
So it is not showing here but for this project is a link.
Plz review readme once again.

you haven't pushed the changes

Please provide me a netlify link to this project,
you are right I haven't done any changes till now as due to multiple openings I assumed that I have updated the file.

@arpit456jain plz merge this one.


Replace network label

I am phasing out the network field in the dataset. But I see you still use it. If you just want to show mainnet/testenet you can check if the faucet array contains an element.

fixed at commit https://github.com/izayl/evm-box/commit/5508bab9d2cb4381a881351190a41cba54a0fb6e


GitVersion v3.6.5 Failed to parse arguments: -verbosity Debug

What You Are Seeing?
Executing: "C:/git/Lingo/Core Services/lingo.ivr.web/tools/GitVersion.CommandLine.3.6.5/tools/GitVersion.exe" -verbosity Debug
Failed to parse arguments: -verbosity Debug

Could not parse command line parameter '-verbosity'. If it is the target path, make sure it exists.

What is Expected?
Executing: "C:/git/Lingo/Core Services/lingo.ivr.web/tools/GitVersion.CommandLine.3.6.5/tools/GitVersion.exe"
{
  "Major":0,
  "Minor":4,
  "Patch":0,
  "PreReleaseTag":"beta.13",
  "PreReleaseTagWithDash":"-beta.13",
  "PreReleaseLabel":"beta",
  "PreReleaseNumber":13,
  "BuildMetaData":"",
  "BuildMetaDataPadded":"",
  "FullBuildMetaData":"Branch.develop.Sha.3bfcd068e345838e9e09b4ffb9759999b24c6c24",
  "MajorMinorPatch":"0.4.0",
  "SemVer":"0.4.0-beta.13",
  "LegacySemVer":"0.4.0-beta13",
  "LegacySemVerPadded":"0.4.0-beta0013",
  "AssemblySemVer":"<IP_ADDRESS>",
  "FullSemVer":"0.4.0-beta.13",
  "InformationalVersion":"0.4.0-beta.13+Branch.develop.Sha.3bfcd068e345838e9e09b4ffb9759999b24c6c24",
  "BranchName":"develop",
  "Sha":"3bfcd068e345838e9e09b4ffb9759999b24c6c24",
  "NuGetVersionV2":"0.4.0-beta0013",
  "NuGetVersion":"0.4.0-beta0013",
  "CommitsSinceVersionSource":13,
  "CommitsSinceVersionSourcePadded":"0013",
  "CommitDate":"2019-04-01"
}

What version of Cake are you using?
v0.33.0
Are you running on a 32 or 64 bit system?
64
What environment are you running on?  Windows? Linux? Mac?
Windows
Are you running on a CI Server?  If so, which one?
Local and Jenkins
How Did You Get This To Happen? (Steps to Reproduce)
Running the same build script as 0.32.1
Output Log
========================================
Get-Version-Info
========================================
Executing task: Get-Version-Info
Executing: "C:/git/Lingo/Core Services/lingo.ivr.web/tools/GitVersion.CommandLine.3.6.5/tools/GitVersion.exe" -verbosity Debug
Failed to parse arguments: -verbosity Debug

Could not parse command line parameter '-verbosity'. If it is the target path, make sure it exists.

Use convention to derive a SemVer product version from a GitFlow or GitHub based repository.

GitVersion [path]

    path            The directory containing .git. If not defined current directory is used. (Must be first argument)
    init            Configuration utility for gitversion
    /h or /?        Shows Help

    /targetpath     Same as 'path', but not positional
    /output         Determines the output to the console. Can be either 'json' or 'buildserver', will default to 'json'.
    /showvariable   Used in conjuntion with /output json, will output just a particular variable.
                    eg /output json /showvariable SemVer - will output `1.2.3+beta.4`
    /l              Path to logfile.
    /showconfig     Outputs the effective GitVersion config (defaults + custom from GitVersion.yml) in yaml format
    /overrideconfig Overrides GitVersion config values inline (semicolon-separated key value pairs e.g. /overrideconfig tag-prefix=Foo)
                    Currently supported config overrides: tag-prefix

    # AssemblyInfo updating
    /updateassemblyinfo
                    Will recursively search for all 'AssemblyInfo.cs' files in the git repo and update them
    /updateassemblyinfofilename
                    Specify name of AssemblyInfo file. Can also /updateAssemblyInfo GlobalAssemblyInfo.cs as a shorthand
    /ensureassemblyinfo
                    If the assembly info file specified with /updateassemblyinfo or /updateassemblyinfofilename is not found,
                    it be created with these attributes: AssemblyFileVersion, AssemblyVersion and AssemblyInformationalVersion
                    ---
                    Supports writing version info for: C#, F#, VB
    # Remote repository args
    /url            Url to remote git repository.
    /b              Name of the branch to use on the remote repository, must be used in combination with /url.
    /u              Username in case authentication is required.
    /p              Password in case authentication is required.
    /c              The commit id to check. If not specified, the latest available commit on the specified branch will be used.
    /dynamicRepoLocation
                    By default dynamic repositories will be cloned to %tmp%. Use this switch to override
    /nofetch        Disables 'git fetch' during version calculation. Might cause GitVersion to not calculate your version as expected.

    # Execute build args
    /exec           Executes target executable making GitVersion variables available as environmental variables
    /execargs       Arguments for the executable specified by /exec
    /proj           Build a msbuild file, GitVersion variables will be passed as msbuild properties
    /projargs       Additional arguments to pass to msbuild

gitversion init     Configuration utility for gitversion

An error occurred when executing task 'Get-Version-Info'.
Executing custom task teardown action (Get-Version-Info)...
Error: System.AggregateException: One or more errors occurred. ---> Cake.Core.CakeException: GitVersion: Process returned an error (exit code 1).
   at Cake.Core.Tooling.Tool`1.ProcessExitCode(Int32 exitCode)
   at Cake.Core.Tooling.Tool`1.Run(TSettings settings, ProcessArgumentBuilder arguments, ProcessSettings processSettings, Action`1 postAction)
   at Cake.Common.Tools.GitVersion.GitVersionRunner.Run(GitVersionSettings settings)
   at Submission#0.GitVersion(GitVersionSettings settings)
   at Submission#0.GetVersionInfo()
   at Submission#0.<<Initialize>>b__0_4()
   at Cake.Core.CakeTaskBuilderExtensions.<>c__DisplayClass24_0.<Does>b__0(ICakeContext x)
   at Cake.Core.CakeTask.<Execute>d__43.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Core.DefaultExecutionStrategy.<ExecuteAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Core.CakeEngine.<ExecuteTaskAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Core.CakeEngine.<RunTask>d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Core.CakeEngine.<RunTargetAsync>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Scripting.BuildScriptHost.<RunTargetAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Core.Scripting.ScriptHost.RunTarget(String target)
   at Submission#0.<<Initialize>>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.CodeAnalysis.Scripting.ScriptExecutionState.<RunSubmissionsAsync>d__9`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.CodeAnalysis.Scripting.Script`1.<RunSubmissionsAsync>d__21.MoveNext()
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at Cake.Scripting.Roslyn.RoslynScriptSession.Execute(Script script)
   at Cake.Core.Scripting.ScriptRunner.Run(IScriptHost host, FilePath scriptPath, IDictionary`2 arguments)
   at Cake.Commands.BuildCommand.Execute(CakeOptions options)
   at Cake.CakeApplication.Run(CakeOptions options)
   at Cake.Program.Main()
---> (Inner Exception #0) Cake.Core.CakeException: GitVersion: Process returned an error (exit code 1).
   at Cake.Core.Tooling.Tool`1.ProcessExitCode(Int32 exitCode)
   at Cake.Core.Tooling.Tool`1.Run(TSettings settings, ProcessArgumentBuilder arguments, ProcessSettings processSettings, Action`1 postAction)
   at Cake.Common.Tools.GitVersion.GitVersionRunner.Run(GitVersionSettings settings)
   at Submission#0.GitVersion(GitVersionSettings settings)
   at Submission#0.GetVersionInfo()
   at Submission#0.<<Initialize>>b__0_4()
   at Cake.Core.CakeTaskBuilderExtensions.<>c__DisplayClass24_0.<Does>b__0(ICakeContext x)
   at Cake.Core.CakeTask.<Execute>d__43.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Core.DefaultExecutionStrategy.<ExecuteAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Core.CakeEngine.<ExecuteTaskAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Core.CakeEngine.<RunTask>d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Core.CakeEngine.<RunTargetAsync>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Scripting.BuildScriptHost.<RunTargetAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Cake.Core.Scripting.ScriptHost.RunTarget(String target)
   at Submission#0.<<Initialize>>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.CodeAnalysis.Scripting.ScriptExecutionState.<RunSubmissionsAsync>d__9`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.CodeAnalysis.Scripting.Script`1.<RunSubmissionsAsync>d__21.MoveNext()<---

Updating the pinned version of GitVersion.CommandLine to 4.0.0 and updating the GitVersion.yml to be compatible with the latest version got us past this issue.

This is related to the change that was made in this issue: https://github.com/cake-build/cake/issues/2141

@shaneray I am going to go ahead and close this issue, and update this related issue with further information.  Thanks again for raising this!


Compiler: whitelist import global in template

What problem does this feature solve?
It would allow to put for example import.meta.env.DEV inside the template to remove render code when building.
<template>
	<DevOnlyButton v-if="import.meta.env.DEV" />
</template>

What does the proposed API look like?
Add import here:
https://github.com/vuejs/core/blob/78b86150b801e7eb4ebf1cdff977e791dc0438f0/packages/shared/src/globalsWhitelist.ts#L3

Alternative proposal: allow customizing the whitelist


Typescript client not working when fastapi responses are in camelCase

Description
I have a fastapi backend. I configured it to return responses in camelCase instead of snake_case. This is how I configured it:
import pydantic
from pydantic.alias_generators import to_camel

class CustomBaseModel(pydantic.BaseModel, revalidate_instances="always", validate_assignment=True):
    class Config:
        alias_generator = to_camel
        populate_by_name = True

The backend works as expected. I tested it with both localhost:8000/docs and curl command. The responses are in camelCase.
I generated a typescript client using hey-api. The typescript response types are in camelCase. Yay!
However, the actual responses the@hey-api/client-fetch gets are in snake_case!!!
This breaks the response types. camelCase fields are undefined as the raw responses are in snake_case.
What am I missing? How do I fix it?
Reproducible example or configuration
No response
OpenAPI specification (optional)
No response
System information (optional)
No response

Hey @vinod-canihelp, let's start with your OpenAPI spec and are you able to provide either a reproducible example or a screenshot of the issue?

afaik, the openAPI spec looks good. The types generated are correct.
Let me create small reproducible example in an hour and share.

Something's fishy... I have 4 APIs. All 4 APIs give camelCase response using curl.
However, two of the APIs give camelCase response using hey-api fetch client while the other two doesn't. Makes no sense. Digging deeper.
If there's an option to log stuff inside the client, it would be very helpful. Let me know if that's an option.

I have a NextJS app for frontend. When the API is called from the nextjs client side code, the api response is camelCase. But when the same API is called from nextjs server side code, the api response is snake_case!!!

Using plain fetch in the nextjs server side gets the data in camelCase. But using hey-api fetch client is gets the response in snake_case

Found the issue. Stale data was cached somewhere. Clearing browser cache and reloading fixed the issue.
Hey @mrlubos! First, I apologize for reporting a wrong bug. Second, is there a recommended way to set cache policy or time-to-live using hey-api fetch-client?

Not at the moment @vinod-canihelp. We don't have a clear section on usage with Next, though I know some people asked about it!


Deprecate the backup and restore endpoints

Addresses: https://jira.duraspace.org/browse/FCREPO-2044

Although /fcr:backup and /fcr:restore are not a part of the Fedora Specification, they serve a very real and practical purpose in the community implementation. I would rather we not deprecate them until we have a time-tested alternative in the import-export utility.

@awoods: I think the better approach is to have a command-line utility that directly invokes the methods on this service. Wrapping that service in an HTTP interface makes very little sense to me.

@awoods: or, put another way, once someone starts to develop a non-modeshape implementation (while re-using the existing API classes), are you saying that that implementation must implement a backup and restore endpoint?

A command-line tool that interacts with the repository directly has its appeal, but will likely suffer from locking issues with the webapp and the command-line tool trying to access the underlying repository at the same time.
Regarding other implementations of the Fedora API, absolutely not. It seems perfectly reasonable to return a "501 Not Implemented" or another suitable response.

Although /fcr:backup and /fcr:restore are not a part of the Fedora Specification, they serve a very real and practical purpose in the community implementation. I would rather we not deprecate them until we have a time-tested alternative in the import-export utility.

Please give specific, concrete, preferably quantifiable conditions that must be reached. Otherwise this is not a real plan, it's just kicking a can down an increasingly narrow alley.

I don't see why we couldn't move the backup/restore functionality into an extension module not unlike how the old fcrepo-transform module worked -- i.e. by adding new endpoints to the core API.

@acoburn, I was thinking the same thing. Externalizing backup/restore into fcrepo-webapp-plus vs deprecating it makes a lot of sense.

👍 to moving this to fcrepo-exts to begin with. We can move it farther out from there.

@awoods: as for process: should we add a warning header now (i.e. "This endpoint will be moving to an extension module in a future release of Fedora") or simply move the related code into an extension module without any associated warning header? I am inclined to think that a warning header would be appropriate.

:+1: to Warning header now.


[api-major] Remove the enhanceTextSelection functionality (PR 15145 follow-up)

For the gulp mozcentral command, this reduces the size of the built pdf.js file by > 10 kB.

/botio test

Please note: I'm assuming that we're not planning on any more releases from the 2-branch, since otherwise we probably need to hold off on landing this.

I was thinking to do one final 2.x release, mainly to incorporate the CSS fixes that somewhat "broke" in the current release. That way we provide users with that fix without requiring them to also upgrade to a new major version. After the release we can then merge the [api-major] patches. Is that OK?

I was thinking to do one final 2.x release in a few days, mainly to incorporate the editor CSS fix that somewhat "broke" in the current release. That way we provide users with that fix without requiring them to also upgrade to a new major version.

That sounds like a good idea to me!

Once that release is done we can merge the [api-major] patches and release PDF.js 3.0. Is that OK?

That sounds perfect :-)
However we might want to wait with releasing version 3 until editing is enabled by default, since it got pushed to Firefox 106 (see e.g. bug 1784272 and bug 1785248), so that we have a "significant" new feature in the version 3 release!?

/botio test

Thank you for working on this!


Running spectral decomposition twice crashes GUI

Which error do you get? If I try to run spectral decomposition a second time, the dialog opens normally, but with the options disabled:


http read -listen

Wouldn't it be great if you could use to power of juttle to set up an http service and write incoming points to your favorite storage backend?
Proposing listen mode for the builtin http read adapter. A simple program would look something like this:
http read -listen 2000
| write elastic

With this program now running, we can now do a POST request to localhost:2000:
customer_id, product_id, price
12, 1209, 3.00
1, 1400, 5.00

Revised http read options:
I'm proposing renaming the -url option to -fetch. The -listen option takes a port number. Either the -fetch option or -listen option must be specified. If both are specified an error is thrown.
If -listen is specified on the -method and -timeField options will apply. All other fields applicable to -fetch will be ignored.

Parameter
Description
Required?

-fetch
URL to issue the HTTP request at
Yes: either fetch or listen must be specified

-listen
Port for http endpoint to listen on
Yes: either fetch or listen must be specified

-method
HTTP method to use
No; -fetch default: GET; listen default: POST

-headers
headers to attach to the HTTP request in the form { key1: "value1", ..., keyN: "valueN" }
No; default: {}

-body
body to send with the HTTP requests
No; default: {}

-timeField
The name of the field to use as the time field The specified field will be renamed to time in the body of the HTTP request. If the points already contain a field called time, that field is overwritten. This is useful when the source data contains a time field whose values are not valid time stamps.
No; defaults to keeping the time field as is

-includeHeaders
When set to true the headers from the response are appended to each of the points in the response
No; default: false

Content Types
Just like http read -fetch, http read -listen accepts text/csv and application/json content-type headers. Requests without a content-type header or with a different content-type value will recieve a 400 bad request response.
JSON
JSON requests will be parsed in the same fashion as http read fetch. Any serialization errors will be returned as a 400 BAD REQUEST
CSV
Each CSV request needs to have a header row with the keys for the following points.
Implementation Details
I'd like to use the node stdlib to create the server, using require('http') as opposed to 3rd party libraries like express. The goal would be to minimize dependencies.

+1 further discussion on gitter.


Cosmos DB: Removed July 31st date.

@mimig1,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

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

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.
It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We've closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions


Fix libraries for Python 3.7 compatibility

Use list instead of tuple.
Fixes: #133
Reference: https://github.com/danni/python-pkcs11/issues/133#issuecomment-1019577286

Merged #136 which includes the same fix. Thanks though :)


Placeholders case sensitive - why?

I can not understand why placeholders case sensitive? This can lead to errors in case insensitive db.

I'm not sure we support any case-insensitive DB backends, but, it would be a good patch anyway for convenience in using the CMS_PLACEHOLDER_CONF.

Closing as this fits our feature request criteria.
If you're still interested in this feature, please create a topic in the Developers Mailing List.


Images for W3KG233 not loading in scamqc

Trying to open this folder:  Travis/contrib/W3KG233/archive/W3KG233-I3KG995
When trying to view images on scamqc they don't appear to load:
https://scamqc.bdrc.io/?folder=Travis%2Fcontrib%2FW3KG233%2Farchive%2FW3KG233-I3KG995%2F

fixed: https://scamqc.bdrc.io/?folder=Travis%2Fcontrib%2FW3KG233%2Farchive%2FW3KG233-I3KG995%2F
(there was an url encoding issue with the '&' character in image path)


[QUESTION] gRPC 官网demo  Error occurred during parsing: Unexpected wire type.

Before you submit this issue, you has been search all existed issues and search the documentation

[] I've been search all existed issues
[] I've been read all documentation

Describe your question

请认真根据 issue 要求描述您的问题

客户端

服务端

求解

duplicate with #1806


Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/TA2k/ioBroker.mystrom

[ ] [E144] common.installedFrom field found in io-package.json. Must be removed.
[ ] [E605] No actual year found in copyright. Please add "Copyright (c) 2021 TA2k<EMAIL_ADDRESS>at the end of README.md
[ ] [E701] No actual year found in LICENSE. Please add "Copyright (c) 2021 TA2k<EMAIL_ADDRESS>at the start of LICENSE

Thanks,
your automatic adapter checker.
P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Do you need help fixing the bugs?

Thanks, that all bugs have been fixed.


Support for smart invert on iOS has regressed

Sometime back in 2018 I wired up support for smart invert by apply an inversion filter to our images when this setting is toggled. However on recent testing, smart invert decides not to invert anything in a Flutter. Thus the inversion has the opposite effect.
If this is no longer a reasonable choice, we should remove this setting and the corresponding Paint.invertColors flag.
@chunhtai @goderbauer

https://github.com/flutter/engine/pull/6176
https://github.com/flutter/flutter/pull/21457

Its possible this is a recent change, or may not be related to an iOS version. On the iPhone 7 this still works as expected.

@jonahwilliams if you give repro steps and expected results we can ask the triagers to try on different versions and devices.

Steps:

go to the iOS settings and search for "Smart Invert" (not classic invert) and enable it.
flutter run the old gallery in flutter/dev/integration_tests/flutter_gallery
most colors should be inverted.
Navigate to studies, then "fortnightly"
The image header should not be inverted.

This works for me on iPhone 7. On the iPad pro after enabling smart invert the screen of the flutter app is not inverted at all

The app was inverted and the fortnightly image header was not inverted (so it still worked) on my iPhone 6s running iOS 13.7, iPhone 12 Pro running iOS 15.4.1, and on my iPhone 14 running iOS 16.2.
All the simulator devices and iOS versions I tried did reproduce the issue and the app wasn't inverted, but the header image was.

Okay, something weird was going on. Closing


Losing WiFi connection on certain networks (IDFGH-200)

Hi,
What can be the reason that always after reboot of the ESP32 pinging to the module stops after 10-60sec. I have used the "simple_wifi" example with nothing in it. I get connected, get an ip and if I ping from my PC to the ESP32 it always stops after 10-60sec. on certain networks? This is the case on Meraki and Cisco with a WLC4400 controller.
I also have the problem with an ESP32 and Arduino framework and PlatformIO.
On my wifi AP at home it keeps on working. But the ESP8266 works on ALL networks, home and work.
What is different and what causes this problem? Is it like a wifi preamble parameter or something else that causes the ESP32 to stop working?
Also tried v2.1.1 and v3.0rc1.
Please help.
Korstiaan

@korstiaanS  do you means the WiFi is disconnected or ping is stop, after 10~60 seconds?  I just can't reproduce this issue, could you provide more detailed log?

After further investigation we found the reason:
By further investigations and packet captures we have encountered the root cause of the connectivity issue.
In normal condition we see by packet capture that the ESP32 module is using the correct IP and correct MAC address of it’s default gateway.
So IP communication with devices outside it’s subnet is correctly send to the default gateway mac (example: 00:08:e3:aa:aa:aa)
Every 60 seconds the ESP32 module receives an IGMP general membership query from the IGMP querier in it’s subnet. (in our case this IGMP querier is our Cisco core switch).
Upon receival of the first IGMP query the ESP module changes the default gateway mac address (example: 00:08:e3:aa:aa:aa) with the source mac address of the igmp querier (example: 00:09:e3:bb:bb:bb)
As of now all IP packets towards it’s default gateway are send towards the incorrect mac address (00:09:e3:bb:bb:bb) and the ESP32 is not reachable anymore from outside it’s subnet.
In our specific setup we have disabled the IGMP querier functionality for the specific VLAN/IP subnet on the Cisco core switch to solve this encountered issue.
Why the ESP32 have problems and the ESP8266 not is for me not clear.

http://lwip.100.n7.nabble.com/ETHARP-TRUST-IP-MAC-and-IGMP-querier-td16082.html

HI @korstiaanS just as @negativekelvin pointed out, you can configure ETHARP_TRUST_IP_MAC to 0 by  LWIP menuconfig. Maybe we can do some optimization when ETHARP_TRUST_IP_MAC is enabled:

Only trust unicast packets
If the MAC address for a specific IP is different than the existing mac in the table, print some warning message
We will discuss how to improve it...

Hi,
Ok.
The problem is also that I use ESP32 on Arduino and there it is not so simple to change the default from 1 to 0.

I use ESP32 on Arduino, is there a way to set ETHARP_TRUST_IP_MAC to 0 and solve this problem temporarily? I am having the same issue currently.

@hrishikesh-thakre The definition for the "ETHARP_TRUST_IP_MAC" is here . You can set it in the menuconfig.

Thanks for reporting, will close due to short of feedback, feel free to reopen with more updates. Thanks.


trojan无法生成订阅

trojan无法生成订阅
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

已解决> trojan无法生成订阅

Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.


🐞 [Bug]: Peertube & Funkwhale deployer not consider errors

Is there an existing issue for this?

[X] I have searched the existing issues

which package/s did you face the problem with?
Dashboard
What happened?
After merging this pull request https://github.com/threefoldtech/tfgrid-sdk-ts/pull/2742
peertube and funkwhale didn't respect clicking deploy as other applications did ... right now clicking deploy - no matter how many errors in form - will just start deploying an instance cause an error happen to user
Steps To Reproduce
No response
which network/s did you face the problem on?
Dev
version
2.5.0-rc1
Twin ID/s
No response
Node ID/s
No response
Farm ID/s
No response
Contract ID/s
No response
Relevant screenshots/screen records

Relevant log output
Nothing

Kubernetes also have an issue

Static Website also got the same issue

fixed and verified on devnet
version : ad30945
now the deploy button is working fine
and even tried to trigger the deployment button while any field is not filled and deployment failed and asked me to continue the details

same for peertube
could not deploy until all fields are filled right

deployment tried and working fine
static website
node pilot
next cloud
will check deploy button in others as well but working fine for now


#0: ttnn bug fix for ttnn.Conv2d bias=None

Nightly looks good, running post commit: https://github.com/tenstorrent/tt-metal/actions/runs/8760601512

Notes:

we expect #7684 to fix the device perf regression, that's in main
resnet 50 E2E perf was close to threshold, maybe noise, re-running and shouldn’t block this PR but should check what it’s like on main
Stable diffusion E2E perf hung, that’s likely also in main , saw that in #7684 device perf too


Include "Release" string of hosts into host scoring

hm so this is a breakdown of the release field on 1.6.0 hosts:
host_release	cnt
""	181
"hostd v1.0.4"	174
"hostd v1.1.0-beta.2"	45
"hostd b194b8f"	12
"hostd dafc054"	2
"hostd v1.1.0-beta.1"	1
"hostd ?"	1
"hostd 1a8a8a5"	1
"hostd v1.0.4-53-g1c2523f"	1
"hostd v1.0.4-29-gbd236b2"	1

that's not great

Closing this for now until we have updated hostd to always include proper versions for the release


IO redirection in a let block causes pipe errors on Linux and MacOS

I've adjusted this from the test file. However, I'll look into the root cause as well, since I want to be sure @spinner doesn't cause any working code to fail.


introduce eslint

was having a read through the sources and figured this might be useful while i was in there.
if not, no worries. tried to align the config with whats in the source, too. to avoid code changes
does raise the question also: you have a fair amount of empty methods, a few which are never used outside tests too. might be worth figuring out if all those are necessary

rebased and fixed new lint errors in case this ever gets picked up

We now have a linter running.


chore: add release documentation

Kindly explain what this PR does.

Can we make the steps to be in a numbered list/bullets?
Just easier to read and follow different ones
@ayildirim21


Ensure that code conforms to convention

Look through code to make sure it's stye matches

Going through and checking the UML I also looked over most code. It all looks good, apart from what was/will be added. Should just need one final check tomorrow.

Sounds good, Once I sort out code on my end I'll go through it again deleting any temporary code comments and put little blurbs on what methods are doing


Default power values for Turbines and molten salt reactors

Yo, just got a MSR setup going and found it to be actually terrible due to the default power gen from turbines. I followed the tutorial, checked my maths and still I got only like 6k rf/t (best case).
Compared to a solid fuel reactor, which takes 1/100th of the resources, machines, and automation I think this is imbalanced.
I think the base rf/mb for steam should be at least 80 rf/t or 160 rf/t instead of 16 rf/t. Right now the vanilla molten salt reactors are basically worthless unless you tweak the config. I could have 60k rf/t with a solid fuel reactor for 1/100th of the resources.
Any thoughts on this? I'm happy to make a pull request to fix the default config values but I wanted your feedback first.

This is with a 2x turbine setup, with a heat exchanger for water -> steam and exhaust steam to low pressure steam.

Hey there! This will be sorted properly in the future as the overhaul gets underway, but for now increasing the steam RF/t as you say, while lowering the coolant heat multiplier config is a way to get round it ;)


Added docs on enabling OCSP Stapling

In PR #984, no instructions were added to the README that told the user how to enable OCSP Stapling.  This PR adds those instructions.

Thanks @kamermans!


Fix chromeFlags

Fixes use of the chromeFlags configuration.
flags is expected here (vs chromeFlags): https://github.com/adieuadieu/serverless-chrome/blob/develop/packages/lambda/src/index.js#L16

Nice catch! Thank you.
Some unit tests would surely work wonders for these kinds of things..... (pointing at myself here.)

Cool, thanks for merging!


Skip new table_ops test under emulation

When emulating we already have to disable most pooling-allocator related
tests so this commit carries over that logic to the new fuzz test which
may run some configurations with the pooling allocator depending on the
random input.

Depending on how CI goes I will update https://github.com/bytecodealliance/wasmtime/issues/4487. This will not pass s390x CI but I'd like to see if it passes aarch64 CI.


Remove "hexadecimal" restriction

This has been discussed in the original PR (starting from https://github.com/TraceContext/tracecontext-spec/pull/1#issuecomment-313010383) but got lost/ignored. In the current form the spec excludes tracing systems that may be using differently formatted strings for trace and/or span IDs.

Couple of things:

I would say base16 not "hexadecimal". "hexadecimal" means you encode a number.
You need to respect HTTP restrictions so you have to encode the "string" or "byte array" or however you call it. So we have to define what is that encoding because otherwise you put a restriction on the traceId to be HTTP compatible.

because otherwise you put a restriction on the traceId to be HTTP compatible.

well, if we're talking about HTTP header spec, isn't that implied?

I would say base16 not "hexadecimal". "hexadecimal" means you encode a number.

https://www.google.com/search?q=define+hexadecimal says "relating to or using a system of numerical notation that has 16 rather than 10 as its base."
The point is, the current spec exclude tracing systems that might choose a different encoding or length of the trace ID. Adrian had an argument about storage implication, which is valid in the sense that yes there are implications, but it's not impossible to resolve. In the best case the two systems use "compatible" trace-ids and can use them directly. In the worse case the receiving instrumentation will record the incoming trace-id as a correlation id.

+1 about removing the base16 and length things.  Skywalking is using three longs for ID(trace segment id and trace id). So length changes for every generated id. If we follow the spec, we must cost more CPU and memory for the ID. This is not good.
Right now, skywalking can only consider to add a new HEAD for this spec if some people want this interop feature. Put two heads, one for skywalking, one for TraceContext Spec. It can work, but it is the best solution. :)
But still, I hope the spec can make the skywalking supporting easier.

Hi, Yuri.
What format does jaeger require that is not hexidecimal? What would happen
if it were not? How would you handle it in jaeger?
It is important we dont add technical debt in the process of doing this
work. Every constraint removed comes at a cost. It would be nice to know
you thought this through, especially as it can help others think this
through.

@adriancole Right now, skywalking is considering put the ids(traceId and spanId) from outer tracer into tags of the EntrySpan.

+1 about removing the base16 and length things. Skywalking is using three
longs for ID(trace segment id and trace id). So length changes for every
generated id. If we follow the spec, we must cost more CPU and memory for
the ID. This is not good.

Hi, sheng. do you need to remove both constraints or just one (length)? On
the technical side, I think there's been some benchmarking around encoding,
which only affects you as you exit the process (this spec has no concern
about in-memory structure). For example, hexadecimal is quite fast to
encode, well under microsecond for the entire context, maybe faster than a
formatted Date header :)

the other thing about encoding, if for memory or perf concerns, I suspect
we will have a binary format defined at some point. For example, there's
already one under experiment in census
https://github.com/census-instrumentation/opencensus-specs/blob/master/encodings/BinaryEncoding.md,
which is laid on http/2 transport in base64 (platform-specific grpc
encoding, but worth mentioning)

Hi Adrian,

What format does jaeger require that is not hexidecimal? What would happen if it were not? How would you handle it in jaeger?

I am not saying that general strings are required or even supported by Jaeger. Jaeger is using 128bit byte array as a trace ID, and cannot support arbitrary string IDs without substantial changes to the backend and client libs. The way I would handle incoming string ID is by recording it as a correlation ID tag.
But it's not about Jaeger, it's about inclusiveness of the spec. Maybe we should start with the goals of this spec, what exactly it is trying to achieve. There are different possible interop modes.

correlation by saving a string to a database allows offline correlation,
but breaks propagation interop, which is the primary goal of the project. I
think there certainly is space to define what we are defining by "context"
when we say this, but we have defined it! So, my suggestion is that when we
invalidate things, we provide for how to retain the charter while doing
this. If the charter is passing trace context, and we accept incompatible
data, we can't punt the responsibility to keep interop working in some
fashion. IOTW hope is not a specification! For example, a lot of this
tension is about a single header. We can in fact define means by which you
can pass incompatible format while still continuing the trace. Otherwise,
the spec grows to a correlation algorithm, right?
A trace context header is used to pass trace context information across
systems for a HTTP request. Our goal is to share this with the community so
that various tracing and diagnostics products can operate together, and so
that services can pass context through them, even if they're not being
traced (useful for load balancers, etc.)

can we define what the charter is? it's not stated anywhere in the repository, hence the confusion.

The goal is mentioned here, we can top-level it, good point
https://github.com/TraceContext/tracecontext-spec/blob/master/HTTP_HEADER_FORMAT.md#trace-context-http-header-format

Let's discuss the charted in #17

copied missing data in
https://github.com/TraceContext/tracecontext-spec/pull/18

Hi, sheng. do you need to remove both constraints or just one (length)?

Skywalking id is long1.long2.long3. The dot is not part of base16 and long is not the certain length literally(After encoding, sure, it can be). So if the both constraints removed, skywalking will be no need to add new head, just need to separate the current sw3-head into two parts. This is my best choice.
And as you known, skywalking has a way to resolve this: support this by using a new head for interop and do not change the sw3-head. In that way, cost of encoding and size of http package will change, right? Maybe not big, but for a very high throughputs app, like some 10K tps application in Chinese e-commerce and telecom systems (large population -> large system...), everything changed, and I have to treat all perf related risks very carefully. Btw, these users have such high throughputs, but can't accept sampling... So you can image what is the situation skywalking facing......

Skywalking id is long1.long2.long3. The dot is not part of base16 and long is not the certain length literally(After encoding, sure, it can be). So if the both constraints removed, skywalking will be no need to add new head, just need to separate the current sw3-head into two parts. This is my best choice.

OK, what would you do if you were given the following ID also in the
trace-context header
trace-context: Para bailar la bamba Para bailar la bamba se necesita
una poca de gracia Una poca de gracia pa' mi pa' ti y arriba y arriba
Ah y arriba y arriba por ti seré, por ti seré, por ti seré-Bamba
bamba-1
What would you propagate in order to continue that trace?
(intentionally being funny, but seriously we need to answer things
like this.. usually we think of our own IDs in isolation, but that's
not the case. Remember henry from china telecom who had 5 trace
systems to propagate to?)
https://twitter.com/henrychenyong/status/901738274632425473

What would you propagate in order to continue that trace?

Besides the context spec, which your guys used, I can introduce two use cases of many tracing system do to propagate the context.
First thing first, the reason of context includes more fieldsthan yours, is not about continue trace, they're about analysis, e.g the application relationship, the service relationship. And you can see if we run the analysis after all trace segments(spans) finished, it's clearly no need for these extra fields, but the analysis latency is very long, and cost more resources in read/write or memory at the same time.
And most of tracing systems use UUID or timestamp-trusted-traceid(skywalking is a kine of implementation).
So this is user case <1>, we propagate parent application code(id), parent service(operation) name etc.
And many tracing system implementation, they use the same span.id style, I called it EagleEye span-id style. EagleEye is an alibaba OSS system, they shared their implementations, so many people use it. The id is like these: 1.0, 1.1, 1.1.0, you can understand easily, 1.1.0-span is the first child of 1.1-span.
That is user case <2>.
@adriancole So, you can see, in order to fit this spec, they will do a lot of works. Most of them are about encoding and length...

Sheng I think you are explaining that different tracing systems have
different existing encodings and lengths. I don't think that is under
debate. Clearly there are many many existing encodings and many of which
cannot be substituted for others the same way you cannot place the contents
of the http header Date into the header Cookie and expect it to work.
Maybe if I ask another way. How would you process the ID of another system
you mentioned even if you are only doing offline correlation? What would
you do with trace context: acbdef that was given to you? What would you
propagate downstream? Would you replace the header with yours, would you
restart a trace? or would you be ok halting all tracing due to this
unexpected value?
Even in discussions of B3, until you are an intermediary it is easy to not
think things through. For example, if you propagated through a tracing
system Y and they disagreed with your format then sent a request downstream
to a skywalking system, this would break your trace in the same way as it
would break without this spec, wouldnt it?
It seems that if in absence of this spec folks can figure out ways to
coexist with B3 we might be able to do at least the same here..

IMO, I think for a correlation id, included trace-id and span-id of course, skywalking saved these two keys(only care max length, not use a separated key, and ascii encoding), generate a new trace. In fact even for sw3-head, we generate a new one too. The difference between these two is,

for sw3, generate a trace-ref;
for other system, generate correlation(tags) values.

User can query trace by correlation trace-id through skywalkingUI. And the can see the correlation values if this trace has correlation ids.
And for more, based on this spec, I hope all participated tracing systems, can provide a standard query condition, e.g. http:/xxx:xx/zipkin/trace?tid=ttttt&spanId=sssss. So I submit an issue about vendor id. After have that, the tracing system can config the mapping from vendor to url(e.g. http:/xxx:xx/zipkin/trace for zipkin) ref #14 .
This can really help users to take benefits from tracing system interop. I think that matters.

Sheng, so what we have the ability to influence here is headers, and
we've mentioned trace-context as the scope of what this header is.
let's step back a sec.
In concrete terms, a propagation system needs to push the context from
one side to another. If only doing one-time log correlation, you could
just accept the incoming trace ID write to your external system, and
be done. If wanting to allocate these things to an operation, you'd
also need a span ID. The trick is that the latter changes, it will
change possibly many times per hop.
So when we define a propagation spec, we do need to indicate what
happens when the span ID changes, similar to how the Date header is
defined as the time a message originated, and placing 2029 as a date
is unexpected, the span part should ideally represent something. In
the way we've discussed this so far, that span part is the previous
remote operation.
So, if we remove the formatting constraint, here's what happens to propagation.

we can still pass the context from one side of the process to the other
we can tokenize IDs and log and/or add tags for out-of-band processing

However, we no longer have a fixed contract of any kind with trace
implementations. Does this matter?

when allocating a remote parent to a new child, we could imply all
tracing systems support linking (to establish a relationship with a
too wide ID). This has a cost to it
when sending a context to a remote party, we could send too little
info, requiring again linking or filling or something else.
the trace id itself may not fit in either side, eliminating the
ability to easily correlate. Some may prefer to overwrite the trace ID
into something they can understand.

Basically, I question the value of these lookups. Do you feel otherwise?
Sometimes I wish we would just make test cases as it takes hours to
discuss in abstract things that are obvious in implementation.

I want to clarify what this issue was about. One aspect of it was about variable-length IDs, which is currently discussed in @bhs's PR #19. The other aspect was about the encoding. For example, suppose some tracing system generates trace-ids in the form {serviceName}-{randomBytes} (@wu-sheng mentioned something like that, only with numbers). We could support it if we allowed arbitrary strings, but there are two problems

we'd still need to talk about some encoding since we might want to reserve - as a trace/span id separator
such trace-id scheme would hardly work if the system that uses it was on the receiving side, where it might get an opaque hexadecimal string

Does that mean that the only acceptable un-encoded representation of a trace-id is opaque byte array? I.e. no system receiving Trace-Context header should attempt to interpret the parts of that byte array since it has no guarantee it's a value compatible with its internal semantics (like two longs in Skywalking).

@yurishkuro I think you are talking in the same issue about completely different problems. I am not saying that they not need to be discussed but the initial issue was about removing "hexadecimal" restriction.

Nobody seems to object to the existing fix-length hex encoding, so closing this.


what other video sites are supported by Adaptivecards

Hi, whether the Adaptive Cards can support any other video website except Youtube, I have tried to use Youtube video URI as the source of Media and it works, but my users cannot see these videos because it's on Youtube and they do not have VPN to see it in China. I also try to find the videos URI in some other websites but cannot use them as source. I want to know whether there have some sites and the videos in the sites can be used in Adaptivecards so I can upload video to the site
[Your detailed feedback here]

URL: https://adaptivecards.io/explorer/MediaSource.html

@denniszhang49,
AdaptiveCards doesn't do anything special. the mimetype is just a hint for video player.
as long a the video can be serviced by uri and amongst the supported video types, it will work.


Using PySide2 5.14 instead of 5.13

Not really an issue, but I wanted to get in touch with the maintainers of the conda recipe.
I know moving forward with Qt versions is a major problem due to all the dependencies that updating Qt might break, but in any case, many things are fixed or improved with the new PySide2 versions, including the compatibility with Python 3.8, qApp macro issues, the __signature__ story, etc.
For this, we decided to make PySide2 5.14 compatible with Qt 5.13 (and 5.12), in the sense that one can build it against that version on Qt, having then all the improvements to libshiboken/libpyside.
I don't know if this can cause any issues on the applications depending on PySide2, but the only source incompatibility now is that when working with qApp one cannot delete it implicitly, but needs to call the shutdown() method.
Maybe this will help the situation you are currently facing with all the additional patches you need to apply for the recipe.
We are following the conda support story, so in case of further issues, don't hesitate to drop us a report in JIRA.

If there is not too much work involved I think we should update:
https://github.com/conda-forge/pyside2-feedstock/pull/71

we cant do that, because the uic utils are part on qt now instead of pyside; so moving to pyside 5.14 would mean no more uic utils

ok, so I guess we should wait for qt5.15?

yes

@jschueller please ping me here or any other platform in case you face some issues while building or runtime bugs, hopefully 5.15 can be working without any problem :smile: :snake:

see https://github.com/conda-forge/qt-feedstock/pull/156, I already tried to update to 5.15 and its not going to be easy


Add support for decimal types

Decimal types are not currently supported, it would be great to include them

Published your changes (and the multi-part checkpoint) as version 0.2.9
#32


rake data:validate

very basic reactive data integrity strategy

Off the top of my head, in the past most of our 'bad data' problems on staging were related to a mismatch in task types and MMTs and creating new papers (it's been a while).  Would those records have been caught as 'invalid'?  I think the logic for this is fine, just want to make sure that we catch our most common scenarios as long as we're doing the work.

@Bestra - no, this script doesn't catch invalid Task types, but we can address that,
and @ryanstocker, good looking out.  1000+ records isn't something we're bumping into yet, but this pattern is more than reasonable, so we'll get it in there. Thanks!

Looks alright to me.


"Fizeșu Gherlii", "Bonț", "Lunca Bonțului", "Nicula", "Săcălaia" are listed in the drop-down

Description:
When user writes "Fizeșu Gherlii", "Bonț", "Lunca Bonțului", "Nicula" and "Săcălaia" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Fizeșu Gherlii"
Expected results
The location appears in the drop-down menu as "Sat Fizeșu Gherlii, CLUJ (Fizeșu Gherlii)"

Step 2
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Bonț"
Expected results
The location appears in the drop-down menu as "Sat Bonț, CLUJ (Fizeșu Gherlii)"

Step 4
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Lunca Bonțului"
Expected results
The location appears in the drop-down menu as "Sat Lunca Bonțului, CLUJ (Fizeșu Gherlii)"

Step 6
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Nicula"
Expected results
The location appears in the drop-down menu as "Sat Nicula, CLUJ (Fizeșu Gherlii)"

Step 8
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 9
Write in the search bar "Săcălaia"
Expected results
The location appears in the drop-down menu as "Sat Săcălaia, CLUJ (Fizeșu Gherlii)"


[Bug] Using a response body in environment settings gives an "Unexpected token % in JSON" error

Overview

Insomnia Version: 5.3.6
Operating System: Win10 Home (Creators Update)
Summary:  If I use the new response parsing feature directly within a request it all works perfectly, but if I transpose the same response into the environment settings then it doesn't work. At the bottom of the page I get the error "Unexpected error % in JSON at position 13"

How To Reproduce

Create new auth request
Perform request and auth successfully
Go into environment settings
Create new variable
Assign it to a response body, use JSONPath and confirm that the Live Preview finds the correct field
Select OK
Observer error at bottom of page and be unable to select "OK" or any other sub-environments

Other Notes
Thanks for adding this feature, it's going to make my life that little bit more pleasant as I'll no longer have to keep copying my JWT back and forth from auth responses

Make sure you have quotes around your tag.

Under the hood, the tag is saved as {% response 'body', 'request_id, '$.json.path.query' %} so, if there are no quotes, the JSON becomes invalid.

Well, now I feel embarrassed. You're quite right, it was a quoting issue. Thanks for your help.

Don't be embarrassed @Fritzbraun! The error doesn't make it clear that that's what the issue is.
Glad that helped and you're welcome 😸

Hey @zkghost. Did you end up figuring it out? I'd be happy to answer any questions you have.
There is a brief bit of documentation here but it could definitely use more examples. Did you find that page?

@gschier I did end up finding it out; I think initially I was using the Nunjucks templates wrong.
Think my problem was that I was searching for things around "setting variables" instead of chaining requests.
That page does look pretty good though, I think it was just my bad for not searching for the right thing 👍

Right. Perhaps I should also make a page for dynamically setting variables that explains that chaining should be used.
Definitely not your fault. The product should always serve the user 🤵

:) Wouldn't hurt.
Thanks also! Used Postman for months and your product is a refreshing alternative :) really like the way variables are integrated. Keep up the good stuff! And the great service :D!

 I always love hearing positive feedback 😄

@gschier Could you write a user-friendly message? And it is not clear what to do.

Unexpected token % in JSON

what happens when the thing I want to send is actually an object and not a JSON string?

@danielo515 this problem doesn't exist when using a variable in a JSON request. The syntax checker will complain but the request will still send


Capistrano deployment overwrites cron jobs of previous deploys

Testing Capistrano deployment on ITS has exposed an unfortunate bug - if we're installing multiple instances on a single server, each time the whenever command is run we end up overwriting the crontab from prior installations. This means that only the last instance to be deployed will have cron jobs running, which is clearly problematic. We should try to find a quick fix for v5.5.1 to be followed up with a more robust fix in #1328.

Ok, this is by design - whenever looks for existing whenever-generated crontab entries and overwrites them, and doesn't distinguish between multiple instances. I'm not sure there's a way to edit whenever, so we might just have to roll this into #1328 and try to get that out in the next month.

Never mind, we should be able to pass a custom identifier to whenever to keep everything separate (see here). I'll try to figure out the best way to do this.

Ok, all done, just reverted to the built-in whenever Capistrano tasks. I added an extra environment variable to the cap deploy command, IDENTIFIER, which can be used to separate between different deployments. Issuing PR now.

Note that we're not currently opening up a PR for master since hopefully this will all be superseded by #1328.

Closed via #1374

Since #1328 didn't make it into v6.0.0, I'm going to quickly open a PR for this for master.


Great job! When will open the dataset, Thanks !

+1

We have released the inference code and checkpoints, please feel free to contact us if you have any questions.


feat(extras): added fsharp support

Added fsharp support  #3470

Would also be great if you could read https://github.com/LazyVim/LazyVim/blob/main/CONTRIBUTING.md
(if you haven't done so).
The doc is new

https://github.com/ionide/Ionide-vim?tab=readme-ov-file#requirements
Check the repo out , this plugin supports both vim and neovim and it is written in lua and vimscript both, to support both editors, and there is no lua only solution for fsharp, it is easily overridable , according to my knowledge


Upgrade selectors

Fixes deprecated selectors in Atom 1.13.0 and above.

Hi, thanks for this. I'm no longer maintaining this package, would you like to be the new maintainer?

That would be great, thank you!

I'm out of office, will be back later this week and will transfer the
ownership  of the project to you.
Thanks again for your contribution,
Claudio
Il dom 26 mag 2019, 15:08 Nathan Allen<EMAIL_ADDRESS>ha
scritto:

That would be great, thank you!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/claudiodangelis/dun-syntax/pull/3?email_source=notifications&email_token=AAHF7C7YEZII43FOONSS5O3PXKDVVA5CNFSM4HPU6LZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWIFOLA#issuecomment-495998764,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHF7C7VG6ISNEOP5C6U3HDPXKDVVANCNFSM4HPU6LZA
.

Sounds good, thanks!

@nallenscott hi, I'm initiating the process of transfering the repository, please make sure to delete your fork otherwise I can't proceed.
I reached out  to Atom support to request information about transfering the package, will keep you updated on this. Thanks for maintaining this project :tada: !
More info: https://help.github.com/en/articles/transferring-a-repository

Deleted, and my pleasure. Thanks for the opportunity!


Make fields store work for nested data

A bit tougher to handle than #70, making $fields work for any nested form data, instead of just top level, would be a nice update.
The problem is that it needs to traverse three data structures (form, errors, constraints), taking undefined values into account. Metadata needs to be either converted to a nested structure, or skipped for non-top level fields. It's a bit of work.

Related: #50

This is working now with v0.6.17. A whole article is written about it here: https://superforms.vercel.app/components


LDSSA Prep Course - Financial help for students

We need to decide to what extent we can offer help in terms of finance? There are several options as follows - feel free to suggest more:

Offer Dataquest promo code (we still need to wrap this up with Dataquest)
Subscribe to the team solutions ($25/month per user for Basic plan and $40 for premium plan)
Buy a few account and ask people to rotate between themselves (There are several drawbacks to this in terms of sharing & progress tracking so I don't think this is very ideal)

Would be very interested to hear what people have to say about this but I think that the students should have a bit of skin in the game as well as their own dataquest accounts.
My favorite option would be to give them a promo code that would allow for a discount. That way we can provide them with a bit of help / incentives to sign up while at the same time ensuring that they have made a small investment that would hopefully increase the motivation to finish.

I agree with Sam on this. In this case we won't be restricted by the number of students we can accept.

Option 1
How much discount does the promocode give? How much do students end up paying with this option?
At a first glance this seems the best option.
Option 2
Who pays to whom with this option?
Do students need to pay us and then we pay Dataquest? If so, I don't like this option much, as it gives us extra work that we probably don't want at this point.
Option 3
Really don't like this one. First because it's not very honest, especially considering that Dataquest is giving us promocodes, in order for us to do it right :)
Then, because tracking progress is a great way to motivate the students in their learnings, so having to share accounts would be messy!

We need to figure out the promo code thing! I'll open up a convo on slack about it since we have a few folks with contacts at data quest.

We have a 50% off on DataQuest, is it viable/desirable to use Academy money to finance it further?

Do we already have to discount code that we can distribute to the students?
As far as helping finance it, we've decided against it.

This is the last we've heard from them, 12 days ago:
Hi Pedro, sorry for my delay in follow-up. I have gotten approval to offer a special discount for your students!

We offer 1/2 price for their first 90 days of either the basic of the premium subscriptions. They simply need to write into<EMAIL_ADDRESS>and request a coupon be added to their account.

I will draft a more official doc around this and share shortly!

Have a great week,
Celeste


Can't run on device

http://stackoverflow.com/questions/35169089/library-load-with-google-calendar-api-obj-c

Are you packaging it as a framework within the app? i.e. - with the Frameworks directory within the app?  The linker path in the error seem to indicate that is what it is expected.

Hi Thomasvl how do I do that? I can't seem to build the framework? The name is in red. Also, when I try to add to "Show in Finder" it can't find it...because it's not there.

Thomas would you be up for doing a quick Skype screenshare?

Thomas, I ended up (hopefully) fixing the problem by changing GTLiOS Core Mach-O Type from Dynamic Library to Static Library. It now runs on both the simulator and device. Will this have any negative side affects?

That "works" in the sense that it no longer makes a framework and just bundles all the code into a static library that is then linked it.
I finally got a chance to update the building docs to cover the framework and cocoapods, so I'm going to going to go ahead and close this out, hopefully the update docs can help folks also.


Bug: Import Module Text

Issue:
Right now the import module text is not consistent in all of the modules for example in emissions it reads:

As an  ECMPS user, I want the import module text to be consistent with respect to what module I am trying to import into:

Import Monitor Plan Data...
Import QA Certification Data...
Import Emissions Data...

Tested and confirmed import module text is now consistent


Increment versions for trustedsigning releases

Increment package versions for trustedsigning releases

API change check
API changes are not detected in this pull request.


Add setupapi support

Rebased against master

PR is failing CI.

Could you rebase to fix the merge conflicts?


Support other spatial operation for 'geo.boundary' query

added @JsonProperty("operation") SpatialOperations operation

Done


Regression: Subject Area FVT fails when run against Janus graph

The Subject Area FVT fails when run against Janus graph. The console shows this error :
"ERROR: OMAG-COMMON-400-016 An unexpected org.odpi.openmetadata.accessservices.subjectarea.handlers.SubjectAreaGlossaryHandler exception was caught by find for Glossary; error message was OMAG-REPOSITORY-HANDLER-400-003 An unexpected error was returned by the metadata server during findGlossary request for open metadata access service Subject Area OMAS on server cocoMDS4; message was OMRS-REPOSITORY-400-055 An unexpected exception was received from a repository connector during the findEntitiesByPropertyValue operation which had message: Could not process individual retrieval call  Suggested action: Review the error message and other diagnostics created at the same time."
The first thing that the FVT does is a find for all glossaries using a criteria of .*
The error comes from Janus graph and occurs on line 1715 in GraphOMRSMetadataStore. I assume some change to search in Janus graph has caused this to fail. The In memory repository works.
@planetf1 This is the second time that the Subject Area FVT has exposed a difference between the repository implementations. I think we should consider running the Subject Area  FVT twice once agains the in memory and once against theJanus Graph.
@cmgrote @grahamwallis are you aware of any Janus Graph repo changes that have occurred recently that might have caused this?

Hi David
Partial reply... the fvt is set up to run against both inmem and graph. This gets done for every PR.

Here's an example run from a recent pr
https://dev.azure.com/ODPi/Egeria/_build/results?buildId=9826&view=logs&j=4dc6fbf2-95db-5f93-ea5a-117822a16d38&t=61dc2478-351e-57b7-3c49-54d8ca2911d9
Search for TermFVT
There's some issues with slf bindings and verbosity but the tests are running. 18 in fact. That is for inmem and graph as we are using parametrised tests to go against both deployed servers
So I assume your failure is in local build. Can you check it works ok on master? If so could it be a change? Happy to try your branch or suggest you create s a draft pr to verify

The error code being reported seems to be from the Enterprise layer, which suggests that it would be independent of the type of local repository, which supports the results reported by @planetf1 above.

@planetf1 I tried locally against the latest master no changes and it was working on in memory and not on graph. The error I was seeing was in Janus specific code. It must be a local quirk - I am glad is not an issue more generally.

The error code being reported seems to be from the Enterprise layer, which suggests that it would be independent of the type of local repository, which supports the results reported by @planetf1 above.
Thanks Graham - I will clean my machine and debug locally.

@davidradl Could you please post the error you are seeing?

Maybe even the full logs... be good to understand what is different about the config.
Also can you confirm how exactly  you are running the tests?

Is this still an issue? Does it relate to a specific branch/commit in your fork - or just master? Happy to try it out locally if you can describe your config.
Also I presume you clear out any old cohort config/graph repos etc prior to the run (the formal FVTs always start clean)

My config must have been incorrect in some way, I retested with a newly created config and it worked.