v5.1.0 - Keep not generating JDL entities in Ionic projects

Hi folks,
It is linked to my previous created error:
https://github.com/oktadeveloper/generator-jhipster-ionic/issues/268
I did have expectation that jhipster-ionic v5.1.0 would fix the error linked above, but the results are the same.
There is only an additional message now after importing the JDL entities using " yo jhipster-ionic:import-jdl blog.jdl ":
><EMAIL_ADDRESS>prettier C:\Users\Mauricio\Documents\JHipsterProjects\jhipster-splited2\mobile
> prettier --write "{,src/**/}*.{js,json,html,md,ts,css,scss,yml}" --loglevel silent

But the entities folder keeps empty:
\mobile\src\app\pages\entities (master -> origin)
λ tree /f
Folder PATH listing
C:.
    entities.module.ts
    entities.page.html
    entities.page.scss
    entities.page.spec.ts
    entities.page.ts

No subfolders exist

And the screenshot of my app is the same:

Backend Details:
`--<EMAIL_ADDRESS>

JHipster configuration, a .yo-rc.json file generated in the root folder

.yo-rc.json file

{
  "generator-jhipster": {
    "promptValues": {
      "packageName": "com.litinow"
    },
    "jhipsterVersion": "6.8.0",
    "applicationType": "monolith",
    "baseName": "backend",
    "packageName": "com.litinow",
    "packageFolder": "com/litinow",
    "serverPort": "8080",
    "authenticationType": "oauth2",
    "cacheProvider": "ehcache",
    "enableHibernateCache": true,
    "websocket": false,
    "databaseType": "sql",
    "devDatabaseType": "h2Disk",
    "prodDatabaseType": "mariadb",
    "searchEngine": false,
    "messageBroker": false,
    "serviceDiscoveryType": false,
    "buildTool": "gradle",
    "enableSwaggerCodegen": false,
    "embeddableLaunchScript": false,
    "creationTimestamp":<PHONE_NUMBER>750,
    "testFrameworks": [],
    "jhiPrefix": "jhi",
    "entitySuffix": "",
    "dtoSuffix": "DTO",
    "otherModules": [],
    "enableTranslation": false,
    "clientPackageManager": "npm",
    "blueprints": [],
    "skipClient": true
  }
}

JDL for the Entity configuration(s) entityName.json files generated in the .jhipster directory

JDL entity definitions

entity Blog {
  name String required minlength(3),
  handle String required minlength(2)
}
entity Entry {
  title String required,
  content TextBlob required,
  date Instant required
}
entity Tag {
  name String required minlength(2)
}
relationship ManyToOne {
  Blog{user(login)} to User,
  Entry{blog(name)} to Blog
}
relationship ManyToMany {
  Entry{tag(name)} to Tag{entry}
}

paginate Entry, Tag with infinite-scroll

Environment and Tools
java version "11.0.6" 2020-01-14 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.6+8-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.6+8-LTS, mixed mode)
git version 2.17.1.windows.2
node: v12.16.1
npm: 6.13.4
yeoman: 3.1.1
yarn: 1.22.0
Docker version 19.03.5, build 633a0ea
docker-compose version 1.25.4, build 8d51620a
Ionic App Details:
+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>deduped

cat: no such file or directory: .yo-rc.json
JHipster configuration, a .yo-rc.json file generated in the root folder

.yo-rc.json file

JDL for the Entity configuration(s) entityName.json files generated in the .jhipster directory

JDL entity definitions

entity Blog {
  name String required minlength(3),
  handle String required minlength(2)
}
entity Entry {
  title String required,
  content TextBlob required,
  date Instant required
}
entity Tag {
  name String required minlength(2)
}
relationship ManyToOne {
  Blog{user(login)} to User,
  Entry{blog(name)} to Blog
}
relationship ManyToMany {
  Entry{tag(name)} to Tag{entry}
}

paginate Entry, Tag with infinite-scroll

To create the ionic app
In a folder outside of the backend app:
       yo jhipster-ionic
             App name: mobile
             Backend app path: \backend

After the app creation:
       cd \mobile
       yo jhipster-ionic:import-jdl blog.jdl

The final folder structure is:
    \Projects
           \backend
                  -- Backend app
            \mobile
                   -- Ionic app

Operational System
Windows 10

Well, that sucks. I'm not sure what's causing this problem now. I was able to reproduce it.
yo jhipster-ionic:import-jdl ../backend/entities.jdl
INFO! The JDL is being parsed...
warn: An Entity name 'User' was used: 'User' is an entity created by default by JHipster. All relationships toward it will be kept but any attributes and relationships from it will be disregarded.
INFO! Found entities: Blog, Entry, Tag.
INFO! The JDL has been successfully parsed.
INFO! Generating 3 entities.

Found the .jhipster/Blog.json configuration file, entity can be automatically generated!

The entity Blog is being updated.

Found the .jhipster/Entry.json configuration file, entity can be automatically generated!

The entity Entry is being updated.

Found the .jhipster/Tag.json configuration file, entity can be automatically generated!

The entity Tag is being updated.

><EMAIL_ADDRESS>prettier /Users/mraible/mobile
> prettier --write "{,src/**/}*.{js,json,html,md,ts,css,scss,yml}" --loglevel silent

Execution time: 6 s.

After it finishes, no files are created.
$ ll src/app/pages/entities
total 40
-rw-r--r--  1 mraible  staff   876B Mar 11 19:17 entities.module.ts
-rw-r--r--  1 mraible  staff   423B Mar 25 12:13 entities.page.html
-rw-r--r--  1 mraible  staff   110B Mar 11 19:17 entities.page.scss
-rw-r--r--  1 mraible  staff   1.0K Mar 11 19:17 entities.page.spec.ts
-rw-r--r--  1 mraible  staff   502B Mar 25 12:13 entities.page.ts

Can you confirm, that the .jhipster folder inside mobile is already populated.
If you remove it and then re-run, the files will be created.
There is a jhipster-core (enabled by default) option that doesn't returns the entity if it didn't changed.
This will make exportedEntities empty and the entity generator will fail.

@mshima figured out what the problem was. Ionic4J is reading your JHipster app's .yo-rc.json and setting skipClient: true - and therefore skips the generation of files. As a temporary workaround, you can remove this property in backend/.yo-rc.json, run import-jdl in Ionic, then add it back in.

I can confirm it now, the workaround worked as expected.
Cheers :)

Sadly, I found a bad behavior linked to this workaround.

To generate it, just do the creation of a backend app skipping the client, set it to use keycloak and do not import any JDL file.
After that, do the creation of an ionic app and test its authentication, everything should work.
Now, import the JDL in the backend app. Do perform the workaround and import the JDL in ionic app.
It will cause the reported issue. The ionic app will fail to any authentication using keycloak.
I tried upgrade ionic app to use jhipster 6.8.0 with no success. Using jhipster 6.7.1 does not work as well.
Kind regards,

@MauricioPenteado This happens when you start your Ionic app and your backend is not running. Clear your local storage for your app and try again (or use an incognito window) with your backend running. I just tried it and it works for me.

Here's the logic that handles grabbing the config from the JHipster backend.
private async addConfig() {
  const scopes = 'openid profile offline_access';
  const redirectUri = this.onDevice() ? 'dev.localhost.ionic:/callback' : 'http://localhost:8100/implicit/callback';
  const logoutRedirectUri = this.onDevice() ? 'dev.localhost.ionic:/logout' : 'http://localhost:8100/implicit/logout';
  const AUTH_CONFIG_URI = 'http://localhost:8080/api/auth-info';

  if (await this.storage.getItem(AUTH_CONFIG_URI)) {
    this.authConfig = JSON.parse(await this.storage.getItem(AUTH_CONFIG_URI));
    await this.storage.removeItem(AUTH_CONFIG_URI);
  } else {
    // try to get the oauth settings from the server
    this.requestor.xhr({ method: 'GET', url: AUTH_CONFIG_URI }).then(
      async (data: any) => {
        console.log('data', data);
        this.authConfig = {
          identity_client: data.clientId,
          identity_server: data.issuer,
          redirect_url: redirectUri,
          end_session_redirect_url: logoutRedirectUri,
          scopes,
          usePkce: true
        };
        await this.storage.setItem(AUTH_CONFIG_URI, JSON.stringify(this.authConfig));
      },
      error => {
        console.error('ERROR fetching authentication information, defaulting to Keycloak settings');
        console.error(error);
        this.authConfig = {
          identity_client: 'web_app',
          identity_server: 'http://localhost:9080/auth/realms/jhipster',
          redirect_url: redirectUri,
          end_session_redirect_url: logoutRedirectUri,
          scopes,
          usePkce: true
        };
      }
    );
  }
}

If you can think of any way to improve this code, please let me know.
The Ionic AppAuth example uses the environment to store configuration in, but I don't think you can dynamically set that.

FWIW, I released v5.1.1 today.

Well done folks!! This new version is working perfectly.
Matt many thanks for your attention. Your tips have helped me a lot to understand how to work with JHipster-Ionic.
The logic that handles grabbing the config from the JHipster backend described above is working beautiful.
I hope that soon I will be able to propose changes to the JHipster code helping further.
Cheers!


cannot write data from hive to clickhouse

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
cannot write data from hive to clickhouse

SeaTunnel Version
1.5.7
SeaTunnel Config
1

Running Command
1

Error Exception
cannot write data from hive to clickhouse

Flink or Spark Version
spark 1.5.7
Java or Scala Version
No response
Screenshots

Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct


Cacheable not work when use nullable datetime in where conditions

var now = DateTime.Now;
return _products
                .AsNoTracking()
                .Where(c => c.IsActive && c.ShowInWebSite && c.ProductImages.Any() && c.AmazingOfferId.HasValue &&
                            ((!c.AmazingOffer.StartDate.HasValue || c.AmazingOffer.StartDate.Value <= now)
                                                          && (!c.AmazingOffer.EndDate.HasValue || c.AmazingOffer.EndDate.Value >= now)))
                .OrderByDescending(c => c.RegDateTime)
                .Select(c => new ProductShowViewModel
                {
                    Product = c.ID,
                    Name = c.Name,
                    ProductImages = c.ProductImages.Select(pi => new ProductImagesPathViewModel { ImageID = pi.ID, ProductImagePath = pi.ImagePath }).ToList(),
                    Code = c.Code,
                    BrandName = c.Brand.Name,
                    SellingPrice = c.SellingPrice,
                    Discount = c.AmazingOffer.Discount,
                    ShortDescription = c.ShortDescription,
                    Sort = c.Sort,

                }).Cacheable().ToList();

when delete date time from where condition cacheable work properly

What doesn't work? It doesn't care about your LINQ query. It cares about the final produced SQL and its parameters.

There is no problem with execution and everything is done correctly but the cache is not done and information is taken from the table for each request.

I think because the present tense has changed, the cache changes and the information is taken from the table every time🤨

Yes, because your parameter: var now = DateTime.Now; is different each time, It can't be cached. Each time a new cache item will be created for it.

Thank you very much🌹


plasma6: black screen with a cursor after login

Describe the bug
After logging in using a fresh user, plasma6 showed only a black screen with a cursor. (see screenshot 1)
plasmashell refused to start, as it could not connect to kactivitymanagerd.
kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.

Full log see plasmashell.txt.
However, kactivitymanagerd seem started normally.
May 28 12:42:16 pc systemd[2838]: Started KActivityManager Activity manager Service

Full log see kactivitymanagerd.txt.
In d-spy, org.kde.ActivityManager could be found in session dbus (see screenshot 2).
dbus services complained a lot of "duplicate name". See dbus.txt.
All logs (journalctl -b 0) see log.txt.
Steps To Reproduce
Use this flake. (nixosConfigurations.pc)
I have tried these modifications but nothing works (on branch next-debug):

switch to default kernel (linuxPackages) without any custom patch.
disable cuda and hostPlatform.gcc.arch = "znver4".
disable all home-manager stuff and impermanence mount about directories under the user home, to keep the home directory as clean as possible.
use X11 instead of Wayland.
switch between Nvidia graphic card only and amd+nvidia hybrid offload.
add nvidia-drm.fbdev=1 to the kernel parameter.

The same problem also exist on @Cryolitia 's GPD (This flake, nixosConfigurations.cryolitia-gpd-nixos).
Expected behavior
Plasma started with the default wallpaper and status bar.
Screenshots

Notify maintainers
I am not sure which people should I notify, as I could not which part of nixpkgs led to this problem.
Metadata

system: "x86_64-linux"
host os: Linux 6.9.1-cachyos, NixOS, 24.05 (Uakari), 24.05
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.18.2
nixpkgs: /nix/store/gy21mdwskf5343sdmwra2x1rm9z24bix-source

Add a :+1: reaction to issues you find important.

Same on me

A strange thing is why plasmashell 6 tries to load qt5 plugins.
May 28 12:42:16 pc plasmashell[3466]: kf.coreaddons: The plugin "/nix/store/r57jxbq8xzwplvp221kpp691jk5ldgg7-system-path/lib/qt-5.15.12/plugins/plasma/containmentactions/plasma_containmentactions_applauncher.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed

There is some guess, from
May 28 12:42:16 pc plasmashell[3466]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
May 28 12:42:16 pc plasmashell[3466]: kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
May 28 12:42:16 pc kactivitymanagerd[3506]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11
May 28 12:42:16 pc kactivitymanagerd[3506]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11
May 28 12:42:16 pc plasmashell[3466]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
May 28 12:42:16 pc plasmashell[3466]: kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
May 28 12:42:16 pc systemd[2838]: Started KActivityManager Activity manager Service.

it may be a race condition. Try systemctl --user restart plasmashell.service to check this guess.
If not caused by this, write export QT_LOGGING_RULES="org.kde.kactivities.*.debug=true" in ~/.config/plasma-workspace/env/debug.sh to enable debug log for KActivityManagerd (sadly, there is no debug log in KActivities library), and then open a tty/ssh and execute dbus-monitor --session "interface='org.kde.ActivityManager'" &> dbus.log to monitor any request to KAMD. Then switch back to SDDM and log in to Plasma. Finally, post the dbus.log and journalctl output here.

it may be a race condition. Try systemctl --user restart plasmashell.service to check this guess.

It does not work.

If not caused by this, write export QT_LOGGING_RULES="org.kde.kactivities.*.debug=true" in ~/.config/plasma-workspace/env/debug.sh to enable debug log for KActivityManagerd (sadly, there is no debug log in KActivities library), and then open a tty/ssh and execute dbus-monitor --session "interface='org.kde.ActivityManager'" &> dbus.log to monitor any request to KAMD. Then switch back to SDDM and log in to Plasma. Finally, post the dbus.log and journalctl output here.

There are only two item in dbus.log:
signal time=1716878876.363339 sender=org.freedesktop.DBus -> destination=:1.3 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
string ":1.3"
signal time=1716878876.363359 sender=org.freedesktop.DBus -> destination=:1.3 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
string ":1.3"

Here is journalctl -b -1 after reboot: journalctl.log

I have found the problem. Some theme packages (such as utterly-nord-plasma) contain a file named nix-support/propagated-user-env-packages whose content is some qt5 library pathes. If I add these theme packages into environment.systemPackages, the qt5 libraries listed in the file will also be added to the environment, causing a conflict with qt6 and plasma6.
Solution is to remove these packages from environment.systemPackages.

It's still a problem that should be fixed, do not close.
I remember that I uses pkgs.nordic, that's probably why I met the problem, too.
CC @romildo if you have any idea.

How do you check the package dependency chain for qt5 libraries instead of qt6?  (May have run into this same problem, but don't have any of the same packages mentioned so far.)

How do you check the package dependency chain for qt5 libraries instead of qt6? (May have run into this same problem, but don't have any of the same packages mentioned so far.)

Try to find some packages that are installed on your machine but merely installed on other people's machines. Remove them and see if the issue has gone. If yes, you may be probably meeting the same issue.

Try to find some packages that are installed on your machine but merely installed on other people's machines.

I don't understand what you're saying.

I don't understand what you're saying.

Some packages are only installed by very few people (mostly some theme packages), so they may be still packaged using qt5 instead of qt6, and the problem may not be reported. Install these packages together with kde6 will cause problem discussed in this issue.


Testing the new system

Trying this out to see how it works on our content.

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

ID: 5416573b-dd99-f3c9-1707-32fb38023788
Version Independent ID: 45ebd856-0161-4ea2-2833-d1ec165ebc97
Content
Content Source

#assign:WilliamAntonRohm

#unassign:WilliamAntonRohm


added package to stop hyphenation of section titles.

Oops, commented in the issue, not here. VErified that this doesn't break anything. That's good enough for me! thanks @cwallen08ucsd !


Unable to connect to Cypress PSOC 62

I'm getting the error below when I try to connect to CY8CPROTO-062-4343W.
pyOCD: 0.26.0
Python: 3.6.9
OS: Ubuntu 18.04.4 LTS

$ pyocd gdb -t CY8C6xxA
0001233:INFO:board:Target type is cy8c6xxa
0001285:INFO:dap:DP IDR = 0x6ba02477 (v2 rev6)
0001299:INFO:ap:AP#0 IDR = 0x84770001 (AHB-AP var0 rev8)
0001310:INFO:ap:AP#1 IDR = 0x84770001 (AHB-AP var0 rev8)
0001323:INFO:ap:AP#2 IDR = 0x24770011 (AHB-AP var1 rev2)
0001337:INFO:rom_table:AP#0 Class 0x1 ROM table #0 @ 0xf1000000 (designer=034 part=102)
0001352:INFO:rom_table:AP#1 Class 0x1 ROM table #0 @ 0xf0000000 (designer=034 part=102)
0001360:INFO:rom_table:[0]<e00ff000:ROM class=1 designer=43b part=4c0>
0001360:INFO:rom_table:  AP#1 Class 0x1 ROM table #1 @ 0xe00ff000 (designer=43b part=4c0)
0001368:INFO:rom_table:  [0]<e000e000:SCS-M0+ class=14 designer=43b part=008>
0001373:INFO:rom_table:  [1]<e0001000:DWT-M0+ class=14 designer=43b part=00a>
0001379:INFO:rom_table:  [2]<e0002000:BPU class=14 designer=43b part=00b>
0001384:INFO:rom_table:[1]<f0002000:CTI class=9 designer=43b part=9a6 devtype=14 archid=1a14 devid=1040800:0:0>
0001388:INFO:rom_table:[2]<f0003000:MTB-M0+ class=9 designer=43b part=932 devtype=31 archid=0a31 devid=0:0:0>
0001397:INFO:rom_table:AP#2 Class 0x1 ROM table #0 @ 0xe00ff000 (designer=034 part=102)
0001404:INFO:rom_table:[0]<e0080000:CTI class=9 designer=43b part=906 devtype=14 archid=0000 devid=40800:0:0>
0001410:INFO:rom_table:[3]<e008e000:TPIU-M3 class=9 designer=43b part=923 devtype=11 archid=0000 devid=ca1:0:0>
0001416:INFO:rom_table:[4]<e007f000:ROM class=1 designer=034 part=102>
0001416:INFO:rom_table:  AP#2 Class 0x1 ROM table #1 @ 0xe007f000 (designer=034 part=102)
0001423:INFO:rom_table:  [0]<e000e000:SCS-M4 class=14 designer=43b part=00c>
0001428:INFO:rom_table:  [1]<e0001000:DWT class=14 designer=43b part=002>
0001434:INFO:rom_table:  [2]<e0002000:FPB class=14 designer=43b part=003>
0001439:INFO:rom_table:  [3]<e0000000:ITM class=14 designer=43b part=001>
0001445:INFO:rom_table:  [4]<e0042000:CTI class=9 designer=43b part=906 devtype=14 archid=0000 devid=40800:0:0>
0001450:INFO:rom_table:  [5]<e0041000:ETM-M4 class=9 designer=43b part=925 devtype=13 archid=0000 devid=0:0:0>
0001453:INFO:cortex_m:CPU core #0 is Cortex-M0+ r0p1
0001457:INFO:cortex_m:CPU core #1 is Cortex-M4 r0p1
0001466:INFO:cortex_m:FPU present: FPv4-SP
0001472:INFO:dwt:2 hardware watchpoints
0001477:INFO:fpb:4 hardware breakpoints, 0 literal comparators
0001487:INFO:dwt:4 hardware watchpoints
0001490:INFO:fpb:6 hardware breakpoints, 4 literal comparators
0001518:INFO:server:Semihost server started on port 4444 (core 0)
0001518:INFO:gdbserver:GDB server started on port 3333 (core 0)
Exception in thread gdb-server-core0:
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/gdbserver/gdbserver.py", line 272, in run
    self.target.halt()
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/cortex_m.py", line 683, in halt
    self.write_memory(CortexM.DHCSR, CortexM.DBGKEY | CortexM.C_DEBUGEN | CortexM.C_HALT)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/cortex_m.py", line 640, in write_memory
    self.ap.write_memory(addr, value, transfer_size)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 540, in _write_memory
    self.write_reg(MEM_AP_TAR, addr)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 512, in write_reg
    super(MEM_AP, self).write_reg(addr, data)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 241, in write_reg
    self.dp.write_ap((self.ap_num << APSEL_SHIFT) | addr, data)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/dap.py", line 402, in write_ap
    self.probe.write_ap(addr, data)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/cmsis_dap_probe.py", line 325, in write_ap
    self._select_ap(addr)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/cmsis_dap_probe.py", line 295, in _select_ap
    self.write_dp(self.DP_SELECT, select)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/cmsis_dap_probe.py", line 280, in write_dp
    self._link.write_reg(reg_id, data)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/pydapaccess/dap_access_cmsis_dap.py", line 786, in write_reg
    self._write(dap_index, 1, request, [value])
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/pydapaccess/dap_access_cmsis_dap.py", line 964, in _write
    size = cmd.get_request_space(size_to_transfer, transfer_request, dap_index)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/pydapaccess/dap_access_cmsis_dap.py", line 217, in get_request_space
    assert self._data_encoded is False
AssertionError

0001525:INFO:server:Semihost server started on port 4445 (core 1)
0001526:INFO:gdbserver:GDB server started on port 3334 (core 1)
Exception in thread gdb-server-core1:
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/gdbserver/gdbserver.py", line 272, in run
    self.target.halt()
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/cortex_m.py", line 683, in halt
    self.write_memory(CortexM.DHCSR, CortexM.DBGKEY | CortexM.C_DEBUGEN | CortexM.C_HALT)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/cortex_m.py", line 640, in write_memory
    self.ap.write_memory(addr, value, transfer_size)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 540, in _write_memory
    self.write_reg(MEM_AP_TAR, addr)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 512, in write_reg
    super(MEM_AP, self).write_reg(addr, data)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/ap.py", line 241, in write_reg
    self.dp.write_ap((self.ap_num << APSEL_SHIFT) | addr, data)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/coresight/dap.py", line 402, in write_ap
    self.probe.write_ap(addr, data)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/cmsis_dap_probe.py", line 325, in write_ap
    self._select_ap(addr)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/cmsis_dap_probe.py", line 295, in _select_ap
    self.write_dp(self.DP_SELECT, select)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/cmsis_dap_probe.py", line 280, in write_dp
    self._link.write_reg(reg_id, data)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/pydapaccess/dap_access_cmsis_dap.py", line 786, in write_reg
    self._write(dap_index, 1, request, [value])
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/pydapaccess/dap_access_cmsis_dap.py", line 964, in _write
    size = cmd.get_request_space(size_to_transfer, transfer_request, dap_index)
  File "/home/marcus/python/lib/python3.6/site-packages/pyocd/probe/pydapaccess/dap_access_cmsis_dap.py", line 217, in get_request_space
    assert self._data_encoded is False
AssertionError

I have Python 3.7.4 , pyOCD 0.26 and I see the same thing.
Could it be something related to the dual-core?

I'm having similar issues.
pyOCD: 0.26.0
Python: 3.7.3
OS: Windows 10 1909
Target: LPC55S69
Probe: DAPLink like
pyocd output:
pyocd gdb -t lpc55s69
0000470:INFO:board:Target type is lpc55s69
0000492:INFO:dap:DP IDR = 0x6ba02477 (v2 rev6)
0000502:INFO:ap:AP#0 IDR = 0x84770001 (AHB-AP var0 rev8)
0000509:INFO:ap:AP#1 IDR = 0x84770001 (AHB-AP var0 rev8)
0000518:INFO:ap:AP#2 IDR = 0x002a0000 (proprietary)
0000524:INFO:rom_table:AP#0 Class 0x1 ROM table #0 @ 0xe00fe000 (designer=015 part=000)
0000528:INFO:rom_table:[0]<e00ff000:ROM class=1 designer=43b part=4c9>
0000528:INFO:rom_table:  AP#0 Class 0x1 ROM table #1 @ 0xe00ff000 (designer=43b part=4c9)
0000533:INFO:rom_table:  [0]<e000e000:SCS-M33 class=9 designer=43b part=d21 devtype=00 archid=2a04 devid=0:0:0>
0000554:INFO:rom_table:  [1]<e0001000:DWT class=9 designer=43b part=d21 devtype=00 archid=1a02 devid=0:0:0>
0000559:INFO:rom_table:  [2]<e0002000:BPU class=9 designer=43b part=d21 devtype=00 archid=1a03 devid=0:0:0>
0000563:INFO:rom_table:  [3]<e0000000:ITM class=9 designer=43b part=d21 devtype=43 archid=1a01 devid=0:0:0>
0000567:INFO:rom_table:[1]<e0040000:TPIU-M33 class=9 designer=43b part=d21 devtype=11 archid=0000 devid=ca0:0:0>
0000617:INFO:rom_table:AP#1 Class 0x1 ROM table #0 @ 0xe00fe000 (designer=015 part=000)
0000660:INFO:rom_table:[0]<e00ff000:ROM class=1 designer=43b part=4c9>
0000666:INFO:rom_table:  AP#1 Class 0x1 ROM table #1 @ 0xe00ff000 (designer=43b part=4c9)
0000680:INFO:rom_table:  [0]<e000e000:SCS-M33 class=9 designer=43b part=d21 devtype=00 archid=2a04 devid=0:0:0>
0000682:INFO:rom_table:  [1]<e0001000:DWT class=9 designer=43b part=d21 devtype=00 archid=1a02 devid=0:0:0>
0000684:INFO:rom_table:  [2]<e0002000:BPU class=9 designer=43b part=d21 devtype=00 archid=1a03 devid=0:0:0>
0000686:INFO:rom_table:  [3]<e0000000:ITM class=9 designer=43b part=d21 devtype=43 archid=1a01 devid=0:0:0>
0000688:INFO:rom_table:[1]<e0040000:TPIU-M33 class=9 designer=43b part=d21 devtype=11 archid=0000 devid=ca0:0:0>
0000689:INFO:cortex_m_v8m:CPU core #0 is Cortex-M33 r0p3 (security ext present)
0000691:INFO:cortex_m:FPU present: FPv5-SP
0000694:INFO:cortex_m_v8m:CPU core #1 is Cortex-M33 r0p3
0000698:INFO:dwt:4 hardware watchpoints
0000699:INFO:fpb:8 hardware breakpoints, 1 literal comparators
0000704:INFO:dwt:4 hardware watchpoints
0000705:INFO:fpb:8 hardware breakpoints, 1 literal comparators
0000715:INFO:server:Semihost server started on port 4444 (core 0)
0000716:INFO:gdbserver:GDB server started on port 3333 (core 0)
Exception in thread gdb-server-core0:
Traceback (most recent call last):
  File "C:\python37\lib\threading.py", line 917, in _bootstrap_inner
    self.run()
  File "C:\python37\lib\site-packages\pyocd\gdbserver\gdbserver.py", line 272, in run
    self.target.halt()
  File "C:\python37\lib\site-packages\pyocd\coresight\cortex_m.py", line 683, in halt
    self.write_memory(CortexM.DHCSR, CortexM.DBGKEY | CortexM.C_DEBUGEN | CortexM.C_HALT)
  File "C:\python37\lib\site-packages\pyocd\coresight\cortex_m.py", line 640, in write_memory
    self.ap.write_memory(addr, value, transfer_size)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 540, in _write_memory
    self.write_reg(MEM_AP_TAR, addr)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 512, in write_reg
    super(MEM_AP, self).write_reg(addr, data)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 241, in write_reg
    self.dp.write_ap((self.ap_num << APSEL_SHIFT) | addr, data)
  File "C:\python37\lib\site-packages\pyocd\coresight\dap.py", line 402, in write_ap
    self.probe.write_ap(addr, data)
  File "C:\python37\lib\site-packages\pyocd\probe\cmsis_dap_probe.py", line 325, in write_ap
    self._select_ap(addr)
  File "C:\python37\lib\site-packages\pyocd\probe\cmsis_dap_probe.py", line 295, in _select_ap
    self.write_dp(self.DP_SELECT, select)
  File "C:\python37\lib\site-packages\pyocd\probe\cmsis_dap_probe.py", line 280, in write_dp
    self._link.write_reg(reg_id, data)
  File "C:\python37\lib\site-packages\pyocd\probe\pydapaccess\dap_access_cmsis_dap.py", line 786, in write_reg
    self._write(dap_index, 1, request, [value])
  File "C:\python37\lib\site-packages\pyocd\probe\pydapaccess\dap_access_cmsis_dap.py", line 964, in _write
    size = cmd.get_request_space(size_to_transfer, transfer_request, dap_index)
  File "C:\python37\lib\site-packages\pyocd\probe\pydapaccess\dap_access_cmsis_dap.py", line 217, in get_request_space
    assert self._data_encoded is False
AssertionError
0000719:INFO:server:Semihost server started on port 4445 (core 1)

0000722:INFO:gdbserver:GDB server started on port 3334 (core 1)
Exception in thread gdb-server-core1:
Traceback (most recent call last):
  File "C:\python37\lib\threading.py", line 917, in _bootstrap_inner
    self.run()
  File "C:\python37\lib\site-packages\pyocd\gdbserver\gdbserver.py", line 272, in run
    self.target.halt()
  File "C:\python37\lib\site-packages\pyocd\coresight\cortex_m.py", line 683, in halt
    self.write_memory(CortexM.DHCSR, CortexM.DBGKEY | CortexM.C_DEBUGEN | CortexM.C_HALT)
  File "C:\python37\lib\site-packages\pyocd\coresight\cortex_m.py", line 640, in write_memory
    self.ap.write_memory(addr, value, transfer_size)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 540, in _write_memory
    self.write_reg(MEM_AP_TAR, addr)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 512, in write_reg
    super(MEM_AP, self).write_reg(addr, data)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 142, in _locking
    return func(self, *args, **kwargs)
  File "C:\python37\lib\site-packages\pyocd\coresight\ap.py", line 241, in write_reg
    self.dp.write_ap((self.ap_num << APSEL_SHIFT) | addr, data)
  File "C:\python37\lib\site-packages\pyocd\coresight\dap.py", line 402, in write_ap
    self.probe.write_ap(addr, data)
  File "C:\python37\lib\site-packages\pyocd\probe\cmsis_dap_probe.py", line 325, in write_ap
    self._select_ap(addr)
  File "C:\python37\lib\site-packages\pyocd\probe\cmsis_dap_probe.py", line 295, in _select_ap
    self.write_dp(self.DP_SELECT, select)
  File "C:\python37\lib\site-packages\pyocd\probe\cmsis_dap_probe.py", line 280, in write_dp
    self._link.write_reg(reg_id, data)
  File "C:\python37\lib\site-packages\pyocd\probe\pydapaccess\dap_access_cmsis_dap.py", line 786, in write_reg
    self._write(dap_index, 1, request, [value])
  File "C:\python37\lib\site-packages\pyocd\probe\pydapaccess\dap_access_cmsis_dap.py", line 964, in _write
    size = cmd.get_request_space(size_to_transfer, transfer_request, dap_index)
  File "C:\python37\lib\site-packages\pyocd\probe\pydapaccess\dap_access_cmsis_dap.py", line 217, in get_request_space
    assert self._data_encoded is False
AssertionError

I can confirm that I have also had this issue on the Musca s1, and that it works correctly after a downgrade to pyocd 0.25.0

@flit can you investigate or recommend the right person to investigate? Looks like there is a problem reported on multiple targets on release 0.26.0.

@marcuschangarm @Quincy-Zh @maclobdell
Is this issue still relevant? I've tested with different PSoC6 flavors and I can not reproduce it with latest pyOCD master.

@bohdan-tymkiv I haven't used the PSOC in awhile. Let's close it if you can't reproduce it.


Allow customization of ServiceMonitor namespace

Adds a values.yaml field to customize the namespace that the ServiceMonitor is deployed into. Prometheus allows for only specific namespaces to be monitored for service monitors and this eases the constraint that it must include 'default'
If we prefer to change the serviceMonitor field's type to an object, something like the following may be preferable.
serviceMonitor:
  enabled: true
  namespace: default

Closes #1490

To be clear, this issue appears only when you used helm template. helm template is known to not automatically set metafata.name so every chart author needs to add name: {{ .Release.Namespace }} to the metadata of every resource template.
Based on the discussion at https://github.com/actions-runner-controller/actions-runner-controller/pull/1491#discussion_r912321046 I'm going to update this to just include name: {{ .Release.Namespace }} in the metadata, so that it works for helm template too.

Hi there!
namespace: {{ .Release.Namespace }} is not very flexible.
For example the ARC is deployed in a dedicated namespace but kube-prometheus-stack usually is deployed under "monitoring" namespace.
This creates the following problem. We want all ServiceMonitors to be added under "monitoring" namespace for easier Prometheus configuration but namespace: {{ .Release.Namespace }} deploys the ServiceMonitor under ARC namespace.
In my opinion https://github.com/actions-runner-controller/actions-runner-controller/pull/1491/commits/d50be98bef03d890b4757624999f23ebdfd0a186
is a more flexible approach for ServiceMonitor deployment.


Disable areas and joins when fetching complete versions of docs for d…

…iffing purposes in getEditable

Yes, we're not. This is the 'editable' route, the sole purpose of which is
to send back a list of ids that are submittable or committable. That
determination is entirely based on the permanent attributes of that
particular doc. We do care about docs "related" to the original page, but
in this case we've found those and we're querying for complete copies of
them and want to do that efficiently; we don't recurse further (if we did
the entire site would be "related"), so it doesn't make sense to waste time
(or generate scary recursion warnings) by joining further during the load.
On Thu, Nov 16, 2017 at 10:02 AM, Stuart Romanek<EMAIL_ADDRESS>wrote:

@stuartromanek commented on this pull request.
Looks good but i also don't have total context for when this happens .. I
guess we're not rendering a template using this data?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/punkave/apostrophe-workflow/pull/121#pullrequestreview-77144461,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fbVz3-mOrIlwOdT44oHBNMzyLMxeks5s3E6ZgaJpZM4QfkW1
.

--
THOMAS BOUTELL, CHIEF SOFTWARE ARCHITECT
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com


sfdx Deploying w Unreleased API Version by Default

Summary
This AM I started having issues with sfdx force:source:deploy -p ...  pushing source w/ API version 56.0 (upcoming/unreleased Winter '23) by default. I eventually just forced the API version used by sfdx to be 55.0 but another dev just reported seeing the same thing also starting this AM. We both initially were on sfx-cli/7.161.0 and then upgraded to sfdx-cli/7.162.0 with no effect.
Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc

Remove the specific sourceApiVersion value from sfdx-project.json that would otherwise force sfdx to deploy using v55.0
Run sfdx force:source:deploy -p force-app against a new scratch org spun up with Summer '22 (v55.0)
Confirm deployment fails with the following message Error package.xml Invalid version specified:56.0

Expected result
sfdx should use latest released version of API (v55.0) for deployment, which should then succeed.
Actual result
sfdx attempts to deploy using unreleased API version v56.0, which results in the deployment failing.
System Information

I am using zsh

{
        "cliVersion": "sfdx-cli/7.162.0",
        "architecture": "darwin-x64",
        "nodeVersion": "node-v14.16.1",
        "pluginVersions": [
                "@oclif/plugin-autocomplete 0.3.0 (core)",
                "@oclif/plugin-commands 1.3.0 (core)",
                "@oclif/plugin-help 3.3.1 (core)",
                "@oclif/plugin-not-found 1.2.6 (core)",
                "@oclif/plugin-plugins 1.10.11 (core)",
                "@oclif/plugin-update 1.5.0 (core)",
                "@oclif/plugin-warn-if-update-available 1.7.3 (core)",
                "@oclif/plugin-which 1.0.4 (core)",
                "@salesforce/sfdx-plugin-lwc-test 1.0.0 (core)",
                "alias 2.1.0 (core)",
                "apex 1.1.0 (core)",
                "auth 2.2.3 (core)",
                "community 2.0.0 (core)",
                "config 1.4.14 (core)",
                "custom-metadata 2.0.0 (core)",
                "data 2.1.1 (core)",
                "generator 2.0.2 (core)",
                "info 2.0.1 (core)",
                "limits 2.0.1 (core)",
                "org 2.0.7 (core)",
                "rest-explorer 0.0.0",
                "salesforce-alm 54.6.4 (core)",
                "schema 2.1.1 (core)",
                "sfdx-cli 7.162.0 (core)",
                "shane-sfdx-plugins 4.43.0",
                "├─ @mshanemc/plugin-streaming 1.1.7",
                "└─ @mshanemc/sfdx-sosl 1.1.0",
                "signups 1.2.0 (core)",
                "source 2.0.11 (core)",
                "telemetry 2.0.0 (core)",
                "templates 55.0.0 (core)",
                "trust 2.0.2 (core)",
                "user 2.1.0 (core)"
        ],
        "osVersion": "Darwin 18.7.0"
}

I'm seeing the same error this morning with sfdx force:source:push --loglevel fatal --forceoverwrite until I add "sourceApiVersion": "55.0" to sfdx-project.json.

Thanks for reporting the issue. We have determined the cause, but the functional area belongs to another team. The workaround will require the presence of property sourceApiVersion in your project json.

Thanks for jumping on this, @peternhale

I also started to see this and some really unhelpful error messages. I am using VS Code to deploy and kept receiving the following response even when I knew 100% there were changes to deploy:
=== Pushed Source
No results found

I eventually looked at the Deployment Settings in Setup, and this is where I saw the deploys failed with the following Invalid version specified error:

It is also worth noting that I have set the "sourceApiVersion": "52.0", value in the project.json file, but it is not being used by SFDX in VS Code.

Update on my issue. I have a monorepo. In the root of the entire project directory, I have a lightweight sfdx-project.json file as this is required for the SFDX tools within VS Code to load. I have another sfdx-project.json in the package directory for package-specific properties such as versioning, namespace, etc.
Adding sourceApiVersion to the root sfdx-project.json file resolved my issue.
{
  "sourceApiVersion": "55.0",
  "packageDirectories": [
    {
      "path": "packages/package/force-app",
      "default": true
    },
    {
      "path": "packages/package/unpackaged",
      "default": false
    }
  ]
}

Good day @TehNrd. I just want to confirm that applying sourceApiVersion to both sfdx-project.json files is not working for when running sfdx commands via vscode. Is that correct? Have you tried running the sfdx commands outside of vscode?

@mshanemc is the solution to this to always specify the sourceApiVersion?

yeah, I'd always recommend specifying sourceApiVersion in the project.  The sf project generate command should set that up for you automatically.


sequential_async_test

I'd like to run multiple async tests from a single page, but execute them sequentially, not in parallel. The idea would be for later tests to delay execution until the previous ones are done.
The goal would be to make tests that share state (across the tests, or in the object under test) be deterministic. Here's a contrived example:
var i = 0;

sequential_async_test(function(test) {
    setTimeout(function() {
        assert_equals(i, 0);
        i++;
        test.done();
    }, Math.round(Math.random() * 100));
}, 'Async test 0');

sequential_async_test(function(test) {
    setTimeout(function() {
        assert_equals(i, 1);
        i++;
        test.done();
    }, Math.round(Math.random() * 100));
}, 'Async test 1');

I guess the alternative is to make separate pages, each with a single async_test. I'll probably do that for the time being.

You can use add_result_callback to achieve this.

This issue has been moved to https://github.com/w3c/web-platform-tests/issues/7157; please continue all discussion there.


Add extension examples to AllControlls

For the sake of testing and adding a bit more coverage I guess we should add the following to AllControls

[ ] Skia
[ ] Maps
[ ] VideoManager
[ ] FFImage
[ ] OxyPlot

FFImage is not ready for production, see https://github.com/fsprojects/Fabulous/issues/600

@vshapenko Is your comment really related to this issue? AllControls sample is obviously internal-only.

@vshapenko Is your comment really related to this issue? AllControls sample is obviously internal-only. And please test your link before posting.

There is no reason to make a sample of FFImage without transformations, because, imho, it is one of most important features of this library

And please test your link before posting.

Apparently this sentence got ignored.

And please test your link before posting.

Apparently this sentence got ignored.

Sorry, missed it, Thanks for correction.

Done in https://github.com/fsprojects/Fabulous/pull/621


Updated Spanish translation

Updated Spanish translation for Volto

Why do we have so many changes here? It looks like the PR is not properly rebased, right?

@erral Only I made a git pull origin master and git rebase master at spanish-translation branch

@macagua @erral I rebased the PR to only include the relevant changes. I'm not sure what went wrong with your rebase before, @macagua

@macagua Needs a changelog entry in the news folder

@macagua Needs a changelog entry in the news folder

@davisagli done with feeeea3


Restrict tags for HiddenTextExpander and Truncate

What
This PR restricts tags for HiddenTextExpander to :span, and also restricts tags for Truncate to [:div, :span, :p]. I chose these tags based on current usage in dotcom and what seemed reasonable.
This PR also makes explicit the tag argument for Markdown so consumers know they can set the tag argument. I was unsure what the allowed tags for this component should be based on current usage of article, tdin dotcom.test_renders_different_tags` also seemed to imply that this component can be relatively flexible so I did not add restrictions. Open to thoughts if you have any.
Why
Part of #491

@manuelpuyol you wrote test_renders_different_tags. Did you intend to imply that any tag could be passed for Markdown?

@manuelpuyol you wrote test_renders_different_tags. Did you intend to imply that any tag could be passed for Markdown?

Looking at dotcom usage for markdown-body we also use it with td and article. The test was intended to guarantee that we could use those tags
I think that restricting that component to :div, :td, :article is fine!


Tile reordering often does not work

Especially when there are only two layers, it is difficult to drag the second tile to the top

Note to self: on the map view (?)

Having trouble finding what is causing this. Appears to be an issue with the ui-sortable library, but cannot seem to track it down.

It's probably okay, since I didn't find it happening consistently. Something to watch out for though.


Feature/multi account support

WIP: Needs testing -- DO NOT MERGE

Adding this pull request as a placeholder. It looks like the multi-account login works. I can't test properly because one of the tentants involved doesn't grant all the required permissions without admin consent (not sure which because https://docs.microsoft.com/en-us/graph/permissions-reference seems to suggest all the required ones don't need consent). I'll see if I can test in another manner.


Batch downloading

This PR adds batch downloading using NUS scripts, which is useful for things like WiFi modding Wii Minis.

Hey, thanks for the contribution!
I should hopefully be able to take at look at this tomorrow, but I just wanted to let you know that I've seen it, and at a quick glance it looks good! Adding back NUSD's script support to NUSGet has definitely been on my agenda for a bit, but I can only handle working with GUIs in short bursts so I hadn't gotten there yet.  I very much appreciate the help with it!

Yeah that's probably for the best to not try and work with this format more lol.
I'm looking to finally push out v1.2.0 soon, because there have been a decent number of improvements that I want to be generally available now, especially with more eyes on NUSGet recently. Most likely I'll give everything a once-over after this PR is merged and then release v1.2.0, and after that I'll look into making a JSON-based format for scripts because yeah that would absolutely be better.

I can't guarantee this will change anything, but could you try this build of the interface on macOS? I messed with the constraints some and at least on Linux and in Qt Designer it shows all of the text as wrapping now.
ui_MainMenu.zip

Spent an honestly ridiculous amount of time in Qt Designer on my old 2010 MacBook tinkering with just about every bit of spacing and constraints I could find, and I finally found something that works correctly. This fixes the spacing on macOS (which fixes the text getting cut off) while retaining the original size of everything, and still looks good on Linux (I'm sure it's fine on Windows as well, but if that's not right then oh well, I'll check it out and fix it before v1.2.0). Hopefully this looks good on your end like it did for me, I was working under macOS 12 so it probably should be identical under something newer.
Here's the UI file I ended up with:
MainMenu.zip

Yep, works just fine on macOS 15 on my M2 MacBook Air too. I copied your work into this PR.

Awesome! In that case, I think that's everything, so I'll go ahead and merge this PR. Thanks!

🫡


Malscan 2.x - Helper Migration

This issue tracks Malscan's 2.x upgrade process with respect to its helper functionality as part of the Python Rewrite project for Malscan 2.x.
Completion Requirements
All of the following should resolve the help output:

[x]  malscan
[x] malscan help
[x] malscan -h
[x]  malscan --help

Additionally, other requirements for this issue to be resolved:

[ ] all failed switches/subcommands must resolve the help output
[ ] 100% unit test code coverage for malscan/help.py
[ ] 100% passing code quality from Scrutinizer-Ci

Help output is now resolved from all 4 required options as of 51384bfebe7d972afca18910fdfc45982b01c671

Failed switches all resolve help output as of 51384bfebe7d972afca18910fdfc45982b01c671 with one important caveat:
Running the command malscan random-command-here will result in a scan if there is a file named random-command-here in the directory the command is run from.
I would rather treat a solo argument as a potential scan target before I error it out, so we do verify whether or not it exists as a file or directory before deciding which way to go.


Bump go-rpmdb and go-containerregistry deps

go-containerregistry => v0.10.0
go-rpmdb => opdev/preflight-next

Signed-off-by: Brad P. Crochet<EMAIL_ADDRESS>

coverage: 73.126% (-0.7%) from 73.856%
when pulling fd3e514038bbc6e186a0d359b0baa5416ea5fb97 on bcrochet:bump-deps
into 0c492b1bff6b71d4f2b107e237aa929e38dfbf8d on redhat-openshift-ecosystem:main.


db create doesn't work

When I ran populate-instance.sh, I got this errors: invenio_error.txt
How can I fix this?
It's a fresh install, Ubuntu 14.04 LTS
I followed these instructions: http://invenio.readthedocs.io/en/latest/deploymentguide/installation-detailed.html
Thanks,
Attila

Can you check which version you are running with
$ psql --version

since the JSONB type was introduced in PostgreSQL 9.4?

$ psql --version
psql (PostgreSQL) 9.3.20

I upgraded my PostgreSQL then it works perfectly.
at now:
$ psql --version
psql (PostgreSQL) 9.4.15

Thank you!


Debugger build fails on AppVeyor

The error raised is:
mkdir -p tmp/x64-mingw32/google/cloud/debugger/debugger_c/2.3.3/google/cloud/debugger
cd tmp/x64-mingw32/google/cloud/debugger/debugger_c/2.3.3
C:/Ruby23-x64/bin/ruby.exe -I. ../../../../../../../ext/google/cloud/debugger/debugger_c/extconf.rb
creating Makefile
cd -
cd tmp/x64-mingw32/google/cloud/debugger/debugger_c/2.3.3
rake aborted!
Couldn't find a suitable `make` tool. Use `MAKE` env to set an alternative.

closed by #1403


Add explicit license disclaimer

A detailed description of the proposed feature
Add explicit disclaimer about license information, possibly including how licenses are identified, somewhere in the documentation.
The motivation for the feature
GitHub includes information about how the license information is generated as well as a disclaimer about legal liability.
How the feature would be relevant to at least 90% of Homebrew users
Homebrew users who have restrictions on which licenses they can use will be explicitly warned about the provenance and guarantees about the license information provided by Homebrew
What alternatives to the feature have been considered
Not including a disclaimer since the existing Homebrew BSD 2-clause license already covers (lack of) liability.

@Homebrew/plc

Sorry but I don’t quite understand what this is is about.

Add explicit disclaimer about license information, possibly including how licenses are identified

What license information? Is this about upstream licenses (as referenced in the formulae) or the license under which Homebrew itself is published?

as well as a disclaimer about legal liability.

Are you referring to the copy in the red box on the linked GitHub page?

What license information? Is this about upstream licenses (as referenced in the formulae) or the license under which Homebrew itself is published?

This is referring to the upstream license information, not Homebrew itself.

Are you referring to the copy in the red box on the linked GitHub page?

Yeah - the copy in the red box is what grabbed my attention.

Not including a disclaimer since the existing Homebrew BSD 2-clause license already covers (lack of) liability.

I think this is sufficient, personally.  We don't really have documentation like that on GitHub.

Closing due to lack of @Homebrew/plc interest.

Thanks for working on this! The licensing stuff is really tricky so we'll have to think carefully on everything that we're approachign this with.


Implied matching

http://www.cmegroup.com/confluence/display/EPICSANDBOX/Implied+Orders
In derivative (and some other i.e. swaps) exchanges there is a concept of implied orders / matching. It's sort of an automatic arbitrage between related contracts (typically of different expiry + spread).
Non trivial to implement but important for trading something other than equity / FX.

I'll have to look into this in more detail as well.

This looks interesting, but I think it's unfortunately going to be outside the scope of the project, at least for the time being.


Revise glossary/kops

The reason for the update is as follows:

title:

Added full name and same as kOps repo.

full_link:

kubernetes/website has updated the link address to /docs/setup/production-environment/tools/kops/

short_description:

The kops official website document has been updated to the description.

version description:

The supported version of kops has been updated

features:

Sync with current kubernetes/website content,The content of the description can refer to /docs/setup/production-environment/tools/kops/

Signed-off-by: ydFu<EMAIL_ADDRESS>

This page is related to content/en/docs/setup/production-environment/tools/kops.md, so wait until this PR is merged before continuing
/hold

The features has been updated.(see https://github.com/kubernetes/website/pull/36796).
Please check this update.
/unhold
/cc @chrisnegus @kbhawkey

/approve

/lgtm


export ignore examples & tests in distribution

would be great if we wouldn't get the examples and tests via composer, when installing with --prefer-dist.
for background see https://www.reddit.com/r/PHP/comments/2jzp6k/i_dont_need_your_tests_in_my_production/

This is "a good thing" in general. But note that the unit tests from here were being run in sabre-io/dav - the tests/phpunit.xml there had:
      <testsuite name="sabre-event">
          <directory>../vendor/sabre/event/tests/</directory>
      </testsuite>

But actually no tests appear there any more. So actually those tests have not been running in sabre-io/dav CI.
A new version of phpunit is now reporting when there is a test suite defined that does not exist. CI started failing in sabre-io/dav. See https://github.com/sabre-io/dav/pull/1316


Unable to retrieve tenant service info

What's meaning of the following error, anybody can tell me how to solve this issuse?
{
"error": {
"code": "BadRequest",
"message": "Unable to retrieve tenant service info.",
"innerError": {
"request-id": "59bf9f1d-f25f-4ae4-bd8a-eadb27f75e5f",
"date": "2018-01-21T13:12:38"
}
}
}

Hi. I have a similar problem. From time to time we can see:
Code: BadRequest
Message: Unable to retrieve tenant service info.
Inner error:
        AdditionalData:
        request-id: 762b4062-bedd-4180-abcb-bfb05c7df768
        date: 2020-03-16T01:00:11
ClientRequestId: 762b4062-bedd-4180-abcb-bfb05c7df768

In the last  two days, I had this error for 5 different accounts

Hi, I have the same issue when I'm trying to read data from my personal azure account. I get 400 Bad Request for
GET https://graph.microsoft.com/v1.0/drives/{drive-id}
and inner exception is: Error message: Unable to retrieve tenant service info.

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Added All present Scripts with Contributor's details

Added All Present Scripts short info with their respective contributor's details

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #12
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update
[x] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

@all-contributors please add @AnandD007 for documentation

@all-contributors please add @AnandD007 for documentation

LGTM💯..Great Job @AnandD007

🤩🥳🤩
Thank You......✨ @avinashkranjan ✨

LGTM💯..Great Job @AnandD007

🤩🥳🤩
Thank You......✨ @avinashkranjan ✨


[Feature] Improve readability of Ram Available and Disk Available output

Please describe the feature you want this project to offer
Available RAM and disk space are now just a plain number - they are difficult to read. They should be showing the amount in GB
Describe the solution you'd like
The values should be displayed in GB, limited to 2 decimal places

Yes, you are right, make sure to handle mb also.  Please proceed with the issue @S-Maciejewski

There will be additional function for formatting the number of bytes into readable string. Do we also want a unit test for such method in the scope of this issue?

@S-Maciejewski a unit test is always preferred , feel free to add the additional function!

Such function is now implemented in PR #20
It handles a range from bytes to petabytes and is unit tested


Not able to run

ubuntu@ip-172-31-45-76:~/watchdog$ sudo python run.py -h
Traceback (most recent call last):
File "run.py", line 4, in
from fillInventory import fill_Inventory
File "/home/ubuntu/watchdog/fillInventory.py", line 2, in
from mongo_connection import mongo_client
File "/home/ubuntu/watchdog/mongo_connection.py", line 1, in
from pymongo import MongoClient
ImportError: No module named pymongo

I have run the below command
sudo python -m pip install pymongo
it is fixed and now i  am getting
ubuntu@ip-172-31-45-76:~/watchdog$ sudo python run.py
Traceback (most recent call last):
File "run.py", line 5, in
from start_scans import start_scan
File "/home/ubuntu/watchdog/start_scans.py", line 7, in
from findTechnology import technologyScan
File "/home/ubuntu/watchdog/findTechnology.py", line 1, in
from wappalyzer import Wappalyzer
ImportError: No module named wappalyzer

This seems like pyv8 issue.. Could you try these steps
$ export LC_ALL=C
$ cd /tmp
$ pip install -e git://github.com/brokenseal/PyV8-OS-X#egg=pyv8
$ git clone https://github.com/emmetio/pyv8-binaries.git
$ unzip pyv8-binaries/pyv8-linux64.zip (or unzip appropriate zip file based on kernal version)
$ mv PyV8 src/pyv8/pyv8/.

Hi Team
I have done that.
On Fri 4 May, 2018, 3:37 PM Prajal Kulkarni<EMAIL_ADDRESS>wrote:

This seems like pyv8 issue.. Could you try these steps
$ export LC_ALL=C
$ cd /tmp
$ pip install -e git://github.com/brokenseal/PyV8-OS-X#egg=pyv8
$ git clone https://github.com/emmetio/pyv8-binaries.git
$ unzip pyv8-binaries/pyv8-linux64.zip (or unzip appropriate zip file
based on kernal version)
$ mv PyV8 src/pyv8/pyv8/.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flipkart-incubator/watchdog/issues/4#issuecomment-386557492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfnNLVvoNL2ISA0BGV1Oi3qJETEqbFLvks5tvCg5gaJpZM4TyXro
.

Could you share what result you get importing PyV8 in python
praj:~ prajal.kulkarni$ python
Python 2.7.10 (default, Oct  6 2017, 22:29:07)
[GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.31)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import PyV8

ubuntu@ip-172-31-45-76:~$ python
Python 2.7.12 (default, Dec  4 2017, 14:50:18)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.

seems like PyV8 was previously installed on the system could be a compatibility issue. You could try a fresh installation

It was some compatibility issue,it is fixed with the new installation.
Thank you for the support.

Perfect! Do give us your feedback on completing the first run!

@cybertricks @prajal
i've same error, so how can i fix? How can i reinstall pyV8?
Thanks

if i do python and i try to import PyV8 i've that output :
Traceback (most recent call last):   File "<stdin>", line 1, in <module> ImportError: No module named PyV8


Updated Twitter section

Added a foreword regarding content in that section too. Ditched the awkward 'Twitterers' too.

@HammyHavoc 👏 - thanks for this great addition plus the well-crafted summary of what types of thing we add to the twitter section.


WIP electron-cash: 3.1.6 -> 3.3

Motivation for this change
Upgrade electron-cash to version 3.3
Unfortunately it's more complicated than expected.
Here is the error I get :
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: wayland-org.kde.kwin.qpa, minimal, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

If somebody could help me debug this, I would be very glad !
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

See https://github.com/NixOS/nixpkgs/pull/44047 and https://github.com/NixOS/nixpkgs/issues/24256, it's a common qt issue. Maybe wrapping it with qt5.qtbase somehow will fix it. Ping @samueldr

Using this gross workaround I just thought of I am able to run most Qt apps in that situation. This update seems to run fine with this. (Read the comments in the gist for details about how.)
~/tmp/nixpkgs/nixpkgs-43390 $ nix-verify -A electron-cash
 $ exec env -i NIXPKGS_ALLOW_UNFREE=1 nix-build -A electron-cash
/nix/store/0s68rakzip5ghigvivgx184kzcx2f52j-electron-cash-3.3

~/tmp/nixpkgs/nixpkgs-43390 $ qt-run result/bin/electron-cash

@GrahamcOfBorg build electron-cash

Failure on x86_64-linux (full log)
Attempted: electron-cash
Partial log (click to expand)
  File "/nix/store/pyvd05namlbgacai4vr5xcpy5wlhhcb2-python3.6-bootstrapped-pip-18.0/lib/python3.6/site-packages/setuptools/dist.py", line 581, in fetch_build_egg
    return cmd.easy_install(req)
  File "/nix/store/pyvd05namlbgacai4vr5xcpy5wlhhcb2-python3.6-bootstrapped-pip-18.0/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 670, in easy_install
    raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('setuptools-markdown')
builder for '/nix/store/259lk8n561lxni9j6vpiwpcxlhiifdv9-python3.6-rlp-1.0.1.drv' failed with exit code 1
cannot build derivation '/nix/store/xy5cxkqqzsczh8kjx4vvzgl919lb9rmm-python3.6-trezor-0.10.2.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/8240rwwx3qx2h802vqf06l5pncy8vbkd-python3.6-keepkey-4.0.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/8hhk9fqw1258rwkjjnhxr0spagclx7ga-electron-cash-3.3.drv': 2 dependencies couldn't be built
error: build of '/nix/store/8hhk9fqw1258rwkjjnhxr0spagclx7ga-electron-cash-3.3.drv' failed

Failure on aarch64-linux (full log)
Attempted: electron-cash
Partial log (click to expand)
[7008/16620] CXX obj/third_party/webrtc/rtc_base/rtc_base_generic/asyncpacketsocket.o
[7009/16620] CXX obj/third_party/webrtc/p2p/rtc_p2p/packetlossestimator.o
[7010/16620] CXX obj/third_party/webrtc/modules/rtp_rtcp/rtp_rtcp/ulpfec_receiver_impl.o
[7011/16620] CXX obj/third_party/webrtc/rtc_base/rtc_base_generic/asynctcpsocket.o
[7012/16620] CXX obj/third_party/webrtc/modules/rtp_rtcp/rtp_rtcp/forward_error_correction_internal.o
[7013/16620] CXX obj/third_party/webrtc/rtc_base/rtc_base_generic/messagedigest.o
building of '/nix/store/3kd7fwwh5jbqajjir6q7zc1ra1c03qvy-qtwebengine-5.11.1.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/s97r7fq8p8in3blhz0vqi6iy8k7rgxkj-python3.6-PyQt-5.10.1.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/j97i0vlyqy1hb40db7p2bwapmkmb7gll-electron-cash-3.3.drv': 3 dependencies couldn't be built
error: build of '/nix/store/j97i0vlyqy1hb40db7p2bwapmkmb7gll-electron-cash-3.3.drv' failed

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: electron-cash
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

I'm not fond of the idea of wrapping Qt executables to workaround the issue, but I think that making the thing usable on mis-matched Qt is better than it not working. Sideway thumb for the Qt wrapper. As far as updating the package, seems alright.

@samueldr I will just add a commentary above the wrapper definition, so it's not left there in the future. I will remove the WIP title when I am done and ping you

@samueldr done, everything is working fine, thanks for the help !


Remove checkstyle warnings from drools core module

The code in the drools-core module generates a number of checkstyle warnings, related to:

order of the imports
use of {}
use of tabs instead of white spaces
lack of properly paired hash and equal functions

The relevant code is here. https://github.com/apache/incubator-kie-drools/tree/main/drools-core

Hi @pibizza, is this task completed?

No it is not. I am going to leave it here for the moment. If you think it is kind of generating issues I can close this and reopen this later.


Enrich local data via the OpenAIRE Graph

References

Requires DSpace/DSpace#3143 (if a REST API PR is required to test this)

Description
The features included in this PR are the result of the OpenAIRE Call Innovation funded project "Enrich local data via the OpenAIRE Graph” awarded by 4Science (https://www.openaire.eu/open-call-winner-phase-1-4science). It provides a closer integration between DSpace and two OpenAIRE services, the Notification Broker and the OpenAIRE REST API.
Detailed documentation about the aims of the project, the implementation and the configuration options is available at https://4science.github.io/oaire-eld/#/
As this PR introduce new features, according to the direction set by the governance we suggest to tentatively target this contribution for 7.1 or later according to community's priorities
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[ ] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[X] My PR passes TSLint validation using yarn run lint
[X] My PR doesn't introduce circular dependencies
[X] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[X] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[N/A] If my PR includes new, third-party dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.

Closing, replaced by #1562


Error while running example ("Cannot convert %s to TensorType" % str_x, type(x))

Hello guys, I am try to run the examples and I keep getting this error.
File "/home/cyb/image-analogies/venv/local/lib/python2.7/site-packages/theano/tensor/basic.py", line 208, in as_tensor_variable
raise AsTensorError("Cannot convert %s to TensorType" % str_x, type(x))
theano.tensor.var.AsTensorError: ('Cannot convert Tensor("ExpandDims:0", shape=(1, 256, 32, 22), dtype=float32) to TensorType', <class 'tensorflow.python.framework.ops.Tensor'>)
Would you have any clues how to fix that ? Thanks a lot!

any solve or hack found? thanks~

i have figured out.
keras 2.x -> keras 1.1.2
pip uninstall keras
pip install keras==1.1.2

set keras to use theano instead of tensorflow
sudo vi ~/.keras/keras.json
(change backend from tensorflow to theano)

Hahaha Thank you I'll try that !!

@neilpanchal I recently hit the same issue. After upgrading/downgrading Theano try flushing the Theano cache with "theano-cache clear" or "theano-cache purge". If neither of those work, removing the cache directory with "rm -rf ~/.theano" should do the job.


Update CRuntime.podspec

Fixes the warning:
:-1: no rule to process file 'Pods/CRuntime/Sources/CRuntime/module.modulemap' of type 'sourcecode.module-map' for architecture 'x86_64' (in target 'CRuntime').

Please update the pod also as soon as you can.
Thanks.

Thanks for looking into this! I tested this out by created a demo projection and pointed CRuntime to point at your branch and this gives me build errors now.
Podfile:
pod 'CRuntime', :git => 'https://github.com/arturdev/CRuntime.git', :branch => 'master'
pod 'Runtime'

I think that's because your Runtime library has already depencency 'CRuntime'...

Anyway, the change is very small, I've added just two symbols .h and nothing special.
The thing is that when you specify s.source_files in the podspec file, you should also specify the file extensions, otherwise, it will link ALL the files in that directory. In your case, there is also a module.modulemap there in the folder which should NOT be linked.
So, you can ignore my PR and add it yourself and update the pods of CRuntime and Runtime libraries.

@wickwirew Are you going to update the podspec?


Add ranging API

Adds the range specifier macro, allowing range to be specified in mathematical notation using string interpolators like:
range"[0, 2)"
or
range"[$myInt, 2)"
or
range"[${myInt + 4}, 2)"
The specifier itself is parsed and (syntactically) validated at compile time using macros.
Currently, the propagation of range information to FIRRTL isn't there yet, it just converts the ranges to a bitwidth. Reasoning (discussed at the Chisel meeting) for pushing this now is to allow people to use the API and leave optimizations to later. The actual more optimized range propagation will be a future pull request.
For those who haven't been following Chisel dev, ranges are a way to specify data widths at a more granular level, allowing more optimal width propagation. For example, it might not make sense to have 1.U +& 1.U +& 1.U be 3 bits wide when only 2 bits are needed to represent 3.U.

Added requested test and fixed isEmpty.
Also, StringContext parses as two separate lists of strings and interpolated variables (indexed such that the interpolated variable elements are between string elements), which makes it difficult to parse using a regex. For example, s"12${56}78" would become two lists: ["12", "78"] (format string) and [56] (interpolated element). I agree that the parser implementation isn't as elegant as I'd like, but I don't think it's possible to get rid of the mutable index and using a tokenizer-like approach (where you eat the input as you traverse it) seems to make sense.

makes sense. One final thing, is it possible to mark (at the very least, with comments) that these are experimental features?

Yeah, I think it makes sense to mark these as experimental. What do you think about requiring users to import a chisel3.experimental package, much like how Scala requires that for the use of macros? Eventually, that import would become a noop when these get mainlines back into chisel3._
Otherwise a comment is fine.

I think an experimental package is an excellent idea

Added experimental package.

lgtm

Per range discussion in #294
I appreciate this as being marked experimental, but it's not clear to me why it can't be done experimentally as a library rather than core feature of Chisel. This could be a perfect candidate annotations propagating from Chisel to Firrtl and then a custom range inference transform could be run before Width Inference.

This feature requires (or will eventually require, once completely implemented) changes to core data types (UInt and creating a Width-like type) and FIRRTL generation (allowing ranges instead of width), so putting it in a separate library would be pretty difficult.

Could you elaborate on what changes to core Chisel data types are required? Obviously the annotations API isn't done but we've been working very hard on it and I think it will be available very soon.
Unless I'm missing something important, this sounds like an exemplar of how annotations should be used. Extra information that does not change the semantics of the circuit but can improve QoR.

I don't think that's a good enough reason in itself. It could be
implemented in a research fork of Chisel/Firrtl, and merged later after a
long, deliberate process.
On Thursday, November 17, 2016, Richard Lin<EMAIL_ADDRESS>wrote:

This feature requires (or will eventually require, once completely
implemented) changes to core data types (UInt and creating a Width-like
type) and FIRRTL generation (allowing ranges instead of width), so putting
it in a separate library would be pretty difficult.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ucb-bar/chisel3/pull/369#issuecomment-261197764, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA-7wupx386SAGnTC86dvhzqR_L1LX3oks5q_B67gaJpZM4K0noq
.

In core Chisel, I think this requires changes to UInt (and friends) so it can support a range width instead of bit widths. I was also under the impression that ranging would be a core FIRRTL feature (rather than annotation), though @azidar would know more. This feature has also been discussed at several meetings, and I don't think there was any significant pushback.
Anyways, if anyone thinks that Chisel is modular enough that this could be cleanly implemented as a library, that would certainly be interesting from a software engineering standpoint. Though it also makes sense for this to be in core Chisel if ranging is going to be in core FIRRTL.
Also, yes, this can be a fork, though that causes significant maintenance and compatibility issues, especially if the ranging API is going to be widely used, as would be expected in DSP contexts.

I believe it could be implemented as follows:
The library provides a way to specify UInts/whatever with ranges. The library outputs to Chisel a UInt with the minimum width necessary to represent the max of the range; it also issues a "Range Annotation" associated with the given port, register, or wire. A Firrtl transformation run before width inference can then perform range inference based on these annotations.
One of the big motivations in making Chisel3 was to reduce Chisel down to a set of core features upon which people could layer libraries. Now it seems like this policy has been reversed to instead expand the API a bunch. I strongly suspect that a library will suffice here which is why I'm so hesitant to add features that Chisel will have to support forever.

I agree we can try and do it as an external library. However, it's prudent to merge now as experimental, and we can easily remove it later.

Waiting on approval.
Plan will be:
Merge now so people can start using it. Note that experimental carries a much lower commitment to continued support.
If the backend can be implemented as a FIRRTL annotation (I imagine it will take some time to try), this can be broken back out in a library. Users would need to add a new dependency to sbt as well as (possibly) change an import statement where this is used.


[SPARK-34438][SPARK SUBMIT] Check path component in isPython/isR, not full URI

This fixes https://issues.apache.org/jira/browse/SPARK-34438

What changes were proposed in this pull request?
This changes spark-submit to accept URIs which have their path component ending in .py as py-spark drivers. This is important to work for example with pre-signed URIs from AWS S3.
Why are the changes needed?
It is surprising to see that a regular URI does not work as expected, i.e. http://my-web-server/driver.py works as expected, but http://my-web-server/driver.py?some-query does not (spark will try to download the latter as a JAR).
Does this PR introduce any user-facing change?
Yes, as it makes spark-submit accept a wider range of inputs as Python or R drivers (the correct range).
How was this patch tested?
We're building our own spark distribution and are using it in production.

Can one of the admins verify this patch?

ok to test

Test build #135183 has started for PR 31565 at commit e7451f6.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39764/

Test build #135185 has started for PR 31565 at commit cced137.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39764/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39764/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39766/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39766/

Test build #135183 has finished for PR 31565 at commit e7451f6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39766/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135183/

Test build #135185 has finished for PR 31565 at commit cced137.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135185/

cc @tgravescs, @steveloughran, @Ngone51 @mridulm @attilapiros FYI

Can one of the admins verify this patch?

Test build #139090 has started for PR 31565 at commit cced137.

Can one of the admins verify this patch?

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43611/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43611/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/43611/

Can one of the admins verify this patch?

Test build #139090 has finished for PR 31565 at commit cced137.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/139090/

Can one of the admins verify this patch?


image file name changes

I pulled the changes and created a new branch and made the file name changes, I'll try it again

Ignore this pull request


Groups timeout

Implements groups timeout:

rollback if a group cannot achieve his status-goal before the timeout
unblock platform boot if previous group cannot achieve his status-goal

Looks great to me now :)


doc: improve prometheus docs

Adding docs about how to read the bearer token from a file

Should be good now?


Import is empty for JAR file(s)

Hi, I was looking for an answer for this in previous threads but couldn't find it. I am trying to import the JAR file 9.0.9 for the following setup, but the import list is empty.

IDE = IntelliJ
Java Version - 10.0.2
Scene Builder version - 2.0
JAR file - 9.0.9

Do I need to revert back to Java version 9 in order for it to import? Any help is appreciated.

Disregard, I downloaded v.8 of jFoenix and it worked


begin DRYing up library versions used by tuts

Add hugo shortcodes[1] for circe and cryptobits versions to
reduce the number of places version numbers are copied.
tut blocks are compiled against library versions in build.sbt
and project/Http4sBuild.scala, but the versions are also part
of surrounding markdown that is not compiled.  This copypasta
allows the compiled tuts to use version B of a library while a
reader following along at home pastes in older version A.  While
typically not a problem, it may allow the tuts, as rendered in
HTML, to break silently.
This change reduces the version copying, but does not sync the
versions in Http4sBuild.scala with the ones displayed in the
rendered HTML.
A good follow-up step might be to generate hugo's config.toml
from sbt.  Or, maybe better, export versions from sbt as
environment variables and use getenv[2] in the shortcode templates.
Also updated version for argonaut-shapeless_6.2 to latest
milestone so all the versions are up-to-date.
[1] https://gohugo.io/extras/shortcodes/
[2] http://gohugo.io/templates/functions/#getenv

Codecov Report

Merging #1127 into release-0.15.x will decrease coverage by 0.13%.
The diff coverage is n/a.

@@                Coverage Diff                @@
##           release-0.15.x   #1127      +/-   ##
=================================================
- Coverage           69.03%   68.9%   -0.14%
=================================================
  Files                 211     211
  Lines                4428    4428
  Branches              444     444
=================================================
- Hits                 3057    3051       -6
- Misses               1371    1377       +6

Impacted Files
Coverage Δ

.../scala/org/http4s/testing/ArbitraryInstances.scala
58.82% <0%> (-23.53%)
:arrow_down:

core/src/main/scala/org/http4s/HttpVersion.scala
93.75% <0%> (-6.25%)
:arrow_down:

core/src/main/scala/org/http4s/Uri.scala
83.63% <0%> (-1.82%)
:arrow_down:

Continue to review full report at Codecov.

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

Heads-up that Travis on bfritz/http4s killed this one with exit code 137:
https://travis-ci.org/bfritz/http4s/jobs/223632032#L4126
Hopefully just a fluke, but it probably means the build used more than the 4gb quota for RAM and was killed by the kernel OOM machinery.

Might be possible to use sbt-site variable substitution with copySiteToStage in build.sbt.
The env var approach would probably require the sbt-site Hugo plugin to be modified to accept a map of environment variables and expose them via sbt.Process().

I found this laying around somewhere:
val hugoGenerateData = taskKey[File]("hugo-generate-data")

hugoGenerateData := {
  val dest = (sourceDirectory in Hugo).value / "data" / "global.json"
  IO.write(dest, s"""{"version":"${(version in ThisBuild).value}"}""")
  dest
}

makeSite <<= makeSite.dependsOn(hugoGenerateData)

There's also https://github.com/sbt/sbt-buildinfo if we want the information available in tut.

Lots of ways to skin this cat., including sbt/sbt-site#98 if it gets merged.
@reactormonk Let me see if I have my head around the sbt-buildinfo route...

~We enable BuildInfoPlugin in the http4s core project.~ - already done
We customize buildInfoKeys to include the additional library versions we're interested in.
In the tuts, we import BuildInfo or BuildInfo._ and the version strings become, for instance, BuildInfo.circeVersion instead of "0.7.1".

Am I on the right track?

If those other libraries use build info, you could refer to their build info and DRY it up with the dependencies in the http4s build.
I've used the build info technique, which is simple and wonderful, but I'm not sure how to reference it in a tut without it being repl output.  It ends up looking something like:

The current version of http4s is:
0.15.9

@rossabaker Yeah, not sure how we'd use the build info and still be explicit about the version in the tut.  Would be more like:
import org.http4s.BuildInfo._ // for appropriate versions

libraryDependencies ++= Seq(
  "org.http4s" %% "http4s-circe" % version
  // Optional for auto-derivation of JSON codecs
  "io.circe" %% "circe-generic" % circeVersion
  // Optional for string interpolation to JSON model
  "io.circe" %% "circe-literal" % circeVersion
)

import org.http4s.BuildInfo._ in a build won't work unless http4s is part of a plugin, which would be silly.
You could use build info to make tut interpolate a string to spit out a valid build definition (use triple backticks for the tut shed):
``tut
s"""libraryDependencies ++= Seq(
  "org.http4s" %% "http4s-circe" % org.http4s.BuildInfo.version
)"""
``

I think that would print out
libraryDependencies ++= Seq(
  "org.http4s" %% "http4s-circe" % "0.17.0-SNAPSHOT"
)

import org.http4s.BuildInfo._ in a build won't work unless http4s is part of a plugin, which would be silly.

I meant in a ```scala block in the tut markdown.  The  ```tut block hack is interesting.  Wish I thought of that before I shaved this yak with build.toml and Hugo data. 😄
Here's my plan:

Pretend the TimeoutSpec build failure never happened.
Merge this as-is since it's a step forward and has approval.
Publish a follow-up PR in the spirit of your global.json hack for consideration.

As I give the  ```tut string interpolation idea more thought, I think there's some cases where it might break down.  More on that in the follow-up PR.


[BUG]:  minimum version OctoPrint 1.5.0 ?

minimum version OctoPrint 1.5.0 ? but Octoprint is in version 1.4.2

That is correct. 1.5.0 is currently in release candidate stages and will be available as a stable release upgrade soon, maybe this upcoming week. You could switch your release channel in octoprint to maintenance/rc and get the latest 1.5.0rc3 now if you want, link below explains how to do that.
https://community.octoprint.org/t/how-to-use-the-release-channels-to-help-test-release-candidates/402?u=jneilliii


removing numbers in fold icon column

Neovim version (nvim -v | head -n1)
NVIM v0.8.0
Operating system/version
macOS Monterey 12.6.1
How to reproduce the issue

happens with no extra configuration, only the defaults in the readme
cat mini.lua

-- Use Vim packages install the plugin, also work with some plugins manager such as packer.nvim
vim.o.packpath = '~/.local/share/nvim/site'
vim.cmd('packadd promise-async')
vim.cmd('packadd nvim-ufo')

-- Setting
vim.o.foldcolumn = '1'
vim.o.foldlevel = 99
vim.o.foldlevelstart = -1
vim.o.foldenable = true

local ufo = require('ufo')
ufo.setup()
vim.keymap.set('n', 'zR', ufo.openAllFolds)
vim.keymap.set('n', 'zM', ufo.closeAllFolds)

nvim --clean +'so mini.lua'

...
Expected behavior
like in read me only fold icons
Actual behavior
numbers on the lines where fold is not available

https://github.com/kevinhwang91/nvim-ufo/issues/4

If someone finds it and don't want to read 100 comments on #4.
To remove it completely:
vim.o.foldcolumn = "0"
To have foldcolumn like in demo video:
vim.o.fillchars = [[eob: ,fold: ,foldopen:,foldsep: ,foldclose:]]

If someone still looks for an answer, this config in this plugin statuscol.nvim removes the numbers while the arrows are still there on the same column:
  {
    'luukvbaal/statuscol.nvim',
    opts = function()
      local builtin = require('statuscol.builtin')
      return {
        setopt = true,
        -- override the default list of segments with:
        -- number-less fold indicator, then signs, then line number & separator
        segments = {
          { text = { builtin.foldfunc }, click = 'v:lua.ScFa' },
          { text = { '%s' }, click = 'v:lua.ScSa' },
          {
            text = { builtin.lnumfunc, ' ' },
            condition = { true, builtin.not_empty },
            click = 'v:lua.ScLa',
          },
        },
      }
    end,
  }

Simple Solution
I fixed this issue by simply setting vim.o.foldcolumn = 'auto:9'. Just read the friendly manual :h foldcolumn


When producing man-pages, ensure NAME section is one line only

There are *roff parsers that are strict about the NAME section being
one line only.  The man(7) on Debian GNU/Linux suggests that this is
appropriate, so we compensate our multi-line NAME sections by fixing
the *roff output.
Noted by Eric S. Raymond
Related to #6264

This seems like a pod2man bug/misfeature, not ours.

Well, but isn't it worth doing it anyway in order to leave @eric-s-raymond's 2.6% grubby urchins corner?

https://www.in-ulm.de/~mascheck/bourne/v7/sh.1

Well, one might argue that it's a Pod::Man misfeature, but then one could also argue that it's up to .pod authors to get it right.  After all, man perlpodstyle does hint at this when explaining the NAME section.
Thing is, we insist on on making it multiline, some programs (not necessarily just doclifter) may parse it strictly.  I see this PR as smoothing it out to fit all tastes.
And look, I did what was needed.  Took me about 10 minutes.  Are we seriously gonna waste a multiple times that time arguing if this is our fault or someone else's?

Thank you :-)
Merged.
master / 1.1.1:
8d483b2de78619e8592f2558301f3295daf59690 When producing man-pages, ensure NAME section is one line only
1.1.0:
0bde96f13837825fa899573728899744a956beff When producing man-pages, ensure NAME section is one line only

Thanks.  I have made my namme section parser a bit more tolerant, but as levitte notes this cleanup was a good idea anyway.
Cleaning up the corpus has been difficult.  I've been working on it for 13 years and am only now approaching completion.  Every little bit helps.


Fixed #27783 -- Switched VariableDoesNotExist to repr() context

Ticket 27783.
Using __str__ and then repring the result looks strange and can lead
to recursive rendering for forms that render templates in as_table.
repr exists for this.

No tests were added as part of b5adaec4c23e3fa8ab52da1c10eb52f775d02209. Can you confirm the issue that needed the force_text() calls is obsolete?

Don't we have any CI builder to test on 1.11 with Python 2.7?

@timgraham The issue still occurs. Simplified:
class Foo(object):
    def __repr__(self):
        return '\xc3\xa9'

print u'%r' % (Foo(),)

https://code.djangoproject.com/ticket/18063 is wontfix, though.

Okay, for 1.x/Python 2 compatibility, this is additionally necessary:
 raise VariableDoesNotExist("Failed lookup for key "
                            "[%s] in %r",
-                           (bit, current)) # missing attribute
+                           (str(bit), current)) # missing attribute

Merged in 7c4289d0b974c9b33bdc569308d8c99d7cac45d4, thanks! I don't think the issue is critical to backport to 1.11 considering things have been this way since 1.0.

I don't think the issue is critical to backport to 1.11 considering things have been this way since 1.0.

2.0 is a long way out. I'd love to see this backported to (at least) 1.11 so users can pick up the fix in (at least) the near future. Any chance to reconsider?

Did something change recently that makes it suddenly more important? Additional time would need to be spent developing a Python 2 compatible version of the patch.

I agree with you that it's a long-standing bug; we disagree because I think that makes it a higher priority for a fix, not a lower priority.
In the Django bug tracker I posted at least one example of the "exception death spiral" that affects projects where they render templates with __str__(), DRF being one of them. This means if you have accidentally missed a variable in a context, the end result for the user is not an exception message, but a blank screen. This is really bad UX for both Django devs, and the actual end users. In other words, this is an opportunity to fix a really pernicious bug that affects upstream projects in ways that they don't fully understand when it happens.

If you want to backport the patch and send a pull request to the stable/1.11.x branch that would be fine.


Line terminations are selectable

This may be very upstream of tomboy-ng but when selecting the text at the end of a line the carriage return/line feed gets selected with it as you swipe the last word. If you select the last word on the line carefully, you can avoid selecting the line terminator and it is possible to select the line terminator just on its own and copy and paste it anywhere in the note.
It is a pretty unusual experience and does not happen in any other editor that I have used including this issues editor and unfortunately I use a note daily to organize the order of a list plus adding and deleting items. I keep getting messed up with that terminator.
Tried the Qt version (which I prefer) but the same issue is there also. Hope that it is something that you can do but not holding my breath. Thanks for the great work that you are doing on this app.
Cheers, Graeme

Graeme, thats an interesting question.  Yes, what you say is correct, there is some artifact of the newline there and you can (or not) select it. And, as you say, its upstream.
I guess I have got used to it and, to some extent, like it, I find its lack on every other editor I use noticeable. I have to agree, it should not really be there.  Will look into it but am not hopeful of a happy ending ....
Will get back to you.
Davo

Yes, as suspected, this is deep withing KMemo and unlikely to be improved upon given how it happens.
I am going to close this ticket but do please feel free to reopen or create a new one if you feel strongly about the problem.
Davo