Make Stateful Constructions: The Capsule Hack

2020-06-17 Note Improve characterization of Constructor and Factory Capsule Hack Representations
I2020-06-14 Note: More about Semblance.
2020-06-06 Note:  This issue on incorporation of state into computational interpretations has become an extended treatment.  It is still offered as an issue, although it may also be the basis for documentation of the approach raised.

oMiser is not object-oriented in any sense that is applied in computer science and programming practice.  The pure functional nature of the oMiser computational model would, on the face of it, suggest that encapsulating any state and operating via successive transformations of that state is not intrinsically available.  That's not the case.
There are oMiser representations of encapsulation that provide for binding of state with scripts for acting on the state.  A particular representation, the Capsule Hack convention, hinges on how enclosures can be used to connect a script and state data within an applicative individual.
The Capsule convention is termed a hack to direct attention to four considerations.

Capsules are an emergent arrangement, however latent in the computational model itself.  Capsules are representation or interpretation, but produced bottom-up, a kind of "hey, look at what I can make oMiser do."  It is grounded in the computation model's reliance on enclosures as a representation of the K combinator, capturing a way that a script, p, can access an enclosed portion of itself as unevaluated data, the current state, within ap(p, x) operation.  (See combinators.txt for interpretation of combinatory structure ‹ca› in ‹ob›.)

Capsules are rather arbitrary and crufty, being a chosen representation that is not inherent at the computation model level yet assured by the stored-program principle as honored by the oMiser formulation.

Capsules are crude demonstrations that very useful computer codes, including classy algorithms, will not resemble the problem they are organized to solve.  This is a critical factor when we consider automated deductions about oMiser scripts as representations of higher-level notions.

That Capsules be so terribly inscrutable and confined to complex arrangements of obs is something that must be overcome by ways of presenting representations at a level that captures the intended sense of a semblance and allows results of applications to be expressed at the intended level.  The fundamental case will be introduction of strings of characters, with arithmetic another.  The reasoning for that will be based on capabilities involving the Capsule Hack.

The development all the way to use of factory scripts as creators of semblance-instance constructors is not the most evident and heart-warming scheme.  To ascertain value beyond mere demonstration of the possibility will take experimental demonstration and assessment of the degree to which confident usage is achievable.
1. Capsules
By convention, a capsule consists of an individual ob instance of the form

let instance = .proc (.ev :: ``pRep :: ` obState) ;

and the oFrugal (ob-exp) hand-compiled script implementing that construction is along the lines of
^pInstance = .C :: ` .PROC
                :: .C :: `.EV
                      ::  .C :: ` ``^pRep
                             :: `  `^obState ;

where

pRep is a script that provides operations on .def(pInstance) in a manner that sustains the capsule's computational semblance as a member of an abstract class (cf. #22).
obSstate is the ob representation of some abstract class domain entity relative to the operations and restraints of the applicative script pRep.
binding names such as ^obState are sometimes use in specimen scripts to emphasize where variable are intended despite typographical limitations in code blocks.

When obState is constrained to be a canonical form with respect to the abstract interpretation, equality of pInstance corresponds to identity of the represented abstract entities.  Otherwise, any identity achieved by simulation must be verified by other means.
1.1 Semblance of Class Domain Instances
The notion of semblance (a corruption of resemblance) is employed here to signify a computationally-accomplished manifestation of an abstraction.  There are many ways to have accomplished that, and there are additional incidental characteristics that accompany  the representation of computational interpretations.   Semblance is a pragmatically-appropriate distinction of such computational representations from the abstraction they stand as interpretations for.
Even when there is establishment of a clear interface boundary for the manifestation of a computational class, pragmatic features remain inescapable part of the established interface.
In this setting, there are two senses of "class."  The shared conception is that there is a quality of an entity -- satisfaction of some predicate -- that determines an entity's membership in a particular class.  Here capsules are taken to be computational-interpretations of abstract class domain entities, and the shared quality is having the capsule instance pattern with the same pRep.  This is a syntactic distinction, not a semantic one.  It is one semblance out of many.  Generally, there can be many semblances of the same class, differentiated by differences in pRep, the representation of obState values, and the manner in which features of the semblance are manifest, both syntactically (by different namings) and semantically (by variation among operations and operands).
Demonstration that semblances be effective computational interpretations of some (semantic) abstract classes is by the constraints on obState that are honored in the creation of an initial pInstance and in how subsequent operations via application of the capsule to appropriate operands constitute interpretation-preserving representations.
In this arrangement, pInstance occurs as an individual, a kind of literal.   As such it is immutable.  And, at the same time, the pInstance provides a tight binding of the obState to the pRep by which semblance is achieved and preserved.
1.2 Applicative Interpretation of Capsules
The convention for use of a capsule is via
ap(pInstance, feature)  = ev(.EV :: ``pRep :: `obState, feature, pRep)

such that in ap-internal evaluation of the pRep script,
 .SELF = .EV :: ``pRep :: `obState
 .A  :: .A :: .A :: .B :: .SELF = pRep
 .A :: .B :: .B :: .SELF = obState
 .ARG = feature

and a new capsule that differs only by introduction of obNext for obState is produced by script
.PROC :: .C :: `.EV
            :: .C :: (.A :: .B :: .SELF)
                  ::  ` ` ^obNext

The oMiser convention for producing traces for operations that cannot go further is sustained here by evaluating script
.C :: (.PROC :: .SELF)
   :: .E :: .ARG

when feature (.arg in that context) is not a defined case.
These characteristics of the Capsule Hack provide the framework for computational interpretation of abstract classes by tightly packaging together (1) the representation of domain entities in obState and (2) associated computational interpretations of theoretical functions over such entities via pRep operations.
2. Idiomatic Semblances
There are additional conventions for the specification and operation of pRep scripts.
2.1 The List Searching Idiom
The feature cases of a Capsule Hack semblance can be represented by a list of pairs,
case = (v1 :: c1) :: (v2 :: c2) :: ... :: (vn :: cn) :: ` default
     = [v1 :: c1, v2 :: c2, ... , vn :: cn, ` default :]

with default the case that is determined when feature does not match any of the ci.
The selection of cases for values of  feature is obtained in functional pseudo-code by
let find(feature, cases)
    = if is-singleton(cases)
      then cases
      else if feature = .b .a cases
           then .a cases
           else find(feature, .b cases);

In this arrangement, the result is always an ob r such that .a(r) is the corresponding case for the specified feature (or the default case otherwise).  This is the Cluster Hack idiom for selecting cases by explicitly-matching obs.  A close variant has the ci be scripts representing predicates, so the
   else if feature = .b .a cases

portion becomes
   else if (.b .a cases) feature

2.2 Semblance Feature Selection
There is technical improvement by restating the definition of find(feature, cases) in a way that
has feature fixed in the iteration through cases.
let finder(feature)
    = rec.again λ.cases
       (if is-singleton(cases)
        then cases
        else if feature = .b .a cases
             then .a cases
             else again .b cases )  ;

(In this Frugalese functional pseudo-code, the infix-dot notation (#24) provides a way to signal left-to-right application and is also a sugaring for rec and λ being defined by applicative scripts in the computational model.  Hand-compiled scripts here illustrate how applicative abstraction can be mechanized in oMiser model of computation.)
Cluster Hack, cases are the same for all instances of the same semblance.  This fixed nature is represented by
let selector(cases)
    = λ.feature ( finder(feature) (cases) ) ;

2.3 Semblance Instance Arrangement
Although we have functional characterizations for selector and finder, there is also indication of where there can be "code motion": evaluating some elements in advance for repeated use without repeated derivation, as in the binding of cases in the result from selector(cases) and in the binding of feature once in the recursive procedure yielded by finder(feature).
The fixed pRep value in a Capsule Hack Semblance Instance consists of the formulation
pRep = .ev :: .a :: ` selector(cases) :: .arg

with selector(cases) returning the script that represents the selector-defined function for accepting feature operand.  Because the selector result is not (directly) recursive, we can simplify  by in-lining selector(cases), giving
pRep = .ev :: .a :: selector(cases).

and any .arg that is requested at the top level of that script sequence will correctly match to feature in the evaluation of ap(pInstance, feature).  In-lining an applicative script is a counterpart of similar practices in optimizing compilers for conventional computers.  It will arise often in hand-compiling oMiser applicative scripts.
The ob-exp code for pRep is then
^pRep = .C :: ` .EV
           :: .C :: ` .A
                 :: ^pSelector(^obCases)

This will be fully worked out in the oFrugal translations of the functional pseudo-code of selector and finder.  For now, we trust that the elimination of a level of application is warranted from what is known about the script returned by selector(cases).
What happens with Capsule Hack semblance of an abstract data type is is that each defined feature operand will determine a script to be evaluated in the same context as evaluation of pRep.  That is (from 1.2 above),
 .SELF = .EV :: ``pRep :: `obState
 .A  :: .A :: .A :: .B :: .SELF = pRep
 .A :: .B :: .B :: .SELF = obState
 .ARG = feature

To complete construction of an instance, a specific list structure for cases is required along with establishment of the (initial) obState.
In addition, all semblances constructed via the Capsule Hack will behave the same when cases has no entry for the feature operand.  The singleton that ends the cases list will always be
` (.C :: ( (.PROC :: .SELF)
       :: .E :: .ARG )

conforming to (1.2) by providing a trace where there is no way to take the evaluation further.
3. Semblance-Instance Constructors
The nature of a Cluster Hack semblance instance is as follows in the development so far.

the common pRep component of every semblance instance is determined by the cases list supplied to selector(cases) in the instance construction.  This is what is typical of all instances of the same semblance.

validity of the initial obState must be established by some means.

3.1 Thinking Out-Loud
One possibility is to have a "new" feature such that instance.new(setup) produces a new instance with _obState derived from setup.  There are two engineering objections: (1) how unacceptable state operands are treated and (2) whether one wants the ability to make new instances to be available to any function where instance is supplied as an operand.  The second consideration applies to other methods as well, and this may involve differentiation of interfaces, a topic for later consideration.
For now, consider
CHTinstance = CHTTconstructor(obSetup)
              where CHTconstructor =  CHFactory(pRep)(pCastOb)

Here prefix CH identifies the Cluster Hack conventions and CHT will be adjusted to identify a particular semblance of a "type.,"
The pCastOb will typically operate as follows

pCastOb(obSetup) yields ob.e(obSetup) if obSetup is invalid for the semblance implementation
pCastOb(obSetup) yields an obState canonical form, if any, for the represented domain entity if relevant
pCastOb(obSetup) simply yields obSetup when it is admissible as obState and alteration is unnecessary

The pCastOb can also be more elaborate, deriving a state in different ways for given obSetup operands.  That would be a semblance-specific situation.  The ob.e(obSetup) yield is still employed in the case that the operand is invalid and the CHTConstructor must fail (resulting in a suitable trace)..
3.2 Factory Determination of Constructor Failure Modes
The ob.e(obSetup) result is distinguishable as a form of trace.  What is wanted as the CHTConstructor in this situation is a trace-form of pCHTInstance that carries enough of its origin to be revealing under inspection.
In the invalid construction case, it is straightforward to replace obCases by the always-tracing singleton,
` ( .C :: (.PROC :: .SELF)
     :: .E :: .ARG )

and the remaining question is what else to provide.  A simple approach would be to employ
obState = (^pCHTConstructor) :: ` obSetup

assuming pCHTConstructor  to be a proc, perhaps.  The resulting pCHTInstance is itself a trace and the obState of that is additional trace.
3.3 A Hack Too Far?
The test of this formulation will be in the successful creation of usable scripts that represent the signified functions under oMiser application.  Updates of this issue will reflect implementation experience.  There can then be assessment of utility, even as a demonstration.

Using functional Frugalese as a pseudo-code is rather confusing with the ob-exp notation of oFrugal as the assembly language for obs and obs taken as scripts.
Distinct use of letter-case for primitives helps differentiate: lower-case in pseudo-code, upper-case in oFrugal ob-exps.
Here is a demonstration with hand-compiled derivation of pFinder.
First
 (if is-singleton(cases)
        then cases
        else if feature = .b .a cases
             then .a cases
             else again .b cases )

has the following hand-compiled ob-exp script
.EV :: (.D :: cases :: .B :: cases)
       :: `( cases
             :: .EV :: (.D :: feature :: .B :: .A :: cases)
                       :: `( (.A :: cases)
                             :: again : : .B :: cases
                              )
              )

Next,
λ.cases
 (if is-singleton(cases)
        then cases
        else if feature = .b .a cases
             then .a cases
             else again .b cases )

is achieved by simple substitution in the script ob-exp.
.EV :: (.D :: .ARG :: .B :: .ARG)
       :: `( .ARG
             :: .EV :: (.D :: feature :: .B :: .A :: .ARG)
                       :: `( (.A :: .ARG)
                             :: again : : .B :: .ARG
                              )
              )

In this case,
rec.again λ.cases
 (if is-singleton(cases)
        then cases
        else if feature = .b .a cases
             then .a cases
             else again .b cases )

also follows by simple substitution.
.EV :: (.D :: .ARG :: .B :: .ARG)
       :: `( .ARG
             :: .EV :: (.D :: feature :: .B :: .A :: .ARG)
                       :: `( (.A :: .ARG)
                             :: .SELF : : .B :: .ARG
                              )
              )

Abstraction of a variable can also be more complicated, as when we want to handle
let finder(feature)
    = rec.again λ.cases
      (if is-singleton(cases)
       then cases
       else if feature = .b .a cases
            then .a cases
            else again .b cases )

where the rewriting to incorporate the feature operand into the recursive script is more involved.
^pFinder =
                            .C  :: ` .D
                                ::  .C :: .ARG
                                       :: `(.B :: A :: .ARG)
.EV :: (.D :: .ARG :: .B :: .ARG)
       :: `( .ARG
             :: .EV :: (.D :: feature :: .B :: .A :: .ARG)
                       :: `( (.A :: .ARG)
                             :: .SELF : : .B :: .ARG
                              )
              )

Deriving pSelector script representation of selector(cases)
let selector(cases)
    = λ.feature ( finder(feature) (cases) );

is representable by
^pSelector = .C :: ` (.C :: ` ^pFinder
                         :: .ARG )
                :: .E :: .ARG  ;

Since the ^pFinder script is non-recursive on its first operand,, we can simplify away the unnecessary application to a feature .ARG with
^pSelector = .C ;; ' ^pFinder ::  .E :: .ARG ;

and ^pFinder will pull the feature operand when ap(ap(^pSelector, obCases), obFeature) is carried out.
This sort of short-circuiting occurs frequently and implementations of pλ and pRec should exploit that whenever the opportunity arises.

To get to
instance = constructor(obSetup)
           where constructor =  factory(pRep)(filter)

Looking into constructor's handling of filter.  it is desirable to avoid carrying out ap(pfilter, obSetup) more than once.  So we will have something like
let factory(pRep)(filter)
    =  rec.pConstructor λ.obSetup
      (let obState = filter(obSetup)
        in if obState = .e obSetup
            then mkfailure(pConstructor) obState
            else  mkInstance(pRep) obState )

[to be continued]

I've gotten in deep here.  I also need to think about how "compute expressions" (issue #30) might rely on the Capsule Hack in some manner.  I am also concerned about ephemeral use of semblances (as in cascading operations) is very costly if the semblance is a proc (issue #22) and impacted by accelerators (issue #26) and proc being rather heavyweight.
With regard to semblance, it is valuable that pRep be a proc, since it is persistent in all of the instances of a semblance.  It needs to be checked how that can work in the workings of the Capsule Hack.  Probably not.  This is a note-to-self.

I've been thinking that starting with factories, the pRep and pCastOb should be joined at the hip, since together they determine the (extensional) computational-class representation.   I need to arrange things so that is explicit and a combination that constitutes a semblance "type."
I am also thinking that at any point, pCastOb(obState) should be idenpotent and appropriate for any feature by which 'obState' is "extracted."
Mull this over.


V1.0 Satellite Sequencer

We need to create a sequencer to schedule satellite commands to happen at various times!
FPrime Reference
https://nasa.github.io/fprime/UsersGuide/gds/seqgen.html

Quick note, based of the description and tags, sequencers in F´ already exists and is built-in to the refs. There are a few things that need to be done though to make it mission-ready.

Based of design patterns in Ingenuity and many other satellites, you'd want to create a main sequence file that is very carefully and checked extensively to ensure that it cannot fail that sets up parameters and initiates other sequences. This is mainly to prevent the deployment binary from completely fatal asserting if a particular command gets hanged.
To facilitate this, you will probably need to create a bunch of sequencers and connect them to the dispatcher. Many Missions had at least 16 sequencers, but it is likely Proves will need less than this.
IMO unit testing and system testing will help a lot in the future for testing the sequence files. That way it'll be a good check if proper commands are being executed per the sequence.


Saleor-Platform Installation Didn't work

The problem
Saleor Documentation said to use
git clone https://github.com/mirumee/saleor-platform.git --recursive --jobs 3
to install the saleor-platform. But it didn't pull sub-modules.
I got nothing in saleor, saleor-storefront and saleor-dashboard folder.
How I solved it
I did
git clone https://github.com/mirumee/saleor-platform.git
cd saleor-platform
rmdir saleor saleor- storefront saleor-dashboard
git clone https://github.com/mirumee/saleor.git
git clone https://github.com/mirumee/saleor-dashboard.git
git clone https://github.com/mirumee/saleor-storefront.git
docker-compose build
I don't know it is the right solution. I'm new here, so please point me out.

The first time I tried that, I got some github access errors. I had to ssh-add my key first. I've done the full clone, etc process a few times this week and have had no issues. I would try again and look for any error messages.

Okay. Thank you.

@Swanhtet-grc Hey,  i hope this might help. https://www.youtube.com/watch?v=AKHUyKu59hI&t=343s

I already got the solution. I opened this issue because I just would to check my solution is the right solution or not.
And I would like to check the official docs of Saleor is right.


[CT-1917] [Regression] Non-error log is not silenced by -q flag.

Is this a regression in a recent version of dbt-core?

[X] I believe this is a regression in dbt-core functionality
[X] I have searched the existing issues, and I could not find an existing issue for this regression

Current Behavior
According to -q:

Suppress all non-error logging to stdout. Does not affect {{ print() }} macro calls.

A new log is printed even though it's not an error.
(elementary) ☁  dbt_project [main] dbt run-operation hello
14:22:47  target not specified in profile 'elementary', using 'default'
14:22:47  Running with dbt=1.4.0
hello
(elementary) ☁  dbt_project [main] dbt -q run-operation hello
14:22:56  target not specified in profile 'elementary', using 'default'
hello

Expected/Previous Behavior
Previously, the log was omitted when passing the -q flag.
(elementary) ☁  dbt_project [main] dbt run-operation hello
14:22:15  target not specified in profile 'elementary', using 'default'
14:22:16  Running with dbt=1.3.0
hello
(elementary) ☁  dbt_project [main] dbt -q run-operation hello
hello

Steps To Reproduce

Name a default target without having a target defined.
Run a dbt command with the -q flag.

Relevant log output
No response
Environment
- OS: macOS
- Python: 3.9.6
- dbt (working version): 1.3.0
- dbt (regression version): 1.4.0

Which database adapter are you using with dbt?
No response
Additional Context
I'd love to contribute.

My suspicion here is:

We set up a basic event logger before we have the full set of information we need to initialize it for real (all flags & configs resolved). This ensures that any real initialization errors don't get swallowed. Relevant: #6434, #6447.
The event you're seeing, MissingProfileTarget, is raised during render_profile, which is happening during initialization and before we call setup_event_logger here:
https://github.com/dbt-labs/dbt-core/blob/c65ba11ae6dca5203228320a7f6388ce1796f104/core/dbt/main.py#L225-L232

Should we simply

Hi @jtcohen6 , thanks a lot for replying.
I personally tend to favor (2) because I think that if a user is using --quiet they'd generally like to keep a program quiet at its entirety except for logs made by them (print()) and it doesn't really matter at what phase the execution is.
What do you think?
If that resonates, care to share any guidelines on how can I make this contribution?

I think it would be as simple as turning line 117 to:
 EVENT_MANAGER.add_logger(
     _get_logbook_log_config() if flags.ENABLE_LEGACY_LOGGER else _get_stdout_config(EventLevel.ERROR)
 )

@peterallenwebb How does this approach sound to you? The downside is, I think we'd never actually log MissingProfileTarget, whether or not the user is actually passing the --quiet flag. (Since we haven't resolved flags before this default logger is set up.)

The approach would work, and it would indeed have the consequences you described.
We could, however, add some log configuration code right after command line arguments are parsed so that we can turn on quiet mode as soon as possible, if it is specified. I think I actually like that approach better?

@peterallenwebb I'm all for it!


current branch not pushed when PUSH_ALL_REFS=false

hi :wave:
first of all thanks for maintaining really cool Github Action!
I wanted to use your action to push just the main branch and tags to the mirror repo with the following action:
---
name: mirror repository
'on':
  push:
    branches:
      - main
    tags:
      - '**'

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
      - uses: actions/checkout@v2
        with:
          fetch-depth: 0
      - name: mirror to bitbucket
        uses<EMAIL_ADDRESS>        with:
          REMOTE: git@bitbucket.org:my-org/my-repo.git
          GIT_SSH_PRIVATE_KEY: >-
            ${{ secrets.BITBUCKET_SSH_PRIVATE_KEY }}
          GIT_SSH_NO_VERIFY_HOST: true
          PUSH_ALL_REFS: false

The problem is that this workflow run pushes only tags to bitbucket repo, the current branch (main) is not pushed at all like suggested in PUSH_ALL_REFS docs in action.yml:

Push all refs instead of just the current branch

@skarzi I'm guessing this is because you're using checkout@v2 -- in my experience you must use actions/checkout@v1 for proper functionality. IIRC checkout@v2 does not populate remote refs from origin.

Thanks for your really quick response :+1:
I have run the above-listed workflow using actions/checkout@v1 and nothing has changed.
Here, you can find the censored output log for the above-listed workflow.
Maybe the solution will be to add some refspec based on github.ref to this line in entrypoint.sh?

I think I may have spotted the error, @skarzi -- I think the problem is the YAML type boolean.
Can you try one of the following:

omitting the PUSH_ALL_REFS parameter altogether (instead of declaring it as false)
you can do PUSH_ALL_REFS: "false" (string argument)

I believe that would fix your issue.
However, I'd still like to patch to properly handle YAML booleans if that's the case.

I think YAML booleans works fine, because env variables are interpoleted using " e.g "${INPUT_PUSH_ALL_REFS}"
Solution 1. won't work like expected, because PUSH_ALL_REFS default is true.
Solution 2. doesn't work either - I have tried with actions/checkout@v1 and actions/checkout@v2, both runs haven't pushed the current branch.

Hmmm. What I'm trying to reconcile is this:
In your job log, I see this line is executed:
eval git push -u --tags --force --prune mirror

However, this should only happen if "${INPUT_PUSH_ALL_REFS}" != "false"
if [[ "${INPUT_PUSH_ALL_REFS}" != "false" ]]; then
    eval git push ${GIT_PUSH_ARGS} mirror "\"refs/remotes/origin/*:refs/heads/*\""
else
    if [[ "${HAS_CHECKED_OUT}" != "true" ]]; then
        echo "FATAL: You must upgrade to using actions inputs instead of args: to push a single branch" > /dev/stderr
        exit 1
    else
        eval git push -u ${GIT_PUSH_ARGS} mirror
    fi
fi

So, if [[ "${INPUT_PUSH_ALL_REFS}" != "false" ]]; then doesn't seem to work as expected.

In your job log, I see this line is executed:

This line is executed because I do not want to push all refs, but only the current branch, so I have set PUSH_ALL_REFS to false  (and also have tried "false" string like suggested in your previous comment).
When I do not declare PUSH_ALL_REFS or set it to true it executes:
eval git push ${GIT_PUSH_ARGS} mirror "\"refs/remotes/origin/*:refs/heads/*\""

and pushes all branches.

Ah, sorry, you're right. I got my wires crossed there for a moment. Happens around 3AM.
I wonder if fetch-depth: 0 is an issue here. This would fetch all refs, so they would also be pushed with push -u mirror

Maybe the solution will be to add some refspec based on github.ref to this line in entrypoint.sh?

This now makes more sense to me and seems like a good suggestion :-)
I'll take a closer look this week and try to make a patch, but would also be happy to review a PR earlier if you'd like to make the contribution.


Merge gz-sensors7 ➡  main

➡  Forward port
Port gz-sensors7  ➡  main
Branch comparison: https://github.com/ignitionrobotics/ign-sensors/compare/main...gz-sensors7
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

@osrf-jenkins run tests please!


Figaro gem on dashing

It would be nice to see support for the Figaro gem in dashing so things like github private tokens can stay private.
I tried adding the Figaro gem to dashing and the values are not being pushed through.

What I have now is:
    load_params = YAML::load_file('config/application.yml')
    github_params = load_params['github'].symbolize_keys

    @token = github_params[:github_token]
    @user = github_params[:github_user]
    @org = github_params[:github_org]

and a config/application.yml with:
github:
  github_token: token
  github_user: me
  github_org: my_work

You might have better luck with a Rails based framework, as Figaro is designed to work with Rails.
Try: https://github.com/gottfrois/dashing-rails

Ill check it out, thanks.


Is there a way to export poses in the asset library as 1-frame animations without having to move them to NLA?

On Blender 3.6, currently, the following option ignores animations that are marked as a pose in the asset library. Is that intended?

I know there is demand for more options like this because someone has made a hacky script:
https://github.com/TokisanGames/blender-pushdownall

Hello,
Do you have more information about what you are talking about? Armature or object asset lib? Local or lib from another file?
In a first test, seems armature local pose asset is already taken into account if  the option "All armature action" is checked. (see simple file attached).

test_armature_pose_assets.blend.zip

More than a month without any answer, closing this ticket


Create Page: Governance

We have a Code of Conduct page: https://developer.tbd.website/code-of-conduct/
Let's make a similar one for Governance at https://developer.tbd.website/open-source/governance/.
And this button:

...located at https://developer.tbd.website/open-source should point to it.
Also update the button to not show the external link icon, and link in same window/tab.
Source file to use for the Governance copy is here: https://github.com/TBD54566975/tbd-project-template/blob/main/GOVERNANCE.md

Some work was done to stand this up already by @dayhaysoos in 7769b6e. Going to inline the rest of the Governance content into this page from GitHub.

Done in 0fb0730


Plan flying animation.

Project title
plan flying animation.
Project Description
How does it work
While loading the page you will have the container with city images with some cloud and a plan and boat all are will be in the moving mode.
Stack:
And in order to tick the check box just put x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS

for more details please refer to the attached images.

https://user-images.githubusercontent.com/73521123/169347099-c071e782-8580-4e27-9acc-fd027b65bace.mp4

@AyushSingh22 sir plz assign me


Add number of lines parameter

This PR adds the parameter to specify the desired number of output lines in the tail operation.

While trying to test this i was getting File not found: flow_cylinder.xml,1 but the file flow_cylinder.xml is there present in the list files.

Can you send me which simulation you were using?

While trying to test this i was getting File not found: flow_cylinder.xml,1 but the file flow_cylinder.xml is there present in the list files.

Can you send me which simulation you were using?

"""DualSPHysics example."""
import inductiva

# Instantiate machine group
machine_group = inductiva.resources.MachineGroup("c2-standard-4")
machine_group.start()

# Download the configuration files into a folder
input_dir = inductiva.utils.download_from_url(
    "https://storage.googleapis.com/inductiva-api-demo-files/"
    "dualsphysics-input-example.zip",
    unzip=True)

commands = [
    "gencase config flow_cylinder -save:all",
    "dualsphysics flow_cylinder flow_cylinder -dirdataout data -svres",
    ("partvtk -dirin flow_cylinder/data -savevtk flow_cylinder/PartFluid "
     "-onlytype:-all,+fluid")
]

# Initialize the Simulator
dualsphysics = inductiva.simulators.DualSPHysics()

# Run simulation with config files in the input directory
task = dualsphysics.run(input_dir=input_dir,
                        commands=commands,
                        on=machine_group)

task.wait()
task.download_outputs()

machine_group.terminate()

While trying to test this i was getting File not found: flow_cylinder.xml,1 but the file flow_cylinder.xml is there present in the list files.

Can you send me which simulation you were using?

"""DualSPHysics example."""
import inductiva

# Instantiate machine group
machine_group = inductiva.resources.MachineGroup("c2-standard-4")
machine_group.start()

# Download the configuration files into a folder
input_dir = inductiva.utils.download_from_url(
    "https://storage.googleapis.com/inductiva-api-demo-files/"
    "dualsphysics-input-example.zip",
    unzip=True)

commands = [
    "gencase config flow_cylinder -save:all",
    "dualsphysics flow_cylinder flow_cylinder -dirdataout data -svres",
    ("partvtk -dirin flow_cylinder/data -savevtk flow_cylinder/PartFluid "
     "-onlytype:-all,+fluid")
]

# Initialize the Simulator
dualsphysics = inductiva.simulators.DualSPHysics()

# Run simulation with config files in the input directory
task = dualsphysics.run(input_dir=input_dir,
                        commands=commands,
                        on=machine_group)

task.wait()
task.download_outputs()

machine_group.terminate()

The problem is that the current task-runner image in use in dev is not expecting the number of lines parameter, that is why the filename has the ,1  suffix (the number of lines).
You can test the by running the task-runner locally from the branch in this PR and it should work.


Your Api Service is down

Your api services are Down can u kindly check it once

Apologies, I had to delete it from my work developer subscription as I am leaving that job.
Please redeploy in your own subscription - let me know if I can help in any way.
I'm really interested in what you were using it for-  I had no idea anyone was using it in production- sorry!

Hi @techDotweb I have restored the service and the database now. Please note I need to take it down again soon, so please deploy into your own subscription. I have upgraded the Function to v4, .NET 6 so that deployment scripts work.


How to add a loading view to a component?

I'm trying to fetch a collection before rendering my component, and would like to initially render a loading view within the component's region until the fetch is complete, and then finish by rendering the component's view. Is this possible to accomplish with Marionette.Component? I've got a loading view ready to use, and have been experimenting with the onBeforeShowView callback, but I'm stuck on how to proceed from here.
Thanks for any advice you may be able to provide! :)

Hey, @dnewkerk. I wouldn't say this is something that should work directly out of the box.
However, without trying it out, I wonder if it would work if you initially rendered your loading view, fetched your data, and then swapped out the view when loaded.
Something like:
var LoadingView = Mn.ItemView.extend(...);
var DataView = Mn.ItemView.extend(...);

var MyComponent = Mn.Component.extend({
  viewClass: LoadingView,

  onShow() {
    this._fetchData().then(() => this._swapViews());
  },

  _fetchData() {...},

  _swapViews() {
    this._oldView = this.view;
    this.view = new DataView();

    // unbind events on the loading view before displaying the new view...

    this.region.show(this.view);
  }
});

var myRegion = new Mn.Region({ el: '#main' });
var myComponent = new MyComponent();

myComponent.showIn(myRegion);

One caveat is that you will need to handle unbinding events that were registered on the loading view when the components was first displayed. This might work. I'm open to ideas for simplifying the API to allow this. One piece that might help guide something like this is the work being done at #46.


District map on capacity dashboard: Incorrect

On the district capacity dashboard, when filet for Government hospitals are enabled, and on the map filter, ordinary beds are selected, only 2 entities show up on the map.
This is incorrect.
Please check the representation on data on the map.
@bodhish

@aparnacoronasafe do update the latitude and longitude for the facilities. It should work.


Example could be improved to handle paths when there are multiple solutions in repo subfolders

Example could be improved to handle paths when there are multiple solutions in repo subfolders

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

ID: 6f70ab0e-7e7d-df8f-5607-8794b5d26024
Version Independent ID: 16b7890e-6e7f-0573-3d79-51bdb04758dd
Content: Implement Continuous Integration and Continuous deployment using Azure Pipelines
Content Source: docs/spfx/toolchain/implement-ci-cd-with-azure-pipelines.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Do you mean you are storing multiple SPFx solutions in the same repo?
While it's possible to do this, the point of the article is to demonstrate how to set up CI/CD with SPFx projects using Azure Pipelines and not go into every setup possible.

@andrewconnell

Do you mean you are storing multiple SPFx solutions in the same repo?

Yes. But I have figured out how to reference the subfolders. It's just that the documentation is not very informative about the folder variables used in YAML files. I suggest the document is updated to at least link to Use predefined variables document as this took me quite some time to figure out.
 /home/vsts/work/1 - Pipeline.Workspace
a - Build.ArtifactStagingDirectory
b - Build.BinariesDirectory
s - Build.SourcesDirectory
drop


Commented out getting image info from /devices endpoint.

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[X] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I run go fmt ./... to check that my code is properly formatted
[X] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #1000 (576134b) into main (ae7217a) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1000      +/-   ##
==========================================
- Coverage   30.70%   30.66%   -0.04%
==========================================
  Files          45       45
  Lines        5497     5491       -6
==========================================
- Hits         1688     1684       -4
+ Misses       3574     3573       -1
+ Partials      235      234       -1

Impacted Files
Coverage Δ

pkg/services/devices.go
60.45% <ø> (-0.08%)
:arrow_down:

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 ae7217a...576134b. Read the comment docs.


Interactive Tutorial - Exploring Your App

Hi @randomtest99,
What is the issue you are facing for the interactive Tutorial - Exploring Your App?

/triage needs-information
/language en

/close
Won't fix because we're removing Katacoda.


WER results

Can I find WER details using this ?

If you want to calculate WER for your test set you have to write your own scripts or use kaldi directly.


Enhancement: remove the CommandInstance construct

Related to #1737
After removing dependency on Vorpal, we'll be able to further refactor the command code and remove the CommandInstance construct. It will help us simplify code and tests and remove obsolete code.
If I understood it correctly, Vorpal requires CommandInstance to store information about the current command in its execution context. Since out setup is easier and the context doesn't span beyond the execution of the single command, we can access all the necessary information from the command itself without having to copy it to the context.
I'll pick up this refactoring, after we closed #1737.

On a related note, we can also simplify validation. Rather than returning a function or undefined, we can implement validation directly in the validate method and by default have the base Command class return true which means that validation passed. I can include this change in the same refactoring.


Update icons and screenshots from the excel file

[X] I have read the contributing guidelines, and I agree with the Code of Conduct.
[X] Have you checked that there aren't other open pull requests for the same changes?
[X] Have you tested that the committed code can be executed without errors?
[X] This PR is not composed of garbage changes used to farm GitHub activity to enter potential Crypto AirDrops.
Any user suspected of farming GitHub activity with crypto purposes will get banned. Submitting broken code wastes the contributors' time, who have to spend their free time reviewing, fixing, and testing code that does not even compile, breaks other features, or does not introduce any useful changes. Thank you for your understanding.

Update icons and screenshots from the excel file

It says skanda890/UniGetUI is some commits ahead of marticliment/UniGetUI, so I created this pull request.

this is to be expected, git does this when there are two different repos, one forked from another


[AutoPR] billing/resource-manager

Created to accumulate context: billing/resource-manager

(message created by the CI based on PR content)

At this point of working on this PR, CI is failing for a test reason and not a path reason anymore

Give up on this PR, let the bot create a new one


Fix behavior of rs.utils.generate_reciprocal_asu() with anomalous flag

This PR fixes the behavior of rs.utils.generate_reciprocal_asu() with anomalous=True to avoid copying centric reflections to the Friedel-minus ASU. This makes the function's handling of centrics consistent with other methods (such as DataSet.stack_anomalous())
I also changed the implementation to use rs.utils.in_asu() instead of rs.utils.hkl_to_asu(), which speeds up the code ~2x.

Codecov Report

Merging #68 (588cd7a) into main (f64b61e) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #68      +/-   ##
==========================================
- Coverage   98.76%   98.73%   -0.04%
==========================================
  Files          38       38
  Lines        1458     1420      -38
==========================================
- Hits         1440     1402      -38
  Misses         18       18

Flag
Coverage Δ

unittests
98.73% <100.00%> (-0.04%)
:arrow_down:

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

Impacted Files
Coverage Δ

reciprocalspaceship/utils/asu.py
100.00% <100.00%> (ø)

reciprocalspaceship/dtypes/base.py
96.84% <0.00%> (-0.13%)
:arrow_down:

reciprocalspaceship/dataset.py
99.02% <0.00%> (-0.04%)
:arrow_down:

reciprocalspaceship/dataseries.py
100.00% <0.00%> (ø)

reciprocalspaceship/dtypes/batch.py
100.00% <0.00%> (ø)

reciprocalspaceship/dtypes/phase.py
100.00% <0.00%> (ø)

reciprocalspaceship/dtypes/m_isym.py
100.00% <0.00%> (ø)

reciprocalspaceship/dtypes/mtzint.py
100.00% <0.00%> (ø)

reciprocalspaceship/dtypes/stddev.py
100.00% <0.00%> (ø)

reciprocalspaceship/dtypes/weight.py
100.00% <0.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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

Nice work!


Rendering script for Pascal3D+

Thanks for sharing the code, it's a great work!
Can you provide the script for Pascal 3D+ datasets to generate masks and ground-truth point clouds for other categories? Thank you very much!

The ground-truth segmentation masks were generated using the provided toolbox, which was written in Matlab.
I can get to releasing the script for creating ground-truth point clouds, but it will probably have to wait a couple of weeks. Leaving this issue open for now.

I've just updated the readme and included the instructions for creating ground-truth point clouds for PASCAL3D+. Please let me know if you have further questions, and feel free to reopen the issue if necessary 🙂

Thanks!


Provide way to get document position information for start and end tags

Background
At Shopify, we are working on a small library to optimize our current HTML rewriting implementation  and wish to use lol-html. We want to define a number of rewrite steps and execute them in a single lol-html pass. By doing this, we can avoid unnecessary traversals the current implementation suffers from.
We're wrapping lol-html in a Ruby gem, and looks something like:
Rewriter
  .new
  .inject_if_selector_missing(
    missing_selector: "link[rel='canonical']",
    inject_at: Location.once("head", Position.end_of_selector),
    injected_string: %(<link rel="canonical" href="#{canonical_url}">),
  )
  .inject_if_selector_missing(
    missing_selector: "meta[property='og:image'][content]",
    inject_at: Location.once("head", Position.end_of_selector),
    injected_string: social_sharing_image_tags,
  )
  .replace("<placeholder/>", "<something else/>")
  .rewrite(html_response_body)

In order to execute this in one pass, we needed access to the StartTag::raw and EndTag::raw method in order to track the position where we will later make the string injections / replacements.
Questions

Is using StartTag::raw and EndTag::raw a reasonable way to go about this, order does lol-html provide another way to do something similar?
Would lol-html be open to providing a pub method to expose the positions offset of StartTag and EndTag, or something similar to allow for single-pass rewriting?

cc: @gmalette
Thanks!

I also need this feature. Related issue: https://github.com/cloudflare/html-rewriter-wasm/issues/5


[WIP] Merge feature branch f/storage-class

Description

How Has This Been Tested?

Test Impact

Request review criteria:

Self checklist (all need to be checked):

[ ] The developer has manually tested the changes and verified that the changes work
[ ] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[x] The developer has tested their solution on a cluster by using the image produced by the PR to main

@shalberd thanks for all the feedback it's really useful, I'll continue reading through it and making changes / comments tomorrow morning. My afternoons tend to get lost to meetings / planning etc - but getting your work merged, this week if possible is my goal.

/lgtm, my comments can be resolved


Example Ambiguous offset result?

I'm not sure if I hold this wrong or if it's a bug, but looks like discussions are disabled, hence asking here :-)
I'm writing a small ics2txt tool at https://github.com/vmiklos/vmexam/tree/master/ics2txt, and checking what code is not covered by tests. One edge case is when assume_timezone() doesn't return Some, i.e. a case where a local time doesn't have a single timezone, but has 0 or 2.
I tested this with the Europe/Budapest timezone, where I know it's the usual European case, i.e. clocks are adjusted in a way that the offset is incremented by 1h on the last weekend of March, on Sun, from 2:00 to 3:00. I would assume this means that the result here for 2:30 local time on that night should be None. However, when I test this, here is what I get:
Sun, 31 Mar 2024 02:29:00 is +0000
Sun, 31 Mar 2024 00:29:00 is +0100
Sun, 31 Mar 2024 06:29:00 is +0200

I.e. the "before 2h" and "after 3h" case works as expected, but that +0000 offset is odd, I expect an error instead of a zero offset.
Is this a bug in time-tz (or one of its dependencies) or is a bug in the tzdata database that I have on Linux?
If it's not a bug in time-tz, is there any real-world example on how to trigger the OffsetResult::Ambiguous and OffsetResult::None cases when one calls assume_timezone() on a PrimitiveDateTime?
(I originally asked this at https://github.com/time-rs/time/discussions/646, but turns out that the impl for this trait is in this crate.)
Thanks.

I'm not sure if I hold this wrong or if it's a bug, but looks like discussions are disabled, hence asking here :-)

What do you mean by "discussions"? I didn't even know that existed on GitHub... Could you tell me how to enable it?

I'm writing a small ics2txt tool at https://github.com/vmiklos/vmexam/tree/master/ics2txt, and checking what code is not covered by tests. One edge case is when assume_timezone() doesn't return Some, i.e. a case where a local time doesn't have a single timezone, but has 0 or 2.
I tested this with the Europe/Budapest timezone, where I know it's the usual European case, i.e. clocks are adjusted in a way that the offset is incremented by 1h on the last weekend of March, on Sun, from 2:00 to 3:00. I would assume this means that the result here for 2:30 local time on that night should be None. However, when I test this, here is what I get:
Sun, 31 Mar 2024 02:29:00 is +0000
Sun, 31 Mar 2024 00:29:00 is +0100
Sun, 31 Mar 2024 06:29:00 is +0200

I.e. the "before 2h" and "after 3h" case works as expected, but that +0000 offset is odd, I expect an error instead of a zero offset.
Is this a bug in time-tz (or one of its dependencies) or is a bug in the tzdata database that I have on Linux?

This can't be a bug with your system tzdata database as the tzdata database is baked into the crate from the official distribution on GitHub.

If it's not a bug in time-tz, is there any real-world example on how to trigger the OffsetResult::Ambiguous and OffsetResult::None cases when one calls assume_timezone() on a PrimitiveDateTime?

I'm not sure what you mean because I can't reproduce this issue on my local machine. Could you post a minimal reproducible test case on this issue? This is what I tried on my local machine which works.
    #[test]
    fn errors() {
        let datetime = datetime!(2024-03-31 02:30:00).assume_timezone(timezones::db::europe::BUDAPEST);
        assert!(datetime.is_none());
        let datetime = datetime!(2024-03-31 02:29:00).assume_timezone(timezones::db::europe::BUDAPEST);
        assert!(datetime.is_none());
    }

What do you mean by "discussions"? I didn't even know that existed on GitHub... Could you tell me how to enable it?

See the screenshots here: https://docs.github.com/en/discussions/quickstart

This can't be a bug with your system tzdata database as the tzdata database is baked into the crate from the official distribution on GitHub.

Ah, great to know, I didn't realize that.

I'm not sure what you mean because I can't reproduce this issue on my local machine. Could you post a minimal reproducible test case on this issue? This is what I tried on my local machine which works.
    #[test]
    fn errors() {
        let datetime = datetime!(2024-03-31 02:30:00).assume_timezone(timezones::db::europe::BUDAPEST);
        assert!(datetime.is_none());
        let datetime = datetime!(2024-03-31 02:29:00).assume_timezone(timezones::db::europe::BUDAPEST);
        assert!(datetime.is_none());
    }

Thanks! that test passes here as well, I can works backwards from there. My "test" was just some manually constructed ical file that tried to do the same (with the above linked ics2txt tool), and I was confused if my API usage is wrong or not. But then this will be something on my end. :-)


Fix Navbar

Fixes:  #4028
Description
navbar are not align at center in lol.html
Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
BEFOR:

AFTER ::

Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

https://github.com/user-attachments/assets/40664742-07c4-48a7-bfeb-3c1f3018e0a9
there are still issues in the navbar .
the dropdown of profile avatar , on clicking on more button dropdown doesnt come .
also fix the navbar responsiveness .

like i am not able to  find your original navbar on index.html --> it's very hard to find that --> i find minimum 40 to 50 minutes but not get --> just because of css and html code within one file and also come some css from style.html and styles.html
so it's very difficult -- > then i do only center the navbar

if you like this changes then merged it otherwise you closed it.

Thank you

the navbars are really messed up . different pages have different navbar design . also there is problem in all navbars  .
u can work on this issue and resolve all pages navbar , make them uniform .

Ohk .. i will work ...


Redox pthreads

This updates the pthread typedefs and sigset_t, following the relatively recent Redox pthreads rewrite.

@bors r+

:pushpin: Commit a778abaf218bfa174bc0ad2f9f3fa14ea3f0a7a1 has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit a778abaf218bfa174bc0ad2f9f3fa14ea3f0a7a1 with merge 76ebf0c88ce6eba6722b8a9fe7a05eba4153b3b3...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 76ebf0c88ce6eba6722b8a9fe7a05eba4153b3b3 to main...


Pre-fill Private Tag when sending directly to contacts

When pressing the pay button on a contact it would be nice if the contact's name was pre-filled in the private tag section.

Closed by #534


Update sbt-spiewak-sonatype to 0.20.1

Updates com.codecommit:sbt-spiewak-sonatype from 0.19.3 to 0.20.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.codecommit", artifactId = "sbt-spiewak-sonatype" } ]

labels: sbt-plugin-update, semver-minor

Broken by what's fixed in #110.

Broken by what's fixed in #110.


build: include CARGO_BUILD_TARGET in the path of release folder

Hi,
This PR is intended to include CARGO_BUILD_TARGET in the path of the release folder if it is specified.
If there are any problems, please let me know.
Thanks.

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

Merged. Thanks @jakechenTW!


Weekly-contest-264 still not predicted

It has been 7 hours since Weekly-contest-264 is finished, but ratings still not predicted yet. Something went wrong ?

Closing this ticket since prediction is working properly


refactor($q): remove unnecessary wrapper/helper functions

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
refactor / cleanup
Mainly just removing things that seem to no longer be necessary. I think $q has changed a fair amount leaving such things behind over time.

LGTM


Include hash of read-only manifest handle values in handle id.

Early-ish checkpoint to solicit feedback. In particular:

seeking to make sure we shouldn't be doing something to else to check read-only status such as scrutinizing any associated connection/type, I'm just presuming the spot where I'm computing and inserting the hash in the unitType.isEntity block within _processStore is one where that entity is implicitly always read-only, but perhaps I am naive/mistaken.
the handle._store.id we discussed in chat is computed here and is not currently updated to include the hash value, should it be? It seems a separate id to me, and then should the hash included be the hash of just that entity's value or the full list of entities (the latter is what's inserted into the handle id)?
removed immediate from the id of particle specs since we're including hash instead which seems sufficient, but if we still want it, let's discuss, because then shouldn't we have it in the read-only entity case as well?
this PR doesn't address the work item around turning off duplicate-id errors for read-only data, but this work should be sufficient for the Social muxing embedded recipe case where the game id value does always vary, so we can file an issue for the duplicate-id work and pursue separately

Part of https://github.com/PolymerLabs/arcs/issues/842

It looks to me like you're not computing an id for the entire store if the stored entities already have one serialized. This actually seems like a pretty good test of read-only-ness (if the entities have ids then they were written by something).

the link you're providing for computation of handle._store.id is actually for entity ids. Definitely fine to ignore this one, but is it the one you mean?

removing immediate is fine, I think

LMK about whether that is the code chunk you were thinking of for handle._store.id; otherwise I think this is looking good.

LMK about whether that is the code chunk you were thinking of for handle._store.id; otherwise I think this is looking good.

TL;DR = I had _store and _stored mixed up, I think the PR is ok, our chat discussion are handle/store id had me double-checking, detail below.
=> Well, yes, with the current PR, running one of the tests added here and logging the entities when their id is computed here in the case where entity.$id is not set:
%  ./tools/sigh test --grep='different ids'
[ { id: 'manifest:the.manifest::0', rawData: { nobId: '12345' } } ]
[ { id: 'manifest:the.manifest::0', rawData: { nobId: '67890' } } ]

Aiming to clarify what I was saying, originally I'd semi-blindly updated that id thinking it was one of the spots where handle id was computed, and then in looking into why the handle id wasn't in fact updated I found, as you note, that it's actually the entity id, and it turns out that entity ends up in handle._stored of the InMemoryVariable (actually _stored not _store, I mis-remembered), and so I removed the update to that id.
I think this PR is fine as-is based on your comment, I noted it since in chat it sounded like you were saying the store id should match the handle id, and in this case it doesn't unless we add something like, after line 922 in manifest.js in this PR:
        if (!entity.$id) {
          let entityHash = digest(JSON.stringify(entity));
          id = `${id}:${entityHash}`;
        }

which will then produce, for those entities:
[ { id: 'manifest:the.manifest::0:58f0de7504ffa8d8d1aa160e6bd2b168bfcd6b24',
    rawData: { nobId: '12345' } } ]
[ { id: 'manifest:the.manifest::0:0e71e39569f80e30bc88abf242b0a8c677d31327',
    rawData: { nobId: '67890' } } ]

Will merge, happy to revise further if new information comes to light...


CST820 datasheet?

Hi,
I was looking for but cound't even find a CST820's manufacturer, let alone a datasheet. Where did you find it to write the library?
Regards

I don't have access to the datasheet. Most cap touch sensors work the same way. I was able to make it work by looking at the register positions in someone else's code.

I have a source code for CST820 driver from the documentation of JC2432W328 display I mentioned here:
https://github.com/witnessmenow/ESP32-Cheap-Yellow-Display/discussions/200#discussioncomment-10078820
But it could be seen from the code the implemented functionality is only partial, that's why I've been looking for the datasheet.
The author of this page mentioned your library and the library from some display's documentation too and he said:
(translated from Japanese)

I found two types of CST820 libraries used for the touch panel. One is published as a library called bb_captouch. The other is included in the 24C demo program, cst820.cpp.
Both support single-point touch, but other operations are unclear.
bb_captouch supports two-point touch, but stops about 100ms after touch.

Some initialization is probably required, but the method written in cst820.cpp does not work.
cst820.cpp has a description of gestures, but this does not work either.
I guess the important parts will not be disclosed unless you sign a contract. I guess there's no other way.

Maybe the author of the code you used to write the library has the datasheet?

Not sure what to say. It's not on my to-do list at the moment. If you find the info, please let me know.


add case sensitivity checks

Added case sensitivity checks per issue #15.
Added tests similar to existing attribute selector tests using case insensitivity.

Thank you for your contribution. I will soon use your code and adapt it to the codebase.

I know this is a bit old, but is there any way to get this into the codebase? Would love to be able to do case insensitive selectors.

Thank for reminding. I'll take a look soon.

Hello @grmoon, after a huge refactoring version 2.0.0 was released, which now has this feature implemented. Please update.


TO add new Logo of Website

Describe the Feature you want to end
I want to change the older logo to new once.
Screenshots (optional)

Want to contribute it under Hacktoberfest.

Do you like this logo?


Library is too large to deploy to Google App Engine

Which version of the client library are you using?
14.0.0
Which version of Java are you using?
1.8
I'm trying to deploy my application that uses the Google Ads API to Google App Engine, but the deployment fails because the library jar is too large. Is there a way to only use version 8 of the API without including v7 and v6? Is there a different way of using the Google Ads API with Google App Engine?

Hey, thanks for reporting. Could you possibly point me at the documentation for the specific limit you're hitting?
I took a look at the binary size, and indeed it looks like the stubs for API versions take up about 80MB in the JAR with support for 4 API versions. When unzipped these take up about 260MB. So would be good to know what the target is so we can look at options to fix, thanks.

A short term workaround would be to compile the library from scratch. Simply deleting the vX directories from here and here should work.

Thanks for the quick reply
This is the error message I got
ERROR: (gcloud.app.deploy) Cannot upload file [/opt/atlassian/pipelines/agent/build/default/build/staged-app/WEB-INF/lib/google-ads-14.0.0.jar], which has size [66095767] (greater than maximum allowed size of [33554432])
It looks like the size limit is 32MB, but I couldn't find any current documentation specifying this limit

Hmm, let me reach out to the app engine folks to see where this comes from and if it's possible to override.

So there's not really a good workaround for the limit on the app engine side. It is at least documented here.
Would you be able to recompile the library from source, removing the old API versions?

When I removed the old API versions and recompiled, the jar size was 49.9 MB. It looks like I might have to start going through and cherry picking the API resources that I am using for the project

So I was able to find a solution for deploying to App Engine. Using the Google App Engine plugin for gradle I was able to add a staging task and set the enableJarSplitting = true . After that my deployments started working.

Oh nice - thank you for investigating and for posting the solution.

Nick, we should document this in our Java library documentation as a known
issue + workaround. Could you file a bug against yourself so we don't
forget?
On Tue, Jul 27, 2021, 1:15 PM Nick Birnie @.***> wrote:

Oh nice - thank you for investigating and for posting the solution.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googleads/google-ads-java/issues/463#issuecomment-887687173,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCOJCFQCQH5IMWUX3RAG4LTZ3SSHANCNFSM5AUG55NQ
.

I know, it's on my list.


Export TMX error!!

I install the soft with win7 x64, the exe path is D:\game\CadEditor
D:\game\nes\DARKWING.NES
D:\game\CadEditor\settings_nes\darkwing_duck\Settings_DarkwingDuck-All.cs
when i used the export tmx
it's got exception!!
I know that Chinese is not good for debug, but the useful message is show here ↓
I update .net  framework from 4.6.2 to 4.7.1
and i don‘t know is it a bug?

有关调用实时(JIT)调试而不是此对话框的详细信息，
请参见此消息的结尾。
************** 异常文本 **************
System.IO.FileNotFoundException: 未能加载文件或程序集“Microsoft.Scripting, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7f709c5b713576e1”或它的某一个依赖项。系统找不到指定的文件。
文件名:“Microsoft.Scripting, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7f709c5b713576e1”
在 PluginExportScreens.ExportTMX.btExport_Click(Object sender, EventArgs e)
在 System.Windows.Forms.Control.OnClick(EventArgs e)
在 System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
在 System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
在 System.Windows.Forms.Control.WndProc(Message& m)
在 System.Windows.Forms.ButtonBase.WndProc(Message& m)
在 System.Windows.Forms.Button.WndProc(Message& m)
在 System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The exception says that CadEditor.exe can't load assembly Microsoft.Scripting. Looks like I forgot to include some files to release archive (I have it somewhere in my local machine, so export works fine for me even without dlls in CadEditor folder) =\
I'll fix it in next release.
It's standart IronPython assemblies:
CadEditor_IronPythonModules.zip
You need to extract it to CadEditor folder (and don't forget to unblock zip archive after download it - https://blogs.msdn.microsoft.com/delay/p/unblockingdownloadedfile/)

Check this file
IronPython.Modules.zip
Later I'll test editor on the fresh machine, if forgot something again, you can install IronPython 2.7. Thanks for testing.

OMG, it works.
it is not enougth after unzip IronPython.Modules.zip into CadEditor folder
First, i download ironPython from github, but the version is 2.7.9 then i think it will be ok ... but fail
Second, i cp all dll from dir of ironPython, but exception of the version...
Third, i reinstall ironPython of 2.7.7 then cp dll and IronPythonLib （Importent folder!!） into cadEditor, the exprot tmx  works...
This is the reason why i don't like learn C#

i uninstall cadeditor and reinstall again. it works ...
maybe install the full IronPython 2.7.7 is the beast choose

最后总结：安装 CadEditor 需要 2.7.7的 IronPython 才能使用导出 tmx 功能

I rewrote TMX export on pure C#, so now it does not need IronPython or any python library at all.
https://github.com/spiiin/CadEditor/releases/tag/v5.2


chore(i8n,docs): processed translations

Checklist:

[X] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X] My pull request targets the main branch of freeCodeCamp.
[X] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

/cc @RandellDawson

Okay I re-ran the download.


BUG: scipy.optimize.minimize with method="newton-cg" is stuck on a local maximum

Preface
I either have a usage problem or there is something wrong with the source code. Because I'm unsure which is the case I both opened a stackoverflow question and this Issue. I will just copy the text I've already written on stackoverflow to here.
tl;dr
I want to find the local minimum for a function that depends on 2 variables. For that my plan was to use the scipy.optimize.minimize function with the "newton-cg" method because I can calculate the jacobian and hessian analytically. However, when my starting guesses are on a local maximum, the function terminates successfully in the first iteration step on top of the local maximum, even though the hessian is negative.
Reproducing code
The reproducing code and the wrongly successfull termination message can be seen below.
The same outcome occurs if I use hess=None, hess='cs', hess='2-point' or hess='3-point' instead of my custom hess function. Also if I use other methods like 'dogleg', 'trust-ncg', 'trust-krylov', 'trust-exact' or 'trust-constr' I basically get the same outcome except nhev = 1 but the outcome is still wrong with x = [0,0].
Either I am doing something terribly wrong here (definitely very likely) or there is a major problem with the minimize function, specifically the "newton-cg" method (very unlikely?).
Regarding the latter case I also checked the source code to see if something's wrong there and stumpled upon something kinda weird(?). However, I don't completely understand the whole code, so I am a bit unsure if my worries are legitimate:
Taking a look at the source code
When the minimize function is called with method="newton-cg" it jumps into the _minimize_newtoncg function (see source code here). I want to go into detail what I believe happens here (so you can tell where I am potentially wrong):
On line 2168 A = sf.hess(xk) the hessian is first calculated in dependence of xk which is at first the start guess x0. For my test case the hessian is of course
A = [[f_xx, f_xy], [f_xy, f_yy]]
with f_ij being the derivatives of f after i and j. In my case f_xy = f_yx is also true.
Next on line 2183 Ap = A.dot(psupi) the product of the hessian A and psupi is calculated. psupi is basically equal to b which is the negative gradient of f at xk. So Ap = A.dot(psupi) results in
Ap = [f_xx f_x + f_xy f_y, f_xy f_x + f_yy f_y].
Now to the (possible) problem
Next, the curvature curv is calculated on line 2186 by np.dot(psupi, Ap). As explained above, psupis the negative gradient of f so this results in
curv = f_xx f_x^2 + 2 f_xy f_x f_y + fyy_f_y^2.
However, all of these derivatives are at xk which is equal to the starting parameters x0 at first. If the starting parameters are exactly at a local maximum, the derivatives f_x and f_y are equal to 0. Because of this, curv = 0. This results in a for loop break on the next line, thus, skipping to update xsupi, psupi and all the other parameters. Therefore, pk becomes [0,0] and _line_search_wolfe12 is called with basically all start parameters. This is where my understanding of the source code stops, however, I feel like things already went wrong after curv = 0 and breaking the for loop.
My concluding question is: What am I doing wrong leading to the minimize function being stuck on a local maximum?
Small update: I now understand that this case of starting at a local maximum and finding a local minimum from there might not have been implemented. So I am unsure if that would be doable to add in the future. If it were, I'd greatly appreciate it.
Reproducing Code Example
import numpy as np
import scipy.optimize as o

def get_f_df(var):
    x = var[0]
    y = var[1]

    f = np.cos(x) + np.cos(y)
    df_dx = -np.sin(x)
    df_dy = -np.sin(y)

    return f, (df_dx, df_dy)

def hess(var):
    x = var[0]
    y = var[1]

    f_hess = np.zeros((2,2))
    f_hess[0,0] = -np.cos(x)
    f_hess[1,1] = -np.cos(y)
    return f_hess

min = o.minimize(get_f_df, (0, 0), jac=True, hess=hess, method="newton-cg")
print(min)

Error message (not an error but the OptimizedResult)
message: Optimization terminated successfully.
 success: True
  status: 0
     fun: 2.0
       x: [ 0.000e+00  0.000e+00]
     nit: 1
     jac: [-0.000e+00 -0.000e+00]
    nfev: 1
    njev: 1
    nhev: 1

SciPy/NumPy/Python version and system information
1.12.0 1.26.4 sys.version_info(major=3, minor=11, micro=0, releaselevel='final', serial=0)
Build Dependencies:
  blas:
    detection method: pkgconfig
    found: true
    include directory: /c/opt/64/include
    lib directory: /c/opt/64/lib
    name: openblas
    openblas configuration: USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER= NO_CBLAS=
      NO_LAPACK= NO_LAPACKE= NO_AFFINITY=1 USE_OPENMP= SKYLAKEX MAX_THREADS=2
    pc file directory: c:/opt/64/lib/pkgconfig
    version: 0.3.21.dev
  lapack:
    detection method: pkgconfig
    found: true
    include directory: /c/opt/64/include
    lib directory: /c/opt/64/lib
    name: openblas
    openblas configuration: USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER= NO_CBLAS=
      NO_LAPACK= NO_LAPACKE= NO_AFFINITY=1 USE_OPENMP= SKYLAKEX MAX_THREADS=2
    pc file directory: c:/opt/64/lib/pkgconfig
    version: 0.3.21.dev
  pybind11:
    detection method: config-tool
    include directory: unknown
    name: pybind11
    version: 2.11.1
Compilers:
  c:
    commands: cc
    linker: ld.bfd
    name: gcc
    version: 10.3.0
  c++:
    commands: c++
    linker: ld.bfd
    name: gcc
    version: 10.3.0
  cython:
    commands: cython
    linker: cython
    name: cython
    version: 3.0.8
  fortran:
    commands: gfortran
    linker: ld.bfd
    name: gcc
    version: 10.3.0
  pythran:
    include directory: C:\Users\runneradmin\AppData\Local\Temp\pip-build-env-d02me32y\overlay\Lib\site-packages/pythran
    version: 0.15.0
Machine Information:
  build:
    cpu: x86_64
    endian: little
    family: x86_64
    system: windows
  cross-compiled: false
  host:
    cpu: x86_64
    endian: little
    family: x86_64
    system: windows
Python Information:
  path: C:\Users\runneradmin\AppData\Local\Temp\cibw-run-aug4qibh\cp311-win_amd64\build\venv\Scripts\python.exe
  version: '3.11'

Thanks for the report @legandro-github and sorry for the long response time. From what I understand the root cause of your issue is that the initial starting guess for the optimizer is located at a local maximum and the gradient is exactly zero. This is a bad edge case that will cause trouble for most gradient based optimizers. I am not sure that we can or should do something about it,

On second thought, we could also check the definiteness of the Hessian matrix before the major loop. In this example, this would definitely indicate that we are on a local maximum.

On second thought, we could also check the definiteness of the Hessian matrix before the major loop. In this example, this would definitely indicate that we are on a local maximum.

What would we do in the circumstance where we don't know the Hessian, and we only know hessp?
One idea would be to evaluate np.dot(xk, hessp(xk)) and see if this is positive - if the matrix is positive definite, then this is guaranteed to be positive. (I think - I'm a little new to this.)

Starting the minimisation at an exact maximum is going to be unlikely. Furthermore, if you detect you're at a maximum and you want to move off and find a minimum, do you go to the left or the right?
So I don't think extra work should be done to then try to find a minimum.
It might be worth trying to detect whether the solution is at a maximum by examining the hessian, as long as extra calcs aren't required.


AST representation of Table

@lizmat new issue, arising out of #22

Outside the block scope of  =table , the following should throw errors =column, =row, =cell.
I dont know whether this should be the Parser or the Renderer's job.

As far as my understanding goes, =table is a block, not a directive.  Having the parser throw an error about a directive being out of place because of a block, means treating some blocks (in this case=table) different from other blocks.  And that feels like damaging the generality and extensibility of the parser to me.

So I feel that this is a renderer issue.

Originally posted by @lizmat in https://github.com/Raku/RakuDoc-GAMMA/issues/22#issuecomment-2006450269

I think it needs a separate issue. Looks to me now that the whole new table design is mostly NYI. @finanalyst could you give me a tree of RakuAST objects that you would like to see produced from the test.rakudoc document?

Outside the block scope of =table , the following should throw errors =column, =row, =cell.
I dont know whether this should be the Parser or the Renderer's job.

As far as my understanding goes, =table is a block, not a directive. Having the parser throw an error about a directive being out of place because of a block, means treating some blocks (in this case=table) different from other blocks. And that feels like damaging the generality and extensibility of the parser to me.

So I feel that this is a renderer issue.

@lizmat As I see it,

=table is a block.
=table has two orthogonal syntax: procedural and textual
the two are distinguished because for a procedural form =table is immediately followed by

=cell | =column | =row | =comment
otherwise =table is textual and follows the same semantics as for RakuDoc v1
=comment is a block as everywhere else and is ignored
=cell is a block, so can have =for cell and =begin cell forms
=column, =row are both directives and may not contain have =for column / =begin column forms.

@lizmat Please find two files in the attached zip
test.zip
test.rakudoc contains the table and a say $=pod to output the pod structure.
dump is the piped output.
As I said above, Raku-Pod-Render, generates the $=pod for a file and processes it, can generate a procedural table from the output in dump. So the AST for a procedural table can mimic the pod. (Note that the legacy parser somehow is able to distinguish a procedural table, which is parsed into a Pod::Block:Named, name=table from a textual table which is parsed into a Pod::Block::Table
So, my suggestion for the AST of =table

to be a Block, type table node,
the difference for the parser is that only one type of RakuDoc block is generated for =table
the Block node would contain an attribute procedural that is False for a textual table and True for a procedural table.
When False, the remainder of the AST is as present (and there is minimal need for HTML encapsulation of cells)
when True, the AST would have leaves of Rows/Columns/Comment (for deparsing),

bearing in mind that if a =table is immediately followed by a =cell, then there is an implied Row (=row)
Each Row and Column are directives, not blocks
Cell is a block
Row & Column can contain metadata options, including :rowspan, :colspan, :label

A Row / Column outside a Table block are illegal.

Closing as resolved


Wallet Instance Attestation response, normative definitions and non normative example

@rohe 's
In https://github.com/italia/eudi-wallet-it-docs/blob/versione-corrente/docs/en/wallet-instance-attestation.rst there is an example on how to Obtain a Wallet Instance Attestation. But only the request part is shown, there is no example of the response part.
@peppelinux 's
We need a normative text and a non normative example of the response

Fixed in: https://github.com/italia/eudi-wallet-it-docs/pull/115


Way to locate resources

Thanks for the great module, just found it. I like the way to add up gold and items in 5e.

Maybe add a way to locate WHERE the gold/items are located? Maybe as a tooltip? It could show a list of what characters are holding the gold/or items.
Is there a way to limit what characters are counted for the max (as of now it counts all gold/items in all characters, I think? This includes dead characters for example, as long as they are in the list.)
Should the summary include characters of which the players do not have any permission?

These are good suggestions @Ikabodo .

Is there a way to limit what characters are counted for the max (as of now it counts all gold/items in all characters, I think? This includes dead characters for example, as long as they are in the list.)

Aha! I must admit I didn't take dead characters into account, my own group always deletes their old skins on death. I'll probably isolate this issue to fix first before I attempt a summary in a tooltip.

Should the summary include characters of which the players do not have any permission?

PCs without any players assigned should probably be assumed as dead, and not show up in any summary.
I'll mark this as feature request, but can't provide timing with the usual end of year business.


React 16.3.2

I've updated the versions.yml file in #801 to point to this latest changelog as well.


JS/TS features initializing hangs. Peek/Go to definition feature does not work

Type: Bug
JS/TS features initializing hangs. Peek/Go to definition feature does not work
VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:52:57.054Z)
OS version: Darwin arm64 22.6.0
Modes:

System Info

Item
Value

CPUs
Apple M2 Pro (12 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
8, 6, 4

Memory (System)
32.00GB (5.19GB free)

Process Argv
--crash-reporter-id 0e441410-02c9-43c9-a7db-89afd3212b23

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

vim
vsc
1.27.1

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30899288
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
3biah626:30602489
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
welcomedialogc:30910334
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixt:30902429
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementst:30887150
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
aa_t_chat:30882232
dsvsc019cf:30909685

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.85.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I've found previous threads and tried

restarting VScode
closing the folder with vscode staying open and reopening the folder (sometimes fixes it for a short period)
Restart typescript server (does not ever fix it)
clone repo to a different folder|
select typescript version from workspace
.vscode/settings excludes node_modules, dist

This is my work repository so I can't share it. I've tried to reproduce it with other repos and I cannot. This is not an issue for the other members of the team. Please tell me what you need me to provide, I can provide sample files.

Please try to put together a minimal example project which demonstrates the issue

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Empty Search Value in Combobox When Selecting 'Created At' Item

I was attempting to create a combobox for setting sorting on my dashboard products page. Then, I noticed that after selecting the items, which are:
const items: ComboxUiItem[] = [
  {
    label: "Id",
    value: "id",
  },
  {
    label: "Name",
    value: "name",
  },
  {
    label: "Price",
    value: "price",
  },
  {
    label: "Quantity",
    value: "quantity",
  },
  {
    label: "Created At",
    value: "createdAt"
  },
]

The combobox component:
import {
  Command,
  CommandEmpty,
  CommandGroup,
  CommandInput,
  CommandItem,
} from "@/components/ui/command"
import {
  Popover,
  PopoverContent,
  PopoverTrigger,
} from "@/components/ui/popover"
import { Button } from "@/components/ui/button"
import { cn } from "@/lib/utils"
import * as React from "react"
import { CaretSortIcon, CheckIcon } from "@radix-ui/react-icons"

export interface ComboxUiItem {
  value: string;
  label: string;
}

interface ComboxUiProps {
  placeholder: string;
  items: ComboxUiItem[];
}

export function ComboxUi({ placeholder, items }: ComboxUiProps) {
  const [open, setOpen] = React.useState(false)
  const [value, setValue] = React.useState("")

  return (
    <Popover open={open} onOpenChange={setOpen}>
      <PopoverTrigger asChild>
        <Button
          variant="outline"
          role="combobox"
          aria-expanded={open}
          className="w-[200px] justify-between"
        >
          {value ? items.find((item) => item.value === value)?.label : placeholder}
          <CaretSortIcon className="ml-2 h-4 w-4 shrink-0 opacity-50" />
        </Button>
      </PopoverTrigger>
      <PopoverContent className="w-[200px] p-0">
        <Command>
          <CommandInput placeholder={placeholder} className="h-9" />
          <CommandEmpty>Not found.</CommandEmpty>
          <CommandGroup>
            {items.map((item) => (
              <CommandItem
                key={item.value}
                onSelect={(currentValue) => {
                  setValue(currentValue === value ? "" : currentValue)
                  setOpen(false)
                }}
              >
                {item.label}
                <CheckIcon
                  className={cn(
                    "ml-auto h-4 w-4",
                    value === item.value ? "opacity-100" : "opacity-0"
                  )}
                />
              </CommandItem>
            ))}
          </CommandGroup>
        </Command>
      </PopoverContent>
    </Popover>
  )
}

I noticed that when selecting the "Created At" item, the combobox search value becomes empty, as shown here:

To fix this issue, I suggest replacing this line:
setValue(currentValue === value ? "" : currentValue)

with this line:
setValue(currentValue === value ? "" : items.find(item => item.label.toLocaleLowerCase() === currentValue)!.value)

Hi, can you check your code with this implementation. The columns.tsx file needs special attention.

This is caused by missing value on the CommandItem. The example was fixed in #1788, you can close this now

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


Feature/daylight saving period

Add Daylight Savings Time support for time string with no specified time zone.

Specs are also added for the new feature.

All credit for the code goes to @raydavis. I just wrapped up the code and added specs to cover the daylight savings timezone feature.

@doz Can you have a look at the code?

Addresses #4


Fix typos

Fixed many typos using https://github.com/vlajos/misspell-fixer

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

Codecov Report

Merging #825 into dev will increase coverage by 0.24%.
The diff coverage is 38.88%.

@@             Coverage Diff              @@
##                dev     #825      +/-   ##
============================================
+ Coverage     48.38%   48.62%   +0.24%
- Complexity     2789     2811      +22
============================================
  Files           116      116
  Lines         27878    27878
  Branches       4651     4651
============================================
+ Hits          13489    13557      +68
- Misses        12175    12188      +13
+ Partials       2214     2133      -81

Flag
Coverage Δ
Complexity Δ

#JDBC42
48.2% <38.88%> (+0.32%)
2772 <1> (+29)
:arrow_up:

#JDBC43
48.17% <38.88%> (+0.02%)
2775 <1> (-1)
:arrow_down:

Impacted Files
Coverage Δ
Complexity Δ

...m/microsoft/sqlserver/jdbc/SQLServerStatement.java
59.8% <ø> (+0.28%)
141 <0> (+6)
:arrow_up:

...n/java/com/microsoft/sqlserver/jdbc/Parameter.java
62.92% <ø> (-0.81%)
64 <0> (ø)

...rc/main/java/com/microsoft/sqlserver/jdbc/TVP.java
44.12% <ø> (ø)
27 <0> (ø)
:arrow_down:

...m/microsoft/sqlserver/jdbc/SQLServerException.java
78.94% <ø> (+1.5%)
33 <0> (+2)
:arrow_up:

.../microsoft/sqlserver/jdbc/SQLServerConnection.java
48.45% <ø> (+0.53%)
348 <0> (+14)
:arrow_up:

...va/com/microsoft/sqlserver/jdbc/SQLServerClob.java
35.58% <ø> (ø)
12 <0> (ø)
:arrow_down:

...soft/sqlserver/jdbc/SQLServerDatabaseMetaData.java
33.33% <ø> (ø)
62 <0> (ø)
:arrow_down:

...va/com/microsoft/sqlserver/jdbc/StreamTabName.java
85% <ø> (ø)
7 <0> (ø)
:arrow_down:

...rc/main/java/com/microsoft/sqlserver/jdbc/DDC.java
45.73% <ø> (+0.43%)
108 <0> (+1)
:arrow_up:

...r/jdbc/dataclassification/SensitivityProperty.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

... and 20 more

Continue to review full report at Codecov.

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


Yarn 2 does not work for recursive projects

It seems that Yarn (2) doesn't work with recursive scanning.
Expected Behaviour: Licenses for yarn dependencies are detected when running a command such as license_finder report --recursive .... with a project using yarn version 2.4.3;
Actual Behaviour: Licenses for yarn dependencies are ignored;
Steps to reproduce: See https://github.com/swarren12/pivotal-license-finder-yarn2-bug
Other information:
It seems that the Docker image for 7.1.0 ships with yarn version 1.22.19; however, using a .yarnrc.yml file this can be overridden. When using yarn version 2.4.3, it seems Yarn licenses aren't detected.
From what I can see, this is because the yarn command is executed from the root directory (e.g. /scan in the Docker image). For yarn version 1, an extra argument is passed (--cwd) but this is omitted for version 2. In yarn.rb, there is at least one occurrence of changing the working directory (Dir.chdir(project_path) { Cmd.run(prep_cmd) }) but other invocations of yarn are missing this.
I believe the easiest fix would be to wrap all Cmd.run() calls in yarn.rb with a Dir.chdir() {} block, but I don't know if this would have a knock-on impact on other versions.

Hey @swarren12 ! Thanks for the issue! Yarn 2 is one of the later additions to LF and we may have missed some cases like this. I'm not sure when we will get to testing this out. In yarn 2, they seemed to remove the --cwd option. I imagine adding the chdir everywhere would not affect v1 because of that flag but I am not sure.
I wonder if just making a PR with the chdir wrappings will show us any new problems in the tests. We can also use it to confirm it fixes the issues that you are seeing.


Artruusi frags partial fix

Codecov Report

Merging #198 (247bd92) into master (5fe2ba9) will decrease coverage by 0.14%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #198      +/-   ##
==========================================
- Coverage   72.28%   72.13%   -0.15%
==========================================
  Files          90       90
  Lines        7977     7997      +20
==========================================
+ Hits         5766     5769       +3
- Misses       2211     2228      +17

Impacted Files
Coverage Δ

src/dds/fragment_assembler.rs
0.00% <0.00%> (ø)

src/dds/dp_event_loop.rs
89.55% <0.00%> (+0.94%)
: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 5fe2ba9...247bd92. Read the comment docs.


[1236] Add retrieve account service

Context
We have a number of use cases that will require us to be able to retrieve and interrogate an account entity from DTTP (e.g. consistency check, onboarding)
Changes proposed in this pull request

Add new service enabling the retrieval and interrogation of an account entity from DTTP
Add RetrieveAccount class enabling us to wrap and expose useful properties
Expose a basic set of properties for now

Guidance to review

Pull down the code and boot up the rails console
Retrieve a real DTTP id from postman (accountid)
Create a new provider e.g. p = Provider.new(dttp_id: "ENTER REAL DTTP ID HERE")
Make the retrieve call through the new module, e.g. Dttp::RetrieveAccount.call(provider: p)
Using postman, check that the response in the ruby class retrieves the correct filters

 [M] Retrieve account

@JonF1 has agreed to take over this PR


Bug in the DecodeDetections layer

On line 220 I think the tf.map_fn should be iterating over tf.range(1, n_classes + 1); at the moment it outputs no predictions for the 20th class on Voc2007.
https://github.com/pierluigiferrari/ssd_keras/blob/3ac9adaf3889f1020d74b0eeefea281d5e82f353/keras_layers/keras_layer_DecodeDetections.py#L218-L226

Apologies, this turned out to be an error in my set up.