Open bot in explorer pane does not work after the first time

Click on open bot in explorer, try to open a bot file that's encrypted
Dismiss the secret popup dialog
Click on open bot

Nothing happens

Couldn't repro

Can this be closed?

I was finally able to repro it with the latest. Addressed in #939


Implement the GUI for Mobile Apps in Flutter

Summary
Implement the GUI for Mobile Apps in Flutter
Description
This task involves designing and implementing the graphical user interface (GUI) for mobile applications in the Flutter project. The GUI should provide an intuitive and user-friendly interface for users to interact with the application's functionalities on mobile devices.
Acceptance Criteria
Which criteria has to be reached to be accepted

[ ] GUI design is consistent with the project's design guidelines
[ ] All required GUI components are implemented and functional
[ ] GUI is responsive and compatible with various screen sizes and resolutions of mobile devices

Tasks
Which tasks are included to add this feature

[ ] Research and design mobile GUI layout
[ ] Implement GUI components using the chosen mobile development framework
[ ] Integrate GUI with backend functionality

Dependencies
Which dependencies are introduced to the project

[ ] Integration with existing backend APIs
[ ] Compatibility with target mobile platforms (iOS, Android)
[ ] Flutter
[ ] flutter_rust_bridge

Estimates
Estimated effort for completion: 20 hours
Additional Information
Any additional information relevant to the development.

implemented down to the last detail.
Since we will probably decide against Flutter, this ticket will not be merged for the time being and will remain on its own branch


Create a file for each factory.

When app is growing and models amount is growing too, it's simpler just to have a bunch of files, one for each model, like rails factory_girl gem does.
But it looks like this gem doesn't either ability to create factories in separate files and documentation. WDYT?

I also already wondered if there is a way to do this. Especially useful when using the Flexible Factory stuff.

But it looks like this gem doesn't either...

By default we use a single factory file for all factory in factory_girl, but I see your point.
If you want different modules/files per factory then I would create them in test/support/#{factory_name}_factory.ex then import/alias those in your ConnCase/ModelCase or on a per test basis. Does that answer your question?
There are some thoughts on this here: https://github.com/thoughtbot/ex_machina#where-to-put-your-factories but maybe it could be improved. Any ideas?

@philipgiuliani Also, the flexible factory stuff is much easier in ExMachina 1.0 beta (on master) because you can put the functions right below the factory that needs them
def user_factory do
  %User{}
end

def make_admin(user) do
  %{user | admin: true}
end

Oh thanks, yes im using 1.0-beta and i really like it. Actually i haven't thought about splitting them up and importing them into the App.Factory module.
This could be a good Solution to split it up. Maybe we could add this "idea" to the README.
defmodule MyApp.Factory do
  use ExMachina.Ecto, repo: MyApp.Repo

  import MyApp.Factory.User
  import MyApp.Factory.Article
  ...
end

defmodule MyApp.Factory.User do
  def user_factory do
    %User{}
  end

  def make_admin(user) do
    %{user | admin: true}
  end
end

That won't work since the import will only be availably inside of factory, but you could do
defmodule MyApp.Factory do
  use ExMachina.Ecto, repo: MyApp.Repo

  # Call `use MyApp.Factory`
  defmacro __using__(_opts) do
    quote do
      import MyApp.Factory.User
      import MyApp.Factory.Article
    end
  end
  ...
end

defmodule MyApp.Factory.User do
  def user_factory do
    %User{}
  end

  def make_admin(user) do
    %{user | admin: true}
  end
end

I will consider adding to the README. I'll have to try it out and hear what people think first. I'd rather not suggest something on the README before knowing it's a good idea :P

Oh exactly, thanks. My project is not big enough yet to use it.. Maybe @asiniy can try it and give feedback!


Sui documentation is outdated & does not work

Re https://docs.sui.io/devnet/build/rust-sdk
The code example does not work - get_owned_objects now requires 4 parameters, rather than a single address argument.

Hi @csknk, Sorry, we are actively working on a whole new set of examples for the Rust SDK. We definitely missed updating some of the code samples in docs to align with the significant changes to Sui in the last few months. Thanks for taking time to let us know, and also for your patience.

Some basic examples on how to use the Rust SDK should come in a few days. I will post here when they're merged into the main branch. Thanks for your patience!

The basic examples for the Rust SDK has been merged into main (#13047). Check out the examples folder in the sui-sdk crate.


ENH: Suppress irrelevant TIFF warnings

Submitted on behalf of @lassoan by cherry-picking commit from lassoan/ITK@tiff_unknown_tag_warning_suppress/
LibTIFF logs hundreds of messages like "TIFFReadDirectory: Warning, Unknown field with tag 65280 (0xff00) encountered." when reading a volume from a TIFF file list that contains custom tags. Presence of custom tags is harmless and it should not flood the console or application log with warnings, because message display can significantly slow down image loading and excessive amount of irrelevant messages makes it difficult to notice important messages.
For background, see https://github.com/SlicerMorph/SlicerMorph/issues/320
PR Checklist

[x] No API changes were made (or the changes have been approved)
[x] No major design changes were made (or the changes have been approved)
[ ] Added test (or behavior not changed)

@lassoan After testing, I realized the Clean() function should be cleaned only in case of error. If not, there will be a seg fault
--- a/Modules/IO/TIFF/src/itkTIFFImageIO.cxx
+++ b/Modules/IO/TIFF/src/itkTIFFImageIO.cxx
@@ -69,7 +69,7 @@ TIFFImageIO::CanReadFile(const char * file)
   TIFFErrorHandler savedWarningHandler = TIFFSetWarningHandler(ITKTIFFTagNotFoundSuppressWarningHandler);
   _ITKTIFFsavedWarningHandler = savedWarningHandler;
   bool success = (m_InternalImage->Open(file) != 0);
-  if (success)
+  if (!success)
   {
     m_InternalImage->Clean();
   }

Yes, I think this was my WIP:

int _itkTIFFErrorHandlerExtR([[maybe_unused]] TIFF *tif, [[maybe_unused]] void *user_data, const char *module, const char *fmt, va_list ap)
{

if (::itk::Object::GetGlobalWarningDisplay())
{

char out[256];

vsnprintf(out, 256, fmt, ap);

std::ostringstream itkmsg;

itkmsg << "WARNING: libtiff(" << (module?module:"") << ") message: " << out << std::endl;

::itk::OutputWindowDisplayWarningText(itkmsg.str().c_str());

}
return 1;
}

int _itkTIFFWarningHandlerExtR(TIFF *tif, void *user_data, const char *module, const char *fmt, va_list ap)
{
return _itkTIFFErrorHandlerExtR(tif, user_data, module, fmt, ap);
}
int
--TIFFReaderInternal::Open(const char * filename)
++TIFFReaderInternal::Open(const char * filename, bool silent)
{
this->Clean();
struct stat fs;
@@@ -42,7 -68,7 +69,22 @@@
#endif
}

--  this->m_Image = TIFFOpen(filename, "r");
++#if defined  TIFFLIB_AT_LEAST
++  std::unique_ptr<TIFFOpenOptions,  tiff_open_options_free> options(TIFFOpenOptionsAlloc());
++  if (silent)
++  {
++    TIFFOpenOptionsSetErrorHandlerExtR(options.get(), nullptr, nullptr);
++    TIFFOpenOptionsSetWarningHandlerExtR(options.get(), nullptr, nullptr);
++  }
++  else
++  {
++    TIFFOpenOptionsSetErrorHandlerExtR(options.get(), _itkTIFFErrorHandlerExtR, nullptr);
++    TIFFOpenOptionsSetWarningHandlerExtR(options.get(), _itkTIFFWarningHandlerExtR, nullptr);
++  }
++  this->m_Image = TIFFOpenExt(filename, "r", options.get());
Does Slicer have a more uptodate version of libtiff in the super build?

Does Slicer have a more uptodate version of libtiff in the super build?

No. We rely on ITK to support TIFF image loading.

re: wip

I think instead of using OutputWindowDisplayWarningText we should not report those at all, or if we do, it should not happen by default.

Thanks a lot @blowekamp, this fix is definitely better than my original proposal. It would still need the filtering of the useless unknown field warning.
To suppress the warning we could add the same message parsing as in my original proposal, but perhaps a simpler and more robust solution would be to suppress this specific warning in libtiff. Hundreds of other projects struggle with the same issue and a fix is available but libtiff maintainers have been reluctant to merge it. I've added a note, but I'm not sure if this will make the maintainers reconsider. If they don't merge the fix then we could fork libtiff and merge the fix and then we would not need to implement the message filtering.

@jcfr thanks a lot for testing and the fix. I experienced crash, too, but I was not sure if it was because I have not rebuilt everything and wanted to do a clean build.

It would still need the filtering of the useless unknown field warning.

There are other ImageIO's that produce a large number of warnings too. Including DICOM with the MONOCHROME tag and MCRImageIO, and others.
There are a couple of other options to consider here.

After this warning message is place into the ITK messaging system, applications can filter the outputs with a custom ITK logger.
There is an existing itk::ProcessObject::GlobalWarningDisplay  property. This could also be used.
Another option to consider it to add a property to ImageIO::Base WarningDisplay (or something similar) to suppress all warnings from IO.

These are some other options to consider.

Ideally, we would only want to suppress this specific warning message from libtiff.

After this warning message is place into the ITK messaging system, applications can filter the outputs with a custom ITK logger.

Parsing all ITK messages all the time in a custom ITK logger, just to get rid of these warnings would not be very efficient.

There is an existing itk::ProcessObject::GlobalWarningDisplay property. This could also be used.
Another option to consider it to add a property to ImageIO::Base WarningDisplay (or something similar) to suppress all warnings from IO.

We would not want to suppress all messages from libtiff.
Overall, adding filtering in the TIFF logger redirection would or fixing libtiff (forking or pushing through this fix) would work better, as they would suppress the irrelevant messages, but nothing else; and they would be simple and efficient.

Parsing all ITK messages all the time in a custom ITK logger, just to get rid of these warnings would not be very efficient.

How many warning messages is your application getting? 🤨

It depends. Usually not a lot. Log files are typically not longer than a few MB. Still, parsing every string, especially if it is done in the main thread might be noticeable.
It would be also nice to avoid parsing, because the message might change in the future. So, the best would be to fix libtiff.
If libtiff maintainers don't merge the fix, do you think ITK might merge the fix to its libtiff?

It depends. Usually not a lot. Log files are typically not longer than a few MB. Still, parsing every string, especially if it is done in the main thread might be noticeable.

I am rather skeptical that is would be measurable.  I had been planning to improve the logging/warning message system in ITK to aid in filtering warning and improve compatibility with other loggers. Primarily allowing the lower to compose the message by giving it the components of filename, line number, warning/error/level and message.

It would be also nice to avoid parsing, because the message might change in the future. So, the best would be to fix libtiff.

Most of the time the message is rather annoying. However, it can be useful with something like an OME-TIFF which has large amount of structure that will not be correctly handled. There are other microscopy TIFF-sh file that can have other necearry information in the TIFF tags to load the image correctly too, although I have not encountered that recently.

If libtiff maintainers don't merge the fix, do you think ITK might merge the fix to its libtiff?

ITK's libtiff is very old, and in need of an update which may require some non-trivial effort.
For your application is there a couple common tags that are being reported? Another option may be to just register these tag that are annoying, that don't effect the reading of the images. For example the ImageJ TIFF TAGS.

I believe that @lassoan's application is 3D Slicer. Is that right Andras?

[x] That PR in libTIFF just got merged.

Yes, latest libtiff has now the option for turning off this warning!
I'll try to build ITK with the latest libtiff and see how it goes.

Yes, latest libtiff has now the option for turning off this warning!
I'll try to build ITK with the latest libtiff and see how it goes.

I have been testing with a 4.6.0 version locally and it has mostly been OK. The issue it that it depends on several other libraries for compression and that I don't readily have. So some if the ITK TIFF compression tests fail.

I've backported the fix from libtiff to ITK's version: https://github.com/InsightSoftwareConsortium/ITK/pull/4920
(it was much easier to do this than upgrade ITK's libtiff)

Should this be closed now, given that #4917 and #4920 were merged?

I think is now out of date now that that https://github.com/InsightSoftwareConsortium/ITK/pull/4917 and https://github.com/InsightSoftwareConsortium/ITK/pull/4920 and #4961 have been merged.


Error in documentation

In the Military Contractors (DoDCON) section there is a typo. There should be no S on microsoftonline.us

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

ID: 0658cf44-97c9-cb23-68bd-146f29eb644c
Version Independent ID: e05ed89e-2dfa-0d31-4198-9170a33ef120
Content: Embed content in your application for government and national cloud - Power BI
Content Source: powerbi-docs/developer/embedded/embed-sample-for-customers-national-clouds.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @KesemSharabi
Microsoft Alias: kesharab

Thanks for your comment, @kevman123. We’ve forwarded your feedback to the writer, who should respond to this thread shortly. Thanks!

Hi @kevman123,
Thanks for spotting this typo and notifying us - it is now fixed.


cannot dispatch application manifests

Apisix yaml
apiVersion: apisix.apache.org/v2beta1
kind: ApisixRoute
metadata:
  name: test-apisix-dashboard
spec:
  http:
  - name: foo
    match:
      hosts:
      - apisix.test.com
      paths:
      - "/test"
    backend:
     serviceName: apisix-dashboard
     servicePort: 80

Apisix trait
apiVersion: core.oam.dev/v1beta1
kind: TraitDefinition
metadata:
  name: apisix-route
spec:
  podDisruptive: false
  schematic:
    cue:
      template: |
        parameter: {
        	apisixRoute: [...{
        		name: string
        		paths: [...string]
            hosts: [...string]
            servicePort:  *80 | int
        	}]
        }

        outputs: apisixRoute: {
            apiVersion: "apisix.apache.org/v2beta1"
            kind:       "ApisixRoute"
            metadata:
                name: context.name
            spec: {
                http: [
                  for v in parameter.apisixRoute {
                  name: v.name
                  match:
                    hosts: [v.hosts]
                    paths: [v.paths]
                  backend:
                   serviceName: context.name
                   servicePort: v.servicePort
                  },
                ]
            }
        }

kubevela APP
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: clonset-app
spec:
  components:
    - name: express-server
      type: cloneset
      properties:
        image: crccheck/hello-world
        port: 8000
      traits:
        - type: apisix-route
          properties:
            apisixRoute:
              - name: apisix-example
                hosts:
                  - "apisix.test.com"
                paths:
                  - "/test"
                serviceName: apisix-dashboard
                servicePort: 80

APP status ERROR
Name:         clonset-app
Namespace:    vela-system
Labels:       <none>
Annotations:  kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"core.oam.dev/v1beta1","kind":"Application","metadata":{"annotations":{},"name":"clonset-app","namespace":"vela-system"},"sp...
              oam.dev/kubevela-version: v1.1.0-alpha.5
API Version:  core.oam.dev/v1beta1
Kind:         Application
Metadata:
  Creation Timestamp:  2021-07-26T03:36:00Z
  Finalizers:
    app.oam.dev/resource-tracker-finalizer
  Generation:  1
  Managed Fields:
    API Version:  core.oam.dev/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
      f:spec:
        .:
        f:components:
    Manager:      kubectl
    Operation:    Update
    Time:         2021-07-26T03:36:00Z
    API Version:  core.oam.dev/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          f:oam.dev/kubevela-version:
        f:finalizers:
      f:status:
        .:
        f:conditions:
        f:rollout:
          .:
          f:batchRollingState:
          f:currentBatch:
          f:lastTargetAppRevision:
          f:rollingState:
          f:upgradedReadyReplicas:
          f:upgradedReplicas:
        f:status:
    Manager:         manager
    Operation:       Update
    Time:            2021-07-26T03:36:00Z
  Resource Version:  32824636
  Self Link:         /apis/core.oam.dev/v1beta1/namespaces/vela-system/applications/clonset-app
  UID:               3d3f2036-9b8f-44b8-9303-cb98f7949606
Spec:
  Components:
    Name:  express-server
    Properties:
      Image:  crccheck/hello-world
      Port:   8000
    Traits:
      Properties:
        Apisix Route:
          Hosts:
            apisix.test.com
          Name:  apisix-example
          Paths:
            /test
          Service Name:  apisix-dashboard
          Service Port:  80
      Type:              apisix-route
    Type:                cloneset
Status:
  Conditions:
    Last Transition Time:  2021-07-26T03:36:00Z
    Reason:                Available
    Status:                True
    Type:                  Parsed
    Last Transition Time:  2021-07-26T03:36:00Z
    Reason:                Available
    Status:                True
    Type:                  Revision
    Last Transition Time:  2021-07-26T03:36:00Z
    Reason:                Available
    Status:                True
    Type:                  Render
    Last Transition Time:  2021-07-26T03:36:22Z
    Message:               cannot dispatch application manifests: cannot apply manifest, name: "express-server" apiVersion: "apisix.apache.org/v2beta1" kind: "ApisixRoute": cannot create object: ApisixRoute.apisix.apache.org "express-server" is invalid: [spec.http.backend.servicePort: Required value, spec.http.match.hosts: Invalid value: "array": spec.http.match.hosts in body must be of type string: "array", spec.http.match.paths: Required value]
    Reason:                ReconcileError
    Status:                False
    Type:                  Applied
  Rollout:
    Batch Rolling State:
    Current Batch:             0
    Last Target App Revision:
    Rolling State:
    Upgraded Ready Replicas:   0
    Upgraded Replicas:         0
  Status:                      rendering
Events:
  Type     Reason       Age                    From         Message
  ----     ------       ----                   ----         -------
  Warning  FailedApply  2m50s                  Application  cannot dispatch application manifests: cannot apply manifest, name: "express-server" apiVersion: "apisix.apache.org/v2beta1" kind: "ApisixRoute": cannot create object: ApisixRoute.apisix.apache.org "express-server" is invalid: [spec.http.match.hosts: Invalid value: "array": spec.http.match.hosts in body must be of type string: "array", spec.http.match.paths: Required value, spec.http.backend.servicePort: Required value]
  Normal   Parsed       2m49s (x7 over 2m50s)  Application  Parsed successfully
  Normal   Revisioned   2m49s (x6 over 2m50s)  Application  Revisioned successfully
  Normal   Rendered     2m49s (x6 over 2m50s)  Application  Rendered successfully
  Warning  FailedApply  2m49s (x5 over 2m50s)  Application  cannot dispatch application manifests: cannot apply manifest, name: "express-server" apiVersion: "apisix.apache.org/v2beta1" kind: "ApisixRoute": cannot create object: ApisixRoute.apisix.apache.org "express-server" is invalid: [spec.http.backend.servicePort: Required value, spec.http.match.hosts: Invalid value: "array": spec.http.match.hosts in body must be of type string: "array", spec.http.match.paths: Required value]

kubeve version
➜ helm list
NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
kubevela        vela-system     1               2021-07-21 09:39:26.327306 +0800 CST    deployed        vela-core-1.1.0-alpha.5 1.1.0-alpha.5

@hongchaodeng  @wonderflow cc

[
spec.http.backend.servicePort: Required value,
spec.http.match.hosts: Invalid value: "array": spec.http.match.hosts in body must be of type string: "array", spec.http.match.paths: Required value
]

As you can see, there are something wrong in you cue template. Remember Cuelang don't treat same indent as same level (YAML does. That could be confusing sometime. Maybe we should develop an simple YAML to cue template tools \cc @wonderflow ), cue only recognize "{}" unfortunately.
I guess this is what you acturally want:
parameter: {
	apisixRoute: [...{
		name: string
		paths: [...string]
		hosts: [...string]
		servicePort: *80 | int
	}]
}

outputs: apisixRoute: {
	apiVersion: "apisix.apache.org/v2beta1"
	kind:       "ApisixRoute"
	metadata:
		name: context.name
	spec: {
		http: [
			for v in parameter.apisixRoute {
				name: v.name
				match: {                                               // <-----use explicit {} here
					hosts: v.hosts                            // v.hosts is already an array, "[ ]" is redundant
					paths: v.paths                            // also here
				}
				backend: {                                           // <-----use explicit {} here
					serviceName: context.name
					servicePort: v.servicePort
				}
			},
		]
	}
}

Before we think of a convient method to  thansform a yaml to cue template. Here not bad debug check list for your cue template in X-definition

Make sure install cue executable file.
copy-and-paste your cue template seperately out of your X-definition(Or always test cue template is right for the first time).
Add a simulated parameter block
Add a simulated context block
excute cue eval -e outputs debug.cue (-e means expression )
check if outputs expression meets your intention

@chivalryq  Thank you for your guidance, this is caused by my carefulness.
/close


Missing Store option on left Panel in simplestorage contract

Hello I have decided to start Free youtube course about Solidity Language https://www.youtube.com/watch?v=M576WGiDBdQ&t=5321s after write this short contract simple storage im getting following error

but on the Video there is not and the smart contract looks the same

Please check your variable name of Array declared it must be People[ ] public people and not people[ ] public people there is typing mistake!


xdg-mime: add module

This is a direct translation of the NixOS module.
If enabled, this module will create the XDG mime database
and desktop file database caches from programs installed
via home-manager. The 'XDG_DATA_DIRS' environment variable
is extended so that programs like 'xdg-open' can find and
make use of these databases.
Not sure if it makes sense to add a test here; the files are auto-generated, big, and one of them even uses a binary format.

Not using xdg-open specifially with this depends on https://github.com/NixOS/nixpkgs/pull/72426

Thanks! I've rebased this to master in 571989f564311475d26200cd303941c68e8488a7.


First improvements to MVP

Visuals:

[ ] react to "Enter" when submitting #tag
[ ] login should disappear when user is logged in, show login info instead

Code:

[ ] change calls to fetch()
[ ] extract css from index page

@petrsvihlik fyi

All finished 🎉 🎉 🎉 🎉


Natural Sort for Strings

Defining this is a bit ridiculous. The point is to provide a better sorting experience for users. Lexicographical sorting (with ASCII order) isn't really what a human would expect. For example:
Apple < Zoo < apple < file100 < file2 < file90 < file99 < zoo
This package natural_sort defines a function natural_sort.Sort(array []string) that sorts its arguments in a natural order:
Apple < apple < file2 < file90 < file99 < file100 < Zoo < zoo
For reference, see:
https://en.wikipedia.org/wiki/Natural_sort_order
http://blog.codinghorror.com/sorting-for-humans-natural-sort-order/

fwiw, you can probably just sort on ToLower(), and it'd probably be fine to not really consider case variants since we'll never have them (and if we do, they won't be very useful).

LGTM


FW engine failure move

This is partially related to initial discussion of a commander rewrite, but FW engine failure detection is spread out across commander (detection), navigator, fw_pos_ctrl (limit pitch - dangerous), and fw_att_ctrl (cut throttle).
https://github.com/PX4/Firmware/blob/d1c3b771ee1fc3691eea9098b7af24404466aef9/src/modules/commander/commander.cpp#L2872
https://github.com/PX4/Firmware/blob/d1c3b771ee1fc3691eea9098b7af24404466aef9/src/modules/fw_pos_control_l1/fw_pos_control_l1_main.cpp#L2497
https://github.com/PX4/Firmware/blob/d1c3b771ee1fc3691eea9098b7af24404466aef9/src/modules/fw_att_control/fw_att_control_main.cpp#L1156
The detection could be moved to the land_detctor (renamed vehicle model?), and the behaviour should be a regular loiter (or wings level glide) with TECS maintaining airspeed (speed weight 2.0) with no thrust.

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


Following documentation results in failure

The build works just fine on Ubuntu, but none of the necessary dependencies are available for the tutorial script.  #include <sc2api/sc2_api.h> cannot be found.

You made a new c++ file ? If so, ensure its CMakeFile ´´'target_link_libraries''' is set properly and references sc2api.

I just tried this and it seemed to work fine. The tutorial project should already be set up with the necessary include paths.

If you want to understand how the documentation results in failure, start with a fresh Ubuntu install and then follow the instructions precisely using the prebuilt binary method.  Dependencies are missing, configurations are incorrect.
As a follow up, I tried the tutorial on Windows as well.  For Windows 10...
Followed build instructions with cmake after cloning repo just fine.
Followed tutorial1.md directions to the point of first build which fails (submitted a PR for a minor correction in docs).  But ultimately end up here:
Unable to start program ...\build\x64\Release\ALL_BUILD     Access is denied

By default the wrong project is built when loaded with visual studio.  Once you manually trigger a build on the right sub-folder, it will build correctly.  I'll check the docs again and submit a pr if they can be clarified at all.


move babel-preset-env from dependencies to devDependencies

This package was installing babel-preset-env (and it's dependencies) in production, where it's actually only used in development to build the package and demos.

You are completely right!


should not merge PascalCase / camelCase into one menu item

should not merge PascalCase / camelCase into one menu item
if i wanna camelCase some thing
i have click x 2 for make it is camelCase
hope can like old version, it is split action

Maybe configuring your own action would be enough?

it is work, but i don't think this is good way for make it


include system head with error

I add system head in my head file YmmVal.h, but it tips error in those addin head:
iomanip
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.35.32215\include\iomanip
[打开链接](vscode-file://vscode-app/c:/Users/guiji/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-sandbox/workbench/workbench.html) (ctrl + 单击)

In included file: no member named 'acosf' in the global namespaceclang(no_member)
cmath(735, 25): Error occurred here
In included file: no type named 'pos_type' in 'std::char_traits<char>'clang(typename_nested_not_found)
ios(30, 25): Error occurred here

seems those error located in cmath, but as i open it, clangd don't report any error in it.
Logs
I[12:06:08.211] clangd version 15.0.7
I[12:06:08.212] Features: windows
I[12:06:08.212] PID: 7092
I[12:06:08.212] Working directory: d:\Code\MyProject\cxx\ParalleData
I[12:06:08.212] argv[0]: C:\Program Files\LLVM\bin\clangd.EXE
I[12:06:08.212] argv[1]: --compile-commands-dir=D:\Code\MyProject\cxx\ParalleData
I[12:06:08.212] argv[2]: --query-driver=C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.35.32215\bin\Hostx64\x64\cl.exe
I[12:06:08.219] Starting LSP over stdin/stdout
I[12:06:08.219] <-- initialize(0)
I[12:06:08.265] --> reply:initialize(0) 45 ms
I[12:06:08.267] <-- initialized
I[12:06:08.275] <-- textDocument/didOpen
I[12:06:08.276] <-- textDocument/documentSymbol(1)
I[12:06:08.277] <-- textDocument/codeAction(2)
I[12:06:08.288] <-- textDocument/documentLink(3)
I[12:06:08.288] <-- textDocument/inlayHint(4)
I[12:06:08.290] Loaded compilation database from D:\Code\MyProject\cxx\ParalleData\compile_commands.json
I[12:06:08.290] ASTWorker building file d:\Code\MyProject\cxx\ParalleData\src\include\YmmVal.h version 1 with command inferred from src\ch02\01\Ch02_01.cpp
[D:\Code\MyProject\cxx\ParalleData]
"C:\\Program Files\\Microsoft Visual Studio\\2022\\Professional\\VC\\Tools\\MSVC\\14.35.32215\\bin\\Hostx64\\x64\\cl.exe" --driver-mode=cl /c /nologo /Zi /FS "/Fdbuild\\windows\\x64\\debug\\compile.ch02_01.pdb" /W3 /WX /Od "/ID:\\Code\\MyProject\\cxx\\ParalleData\\src\\include" /EHsc "/IC:\\Users\\guiji\\AppData\\Local\\.xmake\\packages\\g\\gsl\\v4.0.0\\b1ec133f21b342ada9530623a4d0880a\\include" /TP /std:c++20 "-resource-dir=C:\\Program Files\\LLVM\\lib\\clang\\15.0.7" -- "d:\\Code\\MyProject\\cxx\\ParalleData\\src\\include\\YmmVal.h"
I[12:06:08.292] --> window/workDoneProgress/create(0)
I[12:06:08.292] Enqueueing 21 commands for indexing

System information
Output of clangd --version: 15.0.7
Editor/LSP plugin: vscode
Operating system: win10

it figure out cos I add self define Math.h in program collision with system head file, rename this file is the solution


Add NFCPy support

This Pull Request adds support for using NFCPy supported NFC readers

Except for the points that @s-martin found, I like the changes you did there!

Except for the points that @s-martin found, I like the changes you did there!
Which device did you test on?

I tested on a Rock64 with dietpi. As for the NFC reader it's an ACR122U

Thanks for the updates!

I am unable to check this since I don't have a matching device available. Have you tested your set up properly? Was the installation process smooth.  Since you followed the guidance, I'd suggest to merge this. Maybe you could resolve the above comments and send this for code review again. I have added this to the next release #2211.

I am unable to check this since I don't have a matching device available. Have you tested your set up properly? Was the installation process smooth. Since you followed the guidance, I'd suggest to merge this. Maybe you could resolve the above comments and send this for code review again. I have added this to the next release #2211.

This is tested, but I wanted to resolve the comments first and do a complete clean install again to confirm. I'm sick since a week, and will probably not come around that before the end of the week.

I have improved the installation script and customization by scanning for compatible devices and letting the user choose which one they want to use. It is very similar to the generic_usb RFID module.
The customization code will also generate an explicit device path, that will also allow to use multiple NFCpy compatible devices at the same time.
The code is tested on a fresh installation and works beside one small quirk, which I seemingly cannot fix.
The file src/jukebox/components/rfid/hardware/generic_nfcpy/setup.inc.sh is missing execution rights when checked out. The file is executable on my machine, but I suspect it has something to do, that I committed it on a windows machine...
When I add the execution rights and rerun run_register_rfid_reader.py everything works flawlessly.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 38.384%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
418

Relevant Lines:
1089

💛  - Coveralls

@powertomato it looks like you are finished and as you said you tested it we approved it.
If you have no more changes planned, we would merge it.

Just stumbled over this code line: https://github.com/MiczFlor/RPi-Jukebox-RFID/blob/2bb93679a68ff06497b492f2e0191bd0ce37b2fb/src/jukebox/components/rfid/configure/init.py#L154
@pabera, @AlvinSchiller do we need to add nfcpy there?


Comment API: actions are not hidden when contextValue changes

VSCode Version: Insiders 1.36
OS Version: Mojave 10.14.5

Steps to Reproduce:

Add comment actions (comments/comment/actions) with the comment API.

Actions render clipped and overlapped.

Update the contextValue for a comment after the comment has been rendered, and now the comment action's "when" clause is false.

The comment actions are not hidden as expected. (If the "when" cause is false when the comment thread is drawn initially, then it works as expected. It also does not get fixed when I force a redraw. I've also seen flaky updating when I update a comment label).

Does this issue occur when all extensions are disabled?: N/A

Thanks for reporting this @sbeland! I've opened a separate issue for the rendering issue since that's independent of the update problem.

Awesome! Thank you @RMacfarlane  :)

@RMacfarlane I've also noticed that when I change a comment label, it doesn't force a redraw. Is there an explicit way to make it redraw?

After you update the property on the comment, are you also setting the comments property on the thread? I’m not sure how clear we made this in the documentation, but the mutations that actually cause redraws are

updating the comment thread label
updating the comment thread context value
updating the comment thread collapsible state
updating the comment thread comment array
updating the comment thread range

That being said, I think there may may be a problem with the way we internally id comments. We had a previous version of the API that required specifying a commentId property on comments, we may still be trying to read from that in some cases. If so, then adding commentId on comments would be a workaround


[Region Migration]: IoTV2 Support Region Migration

as title

LGTM. Looking forward to Ms. Zhen’s test.


When registering at Worona from WP Control Panel it doesn't detect the WP site

After installing the plugin and registering at Worona from the WP Control Panel it asked me to add my WordPress site - the fields weren't automatically filled in.

Related: https://github.com/worona/worona-dashboard/issues/42

Should be solved in #106


Dec 755 remove item interface to metadata

Changed so that there is no public interface to the metadata.
I added the validation based on the configuration back in.

:+1: after Justin's comments are addressed

:+1:


Support for service / rpc options

Is your feature request related to a problem? Please describe.
Currently, the protobuf plug-in doesn't appear to understand options defined on either the service level or rpc (method) level.
Describe the solution you'd like
The protobuf v3 spec allows for options defined at the service and rpc (method) level.
Additional context
Example (using Google's http.proto): https://github.com/googleapis/googleapis/blob/2a57c3158a97597941220e64a940760d6a738a69/google/api/http.proto#L129-L136
When using the plug-in today, I get various errors when using service or rpc options:

When using a built-in option, I get an error regarding an unresolved reference (this reference should be found in the descriptor.proto file):

service MyService {
    option idempotency_level = NO_SIDE_EFFECTS;
    ...
}

When using a custom option, I get an error regarding extraneous input (after the semicolon in the option):

service MyService
    option (company.grpc.custom_rule) = {
        my_field: "abc"; // Error after semicolon here
        my_list_field: ["a", "b", "c"];
    };
    ...
}

Regarding first one - idepmotency_level is method's option, it's not applicable for service: https://github.com/protocolbuffers/protobuf/blob/master/src/google/protobuf/descriptor.proto#L684

For second one - AFAIK it should look like this:
service MyService {
    option (company.grpc.custom_rule) = {
            my_field: "abc"
            my_list_field: "a"
            my_list_field: "b"
            my_list_field: "c"
    };
}

When you use {} for field/method level options, you should use "protobuf text format" inside of the block.

https://stackoverflow.com/questions/18873924/what-does-the-protobuf-text-format-look-like
https://github.com/protocolbuffers/protobuf/blob/master/src/google/protobuf/unittest_custom_options.proto#L350

Can you please check if protoc compiles your examples?

I've verified that using Protobuf text format works as expected. This also fixes the parsing for options coming from descriptor.proto. Feel free to close this - it was confusing at first to have protoc allow this syntax and not the plug-in.

Protoc does compile the custom method options as written.

In this case I'll keep it open - at some point plugin should support this syntax as well.

Try:
syntax="proto3";

import "google/protobuf/descriptor.proto";
import "google/protobuf/empty.proto";

message CustomOptions {
    string my_field = 1;
    repeated string my_list_field = 2;
}

extend google.protobuf.ServiceOptions {
    CustomOptions custom_rule = 50003;
}

service MyService {
    option (custom_rule) = {
        my_field: "abc";
        my_list_field: ["a", "b", "c"];
    };
    rpc Get(google.protobuf.Empty) returns(google.protobuf.Empty) {}
}

Here's a full example Maven project - https://www.dropbox.com/s/avs1aeirk834qf9/example.tar.gz?dl=0
When expanded, you can run mvn compile to generate the Java code and service from the proto file. The DescriptorTest program can be executed to show the service options are parsed as expected from the proto file.

I see, you replaced = to :, now it compiles - so semicolons and lists inside of square brackets are supported. Thanks!

When loading the following protobuf file in IntelliJ, multiple errors occur related to the structured options.
https://github.com/grpc-ecosystem/grpc-gateway/blob/master/examples/proto/examplepb/a_bit_of_everything.proto
As soon as a single error is detected, the rest of the file does not parse at all causing syntax highlighting to just stop functioning.

Do you have any status about the issue? Plugin does not support grpc.gateway.protoc_gen_swagger.options.openapiv2_swagger at all as mentioned above.

Checking...

For the grpc.gateway.protoc_gen_swagger.options you either need to copy the "a_bit_of_everything.proto" to the root of the grpc-gateway project and open the project in IntelliJ or you need to add a "Custom Include Path" to the Protobuf plugin config to the root of the grpc-gateway project.  However even when doing that, the file shows multiple errors.

you need to add a "Custom Include Path" to the Protobuf plugin config

I wasn't aware of this.. thanks.
Stil,l I have same problem that I get an error on the semi-colon (after  "go-ws-api";) and on the next line on the first word (version). The files compile without any issue.
syntax = "proto3";
package echopb;

import "google/api/annotations.proto";
import "protoc-gen-swagger/options/annotations.proto";

option (grpc.gateway.protoc_gen_swagger.options.openapiv2_swagger) = {
    info: {
        title: "go-ws-api";
        version: "1.0";
        contact: {
            name: "go-ws-api";
            url: "https://github.com/mch1307/ws-go-api";
            email<EMAIL_ADDRESS>        };
    };
    schemes: HTTP;
    schemes: HTTPS;
    consumes: "application/json";
    produces: "application/json";
};

message EchoMessage {
 string value = 1;
}

service EchoService {
  rpc Echo(EchoMessage) returns (EchoMessage) {
    option (google.api.http) = {
      post: "/v1/echo"
      body: "*"
    };
  }
}

Code mostly take from: https://blog.csnet.me/blog/building-a-go-api-grpc-rest-and-openapi-swagger.1/
It would be great if this could be fixed in the plugin! :-D

This issue is closed as plugin is not supported anymore.
Please switch to https://github.com/jvolkman/intellij-protobuf-editor.


Added working skeleton for createClient REST API endpoint

Works with postman and correctly parses request with ticket data... now just need to integrate with honeyclient

Do we want to use tabs instead of spaces for the whole backend? I noticed that the honeyclient is using spaces.

Golang is actually opinionated in this. The built-in formatter, gofmt, says this on how it formats code:
"Gofmt formats Go programs. It uses tabs for indentation and blanks for alignment. Alignment assumes that an editor is using a fixed-width font."


fix: remove flash saying JS is disabled

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Addressed currently open issue

Closes #16867
Description
Removed the 'JavaScript is disabled....' flash message from the preview pane. See the issue for more details.

@Bouncey Thanks for the review and I made the changes you suggested. If there's anything else, let me know and I should be able to get to this today.


Parametrized tests handling

Hi!
As far as I can see, parametrized tests are not handled properly.
I am not quite sure if it is possible to explore all the test cases without executing the code though.
But maybe you could take a look at such a case.
Here is an example from the official jest documentation:
describe.each([
  [1, 1, 2],
  [1, 2, 3],
  [2, 1, 3],
])('.add(%i, %i)', (a, b, expected) => {
  test(`returns ${expected}`, () => {
    expect(a + b).toBe(expected);
  });

  test(`returned value not be greater than ${expected}`, () => {
    expect(a + b).not.toBeGreaterThan(expected);
  });

  test(`returned value not be less than ${expected}`, () => {
    expect(a + b).not.toBeLessThan(expected);
  });
});

These tests are displayed as a single test in the Test Explorer, not as a separate test case for every set of parameters:

Also, if I try to run either the whole test or a single test case, nothing happens: neither fail nor success.
Thank you for your work!

Cool, sounds like an interesting case to handle.  And thanks for providing an example.

I have a feeling that this issue will be related to jest-community/jest-editor-support#29.  We use jest-editor-support to parse the test files.  There is an open PR jest-community/jest-editor-support#30 that I think will fix this issue.  Maybe go and add your support for it there?

Yes, it looks like my issue is related to that in the jest-editor-support repository.
Closing this issue then as related to a 3rd party.
Thanks!

@rossknudsen hi!
Can I ask you to update to the latest version of https://github.com/jest-community/jest-editor-support ?
It seems that the problem is resolved in the latest version.
Thanks!

@botsman would you mind checking how much of the issues that you raised in this ticket are covered by the recent release of v0.8.0 to the marketplace?  If you feel that this ticket has been covered, then please feel free to close.  If there are some minor defects remaining, then you can either document here, or raise them in a separate issue (I'm easy either way).

@botsman would you mind checking how much of the issues that you raised in this ticket are covered by the recent release of v0.8.0 to the marketplace?  If you feel that this ticket has been covered, then please feel free to close.  If there are some minor defects remaining, then you can either document here, or raise them in a separate issue (I'm easy either way).

I've checked the latest version with the extension with the base example from 1st message:

In order to discover tests, I need to run them first.
Before running:

After running:

If tests are intended to be explored only after execution, then it is fine.

After tests are discovered, the first part of parametrized tests remains in the tests UI:

Both of these issues are really minor for me.
Otherwise it looks good, great job guys!
Thank you!

I've checked the latest version with the extension with the base example from 1st message:

In order to discover tests, I need to run them first.
Before running:

After running:

If tests are intended to be explored only after execution, then it is fine.

After tests are discovered, the first part of parametrized tests remains in the tests UI:

Both of these issues are really minor for me.
Otherwise it looks good, great job guys!
Thank you!

This is not working for me. Perhaps because I have nested describes? I have a parent describe that uses beforeEach to set things up for individual tests and I also have some parameterized tests in that describe like
describe.each([[' '], ['  '], [' - '], [', '], ["'"], [":'"]])(
    'inputValues setter should single quote the separator value, when it starts or ends with whitespace or single quote',
    (actualValue: string) => {
      it(` "${actualValue}"`, () => {
        component.inputValues = {separator: actualValue};
        expect(component.separatorInput).toEqual(`'${actualValue}'`);
      });
    }
  );

In this case, the Text Explorer panel just shows this before and after running the tests.

Doesn't work for me either, just stays the same after running.
test.each([
  {a: 1, b: 1, expected: 2},
  {a: 1, b: 2, expected: 3},
  {a: 2, b: 1, expected: 3},
])('.add($a, $b)', ({a, b, expected}) => {
  expect(a + b).toBe(expected);
});


Fix documentation and package project files

The documentation had a few mistakes which would make the code inside unfunctional and the rojo projectfiles for ohmyprvd-debugger and ohmyprvd-net

ok github isnt letting me delete that ^^^^ but please apply my changes


[SMALLFIX] Fix a compatibility issue for journal replay with security mode change.

Tested locally: restarting a cluster by enabling security from NOSASL to SIMPLE, without formatting the journal.
Without this change, the journal generated with security off would not be replayed correctly into a new version with security on.

@gpang @apc999 @calvinjia

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11564/
Test PASSed.

Merged build finished. Test PASSed.

@apc999  yes, that will be in a separate PR.

@gpang I've replied to your questions, but not totally sure. Maybe can we leave the not-null check to be safe?

Ok, we can leave it in. I just want to understand when objects could be null.


Unable to initialize a new project using the ignite CLI

Describe the bug
I am trying to initialize a new project using the CLI, having the following error with it.
The following error occurred:
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving<EMAIL_ADDRESS>npm error Found<EMAIL_ADDRESS>npm error node_modules/eslint-plugin-n
npm error   dev<EMAIL_ADDRESS>from the root project
npm error
npm error Could not resolve dependency:
npm error peer<EMAIL_ADDRESS>|| ^16.0.0 " from<EMAIL_ADDRESS>npm error node_modules/eslint-config-standard
npm error   dev<EMAIL_ADDRESS>from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error C:\Users\hp\AppData\Local\npm-cache\_logs\2024-10-29T16_26_12_983Z-eresolve-report.txt
npm error A complete log of this run can be found in: C:\Users\hp\AppData\Local\npm-cache\_logs\2024-10-29T16_26_12_983Z-debug-0.log

Using the --legacy-peer-deps & --force also did not work as well.
Ignite version
Ignite 10.0.1
Additional info
System
platform           win32
arch               x64
cpu                8 cores              Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
directory          QuickTestIgniteCli   C:\Users\hp\Desktop\Development\QuickTestIgniteCli
JavaScript (and globally-installed packages)
node                          20.12.0             C:\Program Files\nodejs\node.EXE
npm                           10.8.2              C:\Program Files\nodejs\npm.CMD
@superforms/superforms-rn   0.0.0-development
jetifier                    2.0.0
npm                         10.8.2
yarn                          -                   not installed
pnpm                          -                   not installed
bun                           -                   not installed
expo                          -                   not installed
Ignite
ignite-cli         10.0.1       C:\Users\hp\AppData\Local\npm-cache_npx\bec2839915ba8fc3\node_modules.bin\ignite.CMD
ignite src         build        C:\Users\hp\AppData\Local\npm-cache_npx\bec2839915ba8fc3\node_modules\ignite-cli\build
Android
java               17.0.10      C:\Program Files\Microsoft\jdk-<IP_ADDRESS>-hotspot\bin\java.EXE
android home       -            C:\Users\hp\AppData\Local\Android\Sdk
Tools
git                git version 2.44.0.windows.1   C:\Program Files\Git\cmd\git.EXE

Hello @AbdullahQureshi1080 , thanks for posting this. What's the error you are getting?

hi @AbdullahQureshi1080 - are you experiencing what is documented here

@fpena @frankcalise Updated the comment!
I think it is one of the dependencies, used both flags and still failed. --legacy-peer-deps & --force

@frankcalise Not really. Let me try it with an older version of the CLI and get back to you.

hi @AbdullahQureshi1080 - are you experiencing what is documented here?

@AbdullahQureshi1080 choose not to install dependencies during the CLI, then after the project is created you can do npm install --legacy-peer-deps or use yarn. These are the two workarounds currently

@frankcalise Everything works well on CLI v9.10.1
And the workaround you've shared does not work. I still face the error above shared in the other issue.
~\Desktop\Development
➜  npx ignite-cli@latest new QuickTestIgniteCliv1

✅ What bundle identifier? · com.quicktestignitecliv1
✅ Where do you want to start your project? · C:\Users\hp\Desktop\Development\QuickTestIgniteCliv1
✅ How do you want to manage Native code? · Manual
✅ Do you want to initialize a git repository? (Y/n) · Yes
✅ Remove demo code? We recommend leaving it in if it's your first time using Ignite (y/N) · Yes
✅ Include MobX-State-Tree code? (recommended) (Y/n) · No
✅ Which package manager do you want to use? · npm
✅ Do you want to install dependencies? (Y/n) · No
✅ [Experimental] Expo Router for navigation? (y/N) · No
✅ [Experimental] the New Architecture? (y/N) · No

    █ Creating QuickTestIgniteCliv1 using Ignite 10.0.1
    █ Powered by  ∞ Infinite Red  (https://infinite.red)
    █ Package Manager: npm
    █ Bundle identifier: com.quicktestignitecliv1
    █ Path: C:\Users\hp\Desktop\Development\QuickTestIgniteCliv1
    ────────────────────────────────────────────────────

    🖨  3D-printing a new React Native app
    🎨 Getting those last few details perfect
    ⚙ Configuring app.json
    🛠 Removing fancy demo code

The following error occurred:

    Error: Command failed: rm -rf src
'rm' is not recognized as an internal or external command,
operable program or batch file.

@AbdullahQureshi1080 gotcha so it is related to the issue I posted above. will try to push a fix shortly for this

@AbdullahQureshi1080 can you try with npx ignite-cli@latest (should be 10.0.2)

@frankcalise Tried the latest:10.0.3 it failed on the clean up.
    █ Creating QuickTestIgniteCliv2 using Ignite 10.0.3
    █ Powered by  ∞ Infinite Red  (https://infinite.red)
    █ Package Manager: npm
    █ Bundle identifier: com.quicktestignitecliv2
    █ Path: C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2
    ────────────────────────────────────────────────────

    🖨  3D-printing a new React Native app
    🎨 Getting those last few details perfect
    🧶 Installing npm dependencies (wow these are heavy)
    ⚙ Configuring app.json
    🛠 Generating native template via Expo Prebuild
    🛠 Removing fancy demo code
    🌳 Removing MobX-State-Tree code
    ❌ Cleaning up

The following error occurred:

><EMAIL_ADDRESS>format
> eslint . --fix

Error while parsing C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\app\screens\WelcomeScreen.tsx
Line 22, column 2: '{' expected.
`parseForESLint` from parser `@typescript-eslint/parser` is invalid and will just be ignored

Error while parsing C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\app\screens\WelcomeScreen.tsx
Line 22, column 2: '{' expected.
`parseForESLint` from parser `@typescript-eslint/parser` is invalid and will just be ignored

Error while parsing C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\app\screens\WelcomeScreen.tsx
Line 22, column 2: '{' expected.
`parseForESLint` from parser `@typescript-eslint/parser` is invalid and will just be ignored

Error while parsing C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\app\screens\WelcomeScreen.tsx
Line 22, column 2: '{' expected.
`parseForESLint` from parser `@typescript-eslint/parser` is invalid and will just be ignored

Error while parsing C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\app\screens\WelcomeScreen.tsx
Line 22, column 2: '{' expected.
`parseForESLint` from parser `@typescript-eslint/parser` is invalid and will just be ignored

Error while parsing C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\app\app.tsx
Line 109, column 2: Declaration or statement expected.
`parseForESLint` from parser `@typescript-eslint/parser` is invalid and will just be ignored

C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\App.tsx
  3:17  error  Parse errors in imported module '@/app': Declaration or statement expected. (109:2)  import/namespace

C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\app\app.tsx
  109:2  error  Parsing error: Declaration or statement expected

C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\app\navigators\AppNavigator.tsx
  63:55  error  'WelcomeScreen' not found in imported namespace 'Screens'  import/namespace

C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\app\screens\WelcomeScreen.tsx
  22:2  error  Parsing error: '{' expected

C:\Users\hp\Desktop\Development\QuickTestIgniteCliv2\app\screens\index.ts
  1:15  error  Parse errors in imported module './WelcomeScreen': '{' expected. (22:2)  import/export

✖ 5 problems (5 errors, 0 warnings)

Trying 10.0.2, I will get back to you. Also, I tried it on my work laptop (mac) as well. It had issues as well. I will try to share the log on it as well.

@frankcalise Same errors on 10.0.2. I think it's in total 3 files places:

WelcomeScreen.tsx
App.tsx
Src/app.tsx

I hope this helps to resolve for me and others.

Thanks that is helpful, it seems to be related to removing the demo application for some reason - will look into it

:tada: This issue has been resolved in version 10.0.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Updated atten_results_timeout to 850

This PR is closed in detriment of PR https://github.com/SwitchEV/pyslac/pull/30


support 'echo_pool' option when creating the engine.

I would like to add support for turning on the 'echo_pool' option when creating the engine.
http://docs.sqlalchemy.org/en/rel_0_9/core/engines.html#sqlalchemy.create_engine.params.echo_pool

Mind giving this a rebase?

Thanks for contributing and sorry it's taken so long to get you a reply.  This will be supported by https://github.com/pallets/flask-sqlalchemy/pull/684 which I hope to get merged and released soon.


/ping Controller does not hit

Framework version: 1.0
Implementations: Jersey / Spring / Spring Boot / Spark: Spring Boot

Scenario
I download the code given by you for spring boot and deploy on Lambda.
When I call that Lambda function using AWS API Gateway it works
(https://.execute-api.us-east-1.amazonaws.com/testStage/myLambda)
, ie. spring boot server starts but when I hit the URL (https://.execute-api.us-east-1.amazonaws.com/testStage/ping)  to call  /ping controler it does not work.
it shows
{"message":"Missing Authentication Token"}
Please help to resolve this. Thanks
Expected behavior
Should call /ping controller
Actual behavior
it shows error
{"message":"Missing Authentication Token"}
Steps to reproduce
Full log output
does not print logs

Hey @utsavsohal, did you deploy with the SAM template? What do you see in the CloudWatch Lambda logs? by default the stage published by SAM is prod.

Hey @SAPessi,
Thanks For the Reply,
I checked the SAM(sam.yml) details then I setup the API gateway with  "Prod" as stage name.
Then I Hit the URL : https://{API_ID}.execute-api.us-east-1.amazonaws.com/Prod/ping but it
is still inaccessible as it is showing {"message":"Missing Authentication Token"}.
Please Check the API Details:
Invoke URL: https://{API_ID}.execute-api.us-east-1.amazonaws.com/Prod/abc (To invoke Lambda and start the Spring Boot container and
it works fine if I check the log it shows the Spring Boot Logs)
Stage: Prod
Security: NONE
Method: ANY
Resource path: /abc
API name: zzz
Authorization: NONE

The {"message":"Missing Authentication Token"} likely means that API Gateway cannot find the resource/method you are trying to call. The call never hits your Lambda function and therefore it is not something that we can fix in this framework.
If you have used the SAM template to deploy the API, check the Outputs tab of the CloudFormation stack in the AWS console, the full API endpoint to call the ping method should be displayed there.


Fix text load index store and get

When using several WAS_Text_Load_Line_From_File at the same time, the index value of the current line is overwritten by each next WAS_Text_Load_Line_From_File. As a result, the index value is always equal to that specified in the parameters.

Thanks for the patch!


Doesn't build due to mint changes

Looks like a change to mint has broken building:
% go get -u github.com/lucas-clemente/quic-go
go: finding golang.org/x/crypto/hkdf latest
go: finding golang.org/x/crypto/curve25519 latest
go: finding golang.org/x/crypto latest
go: downloading golang.org/x/crypto v0.0.0-20190228161510-8dd112bcdc25
go: extracting golang.org/x/crypto v0.0.0-20190228161510-8dd112bcdc25
go: finding github.com/lucas-clemente/quic-go-certificates latest
go: finding github.com/bifurcation/mint latest
go: finding github.com/lucas-clemente/aes12 latest
go: finding github.com/cheekybits/genny/generic latest
go: finding golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a
# github.com/lucas-clemente/quic-go/internal/crypto
go/pkg/mod/github.com/lucas-clemente/quic-go@v0.10.1/internal/crypto/key_derivation.go:46:37: cs.KeyLen undefined (type mint.CipherSuiteParams has no field or method KeyLen)
go/pkg/mod/github.com/lucas-clemente/quic-go@v0.10.1/internal/crypto/key_derivation.go:47:35: cs.IvLen undefined (type mint.CipherSuiteParams has no field or method IvLen)

We’re not using mint any more.

I am having the exact same issue:
go get
go: extracting github.com/lucas-clemente/quic-go v0.10.1
go: extracting github.com/lucas-clemente/aes12 v0.0.0-20171027163421-cd47fb39b79f
go: extracting github.com/lucas-clemente/quic-go-certificates v0.0.0-20160823095156-d2f86524cced
# github.com/lucas-clemente/quic-go/internal/crypto
../../.go/pkg/mod/github.com/lucas-clemente/quic-go@v0.10.1/internal/crypto/key_derivation.go:46:37: cs.KeyLen undefined (type mint.CipherSuiteParams has no field or method KeyLen)
../../.go/pkg/mod/github.com/lucas-clemente/quic-go@v0.10.1/internal/crypto/key_derivation.go:47:35: cs.IvLen undefined (type mint.CipherSuiteParams has no field or method IvLen)

To be specific: Building the example with Go modules does not work at all anymore:
$ go version
go version go1.12 linux/amd64

$ wget https://raw.githubusercontent.com/lucas-clemente/quic-go/v0.10.1/example/echo/echo.go
// ...
Saving to: ‘echo.go’

$ go mod init test123
go: creating new go.mod: module test123

$ go get
go: extracting github.com/lucas-clemente/quic-go v0.10.1
go: finding github.com/lucas-clemente/aes12 latest
go: finding github.com/bifurcation/mint latest
go: extracting github.com/lucas-clemente/aes12 v0.0.0-20171027163421-cd47fb39b79f
go: finding github.com/lucas-clemente/quic-go-certificates latest
go: extracting github.com/lucas-clemente/quic-go-certificates v0.0.0-20160823095156-d2f86524cced
go: finding github.com/cheekybits/genny/generic latest
go: finding golang.org/x/crypto/hkdf latest
go: finding golang.org/x/crypto/curve25519 latest
go: finding golang.org/x/crypto latest
# github.com/lucas-clemente/quic-go/internal/crypto
../../.go/pkg/mod/github.com/lucas-clemente/quic-go@v0.10.1/internal/crypto/key_derivation.go:46:37: cs.KeyLen undefined (type mint.CipherSuiteParams has no field or method KeyLen)
../../.go/pkg/mod/github.com/lucas-clemente/quic-go@v0.10.1/internal/crypto/key_derivation.go:47:35: cs.IvLen undefined (type mint.CipherSuiteParams has no field or method IvLen)

Yes. If I clone the repo and build, it works, even with modules enabled -- though it has to migrate the project to modules first. But if I use go get, or it gets fetched as a dependency for something else (e.g. caddy) it doesn't build.

Caddy uses a vendored version of this library. When / If Caddy wants to switch to Go mod, I’ll be happy to cut a new release for that from the gquic branch.


Allow decl_error to implement From<frame_system::Error>

Fix https://github.com/paritytech/substrate/issues/4384
decl_error now accept a new optional line, impl_from_frame_system($frame_system) and if this line is given then it crate 3 new variants. and also implement From<frame_system::Error>.
Note: This PR is controversial, see related issue.
Also better to use an attribute: #[impl_from_frame_system($(frame_system)]
CC @shawntabrizi

So, from any module, I could write:
let sender = ensure_signed(origin)?;

And it would just work?

Yes

implemented using attributes

yes

#[substrate(impl_from(frame_system))] is bit missleading to me, otherwise there is
#[substrate(from_frame_system(frame_system))], or
#[impl_from_frame_system(frame_system))]

@xlc @thiolliere @bkchr
We decided to not merge this in, and instead just use as_str for now. Should hope to get a better error story in the future.


join network from anoma-network-config GH releases

replaces #601. Depends on #616 and https://github.com/heliaxdev/anoma-network-config/pull/4

force pushed this for our release candidate


What this mean?

../results/scienceqa/chameleon_chatgpt_minitest.json
Result file exists: ../results/scienceqa/chameleon_chatgpt_minitest.json
Count: 100, Correct: 44, Wrong: 56

Hello,
It means that the experiment with identical arguments has already been run, and the results can be found in the file located at ../results/scienceqa/chameleon_chatgpt_minitest.json.
The script subsequently displays the following statistics:

Count: 100: A total of 100 examples were processed.
Correct: 44: Out of these, 44 examples had accurate predictions.
Wrong: 56: Conversely, 56 examples had incorrect predictions.

soooo.....that's what your run.py does. cool.
You should write (or get Chameleon LLM to write) a tutorial on how to get this thing running. dotenv etc. so we can do something special with it.
Write it for beginners like me. I had to get gpt-4 to tell me how to put in all the dotenv stuff because i know nothing...
Maybe you're not interested, and believe newbs can look elsewhere, but it would be cool as your project looks promising. Thanks for making it.

Hi @ogoflowgo , I was wondering where did you find this file: ../results/scienceqa/chameleon_chatgpt_minitest.json?


feat: allow changing iconButtonFactor

Pull Request
Description
This PR adds a new field to QuillToolbarBaseButtonOptions for the icon button factor, which defaults to the existing kIconButtonFactor constant.
The new version of flutter_quill has a kIconButtonFactor which is inconsistent with the rest of my (non-Quill) buttons, so this PR allows me to change the icon button factor from 1.77 to 1.6.
Features

Add a new field to QuillToolbarBaseButtonOptions for the icon button factor, which defaults to the existing kIconButtonFactor constant.

Additional notes

Suggestions
We could also change the default kIconButtonFactor to 1.6 which matches other default Flutter buttons better.
Checklist

[x] I have added/updated relevant documentation
[X] I have tested these changes locally.
[X] I have followed the code style and guidelines.
[x] I have updated CHANGELOG.md with my changes in the next section
[x] I have run `dart format .`` on the project
[x] I have run dart fix --apply on the project
[x] I have run flutter test and flutter analyze and it passed successfully
[x] I have run ./before-push.sh and everything is fine

@freshtechtips actually there is one who knows the repo very well

@freshtechtips actually there is one who knows the repo very well

Glad to hear that. I wasn't expecting a new pull request

Just one tiny little thing, did you passed that assign that new parameter to the new created button options in the childBuilder on the buttons? because otherwise everyone that is using the childBuilder will get invalid options settings

Just one tiny little thing, did you passed that new parameter to the newly created button options in the childBuilder on the buttons? because otherwise everyone that is using the childBuilder will get invalid options settings

Good catch, let me add that

Just one tiny little thing, did you passed that new parameter to the newly created button options in the childBuilder on the buttons? because otherwise everyone that is using the childBuilder will get invalid options settings

Good catch, let me add that

You don't have to do it if you want to merge the pull request now,
we can do it later and by later I mean today or tomorrow and not delaying forever
but that is up to you
In both cases we will do it correctly

Seeing as tests are passing, I'll remove the dependency_override which will probably make tests fail. This will of course resolve itself when 8.3.0 is published to pub.dev

Seeing as tests are passing, I'll remove the dependency_override which will probably make tests fail. This will of course resolve itself when flutter_quill: ^8.3.0 and flutter_quill_extensions: ^0.6.5 are published to pub.dev

Correct, but there is a better way to do it, using pubspec.yaml
Please take a look at the contributing page
You will find how to use the disable and enable local development
This way, we don't have to touch the pubspec.yaml in order to test the changes

I think we are ready to merge, @singerdmx what do you say?

LGTM

@adil192 Let me know when you are ready to merge


Use the cifmw venv to run VA validations

In zuul VA validation jobs we are installing via setup_molecule the cifmw collection and dependencies but we are using the zuul executor venv, leading to missing deps like custom filters or jmespath missing.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/approve


hercules-ci-{agent,cnix-expr}: Force use of propagated boehmgc

This was already in effect, but only by coincidence. A direct
boehmgc could presumably be added implicitly in the generated
code by fixing the pkg-config to nixpkgs mapping.
This commit should counteract that, or, in case of a rename,
cause an evaluation error so that it can be fixed, instead of
building and crashing at runtime.

Motivation for this change
Make hercules-ci-cnix-expr and hercules-ci-agent packages robust against a potentially disastrous cabal2nix improvement.
bdw-gc = null in the generated hackage-packages code is technically a bug, but required for nix bindings to work correctly.
Things done

Built on platform(s)

[x] should produce no rebuilds
[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Do you mind opening an issue about the incorrect handling of boehm-gc in cabal2nix as well? Quite confused by the appearance of bdw-gc…

@sternenseemann done: https://github.com/NixOS/cabal2nix/issues/529
I don't think we have an actual use case for it though.

Well, I've accidentally learned that the bdw-gc dependency isn't necessary in the cabal file either. I'm removing the bdw-gc reference in 0.9, so this change won't be necessary (and need to be reverted). I'm glad we can keep it simple, which is the best outcome. Sorry for the noise.


Added :default param for I18n.localize

When using I18n.l, there are guards needed when a date is potentially nil:
date && I18n.l(date)
date ? I18n.l(date) : 'present'

This change will return the default when passed in:
I18n.l(date, default: nil)
I18n.l(date, default: 'present')

Looks good to me, and a sensible alternative to what was discussed in #294.
I've applied this patch to a branch called pr-251, just to see if the Travis tests will pass there. If they do, then I will merge this to master.
Thanks for your contribution!

I notice a 2 year gap between this code being written and committed.. what's the timeline like for the next release?

Middle/end of January is when I plan on doing the 0.8.0 release. Once things are less crazy

On 8 Dec. 2016, at 14:07, Kira McLean<EMAIL_ADDRESS>wrote:
I notice a 2 year gap between this code being written and committed.. what's the timeline like for the next release?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Awesome. Is there a way to know what issues are blocking release? I'll have some free time over the next few weeks and would be happy to help.

Take a look at the 0.8.0 milestone on GitHub. If you've got time to help; that would be appreciated.
I'm happy to release 0.8.0 straight off master at the moment, but doing a release this close to the end of the year and when that release effects so many Rails versions... probably not a great idea.

On 9 Dec. 2016, at 06:48, Kira McLean<EMAIL_ADDRESS>wrote:
Awesome. Is there a way to know what issues are blocking release? I'll have some free time over the next few weeks and would be happy to help.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Documentation fixes

Thank you!
Thank you for your contribution.
Please make sure that your submission includes the following:
Must

[ ] The code compiles without errors or warnings.
[x] All examples work.
[x] cargo fmt was run.
[ ] Your changes were added to the CHANGELOG.md in the proper section.
[x] You updated existing examples or added examples (if applicable).
[x] Added examples are checked in CI

Nice to have

[x] You add a description of your work to this PR.
[x] You added proper docs for your newly added features and code.

This PR is taken from #666 and fixes broken links and other warnings rustdoc may dislike. I've added the eh1 feature to the rustdoc checks where it makes sense, so that the CI will not generate warnings, even though that is largely ineffective.
The PR also changes efuse docs a bit, to both improve readability and to fix the markdown syntax.

CI failure is spurious: failed to get 200 response from https://crates.io/api/v1/crates/esp32s2/0.15.0/download, got 503
I don't think this PR warrants a changelog entry so that's also red.


First real implementation of GitRelation

This PR put all previous work together:

We create a generic GitRelation that depending of the table name provided, it is created with a specific schema and a specific metadata iterator.
Fix some typos on Schema
Fix some typos on implicit methods
Fix bug when a reference is not pointing to a commit

Blobs table is missing because is mandatory filtering to provide it.

Merge https://github.com/src-d/spark-api/pull/21 first


Cannot use package without authentication

npm ERR! code E401
npm ERR! 401 Unauthorized - GET https://npm.pkg.github.com/@nfdi4health%2fsemlookp-widgets - unauthenticated: User cannot be authenticated with the token provided.

GitHub Packages only supports authentication using a personal access token (classic).
https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry


Fix file creation

If a data bag is updated, the resulting files are not updated
This fixes the issue

@shortdudey123 thanks again =)


Restrict 'other' permissions for chef-server.rb.

This PR removes all permissions for 'other' on /etc/opscode/chef-server.rb. This file can hold sensitive data such as the LDAP bind_password, so it should not be accessible by anyone other than owner/group (both root in this case).

:+1: looks good

:+1: Let's ge this in before our next release.

@itmustbejj Do you mind rebasing against master?  Once that is done I'll merge this.

@itmustbejj I went to rebase this myself and had a thought.  Do we want to fix this for existing installs as well?  We can potentially do this in this recipe: https://github.com/chef/chef-server/blob/master/omnibus/files/private-chef-cookbooks/private-chef/recipes/config.rb
Thoughts @chef/chef-server-maintainers

@stevendanna Rebased and added a commit in the config.rb you mentioned above for existing config files.


can we do parallel execution feature using Cucumber-mink? If so, how?

Not really, or maybe by launching several browser. You can do it manually thought.


cannot import name 'ColPali' from 'transformers'

---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
Cell In[5], line 1
----> 1 from transformers import ColPali

ImportError: cannot import name 'ColPali' from 'transformers' (/home/usr/miniconda3/envs/torch_241_cu118/lib/python3.10/site-packages/transformers/__init__.py)
Same error on transformers==4.45 and 4.46

Take a look at the README, you should import it from colpali_engine.models, not from transformers.

Ideally ,the model card README in HF should have been updated as well.

Then ideally ,the model card README in HF should have been updated as well.

Can you please send me the url of the mentioned model card? If it turns out it is outdated, I will fix it.

1.https://huggingface.co/vidore/colpali-v1.2-hf-deprecated


Make the nginx log directory owned by zulip

This is required to make log2zulip not error out when reading the nginx
error.log.

Merged, thanks @zbenjamin !


docs: Don't include extra string example

As discussed in
https://github.com/prql/prql/commit/acfe4b3c14a930a4ff3652be3c50d1d230a2ae51
(also some gentle reformatting)

I agree the triple double-quote example is too clever by half. It might be worth mentioning on the Strings page.
Good links to Assigns & Aliases
I see you have re-enabled Prettier. My monitor's not wide enough to see the full table - that's why I experimented with turning it off.
But... LGTM. Ship it! Thanks.


[Bug]: "Sorry, but your account doesn't have access" error is displayed In the Edit mode of the App

Is there an existing issue for this?

[X] I have searched the existing issues

Description
"Sorry, but your account doesnt have access" error is displayed In the Edit mode of the App

Steps To Reproduce

Login as admin
Create. anew app
in home page create a crud page now
Now add new db
from active tab
Create a new crud page
The error is displayed when the page got created

Public Sample App
No response
Issue video log
No response
Version
release

API is returning blank array for userPermissions when you click on Generate page from Datasources active tab:
API: https://release.app.appsmith.com/api/v1/layouts/:layoutId/pages/:pageId?applicationId=:appId

@nsarupr @trishaanand


Loading game from file

doesn't work if the human player does not write a name
maybe we have to enter a base name for player that can be changed
observation  agent seems to play slower after loading

doesn't work if the human player does not write a name maybe we have to enter a base name for player that can be changed observation agent seems to play slower after loading

This is a good idea, can you add this feature in this branch, so the players are automatically called player 1 and player 2 if the name boxes are left empty


KMDUMPISA environment variable still valid?

I'm building a HIP application with ROCm as backend (ver 3.9) and I'm trying to dump the ISA of the kernels by having KMDUMPISA environment variable set during build (via export KMDUMPISA=1), but that seems to be ignored. No xxx.isa files are produced.
Is this environent variable still valid in the latest ROCm releases? Is there any alternative option for ISA dumps?
The hipconfig output follows in case that helps:
HIP version  : 3.9.20412-6d111f85

== hipconfig
HIP_PATH     : /opt/rocm/hip
ROCM_PATH    : /opt/rocm
HIP_COMPILER : clang
HIP_PLATFORM : hcc
HIP_RUNTIME  : ROCclr
CPP_CONFIG   :  -D__HIP_PLATFORM_HCC__=  -I/opt/rocm/hip/include -I/opt/rocm/llvm/bin/../lib/clang/12.0.0 -I/opt/rocm/hsa/include -D__HIP_ROCclr__

== hip-clang
HSA_PATH         : /opt/rocm/hsa
HIP_CLANG_PATH   : /opt/rocm/llvm/bin
clang version 12.0.0 (/src/external/llvm-project/clang 60f39e2924d51c1e8606f2135f95e9047fb1da5d)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /opt/rocm/llvm/bin
LLVM (http://llvm.org/):
  LLVM version 12.0.0git
  Optimized build.
  Default target: x86_64-unknown-linux-gnu
  Host CPU: znver2

  Registered Targets:
    amdgcn - AMD GCN GPUs
    r600   - AMD GPUs HD2XXX-HD6XXX
    x86    - 32-bit X86: Pentium-Pro and above
    x86-64 - 64-bit X86: EM64T and AMD64
hip-clang-cxxflags : hipcc-cmd: /opt/rocm/llvm/bin/clang++  -L/opt/rocm/hip/lib -O3 -lgcc_s -lgcc -lpthread -lm  --cxxflags -Wl,--enable-new-dtags -Wl,--rpath=/opt/rocm/hip/lib:/opt/rocm/lib -lamdhip64  -L/opt/rocm/llvm/bin/../lib/clang/12.0.0/lib/linux -lclang_rt.builtins-x86_64
-D__HIP_ROCclr__ -std=c++11 -isystem /opt/rocm-3.9.0/llvm/lib/clang/12.0.0/include/.. -isystem /opt/rocm/hsa/include -D__HIP_ROCclr__ -isystem /opt/rocm/hip/include -D__HIP_ARCH_GFX1012__=1  -D__HIP_ARCH_GFX803__=1  -O3
hip-clang-ldflags  : hipcc-cmd: /opt/rocm/llvm/bin/clang++  -L/opt/rocm/hip/lib -O3 -lgcc_s -lgcc -lpthread -lm  --ldflags -Wl,--enable-new-dtags -Wl,--rpath=/opt/rocm/hip/lib:/opt/rocm/lib -lamdhip64  -L/opt/rocm/llvm/bin/../lib/clang/12.0.0/lib/linux -lclang_rt.builtins-x86_64
 -L/opt/rocm/hip/lib -O3 -lgcc_s -lgcc -lpthread -lm

=== Environment Variables
PATH=/home/elias/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/rocm/bin:/opt/rocm/profiler/bin:/opt/rocm/opencl/bin:/opt/rocm/hip/bin
HIP_PRINT_ENV=1
HIP_PATH=/opt/rocm/hip
HIPCC_VERBOSE=1

== Linux Kernel
Hostname     : Neptune
Linux Neptune 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:        20.04
Codename:       focal

Thanks @ekondis for reaching out.
We are able to reproduce this issue and working with HIP team on this.
We will provide resolution soon.
Thank you.

Recommend to use -save-temps flag with hipcc while compiling.
for ex: /opt/rocm/hip/bin/hipcc -save-temps  bit_extract.cpp -o bit_extract

Thank you. -save-temps seems to work fine.
I suspected that switching from hcc would be the cause as I could not find it in the installation.

Thanks @ekondis
I will work with Documentation team for the modification of relevant information, if any.
Thank you.


Testing: When pushing and triggering a test, send the branch name with the test

When you push to the repo (from wherever) you're on a branch. Puppeteer will need to know what branch you're pushing to so that the new project it creates can pull from that branch. Therefore we need to get github to send that information to puppeteer.
Alternatively, the dev changes .env to reflect the name of the branch they're pushing to.
Alternatively, we could create a hook that edits .env to include the name of the current branch, but that isn't as modular.

We can probably do it using github.ref
https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#github-context

Closed by #86


MNTP index value converter + fixing issue in helper function

There was an issue with the TryGetPropertyIndexValue where we could still get a NullRef exception for some edge cases that is fixed now.
I also added a Index value converter for MNTP based on the name that use cache and db call when needed. As it can impact the database I left it outside of the list of default converters so people can decide to pick it or not. Tested in v10.

Hi, is there an opportunity to review my PR ? thank you. It looks like some checks are not successful but I do not believe it is related to my changes. Can someone re run them ?

Hi @giuunit ,
The integration comes with a set of default converters but we try to limit that as much as possible, allowing instead for users to register their own as detailed here (or replace one of the existing ones).
So I would recommend you register your SimpleMultinodeTreePickerIndexValueConverter on your side. Adding too many converters by default, for even more complex types in Umbraco, might not suit with everyone using the integration. So I think it's best to keep the scopes isolated.
I will release today patch versions with the fix for the ConverterExtensions helper.
Thank you,
Adrian

thats awesome thank you


Publishing 1.3.0 release

Does the 1.3.0 release is published ?
I can't find it by NPM.
Greetings.

v1.3.0 published.
https://www.npmjs.com/package/izitoast


Add Oshama scramble by t pazolite

Song Name
Oshama scramble
Artist Name
t pazolite
Source
Youtube
Youtube Link
yHgIYfNF8kY
Direct File Link
No response
Song ID
701013
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 44062068
Downloaded: No

accept


cifar10.train.npz or cifar10_train.npz

First: the setup
In the Readme, it is written to download the stats cifar10.train.npz.
If I download the pre-trained weights https://drive.google.com/file/d/1IhdFcdNZJRosi3XRT7-qNmiPGTuyuEXr/view?usp=sharing, containing the ./logs/DDPM_CIFAR10_EPS/flagfile.txt  there is the flag --fid_cache=./stats/cifar10_train.npz which is written in a different way. I guess the same file is meant.
Second: the computation of FID is slowly because running on CPU()
I don't get any FID because the FID calculation takes hours...

You are absolutely correct. Thank you very much for reporting this issue.
The flagfile.txt has been corrected and the compressed file of pre-trained weights has been re-uploaded.
Closing the issue now.


Create a group_vars directory into the project structure.

Resolves #28
Similar to the host_vars directory that we have, create a group_vars one for convenience to the users
@rajan-mis  I don't  think we should remove host_vars...  correct?

@whowutwut Thanks Victor.  i think for now we can keep host_vars directory as well . I am thinking to move complete inventory inside inventory directory like ,
inventory/host_vars
inventory/group_vars
inventory/hosts


API cleanup: /v1/domains/* returns Domain

Furthering API cleanup, we return plain pb.Domain objects from the /v1/domains/* URI rather than DomainInfo objects wrapped in GeDomainInfoResponse.

Codecov Report

Merging #886 into master will not change coverage.
The diff coverage is 40%.

@@           Coverage Diff           @@
##           master     #886   +/-   ##
=======================================
  Coverage   48.51%   48.51%
=======================================
  Files          34       34
  Lines        2360     2360
=======================================
  Hits         1145     1145
  Misses       1011     1011
  Partials      204      204

Impacted Files
Coverage Δ

core/monitor/monitor.go
0% <ø> (ø)
:arrow_up:

core/keyserver/keyserver.go
0% <0%> (ø)
:arrow_up:

core/adminserver/admin_server.go
49.43% <66.66%> (ø)
: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 7e2628b...04335b7. Read the comment docs.


alert saying app is damaged?

I keep getting this, after downloading from multiple browsers.
¯_(ツ)_/¯
I really appreciate you working on this, I love the design and am just excited to use it.

Read the website/readme, or look through the existing issues. This is a known issue and has been solved with a temporary workaround and the solution is right on the site above the fold
On Aug 27, 2016, 11:53 PM -0400, Cameron Alexander<EMAIL_ADDRESS>wrote:

I keep getting this, after downloading from multiple browsers.
¯_(ツ)_/¯
I really appreciate you working on this, I love the design and am just excited to use it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (https://github.com/devinhalladay/spotio/issues/20), or mute the thread (https://github.com/notifications/unsubscribe-auth/AB2F3WEI2KR6HdqEhGqUhI6PCvN8xwdpks5qkQZOgaJpZM4Ju1xB).

dang, I see it now. thank you and sorry for the spam.

Oh no! I'm sorry if I came across as salty haha, you caught me right when I had woken up. Thanks for closing the issue :) enjoy spotio! Make sure yore subscribed to the newsletter on the site because we have some major updates coming in the next few weeks
On Aug 28, 2016, 1:19 AM -0400, Cameron Alexander<EMAIL_ADDRESS>wrote:

Closed #20 (https://github.com/devinhalladay/spotio/issues/20).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (https://github.com/devinhalladay/spotio/issues/20#event-769896986), or mute the thread (https://github.com/notifications/unsubscribe-auth/AB2F3SkFXSd01KLECZdRxLnibqldpmazks5qkRpugaJpZM4Ju1xB).


[WIP] Use Sanity

DatoCMS had some limitations around repeated content that I didn't enjoy working around -- and the interface for repeated content left something to be desired. While lacking in other areas, Sanity has better support for those than any other solution I found, which for now outweighs the cons of switching. This is a site built primarily on repeatable content, after all (that's essentially all a recipe is).
TO-DO:

[x] convert API to use Sanity
[x] render fields as markdown
[x] update getStaticPaths & getStaticProps
[x] use static metadata for site titles & description
[x] update DatoCMS references to Sanity references (about page, README)
[x] support sections in recipe pages
[x] add equipment section to recipe pages
[x] ~homepage recent recipes always putting graham cracker crust first??~ (fixed itself 🤷🏼♂)
[x] update homepage with featured meal
[x] add support for meals

[x] add meals index page
[x] add meals button to header (maybe replace categories?)
[x] add meals link to footer
[x] add meal detail page

[x] ~replace remark with markdown-it, and use the superscript plugin for notes~ (do this later, if at all)
[ ] fix failing lighthouse build process

Lighthouse works locally. It works on other branches. It just doesn't work here. 🤔


Added new blocks, fixed old version of results blocks

added summary blocks which are created when you specify INPUTS YES in the [REPORT] section of an input file.

added a SWMM version checker as self.version, did not implement it

fixed result blocks for old version of report files

I'm pretty new to open source contributions so I'd appreciate the feedback, and I don't know how to write tests but I will try to learn and update your current tests.
Thanks for making this!

Coverage decreased (-7.7%) to 70.401% when pulling 636a83f5242e599e62e3845e7fe37c78ba347143 on mataslauzadis:master into d57c3ada8888b1dfa8060a23b361a0dfe43fa30e on lucashtnguyen:master.

@mataslauzadis thanks for this PR! Sorry it took so long for me to review -- I haven't engaged with this project in a while but it is back on my radar. Your contributions look great -- tests can come later!


Add the official readthedocs link to the sidebar of the project

What maintenance does this project need?
Hi all,
I just noticed, that the official documentation link is missing in the sidebar: pyflow-wellies
It would be beneficial to add this to the repository, too.
Kind regards,
Tobias
Organisation
No response

Done, thanks!


add new devices and tests

Pull Request Test Coverage Report for Build 1985

13 of 13 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1974:
0.0%

Covered Lines:
1108

Relevant Lines:
1108

💛  - Coveralls


Error:  ...File "json2csv.py", line 82 for k, val in row.items()})

Ok, I am either doing something wrong, or there is something wrong with the code :/.
I am literally testing the code by using the following as example.
"testfile.json"
{
  "nodes": [
    {"source": {"author": "Someone"}, "message": {"original": "Hey!", "Revised": "Hey yo!"}},
    {"source": {"author": "Another"}, "message": {"original": "Howdy!", "Revised": "Howdy partner!"}},
    {"source": {"author": "Me too"}, "message": {"original": "Yo!", "Revised": "Yo, 'sup?"}}
  ]
}

Then I am creating the outline file with the following piece of code
    python gen_outline.py --collection nodes /home/irving/workspace/json2csv_2/testfile.json -o /home/irving/workspace/json2csv_2/testfile_outline.json

Granted the results of "testfile_outline.json" are not the same as what it is on the "README.md", but I kept on going.
  So I type the following piece of code.
    python json2csv.py /home/irving/workspace/json2csv_2/testfile.json /home/irving/workspace/json2csv_2/testfile_outline.json -o /home/irving/workspace/json2csv_2/testfile.csv

This give me the following error
    File "json2csv.py", line 82
    for k, val in row.items()})
    ^
    SyntaxError: invalid syntax

What am I doing wrong?  Thoughts?
(By the way I did test the outline JSON from "README.md" and got same results)

Which version of Python are you using? I wrote this targeting python2.7

I think I might off missed that on the documentation, since I am running
it on python 2.6.6.
I'll upgrade to 2.7 and see if the problem goes away.
Thank you,
Irving Duran
On 10/08/2015 10:01 AM, F. Gabriel Gosselin wrote:

Which version of Python are you using? I wrote this targeting python2.7
—
Reply to this email directly or view it on GitHub
https://github.com/evidens/json2csv/issues/15#issuecomment-146572129.

Upgraded to python 2.7 and it works like a charm.  Thanks for the share!


Add support for event streaming

As a developer, I need to be able to receive status updates from Husqvarna so I don’t need to poll their web api for changes to the mower.
I need a client setup that can handle event based callbacks based on the event type.
https://developer.husqvarnagroup.cloud/apis/Automower+Connect+API#/websocket

The streaming client needs to be applied to the AutomowerAccessory class so the status updates can be applied directly to the characteristics.
Design Considerations

Need to add a start/stop method to control the streaming client.
Need a mechanism to handle liveness checks on a secondary thread
Need event callback handlers based on the event type (battery updated/state changed)

The event stream appears to be at the account level and not at the mower level.
That would mean the stream must be on the platform, with the data being routed into the accessory instance based on the id.
The platform already registers all the mowers on the account, which the accessory.context.mowerId should match the id in the event data.


Update stream-analytics-introduction.md

@JasonWHowell : Thanks for your contribution! The author, @jseb225, has been notified to review your proposed change.


Can't access to my neato Connected

Hi,
I just start to play with your API, but I can't use any robot method. There is no problem to retreive my robot throught my credentials, but when I want to run a robot method (ie: robot.get_current_state) I get the following error message
Traceback (most recent call last):
File "sample/sample.py", line 13, in
print("State:\n", robot.state)
File "/usr/local/lib/python3.4/dist-packages/pybotvac-0.0.1-py3.4.egg/pybotvac/robot.py", line 94, in state
return self.get_robot_state().json()
File "/usr/local/lib/python3.4/dist-packages/pybotvac-0.0.1-py3.4.egg/pybotvac/robot.py", line 70, in get_robot_state
return self._message({'reqId': "1", 'cmd': "getRobotState"})
File "/usr/local/lib/python3.4/dist-packages/pybotvac-0.0.1-py3.4.egg/pybotvac/robot.py", line 43, in _message
headers=self._headers)
File "/usr/local/lib/python3.4/dist-packages/requests/api.py", line 110, in post
return request('post', url, data=data, json=json, **kwargs)
File "/usr/local/lib/python3.4/dist-packages/requests/api.py", line 56, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/local/lib/python3.4/dist-packages/requests/sessions.py", line 461, in request
prep = self.prepare_request(req)
File "/usr/local/lib/python3.4/dist-packages/requests/sessions.py", line 394, in prepare_request
hooks=merge_hooks(request.hooks, self.hooks),
File "/usr/local/lib/python3.4/dist-packages/requests/models.py", line 298, in prepare
self.prepare_auth(auth, url)
File "/usr/local/lib/python3.4/dist-packages/requests/models.py", line 500, in prepare_auth
r = auth(self)
File "/usr/local/lib/python3.4/dist-packages/pybotvac-0.0.1-py3.4.egg/pybotvac/robot.py", line 108, in call
msg='\n'.join([self.serial.lower(), date, request.body]).encode('utf8'),
TypeError: sequence item 2: expected str instance, bytes found

Had the same issue, fixed it with this :
msg='\n'.join([self.serial.lower(), date, request.body.decode('utf8')]).encode('utf8')
in robot.py
Did not search for another, maybe cleaner fix, since I didn't had the time to play more with the API.

a bit better but I think the problem is coming from a change on Neato's server as I now have the following message:
rob.get_schedule()
<Response [200]>
rob.get_robot_state()
<Response [200]>

No, you may have another issue, I got proper response from neato.

ok I got it get_robot_state do not return the state, we need to use the property state to get it:

robot.state
{'availableCommands': {'resume': False, 'goToBase': False, 'stop': False, 'pause': False, 'start': True}, 'availableServices': {'houseCleaning': 'basic-1', 'manualCleaning': 'basic-1', 'schedule': 'basic-1', 'spotCleaning': 'basic-1', 'easyConnect': 'basic-1'}, 'meta': {'firmware': '2.0.0', 'modelName': 'BotVacConnected'}, 'data': {}, 'details': {'charge': 96, 'isDocked': True, 'isCharging': False, 'dockHasBeenSeen': False, 'isScheduleEnabled': False}, 'result': 'ok', 'error': 'ui_alert_invalid', 'action': 0, 'state': 1, 'cleaning': {'category': 2, 'mode': 2, 'spotWidth': 0, 'modifier': 1, 'spotHeight': 0}, 'reqId': '1', 'version': 1}

or self.get_robot_state().json()

CLosing issue


Disconnected from device

E/flutter (29833): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: MissingPluginException(No implementation found for method permit on channel method_channel)
E/flutter (29833): #0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:332:7)

same happened with me

the permit method isn't part of the package. the PERMIT method was created in the example project just to help with handling permissions instead of installing another package. it implementation will only work for the example project and if you look inside the MainActivity.kt in the android folder in the example folder, you will see its implementation and how it is handled.
For a real project, please use a package like permission_handler to request for permissions.


Frozen array in reactive breaks list rendering

Version
3.0.0-alpha.9
Reproduction link
https://codesandbox.io/s/hopeful-newton-su9mz
Steps to reproduce

Create frozen array
Use that array as a value in reactive
Pass that value as a prop in render function

What is expected?
Frozen arrays should be supported in lists
What is actually happening?
Rendering breaks

I did some poking around and will add that rendering only breaks when the frozen array contains objects. If it contains primitives it (from what I can tell) works as expected.